We've updated the ServiceNow Community Code of Conduct, adding guidelines around AI usage, professionalism, and content violations. Read more

Issue with Mid Server

Admin7267
Kilo Sage

3 weeks ago

User mid_user associated with down MID Server: b067e5bddb6c37844de6187344961984. No login attempts within reporting period.

 

Need help to resolve this issue.

0 Helpfuls
  • 658 Views
3 REPLIES 3

shubhamseth
Mega Sage

3 weeks ago

@Admin7267 

 

first check whether MID server are currently down or UP. 

if it is already UP then - 

 

try resolving this error manually and restart the MID server - you should get this issue again then we are good 

 

if after restarting same issue coming up then check the agent and wrapper logs. 

if MID server is down - Kindly check the a agent and Wrapper log for error and further troubleshooting. 

 

✔️ If this solves your issue, please mark it as Correct.


✔️ If you found it helpful, please mark it as Helpful.


—
Shubham Jain


0 Helpfuls

Mohit 101
Tera Contributor

3 weeks ago

hi @Admin7267 ,

Follow these steps to resolve the issue,

  1. Verify User Account Status:
    • Navigate to System Security > Users and find mid_user.
    • Ensure the Locked out checkbox is not selected.
    • Confirm the user still has the mid_server role assigned.
  2. Restart the MID Server Service:
    • Windows: Open Services (services.msc), find the "ServiceNow MID Server" service, and click Restart.
    • Linux: Execute sudo systemctl restart servicenow-mid or use the stop.sh and start.sh scripts in the /agent folder.
  3. Check the Config File:
    • Open agent/config.xml on the host machine.
    • Verify the mid.instance.url is correct and matches your instance.
    • If the password was recently changed on the instance, update the mid.instance.password parameter in this file (it will re-encrypt after restar

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for.

Thank You.

0 Helpfuls