MID Server - Fresh Setup, but not appearing in MID Servers list to Validate

Andrew S1 · ‎08-05-2018

Hi folks,

First go at getting a MID Server up and running, and really close !

Environment is as follows:

SNOW Instance: Personal Dev, Jakarta

MID Server: VirtualBox: Windows 2016 Server. Host OS: Windows 10.

I followed the ITOM Guided Setup to setup the MID Server and all went well until I got to the "Validate" Step - at this point the MID Server didn't appear in the list of MID Servers.

Checked the following on the MID Server (Virtual Box) Host:

- agent log showed no errors, reported that the service had started.

- Windows Services showed the new Service up and running as LocalSystem.

The VM Windows Server box has connectivity through my home LAN to the internet and can access the SNOW instance with no problems.

I turned Windows Firewall off on the Server machine as well, just as part of troubleshooting.

But all to no avail - going into the MID Servers app in SNOW shows no entries, despite all the stuff I've checked apparently showing that all is well.

The new user account I created has the right roles and the agent log even verifies this.

I'm sure I'm missing something really dumb and would be grateful for any pointers !

Rajesh Kannan · ‎08-06-2018

Hi Andrew,

I faced the same issue in Jakarta version.

As a workaround,

1) Uninstall the MID Server using the script available in agent/bin folder.

2) After uninstallation completed, Download the fresh MID server installation files and extract it.

3) you need to manually edit the config.xml and update the parameters ServiceNow instance URL, MID User Name/password created in the instance and MID Server Name.

4) update the parameter "wrapper.name" and "wrapper.displayname" in wrapper-override.conf file available under folder agent/conf.

5) Execute the "start.bat" available agent folder after updating the above information in config.xml and wrapper conf. Now it will create a MID Server record in ServiceNow instance.

Regards,

Rajesh.

View solution in original post

Sandeep Rajput · ‎05-26-2020

I have faced the same issue with Orlando release, where I tried everything but still the mid server didn't show up on my instance. Removed the entire MID server Orlando installation package from the windows server and installed the MID server application compatible with the NewYork release (mid.newyork-06-26-2019__patch4-hotfix1-12-16-20...). Followed the same installation procedure and this time it showed up in the list of my MIDServer.