ConfigMgr Secondary Site Upgrade Error on CM Version 2111

Question

Hello,

I updated our MECM Primary site to version 2111 successfully, however the secondary site upgrade failed.

We are getting this error:

[Failed]:Current SUM configuration uses virtual locations for some of the active SUPs. Please remove any virtual locations from the existing SUM configuration.

With this error secondary site will not upgrade, there are no options to recover site.

Any ideas on how to solve this issue? Please help

Account used to do prereq check has SYSADMIN permission to CM database

Answer 1

Hi, @anaconda1442
Thank you for posting in Microsoft Q&A forum.

We may try to add the primary site server's computer account as Sysadmin and Securityadmin in secondary SQL.
And the same as of "NT AUTHORITY\SYSTEM" account.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

---

Answer 2

Hi AllenLiu-MSFT,

Good news is that Microsoft support finally was able to fix this problem. Long story short, Microsoft DBA observed severe damage on the secondary site database. After Microsoft support staff many failed attempts to recover site, several senior DBA's dived deep in recovery by detaching corrupted database, registry and etc. Re-attached repaired database to a state the primary site server can recover and then it finally worked. The recovery and rebuild process took several days. MS DBA determined probable cause was a link failure between the two sites, further Network logs on our end show Secondary site had a network outage prior to upgrade. So a network outage on our long distance secondary site can happen anytime which can cause this problem to occur again. Only pre-caution I can take is to make sure a complete backup of secondary site is done prior to a future upgrade. I'll provide feedback to MECM developers so they may have a solution that can prevent this from happening on a future upgrade. I'll now close this QnA marked as complete.

Answer 3

Good news is that Microsoft support finally was able to fix this problem. Long story short, Microsoft DBA observed severe damage on the secondary site database. After Microsoft support staff many failed attempts to recover site, several senior DBA's dived deep in recovery by detaching corrupted database, registry and etc. Re-attached repaired database to a state the primary site server can recover and then it finally worked. The recovery and rebuild process took several days. MS DBA determined probable cause was a link failure between the two sites, further Network logs on our end show Secondary site had a network outage prior to upgrade. So a network outage on our long distance secondary site can happen anytime which can cause this problem to occur again. Only pre-caution I can take is to make sure a complete backup of secondary site is done prior to a future upgrade. I'll provide feedback to MECM developers so they may have a solution that can prevent this from happening on a future upgrade.