Midserver is down, service not starting- The service did not start due to a logon failure. (0x42d) - Support and Troubleshooting

Midserver is down, service not starting- The service did not start due to a logon failure. (0x42d) Issue Unable to start MID server service - The service did not start due to a logon failure. (0x42d)

STEPS TO REPRODUCE:

1) Open cmd.exe as an administrator

2) Browse to " \agent" folder and stop the service by running "stop.bat" file

3) Now, start the MID server service by running "start.bat" bat, below error's will be observed in command prompt window;

4) In the wrapper.log file (" \agent\log\wrapper.log"), below errors will be seen;

Cause MID server service running with a non-admin user account. Open the services.msc on MID server host machine, MID server service logon user is non-admin user of lacs permission to start the service. Resolution Either run the MID server service with 'Local System Account' or follow below documention prodedure There is a section "Run a Windows MID Server as a non-admin after manual installation" which explains how to run service with non admin account which you can follow if you do not want to run the MID server service with local system account. https://docs.servicenow.com/bundle/utah-servicenow-platform/page/product/mid-server/concept/mid-server-install-prereqs.html#title_non-admin-mid-install There is one separate KB as well which explain the same thing. https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1116916