MID Server Stopped and now Will not start
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2019 11:12 AM
Hello,
What would be the cause for a MID server to stop all of sudden and don't get beck online?
Already checked MID user account and password, everything correct.
Checking the host, the Windows Service will not come up.
The wrapper log says:
2019/09/04 11:50:59 | Update can not be used to change the wrapper.ntservice.account value. Please uninstall then reinstall the service.
2019/09/04 11:54:04 | The Discovery MID Server_ServerName service was launched, but failed to start.
If I open the installer.bat to try to perform a Test Connection it doesn't do anything, keeps frozen.
- Labels:
-
Orchestration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2019 01:06 PM
Hi Luiz, have you tried to start the service from services.msc? Should be called "ServiceNow MID Server_{name}"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2019 10:34 PM
On the mid server machine Go to services and identify your mid-service, if mid server stop or start service is stuck kill that then start the mid server.
For me the stop process was stuck and it was blocking start.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2019 10:37 PM
Hi Luiz,
You can try reinstalling it if this is part of an upgrade.
More information on the link below:
https://hi.service-now.com/kb_view.do?sysparm_article=KB0635789
Regards,
Raf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2019 12:05 PM
Thanks everyone that contributed.
We worked with HI support and even though was not part of upgrade or anything else, the solution was to reinstall the MID server in the host and create a new windows service.
Somehow there was a problem with the Java SDK and the Wrapper.
After reinstall, problem solved.