Upgrade MID server after upgrade to Geneva

[Kim Kronborg]

Is it necessary to manually upgrade the MID server after the servicenow instance is upgraded from fuji to geneva ?

After upgrade to geneva I experience problems with MID server saying the following :

"Unable to install the ServiceNow MID Server service - The specified service already exists. (0x431)

Update can not be used to change the wrapper.ntservice.account value.   Please uninstall then reinstall the service."

Does anybody have experience with this message ?

Thanks,

Kim

[vinothkumar]

We are also in a plan to upgrade our instance to Geneva, Share me the solution with me as well, if you got answer for this.

[Kim Kronborg · Accepted solution]

Uninstalled the service and reinstalled it again manually - now it works

[matthuy]

Here's our experience when upgrading from Fuji to Helsinki:

1. SN Instance is scheduled to be upgraded

2. MidServers try to contact SN Instance to see if it needs to be upgraded (it needs the version information), but SN Instance is unavailable (503).

3. After 2 tries, the MidServer service stops itself

4. Mean while the SN Instance is done with the upgrade and is back online.   MidServer service is still stopped and will not auto upgrade itself

5. Manually start the MidServer service, it detects a version change and auto upgrade proceeds.

HTH

[Sudhakara Redd2]

In my Case, I have upgrade my instance to Helsinki. MID Server was down. I did update credentials in config.xml, MID Server was up but it was not pulling any data. I was getting same error which mentioned above. Later I changed Service name and display name in Wrapper and Wrapper-Override files and I started my MID Server by using start batch. New service has created, MID server up and running and connection got established.

If everything went well, Under MID Servers, you can see Version details will update to latest version of your instance.