MID server issue after clone due to version differences
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2023 10:39 AM
Hello All,
We upgraded our non prod instance to Utah 7 for testing purpose and our prod is on Utah 6 .
When we cloned, the mid on non-prod instance was down due to the version conflict.
Please guide me on what are the 4 files (config.xml...) that need to be copied from backup to agent directory to resolve this.
Also looking for guidance on diff troubleshooting steps/methods on midserver issues when its down.
TIA
- Labels:
-
Architect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2023 08:40 AM
Hi,
upgrade your MID if that didn't happen automatically.
Refer to:
https://docs.servicenow.com/en-US/bundle/vancouver-servicenow-platform/page/product/mid-server/conce...
and
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0812239
Hope it's going to help you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2023 04:08 AM
When dealing with version conflicts during an upgrade, you'll want to copy these four files from your backup to the agent directory: config.xml, wrapper.conf, logging.properties, and mid.conf. After that, make sure to restart your mid server.
