- My View
While restarting the Mid server , I am receiving below error message,
"error 1069 the service did not start due to a logon failure"
I have checked the ServiceNow mid server User credentials and the Service account logon credentials. Both are active and have appropriate rights.
Then I have tried to open the installer file to perform the test connection from the Installer UI. While trying to open the Installer UI, I have received the below error message,
"error of type java.lang.illegalStateException occured Error starting the installer"
Kindly share your knowledge, if anyone came across this issue.
Thanks in Advance!
Please reinstall mid your and then start you mid server.
Please mark answer as Correct, helpful as appropriate.
Indeed, as Sachin suggested, try reinstalling your MID Server.
I'll also suggest your open the properties of your MID Server Windows Service and make sure that the service is using the right windows account. I'm almost sure that is the problem you're having.
Keep in mind that your windows account needs to be a network account with local administrative rights.
I hope this helps!
The following thread makes reference to the same error but for a different system:
Just a confirmation you just need to include the right windows account for that service... and don't forget to restart the service once you have done the change
Thank you for your response Berny!
The windows account you are pointing out is the mid server Logon credentials right? If yes, I have checked with the AD team for that account admin right and they confirmed, account is properly setup.
kindly share the troubleshooting steps which needs to be verified from my end to confirm, windows account are properly configured.
The account that is used for the MID Server service (found under Windows Services) is the one that is going to be used as the network user with local administrative rights to perform the discovery process on the windows machines. This is the account that ServiceNow will use to attempt all the probes/patterns when the windows credential under the servicenow credential module does not exist or work against the targeted hosts.
Since that account will be the one through the one the MID Server will run, it need to be at minimum an network user with administrative local access at the MID Server
Thank you Breny!
Issue got resolved !!
We recently implemented CMDB and Discovery into ServiceNow. The midservers are used by discovery and other integration processes. Our The server teams will support the actual servers, but there are software components, such as Java. does ServiceNow upgrade Java or the mid server software.......is there anything me as a SN adin or my company needs to do
I'm not the final authority on this, but I believe the midserver updates the java. Here's the 2 main clues why I think this.
1. We've been running Discovey on Windows midservers for several years and have NEVER had to upgrade JAVA.
2. In the midserver's agent folder, there is a folder named jre. It appears that the JAVA runtime engine resides in that folder. And anything under the agent folder is maintained by the midserver.
All that said, I am perfectly willing to hear from others who are more knowledgeable than me on the subject. I'm always happy to be proven wrong, so that I may adjust my thinking to be closer to the truth.