Mid server Down - Error "Timed out waiting for wrapperServiceMain" seen in wrapper logIssue MID Server is in Down state, and the error "Timed out waiting for wrapperServiceMain" seen in the wrapper.log file. A host machine restart doesn't help. Attempting to restart the Windows service results in Microsoft error - 1053 Windows could not start the service.Error 1053: the service did not respond to the start or control request in a timely fashion. CauseThis can be found in the wrapper log: Child process: Java version: timed out2021/02/04 18:44:18 | Failed to resolve the version of Java.2021/02/04 18:44:18 | <-- Wrapper Stopped2021/02/04 18:44:28 | Timed out waiting for wrapperServiceMain2021/02/04 18:49:05 | --> Wrapper Started as Service2021/02/04 18:49:05 | Java Service Wrapper Standard Edition 64-bit 3.5.402021/02/04 18:49:05 | Copyright (C) 1999-2019 Tanuki Software, Ltd. All Rights Reserved.2021/02/04 18:49:05 | http://wrapper.tanukisoftware.com2021/02/04 18:49:05 | Licensed to ServiceNow, Inc. for MID The log "Failed to resolve the version of Java." is simply from attempting to run "java -version" to get the java version. That should take a split second. You can confirm how long it takes to run that from the command line. Alternatively the wrapper log may look more like: 2019/04/20 04:42:49 | Startup failed: Timed out waiting for a signal from the JVM. 2019/04/20 04:42:50 | JVM did not exit on request, termination requested. 2019/04/20 04:42:52 | JVM exited after being requested to terminate. 2019/04/20 04:42:52 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. The potential root cause of this issue could be: The WrapperManager not getting launched, because of the JVM launch getting timed out. The host VM or Windows isn't giving the wrapper/java process enough CPU timeAntivirus taking too long to check the file/process as it launchesStartup method taking time to complete/execute.ResolutionThe correct solution is to resolve the performance issue of the host. This can be worked-around in some cases by adding the following java properties to the wrapper-override.conf file located in the <install folder>\agent\conf\ folder. wrapper.startup.timeout=300wrapper.jvm_exit.timeout=300 Another property wrapper.ping.timeout=300 already exists in wrapper.conf file and the default value is 300 seconds. The above property defines the number of seconds to allow between the time that the Wrapper launches the JVM process and the time that the JVM side of the Wrapper responds that the application has started. Adding this property to wrapper-override.conf, but with value "0" (zero) means never time out.Related LinksIt is the job of the 3d party software Tanuki Service Wrapper to launch the Java JVM process, and so the problems the MID Server application can have are common to many other Java applications, so other causes and solutions may be founds searching the web. Tanuki docs: https://wrapper.tanukisoftware.com/doc/english/introduction.html All parameters mentioned above are listed here: https://wrapper.tanukisoftware.com/doc/english/props-advanced.html including wrapper.startup.timeout Also read "My application does not start. What can I do to narrow down the problem?" from https://wrapper.tanukisoftware.com/doc/english/troubleshooting.html