SCCM fails to upgrade

Carl94580345 41 Reputation points
2026-07-31T21:45:05.7566667+00:00

SCCM fails to upgrade due to no communication with scom. SCOM is not there, it only thinks it is.

ERROR: Failed to find folder that stores msi file SQLSysClrTypes.msi CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:38 PM 13232 (0x33B0)

Failed to find SQLSysClrTypes.msi CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:39 PM 13232 (0x33B0)

Failed to install SQLSysClrTypes.msi CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:39 PM 13232 (0x33B0)

Failed to install SQL redist CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:39 PM 13232 (0x33B0)

STATMSG: ID=11001 SEV=E LEV=M SOURCE="SMS Server" COMP="CONFIGURATION_MANAGER_UPDATE" SYS=RK05-MGT-VP001.ad.northcentral.edu SITE=OIT PID=6720 TID=13232 GMTDATE=Fri Jul 31 21:33:39.052 2026 ISTR0="725866CC-E043-4563-B071-A7E66B523F1C" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X0 CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:40 PM 13232 (0x33B0)

There is no objects to restore. CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:40 PM 13232 (0x33B0)

INFO: Installing Site Component Manager ... CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:40 PM 13232 (0x33B0)

INFO: File \\?\E:\Microsoft Configuration Manager\inboxes\sitecomp.box\shutdown.trn does not exist. No zapping needed. CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:40 PM 13232 (0x33B0)

Drop site role reset trnfile: E:\Microsoft Configuration Manager\inboxes\sitecomp.box\resetall.trn CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:40 PM 13232 (0x33B0)

Old build 9141 is detected installed CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:40 PM 13232 (0x33B0)

INFO: Installing Site Component Manager... CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:40 PM 13232 (0x33B0)

INFO: Installing Site Component Manager under acct <NT AUTHORITY\SYSTEM> path <E:\Microsoft Configuration Manager\bin\x64\sitecomp.exe> CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:50 PM 13232 (0x33B0)

INFO: There is no post setup script. CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:50 PM 13232 (0x33B0)

INFO: Starting Site Component Manager... CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:50 PM 13232 (0x33B0)

INFO: Started Site Component Manager service CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:52 PM 13232 (0x33B0)

INFO: Site Component Manager installation completed. CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:52 PM 13232 (0x33B0)

INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:52 PM 13232 (0x33B0)

Turned on activation for service broker queue CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:52 PM 13232 (0x33B0)

omExitMomMaintenanceMode - beginning. CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:52 PM 13232 (0x33B0)

Attempting to call SCOM Maintenance Mode interface. CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:52 PM 13232 (0x33B0)

omExitMomMaintenanceModeSCOM - Failed to CoCreateInstance for class SCOMMaintenanceModeControl. The error is 0x80040154. CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:52 PM 13232 (0x33B0)

Attempting to call MOM 2005 Maintenance Mode interface. CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:52 PM 13232 (0x33B0)

omExitMomMaintenanceModeMOM2005 - Failed to CoCreateInstance for MOMRuntimeAPI. The error is 0x80040154. CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:52 PM 13232 (0x33B0)

omExitMomMaintenanceMode - ended. CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:52 PM 13232 (0x33B0)

Mom agent has not been restored from the maintenance mode. CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:52 PM 13232 (0x33B0)

Failed to apply update changes 0x80004005 CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:52 PM 13232 (0x33B0)

INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:52 PM 13232 (0x33B0)

Error information persisted in the database. CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:52 PM 13232 (0x33B0)

Waiting for changes to the "E:\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds... CONFIGURATION_MANAGER_UPDATE 7/31/2026 4:33:52 PM 13232 (0x33B0)

Microsoft Security | Intune | Configuration Manager | Deployment
0 comments

3 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-07-31T21:45:23.7766667+00:00

    The primary failure shown in the log is not SCOM communication. The upgrade is failing because required redistributable files are missing, specifically SQLSysClrTypes.msi.

    The documented cause is that the update can’t find required files in one or both of these locations for the affected package GUID 725866CC-E043-4563-B071-A7E66B523F1C:

    1. EasySetupPayload on the service connection point:
      • Online mode: \\<ServiceConnectionPoint>\EasySetupPayload\725866CC-E043-4563-B071-A7E66B523F1C\Redists
      • Offline mode: \\<ServiceConnectionPoint>\EasySetupPayload\Offline\725866CC-E043-4563-B071-A7E66B523F1C\Redists
    2. CMUStaging on the site server:
      • <ConfigMgrInstallPath>\CMUStaging\725866CC-E043-4563-B071-A7E66B523F1C\redist

    Use this path to troubleshoot:

    1. Identify whether SQLSysClrTypes.msi exists in the EasySetupPayload location for that package GUID.
    2. Check whether the same file exists in CMUStaging for that package GUID.
    3. If the file is missing from EasySetupPayload, restore the update payload source first.
    4. If the service connection point is online:
      • Verify the SCP can connect to the internet and required endpoints.
      • Change the update state so it can be downloaded again.
      • Download the package again from the console, or use CMUpdateReset.exe.
      • Review dmpdownloader.log and ConfigMgrSetup.log after the download.
      • Confirm the required files are present in EasySetupPayload\725866CC-E043-4563-B071-A7E66B523F1C\Redists.
    5. If the file exists in EasySetupPayload but is missing from CMUStaging, the issue is with staging content on the site server. Recheck the staging folder for the affected package and restore the missing file set before retrying the in-console update.

    The SCOM-related entries (Failed to CoCreateInstance... 0x80040154) occur later in the log and do not match the documented cause of the Install Files failure. The supported fix is to restore the missing redistributable payload for the update package and then retry the installation.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Carl94580345 41 Reputation points
    2026-08-03T18:03:29.49+00:00

    No matter where I put SQLSysClrTypes.msi the update failed.

    I ran the update for 2603 and that succeeded.

    Was this answer helpful?

    0 comments
  3. Carl94580345 41 Reputation points
    2026-08-03T18:04:42.5866667+00:00

    No matter where I put SQLSysClrTypes.msi the update failed.

    I ran the update for 2603 and that succeeded.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.