Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED SCCM 2012 Cannot Finish the Updates 1802 & 1710

  • Thread starter Thread starter Rashid
  • Start date Start date
  • Replies Replies 3
  • Views Views 6K
Status
Not open for further replies.

Rashid

New Member
Messages
3
Reaction score
0
Points
1
I tried to updates the sccm 2012 updates 1802 & 1710 Hotfix also, both updates are failed to while doing the updates.

Please help me to sort this issue, this issue is persiste since last two months, i tired alots of links but all are failed..

CM Update Logs

Staging folder has hash = 0F27A7C904748E4C1CD5A0172F158494E160E988232DE78D23E9BBF4735E4F49 CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:20:48 PM 1948 (0x079C)
Staging folder (\\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\EAB25B02-02DD-4A14-B6D0-BA5BDE540D66) has hash 0F27A7C904748E4C1CD5A0172F158494E160E988232DE78D23E9BBF4735E4F49 which does not match hash from content library 1E142E657181BAE68A434DE01E5AF3AA542FE3A08F15845B948A4FDAA34A26E8 CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:20:48 PM 1948 (0x079C)
Delete folder \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\EAB25B02-02DD-4A14-B6D0-BA5BDE540D66\ returned 0. Extractring the content from content library... CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:20:53 PM 1948 (0x079C)
update package content EAB25B02-02DD-4A14-B6D0-BA5BDE540D66 has been expanded to foler \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\EAB25B02-02DD-4A14-B6D0-BA5BDE540D66\ CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
Successfully reported ConfigMgr update status (SiteCode=WBM, SubStageID=0xd0005, IsComplete=1, Progress=50, Applicable=1) CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
File '\\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\EAB25B02-02DD-4A14-B6D0-BA5BDE540D66\SMSSetup\update.map.cab' is signed and trusted. CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
Signing root cert's thumbprint: cdd4eeae6000ac7f40c3802c171e30148030c072 CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
Extracting file \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\EAB25B02-02DD-4A14-B6D0-BA5BDE540D66\SMSSetup\update.map.cab to \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\EAB25B02-02DD-4A14-B6D0-BA5BDE540D66\SMSSetup\ CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
Extracted \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\EAB25B02-02DD-4A14-B6D0-BA5BDE540D66\SMSSetup\update.map CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
Successfully reported ConfigMgr update status (SiteCode=WBM, SubStageID=0xd0005, IsComplete=1, Progress=75, Applicable=1) CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
Successfully read file \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\EAB25B02-02DD-4A14-B6D0-BA5BDE540D66\SMSSetup\update.map CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
Successfully reported ConfigMgr update status (SiteCode=WBM, SubStageID=0xd0005, IsComplete=2, Progress=100, Applicable=1) CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
FQDN for server QAWBMSCCMSV13 is qawbmsccmsv13.wbm.local CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
INFO: Target computer is a 64 bit operating system. CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
INFO: Checking for existing setup information. CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
INFO: Setting setup type to 1. CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
INFO: Checking for existing SQL information. CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
INFO: 'qawbmsqlsv12.wbm.local' is a valid FQDN. CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
INFO: Verifying the registry entry for Asset Intelligence installation CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
INFO: Found registry key for installation of Asset Intelligence full version CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
INFO: Setup detected an existing Configuration Manager installation. Currently installed version is 8577 CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
INFO: Phase is 1C7 CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:21:59 PM 1948 (0x079C)
INFO: SDK Provider is on qawbmsccmsv13.wbm.local. CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:00 PM 1948 (0x079C)
Set working directory to the staging folder C:\Program Files\Microsoft Configuration Manager\CMUStaging\EAB25B02-02DD-4A14-B6D0-BA5BDE540D66\SMSSetup CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:00 PM 1948 (0x079C)
INFO: Setting the default CSV folder path CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:00 PM 1948 (0x079C)
INFO: Language: Mobile Device (INTL), LangPack: 0. CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:00 PM 1948 (0x079C)
INFO: Configuration Manager Build Number = 8634 CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:00 PM 1948 (0x079C)
INFO: Configuration Manager Version = 5.0 CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:00 PM 1948 (0x079C)
INFO: Configuration Manager Minimum Build Number = 800 CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:00 PM 1948 (0x079C)
Preparing prereq check for site server [QAWBMSCCMSV13.WBM.LOCAL]... CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:00 PM 1948 (0x079C)
prereqcore has hash value SHA256:E802293280BCE745A0E4C128EB0FB8F258485E16F92B72AE28CC3EE4C2A11326 CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:00 PM 1948 (0x079C)
Running prereq checking against Server [QAWBMSCCMSV13.WBM.LOCAL] ... CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:00 PM 1948 (0x079C)
INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:19 PM 1948 (0x079C)
Error information persisted in the database. CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:19 PM 1948 (0x079C)
Waiting for changes to the "\\qawbmsccmsv13.wbm.local\SMS_WBM\inboxes\cmupdate.box" directories, updates will be polled in 296 seconds... CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:19 PM 1948 (0x079C)
Detected a change to the "\\qawbmsccmsv13.wbm.local\SMS_WBM\inboxes\cmupdate.box" directory. CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:19 PM 1948 (0x079C)
Waiting for changes to the "\\qawbmsccmsv13.wbm.local\SMS_WBM\inboxes\cmupdate.box" directories, updates will be polled in 296 seconds... CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:19 PM 1948 (0x079C)
Detected a change to the "\\qawbmsccmsv13.wbm.local\SMS_WBM\inboxes\cmupdate.box" directory. CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:19 PM 1948 (0x079C)
Waiting for changes to the "\\qawbmsccmsv13.wbm.local\SMS_WBM\inboxes\cmupdate.box" directories, updates will be polled in 296 seconds... CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:22:19 PM 1948 (0x079C)
There are no pending update package to be processed. CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:27:15 PM 1948 (0x079C)
INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:27:15 PM 1948 (0x079C)
Waiting for changes to the "\\qawbmsccmsv13.wbm.local\SMS_WBM\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds... CONFIGURATION_MANAGER_UPDATE 22/05/2018 01:27:15 PM 1948 (0x079C)


Thanks in Advance
 

Attachments

  • SCCM UPDATE FAILED.JPG
    SCCM UPDATE FAILED.JPG
    67.2 KB · Views: 4
  • sccm 1802.JPG
    sccm 1802.JPG
    46.5 KB · Views: 5
  • sccm update 1710.JPG
    sccm update 1710.JPG
    57.3 KB · Views: 2
  • ERROR LOG CM UPDATE.JPG
    ERROR LOG CM UPDATE.JPG
    407.6 KB · Views: 5
Last edited:
From the screenshot i see the prerequisite check has failed. Can you upload ConfigMgrPrereq.log located in c: drive.
 
Status
Not open for further replies.
Back
Top