Mid sever is not showing in the midserver > servers list post installation successful in the vm

[Venkata Sai Ama]

Our instance is currently in Utah , When we tried installing the mid server  in the VM, We gave servicenow midserver user credentials post connecting the test , we also selected midserver service account which is gmsa account. Post validation we installed and started the midserver , please find below screenshot for your reference.

Even after successful installation and validation of midserver from the VM , we are unable to see the midserver in the servers list in servicenow, we tried to run :

1. C:\SNOW MID\agent\bin and double click on InstallMID-NT batch file.
   2.  C:\SNOW MID\agent\bin and double click on StartMID-NT batch file.

but not worked, we still cant see the midserver in our list in servicenow , please help on this as we have an immediate requirement and halted here.

[Peter Bodelier]

Hi @Venkata Sai Ama

I'd first start by checking the firewall configuration, to verify the server is able to contactyour ServiceNow instance.

If that all checks out, check you agent0.log file for any errors.

[Harish Bainsla]

there are a few troubleshooting steps you can follow to resolve this issue:

1. Check MID Server Logs:

   • Look for MID Server logs, usually located in the "logs" directory of your MID Server installation folder. Check for any error messages or issues in these logs. This can provide valuable information about what might be going wrong.

2. Validate ServiceNow Configuration:

   • Ensure that the ServiceNow instance is configured correctly to communicate with the MID Server. In your ServiceNow instance, navigate to "MID Servers" and verify that the MID Server is registered and active.
   • Confirm that the MID Server is associated with the correct ServiceNow instance.

3. Network and Firewall Settings:

   • Verify that the network and firewall settings allow communication between the MID Server and your ServiceNow instance. Ensure that the necessary ports (usually 443) are open and that there are no restrictions that might be blocking communication.

4. ServiceNow User and Roles:

   • Check the user and roles assigned to the MID Server in your ServiceNow instance. The user account used for the MID Server must have the necessary roles and permissions to interact with the instance.

5. ServiceNow Version Compatibility:

   • Ensure that the MID Server version is compatible with the version of your ServiceNow instance. Sometimes, using an older or newer MID Server with an instance can cause issues.

6. ServiceNow Credentials:

   • Confirm that the credentials provided to the MID Server during installation are accurate and have the necessary permissions in your ServiceNow instance.

7. Restart the MID Server Service:

   • Sometimes, simply restarting the MID Server service can resolve connectivity issues. You can do this by stopping and then starting the MID Server service from the Windows Services application.

8. Check for Pending Activations:

   • If you see the MID Server in your instance but it's not active, you may need to activate it. This can be done from the "MID Servers" list in your instance.

9. Check the Configuration Files:

   • Review the MID Server configuration files for any errors or misconfigurations. This includes the MID Server properties file.

10. ServiceNow Support:

    • If the issue persists and you've exhausted troubleshooting options, consider reaching out to ServiceNow Support. They can provide assistance and guidance specific to your environment.