Let’s find the solution for the ConfigMgr Secondary Server Upgrade Issue in the production environment. You need SQL permissions to try this solution. We always recommend testing this solution in an isolated environment first.
Once the parent primary server is upgraded to the latest version of ConfigMgr, you can start installing the secondary server. Let’s start the SCCM Secondary Site Server Upgrade.
Read More – How to Install Secondary Server & How to FIX SCCM secondary server installation failure.
| Index |
|---|
| Error |
| Troubleshoot-Secondary-Server-Upgrade-Issue-using-hman.log |
| SQL Query Checks to Confirm |
| Solution |
| Confirmation of Issue is Fixed ConfigmgrSetup.log |
| Resources |
Error – ConfigMgr Secondary Server Upgrade Issue
The Secondary server upgrade was not proceeding further due to the site GUID information missing from the SC_SiteDefinition_Property table in the Primary server database.
CSiteControlSetup::ReadSiteGuidFromSCF: Site definition property for site GUID
This could have happened since I have run the ‘Retry secondary site’ option.
- I found there was no update on the Configmgrsetup.log on the secondary.
- Looked at the Primary hman.log and found the below entry.
Troubleshoot Secondary Server Upgrade Issue using hman.log
We checked the HMAN.log to understand the problem with the Configuration Manager (a.k.a SCCM) secondary server upgrade issue. We found the following issues with secondary server upgrades.
Start upgrading secondary site DK2 – SMS_HIERARCHY_MANAGER –
CSiteControlSetup::ReadSiteGuidFromSCF: Site definition property for site GUID not found.
CHierarchyManager::InitSiteControl : Failed to initialize installmap content for Secondary site [DK2].
Cannot upgrade site control file for this secondary site. Will not upgrade this secondary site.
INFO: .SLG file not found – SMS_HIERARCHY_MANAGER 9/10/2016 2:43:06 PM 11360(0x3048)
SQL Query Checks to Confirm – ConfigMgr Secondary Server Upgrade Issue
We also checked the SQL DB to understand whether the secondary server site GUID is present in the database or not. However, there was no entry of SiteGuid in the database. You can copy the SQL query from the GitHub repository.
There was no result.
select ID from ServerData where sitecode = 'DK2' ID= 292145Solution – ConfigMgr Secondary Server Upgrade Issue
Take a backup of the Primary database.
- Run the below query and update the SC_SiteDefinition_Property table with the secondary details.
INSERT INTO SC_SiteDefinition_Property VALUES(292145 , ‘SiteGUID’, ”, ”, 0)
Also, I updated the Build number and the version in the site table for the DK2 site with the SCCM 2012 R2 version, as it was showing the R2 SP1 version due to the previous attempt failing.
- update sites set BuildNumber=’7958′ where sitecode=’DK2′
- update sites set version=’5.00.7958.1000′ where sitecode=’DK2′
- Also, I updated the status to 7 to bring it to the Upgrade failed status.
update sites set status=7 where sitecode=’DK2′
- Reinitiated the upgrade process again and monitored the log flow
From the Hman.log we found the upgrade notification has been sent to the Secondary.
Hman.log
Check HMAN.log to understand the process of ConfigMgr Secondary Server Upgrade Issue
HierarchyManager::ProcessSiteModeSettings: secondary site DK2 has the same site mode settings as the current site SMS_HIERARCHY_MANAGER
Created site control notification for site DK2 SMS_HIERARCHY_MANAGER
INFO: DEEPAK.MECM.DK.com is a valid FQDN. SMS_HIERARCHY_MANAGER
Confirmation of Issue is Fixed ConfigmgrSetup.log – ConfigMgr Secondary Server Upgrade Issue
I looked at the ConfigmgrSetup.log from the Secondary and found that the logs are getting updated, and the upgrade was completed successfully. Please try to fix the ConfigMgr Secondary Server Upgrade Issue.
ConfigmgrSetup.log -ConfigMgr Secondary Server Upgrade Issue
INFO: Configuration Manager Setup full version is 5.00.8239.1000 Configuration Manager Setup 9/10/2016 3:46:53 PM 0792 (0x2A28) INFO: Deleting Inbox Rules registry key. Configuration Manager Setup 9/10/2016 3:46:53 PM 10792 (0x2A28) INFO: Creating Inbox Source registry key …Configuration Manager Setup 9/10/2016 3:46:53 PM 10792 (0x2A28)
INFO: Verifying inbox folder permissions: Configuration Manager Setup 9/10/2016 3:46:53 PM 10792 (0x2A28) INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure Configuration Manager Setup 9/10/2016 3:46:54 PM 10792 (0x2A28) INFO: send message 0x00050051 to parent Configuration Manager Setup 9/10/2016 3:46:54 PM 10792 (0x2A28)
INFO: Automatic Updates detection task was called – IAutomaticUpdates->DetectNow returned 8024a000 Configuration Manager Setup 9/10/2016 3:46:54 PM 10792 (0x2A28) INFO: Configuration Manager Setup – secondary site upgrade completed. Configuration Manager Setup 9/10/2016 3:46:54 PM 10792 (0x2A28) INFO: send message 0x00050002 to parent Configuration Manager Setup 9/10/2016 3:46:54 PM 10792 (0x2A28)
Disclaimer—We are not responsible if you encounter any issues after following these SQL Queries. MS doesn’t support SQL DB Modification. Execute at your own risk.
Resources -ConfigMgr Secondary Server Upgrade Issue
- SCCM Secondary Site Upgrade Issue FIX by Kannan – https://www.anoopcnair.com/sccm-secondary-site-upgrade-issue/
- To find the site value indicating a request for secondary site status – https://docs.microsoft.com/en-us/sccm/develop/reference/core/servers/configure/sms_site-server-wmi-class
We are on WhatsApp. To get the latest step-by-step guides and news updates, Join our Channel. Click here –HTMD WhatsApp.
Author
Deepak Rai is a Technical Lead with over 14 years of experience in IT. He specializes in SCCM, Intune, and Azure. Throughout his career, he has worked on various platforms such as Active Directory, Exchange, Veritas NETBACKUP, Symantec Backup Exec, NDMP devices like Netapp, EMC Data Domain, Quantum using Backup Exec 2010 and 2012, and HP StorageWorks 4048 MSL G3. He also has experience in data deduplication-related troubleshooting. Ultimately, he returned to his roots as an IT Engineer focusing on SCCM technology.
THANK YOU!! I had one secondary that refused to update after updating the primary. I followed your instructions and was able to successfully update the affected secondary server.