MID Server fails to start - WrapperManager Error: Failed to connect to the Wrapper at port 32,000Issue MID Server is not starting, and the following error can be seen in the agent\logs\wrapper.log 2021/12/03 07:18:02 | WrapperManager Error: Exiting JVM...2021/12/03 07:18:03 | JVM exited while loading the application.2021/12/03 07:18:09 | Launching a JVM...2021/12/03 07:18:09 | WrapperManager: Initializing...2021/12/03 07:18:10 | Logger for 'glide' has not been configured by the container, configuring now:2021/12/03 07:18:10 | Configuring log handler: java.util.logging.FileHandler2021/12/03 07:18:10 | Setting useParentHandlers=false for Logger 'glide'2021/12/03 07:18:10 | Overriding formatter to: com.glide.util.DefaultLogFormatter (for handler: java.util.logging.FileHandler)2021/12/03 07:18:31 | WrapperManager Error: Failed to connect to the Wrapper at port 32,000. Cause: java.net.ConnectException: Connection timed out: connect2021/12/03 07:18:31 | WrapperManager Error: Exiting JVM...2021/12/03 07:18:31 | JVM exited while loading the application.2021/12/03 07:18:31 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.2021/12/03 07:18:31 | There may be a configuration problem: please check the logs.2021/12/03 07:18:32 | <-- Wrapper StoppedResolutionThis error tells that the JVM is not able to connect to the Java Service Wrapper. This is probably caused by port conflicts (in the above case, port 32000) if this port is used by other applications, or not open the firewall side, or is blocked by a software firewall on the server. Port in Use If port 32000 is already in use by another process, Tanuki Wrapper should just Warn and find a port that is not in use, as documented here:https://wrapper.tanukisoftware.com/doc/english/prop-port.html To check, from a Command Prompt, running as Administrator, you can work out what other process might be using the same port. e.g. netstat -ano -p tcp | find "32000" tasklist | find "6040" where 32000 is the port shown in the error, and 6040 is a process ID shown by netstat Firewall Windows Servers are likely to be running Windows Defender Firewall. Add a new rule for IncomingTCPport 32000