Mid Server Issues

[Niks3562]

Hi,

When I am trying to restart the GCP mid server then it will throw 2 errors in ServiceNow.

1. MID Server failed to upgrade

2. Reinstall Service verification was failed during MID Server upgrade. It is possible that a required service re-installation was skipped. Make sure that the Service is installed with the same version as MID Server after upgrade.

Thanks in Advance

Nikita

[Niks3562]

Hi,

Thankyou for your response. 

Please let me know how I can upgrade the version of the service.

[Peter Bodelier]

Hi @Niks3562 

What @Sandeep132  is correct, but doesn't always work.

If that is the case, download the MID server installation from your upgraded instance, and follow this article, to replace the old Mid by the new one

How to manually Clone a MID Server so that you don't have to reconfigure all integrations features t...

Kind Regards,

Peter Bodelier

[Shamma Negi]

You can go to Mid Server and search in Related Link. It will give you an option to fix the issues or validate.

Try fixing it from there.

If it doesnt fix check the config.xml file check the value passed there.

[Hitoshi Ozawa]

Hi,

Old thread but got the same error and was able to resolve the issue without a reinstall.

Got the message "Reinstall Service verification was failed during MID Server upgrade. It is possible that a required service re-installation was skipped. Make sure that the Service is installed with the same version as MID Server after upgrade." this morning.

When I checked, there was an attempt to update MID Server and it failed after that. Tried to manually start the MID Server but after few seconds, it would stop again.

What I did was to look at the log file in agent/logs directory.  I found the following message in my log.

Persistence directory already locked by another process: /servicenow/<xxx>/agent/work/cache

This lead me to the following knowledge.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1122605

After I deleted the .lock file, everything went back to normal.

The lesson here is to always check the log file first to find the cause of the error instead of just relying on the message that appears.