Mid server error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2024 10:20 AM
Evening guys
We have a mid server that has been running fine, we are now pointing it at our test instance and have encountered an error on the server side, screenshot below. We did not change any of the config on the file other than the url and the user account the mid server is using exists in temp. Any thoughts?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2024 04:44 PM - edited 05-02-2024 04:45 PM
The error message you're seeing, "Windows could not start the ServiceNow MID Server service on Local Computer. Error 1069: The service did not start due to a logon failure," typically indicates a problem with the credentials used by the MID Server service to log on to your Windows system.
Here are steps you can follow to resolve this issue:
1. Check Service Account Credentials
- Open the Services application on your Windows server (you can type services.msc in the Run dialog).
- Find the ServiceNow MID Server service in the list.
- Right-click on the service and select Properties.
- Go to the Log On tab.
- Check the credentials and save it.
2. Restart the Service - Try to restart it couple of time
3. Check User Permissions by validating in Local Policies ->User Rights Assignment -> Log on as a service
4. Check Account Lockout or Disablement
5. Check firewall and network policies as well.
If my response has resolved your query, please consider giving it a thumbs up and marking it as the correct answer!
Thanks & Regards,
Sanjay Kumar