Unsolved
1 Rookie
•
6 Posts
0
159
WMS 4.3 Tomcat error
Hello all and thanks for any help! I'm trying to standup a new WMS 4.3 Standard instance on Windows Server 2022 Standard (dedicated server, fresh build). I can get the WMS Setup, but after installing Microsoft Configuration Manager client, I start seeing the below error in Tomcat logs and cannot access the management site. I tried to uninstall MCM client and still get the error, I try to re-install WMS and it works for a bit and then the error comes back.
Error: SEVERE [main] com.dell.custom.customHttp11NioProtocol.AESCBCEncryptionUtil.decryptWithAESCBC Error in decrypting the key : Given final block not properly padded. Such issues can arise if a bad key is used during decryption.
INFO [main] com.dell.custom.customHttp11NioProtocol.CustomHttp11NioProtocolWrapper.addSslHostConfig Error : Tried to decrypt the keystore password. Setting the password without decrypting
Thank you,
Jason
DELL-Scott H
3 Apprentice
3 Apprentice
•
745 Posts
0
April 22nd, 2024 13:33
You have a port conflict with the SCCM client and tomcat. I have seen this before.
This is a bit old, but you should be able to use it to get you headed down the proper path.
java.net.BindException: Address already in use: JVM_Bind
JBVCU
1 Rookie
1 Rookie
•
6 Posts
0
April 23rd, 2024 21:34
O.K., fresh install of 4.3, I stopped the SCCM client for the install. The install completed, I got to the Inital setup page. I change the server.xml to 8010 and restarted the server. I'm still getting the same error message in the Tomcat log and the page is not coming up.
<Server port="8010" shutdown="SHUTDOWN">