locked
1511 to 1606 Upgrade Stuck RRS feed

  • Question

  • I kicked off an upgrade on my primary site from 1511 to 1606 on my lab environment after all the pre-reqs had passed. However I checked it this morning and it seems to just be stuck doing the same thing over and over.

    it has been "Update Pack Installing" for almost 2 days now

    CMUpdate.log keeps stating that it failed to find the manifestversion node then starts waiting and the process starts all over again, however Googling that error yielded very little. Log entry below

    <#
    Waiting for changes to the "C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 16:58:08.645+300><thread=1084 (0x43C)>
    This is running against 1511 RTM or 1512 TP. Use default publisher flag 0x2  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:08:08.734+300><thread=1084 (0x43C)>
    INFO: setup type: 1, top level: 1.  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:08:08.772+300><thread=1084 (0x43C)>
    Successfully reported ConfigMgr update status (SiteCode=HOM, SubStageID=0xd0007, IsComplete=1, Progress=1, Applicable=1)  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:08:09.000+300><thread=1084 (0x43C)>
    Successfully reported ConfigMgr update status (SiteCode=HOM, SubStageID=0xd0007, IsComplete=2, Progress=100, Applicable=1)  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:08:09.491+300><thread=1084 (0x43C)>
    Successfully reported ConfigMgr update status (SiteCode=HOM, SubStageID=0xd0008, IsComplete=1, Progress=1, Applicable=1)  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:08:09.737+300><thread=1084 (0x43C)>
    There is no service window defined for the site server to apply the CM server updates.  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:08:09.986+300><thread=1084 (0x43C)>
    Successfully reported ConfigMgr update status (SiteCode=HOM, SubStageID=0xd0008, IsComplete=2, Progress=100, Applicable=1)  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:08:10.177+300><thread=1084 (0x43C)>
    Successfully reported ConfigMgr update status (SiteCode=HOM, SubStageID=0xd0005, IsComplete=1, Progress=1, Applicable=1)  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:08:10.383+300><thread=1084 (0x43C)>
    Successfully reported ConfigMgr update status (SiteCode=HOM, SubStageID=0xd0005, IsComplete=1, Progress=25, Applicable=1)  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:08:10.844+300><thread=1084 (0x43C)>
    Ignoring drive F:\. File F:\NO_SMS_ON_DRIVE.SMS exists.  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:08:11.052+300><thread=1084 (0x43C)>
    Ignoring drive C:\. File C:\NO_SMS_ON_DRIVE.SMS exists.  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:08:11.267+300><thread=1084 (0x43C)>
    Ignoring drive E:\. File E:\NO_SMS_ON_DRIVE.SMS exists.  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:08:11.460+300><thread=1084 (0x43C)>
    Checking if the CMU Staging folder already has the content extracted.  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:08:11.660+300><thread=1084 (0x43C)>
    Creating hash for algorithm 32780  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:08:12.102+300><thread=1084 (0x43C)>
    Staging folder has hash = C71743983544DEA5820DA8C3654326707DCDB932A8BFA27A2EAC52AB19CD2B08  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:10:47.125+300><thread=1084 (0x43C)>
    Staging folder (\\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\) has hash 991A0DBA007EA04DE7710BDCB17BEAE51C1F239D9889272BFF4618A564BFEFDF which does not match hash from content library C71743983544DEA5820DA8C3654326707DCDB932A8BFA27A2EAC52AB19CD2B08  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:10:47.165+300><thread=1084 (0x43C)>
    Delete folder \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\ returned 0. Extractring the content from content library...  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:11:19.485+300><thread=1084 (0x43C)>
    update package content 0D256560-ED2C-45B5-8D75-4D38AB3F758C has been expanded to foler \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:41.884+300><thread=1084 (0x43C)>
    Successfully reported ConfigMgr update status (SiteCode=HOM, SubStageID=0xd0005, IsComplete=1, Progress=50, Applicable=1)  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:41.930+300><thread=1084 (0x43C)>
    File '\\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\SMSSetup\update.map.cab' is signed and trusted.  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:42.258+300><thread=1084 (0x43C)>
    Signing root cert's thumbprint: cdd4eeae6000ac7f40c3802c171e30148030c072  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:42.563+300><thread=1084 (0x43C)>
    Extracting file \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\SMSSetup\update.map.cab to \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\SMSSetup\  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:43.199+300><thread=1084 (0x43C)>
    Extracted \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\SMSSetup\update.map~  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:43.434+300><thread=1084 (0x43C)>
    Successfully reported ConfigMgr update status (SiteCode=HOM, SubStageID=0xd0005, IsComplete=1, Progress=75, Applicable=1)  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:43.747+300><thread=1084 (0x43C)>
    Successfully read file \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\SMSSetup\update.map  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:44.158+300><thread=1084 (0x43C)>
    Successfully reported ConfigMgr update status (SiteCode=HOM, SubStageID=0xd0005, IsComplete=2, Progress=100, Applicable=1)  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:44.764+300><thread=1084 (0x43C)>
    ~FQDN for server SCCM-PRI is SCCM-PRI.Home.local  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:45.108+300><thread=1084 (0x43C)>
    INFO: Target computer is a 64 bit operating system.  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:45.588+300><thread=1084 (0x43C)>
    INFO: Checking for existing setup information.  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:45.625+300><thread=1084 (0x43C)>
    INFO: Setting setup type to  1.  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:45.662+300><thread=1084 (0x43C)>
    INFO: Checking for existing SQL information.  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:45.960+300><thread=1084 (0x43C)>
    INFO: 'SCCM-PRI.Home.local' is a valid FQDN.  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:46.114+300><thread=1084 (0x43C)>
    INFO: Verifying the registry entry for Asset Intelligence installation  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:46.349+300><thread=1084 (0x43C)>
    INFO: Found registry key for installation of Asset Intelligence full version  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:46.611+300><thread=1084 (0x43C)>
    INFO: Setup detected an existing Configuration Manager installation. Currently installed version is 8325~  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:46.850+300><thread=1084 (0x43C)>
    INFO: Phase is 1C7~  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:47.435+300><thread=1084 (0x43C)>
    INFO: SDK Provider is on SCCM-PRI.Home.local.  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:47.768+300><thread=1084 (0x43C)>
    Set working directory to the staging folder C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\SMSSetup  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:48.113+300><thread=1084 (0x43C)>
    INFO: Setting the default CSV folder path  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:48.568+300><thread=1084 (0x43C)>
    INFO: Language: Mobile Device (INTL), LangPack: 0.  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:48.987+300><thread=1084 (0x43C)>
    INFO: Configuration Manager Build Number = 8412  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:49.454+300><thread=1084 (0x43C)>
    INFO: Configuration Manager Version = 5.0  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:50.064+300><thread=1084 (0x43C)>
    INFO: Configuration Manager Minimum Build Number = 800  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:50.415+300><thread=1084 (0x43C)>
    Successfully reported ConfigMgr update status (SiteCode=HOM, SubStageID=0xd0006, IsComplete=1, Progress=1, Applicable=1)  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:50.714+300><thread=1084 (0x43C)>
    Found redist manifest C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\redist\ConfigMgr.Manifest.cab and set redist folder to C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\redist.  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:51.085+300><thread=1084 (0x43C)>
    INFO: Extracted file C:\Windows\TEMP\ConfigMgr.Manifest.xml  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:51.569+300><thread=1084 (0x43C)>
    ERROR: Failed to find ManifestVersion node  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:51.850+300><thread=1084 (0x43C)>
    Failed to verify redist file for update C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\redist\ConfigMgr.Manifest.cab  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:51.965+300><thread=1084 (0x43C)>
    Waiting for changes to the "C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...  $$<CONFIGURATION_MANAGER_UPDATE><12-24-2016 17:19:52.132+300><thread=1084 (0x43C)>
    #>

    Has anyone seen this before?

    Saturday, December 24, 2016 10:31 PM

