Start a Conversation

Unsolved

J

1 Rookie

 • 

6 Posts

159

April 17th, 2024 14:15

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

3 Apprentice

 • 

745 Posts

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.

  • Request WMS service logs for review
    • Tomcat related log files:
      • C:\Program Files\DELL\WMS\Tomcat-8\logs
    • Stratus website log file:
      • C:\Program Files\DELL\WMS\Tomcat-8\stratus.log
    • Noted date gaps in logs
      • This gives us the likely window for how long it’s been an issue
    • Check Logs for error binding to port 8005
      • SEVERE [main] org.apache.catalina.core.StandardServer.await StandardServer.await: create[localhost:8005]:

java.net.BindException: Address already in use: JVM_Bind

  • Start > run > cmd > Netstat -ano
    • Provides list of ports in use on the server
    • Confirm whether port 8005 (default tomcat port) is already in use
      • Windows Express Updating Service for security updates may conflict
        • Would appear as system service with low PID such as PID =’4’
      • Check PID against Taskmgr if unsure of Process name
    • Resolve Port Conflict by updating Tomcat config to use different port:
      • Tomcat Port defined in:
        • C:\Program Files\DELL\WMS\Tomcat-8\conf\server.xml
      • Confirm availability of open ports with netstat -ano
        • Recommend port 8010 to give space for other services and skip over other tomcat port requirements
      • Restart service (or entire server)
      • Confirm functionality restored

1 Rookie

 • 

6 Posts

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">

No Events found!

Top