MID server (down) issue after clone due to version differences

CV1
Tera Contributor

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

1 REPLY 1

Danish Bhairag2
Tera Sage
Tera Sage

Hi @CV1 ,

 

Can u check these below article from servicenow

 

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

 

Please read the paragraph attached in the screenshot

 

Thanks,

Danish