SOLVED Secondary Sites failed to upgrade while upgrading SCCM to 1702

[Navneet Singh]

We are upgrading our Sccm infra from CB 1610 to 1702. Primary Site got upgraded successfully.

But we are facing issue while upgrading our secondary sites. Some secondary sites got upgraded successfully but some are failing to upgrade. Following are the errors which we are getting:

1. The collation of the site database does not match the collation of the parent site's database. All sites in a hierarchy must use the same database collation.
2. Current SUM configuration uses virtual locations for some of the active SUPs. Please remove any virtual locations from the existing SUM configuration.
3. Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup cannot continue

And it is not our first upgrade. We upgraded from 1511 --> 1602 --> 1606 --> 1610 smoothly.

Dont know why this time while upgrading from 1610 --> 1702, we are getting above errors.

Collation has been verified it is same at both ends(primary site and secondary site, don't why error comes up that there is a mismatch in Collation)

 

[Prajwal Desai]

For point 1, check and let me know if this helps - https://prajwaldesai.com/community/threads/sccm-2016-unable-to-deploy-secondary-site.922/

 

[Prajwal Desai]

"Some secondary sites got upgraded successfully but some are failing to upgrade." - This looks strange to me

 

[Prajwal Desai]

Point 3 - This is something you need to check. The error description is very clear. Open SQL Server Management Studio and connect to your database server and instance. Expand Security > Logins. Right-click on “NT AUTHORITY\SYSTEM” and select Properties. On the “Server Roles” node, check the box for sysadmin.

 

[Navneet Singh]

For first comment: already checked that article but it didn't help us.

Second, yes it is strange to me as well, we have 8 secondary's out of which 2 got upgraded successfully.

NT AUTHORITY\SYSTEM -- has sysadmin rights, already verified.

Further, we are doing SCCM upgrade 4th time,don't know why this time we are encountering this error. Need to confirm if it can it be a MS bug ?

 

[Navneet Singh]

Hi Prajwal

We have managed to solve this issue of ours:

We gave Sysadmin and Security admin rights to Primary site server computer account(same as of “NT AUTHORITY\SYSTEM” account) in secondary SQL.

This is not the prereq, we raised case with MS and as per the troubleshooting we managed to upgrade the secondary sites by giving the above mentioned permissions. We don't know the root cause of the issue, but this thing helped us.

Navneet Singh

 

[Prajwal Desai]

That's cool @Navneet Singh