The Zurich release has arrived! Interested in new features and functionalities? Click here for more

MID Server does not create automatically MID Server Record after installation.

AB6
Tera Contributor

‎03-03-2025 10:06 AM

Hi Experts.
I installed a MID Server on a Windows Server and when I complete all the wizard steps, I verified that the MID Server service is running, but when I navigate into the servicenow instance, the MID Server record is not created automatically.

What could be the reason that the MID Server record is not created automatically in the servicenow instance?
could you provide some advise to troubleshooting this specific error?
What do I need to make sure that I configure correctly? for example, I reviewed the config file and I can se that everything looks good.

I hope that you can help me to resolve this issue.
Regards.

Labels:
0 Helpfuls
  • 527 Views
1 REPLY 1

Selva Arun
Mega Sage
Mega Sage

‎03-03-2025 10:40 AM

Hi there,

 

It sounds like your MID Server record is not being created automatically in your ServiceNow instance after installation. This can happen for a few reasons, but here are some steps you can follow to troubleshoot and resolve the issue:

 

  1. Check the MID Server configuration file.
    Open the config.xml file in the MID Server installation directory and make sure the following are correct:

    • The mid.instance.url is pointing to the correct ServiceNow instance URL (for example, https://yourinstance.service-now.com).
    • The mid.username and mid.password are correct and belong to a ServiceNow user account that has the "mid_server" role.

  2. Verify network connectivity.
    Make sure the MID Server can connect to your ServiceNow instance. You can test this by opening a browser on the MID Server host and navigating to your ServiceNow instance URL.
    If your network uses a proxy, ensure the proxy settings are properly configured in the config.xml file.

  3. Review the MID Server logs.
    Check the logs in the agent/logs directory of the MID Server installation folder. Look for any errors or warnings, such as connectivity issues or authentication problems. These logs can give you clues about why the MID Server record isn’t being created.

  4. Check the MID Server service.
    Make sure the MID Server service is running on the Windows Server. Even if it appears to be running, try restarting it to see if that resolves the issue.

  5. Verify the ServiceNow instance.
    In your ServiceNow instance, go to "MID Server > Servers" and check if there are any partially created records or errors then restart the MID Server service on the Windows Server.

  6. Confirm user permissions.
    The ServiceNow user account used in the config.xml file must have the "mid_server" role. Without this role, the MID Server won’t be able to register itself in the instance.

  7. Check version compatibility.
    Make sure the MID Server version you installed is compatible with your ServiceNow instance version. If there’s a mismatch, the MID Server might fail to register.

  8. Re-run the configuration wizard.
    If everything seems fine but the issue persists, try re-running the MID Server configuration wizard. Sometimes, a small misstep during the initial setup can cause issues.

If none of these steps resolve the issue, you can refer to the following resources for more detailed guidance:

If you’ve gone through all these steps and the problem still isn’t resolved, I’d recommend reaching out to ServiceNow support. Be sure to include the logs from the MID Server, as they can provide more specific guidance based on the errors.

I hope this helps!

 

If you believe the solution provided has adequately addressed your query, could you please **mark it as 'Helpful'** and **'Accept it as a Solution'**? This will help other community members who might have the same question find the answer more easily.

 

Thank you for your consideration.

 Selva Arun

0 Helpfuls