Issue:
During an upgrade of MECM from version 2303 to 2403, the process encounters a recurring issue. The upgrade progresses through the 'Upgrading the ConfigMgr database' step, moves briefly to 'Install Files,' and then loops back to 'Upgrading the ConfigMgr database,' repeating this cycle indefinitely. This behavior persists regardless of the upgrade approach, whether applying the 2303 hotfix first or upgrading directly to version 2309 or 2403.
Observed Steps in CMUpdate.log
INFO: successfully reset inbox permission Message Processing Engine CONFIGURATION_MANAGER_UPDATE 12/5/2024 7:35:52 AM 11732 (0x2DD4)
Successfully reported ConfigMgr update status (SiteCode=MGM, SubStageID=0xd0012, IsComplete=1, Progress=1, Applicable=1) CONFIGURATION_MANAGER_UPDATE 12/5/2024 7:35:52 AM 11732 (0x2DD4)
INFO: Copying 1898 files CONFIGURATION_MANAGER_UPDATE 12/5/2024 7:35:52 AM 11732 (0x2DD4)
INFO: F:\Program Files\Microsoft Configuration Manager permission set successfully.
CONFIGURATION_MANAGER_UPDATE 12/5/2024 7:35:52 AM 11732 (0x2DD4)
INFO: Successfully created local user group SMS Admins on the local machine with NT AUTHORITY\SYSTEM as the member. CONFIGURATION_MANAGER_UPDATE 12/5/2024 7:35:52 AM 11732 (0x2DD4)
------------------------------------------------------------------------------------------------------------------------------------------------
Then, it restarts as shown here:
*************************************************************************************************************************** CONFIGURATION_MANAGER_UPDATE 12/5/2024 7:40:58 AM 1624 (0x0658)
CONFIGURATION_MANAGER_UPDATE service is starting... CONFIGURATION_MANAGER_UPDATE 12/5/2024 7:40:58 AM 1624 (0x0658)
Microsoft Microsoft Configuration Manager v5.00 (Build 9128) CONFIGURATION_MANAGER_UPDATE 12/5/2024 7:40:58 AM 1624 (0x0658)
Process ID: 12056 CONFIGURATION_MANAGER_UPDATE 12/5/2024 7:40:58 AM 1624 (0x0658)
Worker thread ID: 1624 CONFIGURATION_MANAGER_UPDATE 12/5/2024 7:40:58 AM 1624 (0x0658)
Inbox source is local on SCCM.DOMAIN.COM CONFIGURATION_MANAGER_UPDATE 12/5/2024 7:40:58 AM 1624 (0x0658)
Set inbox to F:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box CONFIGURATION_MANAGER_UPDATE 12/5/2024 7:40:58 AM 1624 (0x0658)
The logs may initially show activity suggesting issues with dropping and adding an SQL constraint during the upgrade. However, avoid being misled by potential false positives in the log files. Instead, start by verifying the registry settings as outlined below.
Root Cause
This is a known bug in Microsoft's backlog and is anticipated to be resolved in a future update. The issue stems from incorrectly named registry values:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole
- MachineAccessRestriction
- MachineLaunchRestriction
The registry keys were unexpectedly renamed with an ...old suffix, which disrupted the upgrade process. These keys are binary values and should not be recreated manually. Our engineers can assist in properly resolving this error to ensure a smooth upgrade process.
For more information or assistance, please contact our team of experts at service@helient.com.
1 minute read