Answers

  • I fixed it, here's the process of events

    I decided to go into the EasyPayload folder and find the 1606 installer, I then ran the setup.hta which had the option to upgrade grayed out, but I found something interesting in the ConfigMgrSetupWizard.log 

    ConfigMgrSetupWizard Information: 1 : 1511 and 1602 builds are detected. Upgrade is blocked

    Seeing that error made me think, If it's detecting 1602 but it is not installed let me try to manually upgrade it. I went into the EasyPayload folder, found the 1602 installer and ran the setup.hta (funny enough it was the only one that gave me the option to upgrade it was grayed out for all the others) I selected upgrade, left the server be for about an hour and came back to a server now running 1602. 
    In the Updates and Servicing node 1606 which started this whole issue now stated "Install Failed" and hot fixes for 1602 are also now available so it looks like I'm back in business, now I just need to continue the upgrade up to 1610.

    • Marked as answer by L_P_G Tuesday, January 17, 2017 5:33 PM
    Tuesday, January 17, 2017 5:33 PM

All replies

  • I have the exact same symptoms as you. If knows of a solution, I would be grateful for a response.

       
    Thursday, December 29, 2016 8:19 PM
  • Same problem, tried everything but no success.

    Can somebody help?

    Tuesday, January 3, 2017 9:22 AM
  • I fixed it, here's the process of events

    I decided to go into the EasyPayload folder and find the 1606 installer, I then ran the setup.hta which had the option to upgrade grayed out, but I found something interesting in the ConfigMgrSetupWizard.log 

    ConfigMgrSetupWizard Information: 1 : 1511 and 1602 builds are detected. Upgrade is blocked

    Seeing that error made me think, If it's detecting 1602 but it is not installed let me try to manually upgrade it. I went into the EasyPayload folder, found the 1602 installer and ran the setup.hta (funny enough it was the only one that gave me the option to upgrade it was grayed out for all the others) I selected upgrade, left the server be for about an hour and came back to a server now running 1602. 
    In the Updates and Servicing node 1606 which started this whole issue now stated "Install Failed" and hot fixes for 1602 are also now available so it looks like I'm back in business, now I just need to continue the upgrade up to 1610.

    • Marked as answer by L_P_G Tuesday, January 17, 2017 5:33 PM
    Tuesday, January 17, 2017 5:33 PM
  • Another solution is:

    Clear records for SQL dbo.CM_UpdatesPackage
    Delete folders EasySetupPayload and CMUStaging form C:\Program Files\Microsoft Configuration Manager\

    Restart SMS_Executive service.

    Do not install 1602 or 1606!

    Wait for downloading 1610 and install it.

    Sunday, January 22, 2017 9:47 AM