@Carol2 see my comment below but first check the agent0.log.0 and wrapper.logn file on the host machine for those mid servers that failed to upgrade.
1. when upgrading to patch 7a some servers upgraded, and some did not upgrade - For those that failed, did you check if the mid server host has access to install.service-now.com and default port 443 is open?
2. It is not recommended to have multiple MID Servers logged in with the same MID Server username. would changing the username and password assist and where do i change the login details? - Having same user name / password on different mid server doesnt not impact a succcesful upgrade. this is just a security recommendation from ServiceNow. You can always change the user name /password from the config file in the agent folder on the host machine.
3. Could not decrypt file discovery whitelist after sync - how to resolve this issue . Ensure the mid server is validated. Reference KA - KB0727848
4. Aborting MID Server upgrade due to pre-upgrade check failure - how to resolve this issue .- check the agent0.log.0 file to see what pre-ugrade check is failing
N/B: Please mark as helpful
