none
Update 1602 in "Checking prerequisites" state

    Question

  • Hi!

    I tried to update my CM site to version 1602. The update appeared on console and I right-clicked Run prerequisites check". Now the status for the Update is "Checking prerequisites" for 3 days. In CMUpdate log I find errors:

    • Error in verifying the trust of file 'e:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\SMSSetup\update.map.cab'.
    • Failed to verify the file [e:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\SMSSetup\update.map.cab] is signed by Microsoft.

    And SMSSetup folder does not exist in folder e:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\

    How to restart the Update?

    Thanks,


    UV

    Saturday, March 19, 2016 9:10 AM

Answers

  • I may have made some headway on my instance of the issue. First I ran a query on my SCCM SQL instance:

    SELECT *
      FROM <Database Name>.dbo.CM_UpdatePackages
     where PackageGuid='037CD17E-4D7B-40E1-802B-14BB682364C7' or PackageGuid='609F1263-04E0-49A8-940B-09E0E34DE2D2';

    This returned results showing that my database had records of those upgrade packages (I believe the first one was the GUID back before the update was released to GA, and the second is the new package GUID).

    Next, I ran:

    DELETE FROM <Database Name>.dbo.CM_UpdatePackages
     where PackageGuid = '037CD17E-4D7B-40E1-802B-14BB682364C7' or PackageGuid = '609F1263-04E0-49A8-940B-09E0E34DE2D2';

    That sucessfully removed the records. I refreshed my Updates and Servicing pane in the Configuration Manager Console and sure enough, the 1602 record that had been stuck there was finally gone!

    After that I restarted the SMS_Executive service, and the 1602 update magically reappeared in my Updates and Servicing pane - it is currently in the downloading process and I can see that is it finally populating the EasySetupPayload folder (2.10GB so far).

    I'll report back when that download has finished on how the rest of the process goes - hopefully no more issues running the prerequisite check and then running the real upgrade.

    UPDATE:

    Downloaded completed normally (I didn't even have to restart SMS_Executive again), Prerequisite check passed without issues. I've got to run the upgrade through our CAB process now before I can actually run the real update, but so far things are looking good!


    • Edited by Tom W Brisby Wednesday, March 30, 2016 11:15 PM
    • Proposed as answer by Motorhead85 Thursday, March 31, 2016 12:53 AM
    • Marked as answer by urmasv Friday, April 01, 2016 11:53 AM
    Wednesday, March 30, 2016 11:01 PM

All replies

  • two things you could check:

    Start the service 'CONFIGURATION_MANAGER_UPDATE'

    run the prereq.check manually (..EasySetupPayload\037cd17e-4d7b-40e1-802b-14bb682364c7\SMSSETUP\BIN\X64\prereqchk.exe)

    Saturday, March 19, 2016 9:34 AM
  • With manual check I get only SQL memory allocation warning. Errors in CMUpdate log remains the same.

    In console Update status is still Checking prerequisites.

    Thanks,


    UV

    Saturday, March 19, 2016 10:07 AM
  • I'm also seeing the same issue. Restarting the sms executive service did remedy the status when it was hung on downloading, but the "checking prerequisites" status has survived multiple reboots. I followed -Reto-'s advice and discovered i needed a couple more Gb of free space from the pre-req checker. That eliminated the error, but the status of the 1602 update is still hung at checking pre-reqs. CONFIGURATION_MANAGER_UPDATE service is waiting for changes to the "C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, which is empty. I'm looking in the wrong place at this point, though, because the "Update Pack Installation Status" shows the start of the prerequisite check yesterday and got past it, but the update does not actually appear to be installed.


    • Edited by AMReagan Saturday, March 19, 2016 4:11 PM
    Saturday, March 19, 2016 3:50 PM
  • Was able to manually run the upgrade by launching C:\Program Files\Microsoft Configuration Manager\EasySetupPayload\037cd17e-4d7b-40e1-802b-14bb682364c7\splash.hta
    Saturday, March 19, 2016 4:21 PM
  • Hi!

    I can start setup from EasySetupPayload\... folder but it fails. And it is not supported AFAIK.

    But I also found error "Staging folder (e:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\) has hash 910FE4D30ADA643038F17D1EC359E651B4A29BD5754BC74AF907113E6A8D45AF which does not match hash from content library DCA1C7C785CD2632401B2E8291E309D669086502BBE75825F0758379C29D8ACC" from CMUpdate.log - it seems something is wrong with data in content library?

    Thanks,


    UV

    Monday, March 21, 2016 7:08 PM
  • Please DO NOT run setupwpf.exe from EasySetupPayload folder. It is not supported.

    CM has a lot of validation in place to validate the content downloaded from internet. Signature is just one of the validation. Please make sure your environment trust the Microsoft ROOT CA certificate.

    If it is still showing the same error, you can simply right click on the file "e:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\SMSSetup\update.map.cab" and look at the "Digital signature" tab and see if your OS is validating it correctly.

    Thanks


    --Richard This posting is provided “AS IS” with no warranties and confers no rights.

    Tuesday, March 22, 2016 1:17 AM
  • As I told in the beginning there is not such folder like SMSSetup under folder e:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7. Every time CMUpdate runs its cycle it seems it recreates all folders under the folder CMUStaging, from CMUpdate.log:

    „Delete folder e:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\ returned 0“

    I can check the file „E:\Program Files\Microsoft Configuration Manager\EasySetupPayload\037cd17e-4d7b-40e1-802b-14bb682364c7\SMSSETUP\update.map.cab“ - everything is OK with its signature, MS CA-s are definitely trusted.

    Thanks,


    UV

    Tuesday, March 22, 2016 6:12 AM
  • I was troubleshoting upgrading for v1602 for two evenings, tried first to run upgrade from console which failed because of lacking hdd space (I still have 12gb free). Then I tried to execute slash.hta directly from downloaded folders, but it failed because not supporting right command lines. Finally, I got the thing working by uninstalling connector role, rebooting and installing it back. Then the precheck succeed and I´m now running the upgrade process itself.

    I´m missing MS documentation what log files are included in this whole process....

    • Edited by yannara Tuesday, March 22, 2016 2:41 PM
    Tuesday, March 22, 2016 2:38 PM
  • Didn't help :( Precheck (manual) succeeds with no errors.

    Thanks,


    UV

    Wednesday, March 23, 2016 1:03 PM
  • UV,

      The logic is that it will DELETE the folder (Delete folder e:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\) is when CM Admin tries to run the prereq check again. When it fails, the folder should be there assuming the content is correctly processed by SMS_DISTRIBUTION_MANAGER (DistMgr) and stored in the content library on the site server.

      if you are seeing the folder CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7 folder is there, but sub-folder e:\Program Files\Microsoft Configuration Manager\CMUStaging\037CD17E-4D7B-40E1-802B-14BB682364C7\SMSSetup folder is not; then it is something different, you have to check the content library and see if the content has been processed correctly.

      This is the successful workflow:

    T0: CM Admin chooses to install/run prereq 1602 through CM Admin console

    T1: It notifies HMan (SMS_HIERARCH_MANAGER), to create a software distribution package

       You should see logging in Hman.log: Creating easy setup package...

       and EXEC sp_UpdateEasySetupSettings N'P0100006','1',...

    T2: Get the package ID from the above log line, in my case it is: P0100006

    T3: Check distmgr.log (SMS_DISTRIBUTION_MANAGER)

       should see log Successfully created/updated the package P0100006

    T4: CMUpdate.log extract the content from content library, validate the signature and run the prereq check

    Double check the content library on the site server, usually on the drive with largest free disk space

    Check C:\SCCMContentLib\DataLib\P0100006.1, and see if the folder structure there is correct. you should see  C:\SCCMContentLib\DataLib\P0100006.1\SMSSetup\update.map.cab.INI over there

    If you don't, focus on distmgr.log and see any errors related to processing the package P0100006. (distmgr needs to do the work to have the payload stored in the content library on the site server) 

    If this is a hierarchy, also check despool.log regarding to package P0100006

    NOTE: in your env, the package ID is not P0100006, but you can find it in hman.log shown above (or you can check DB table EasySetupSettings)

    NOTE: I CAN NOT stress enough, do NOT follow other people' suggestion to run setup directly for EasySetupPayload. It is not supported. And if this is an environment with hierarchy, that is going to cause trouble.

    Thx

    Richard [MSFT]


    --Richard This posting is provided “AS IS” with no warranties and confers no rights.


    Wednesday, March 23, 2016 9:58 PM
  • PLEASE DO NOT run directly from EasySetupPayload folder, the structure is internal. It is definitely not supported and it will cause lots more pain if you have a hierarchy.

    Thx

    Richard [MSFT]


    --Richard This posting is provided “AS IS” with no warranties and confers no rights.

    Wednesday, March 23, 2016 10:04 PM
  • Hi!

    I still have total mess with one SCCM site:

    1. It seems 1602 Update is not fully downloaded, total size for EasySetupPayload folder is only ~785 MB istead of ~1,7 GB. Anyway, SMSSetup folder exists here.
    2. CMUStaging folder misses SMSSetup subfolder and files.
    3. In content library SMSSetup folder and files are also missing, it seems to be copy of SMUStaging folder.

    I know something went wrong with my 1602 upgrade. Probably I run out of disk space and restarted the server.

    It seems to be very complicated now and probably it will be easier to rebulid the site. And yes, I can find "EXEC sp_UpdateEasySetupSettings" line from old HMAN.log, package successful creation can be found in Distmgr.log, etc.

    Package Microsoft Corporation Configuration Manager Easy Setup Package seems to be hidden package, so I don't know how to manage/troubleshoot it. It can be found only in Monitoring/Content status area.

    But it is still interesting how to solve the problem? Is it somehow possible to restart the upgrade (new download, new package, new upgrade)?

    Thanks,


    UV

    Thursday, March 24, 2016 1:16 PM
  • Hi UV

      If EasySetupPayload\<1602PackageGuid> has only 785mbytes, then definitely the content was not fully downloaded. Even when hman/distmgr successfully create the software dist package, the content will be in-complete for CM to trust and continue installation.

      DmpDownloader should not report content is ready if it has not fully downloaded the content. I am suspecting somehow the 1602 redist failed to download. If there is not un-supported way done to get the CM into the situation, please go through Microsoft connect and open a bug for us. And even if there is un-supported way done, if you want, you still can let us know what you have done through connect, and we will look into that to see if there is any area we can improve. In next release, we are looking into better monitoring and error reporting to help CM Admins to track the progress.

      For 1602, we are creating a few work flow charts to help CM Admins to understand and troubleshoot CM update channel. The first one is about content download: https://technet.microsoft.com/en-us/library/mt711512.aspx?f=255&MSPPError=-2147217396

    More will be coming soon.

    Thanks

    Richard [MSFT]


    --Richard This posting is provided “AS IS” with no warranties and confers no rights.

    Thursday, March 24, 2016 4:28 PM
  • I seem to be having a very similar issue, yet there are still some differences. Everyone so far seems to at least have some kind of data showing up in the EasySetupPayload folder. However, in my environment this folder is simply blank.

    Somehow, the 1602 update showed up in my Updates and Servicing section this morning (EasySetupPayload folder was still blank). So I triggered the prerequisite check, and now my site is just stuck in a "Checking Prerequisites" state. There is nothing listed in the Site Servicing Status section at all.

    I've tried removing the Service Connection Point role, deleting the EasySetupPayload folder, deleting all contents of the CMUSStaging folder, rebooting the site server, setting up the Service Connection Point role again (online mode, no proxy), and watching the logs.. Nothing has changed in the behavior. The 1602 update is still listed in the Updates and Servicing section as "Checking Prerequisites", but there is nothing listed in the Site Servicing Status section.

    hman.log shows the following: "Get update pacakge 609F1263-04E0-49A8-940B-09E0E34DE2D2, \\*SITE_SERVER_NAME*\EasySetupPayLoad\609F1263-04E0-49A8-940B-09E0E34DE2D2"

    But then the next entry shows "Failed to calculate hash".

    dmpdownloader.log shows: "Manifest.cab was successfully moved to the connector outbox" and then seems to repeatedly try to "Get new Easy Setup Package IDs". Eventually, it says "searching for QFE packages in D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\offline", then "WARNING: Failed to obtain easy setup payload. Retry in the next polling cycle".

    Through all of this the EasySetupPayload folder never receives any data, and I appear to be stuck with the entry in the Updates and Servicing node saying that the Prerequisite check is running..



    • Edited by Tom W Brisby Wednesday, March 30, 2016 8:07 PM Spelling correction
    Wednesday, March 30, 2016 8:05 PM
  • I am having the exact same problem except it is with installing Hotfix 3122637. Have tried the same steps as Tom tried above except mine is stuck at Chekcing Pre-Requisites. The Package in the Data content store does not contain all the files needed for the update Definitely seems like there may be an issue with downloads failing and causing the install to get stuck.

    You would think there would be a way to restart the download, maybe a sql query or similar? Otherwise is there a way to manually download the file and place them in the package folder?

    • Edited by Motorhead85 Wednesday, March 30, 2016 9:58 PM More Info
    Wednesday, March 30, 2016 9:40 PM
  • I may have made some headway on my instance of the issue. First I ran a query on my SCCM SQL instance:

    SELECT *
      FROM <Database Name>.dbo.CM_UpdatePackages
     where PackageGuid='037CD17E-4D7B-40E1-802B-14BB682364C7' or PackageGuid='609F1263-04E0-49A8-940B-09E0E34DE2D2';

    This returned results showing that my database had records of those upgrade packages (I believe the first one was the GUID back before the update was released to GA, and the second is the new package GUID).

    Next, I ran:

    DELETE FROM <Database Name>.dbo.CM_UpdatePackages
     where PackageGuid = '037CD17E-4D7B-40E1-802B-14BB682364C7' or PackageGuid = '609F1263-04E0-49A8-940B-09E0E34DE2D2';

    That sucessfully removed the records. I refreshed my Updates and Servicing pane in the Configuration Manager Console and sure enough, the 1602 record that had been stuck there was finally gone!

    After that I restarted the SMS_Executive service, and the 1602 update magically reappeared in my Updates and Servicing pane - it is currently in the downloading process and I can see that is it finally populating the EasySetupPayload folder (2.10GB so far).

    I'll report back when that download has finished on how the rest of the process goes - hopefully no more issues running the prerequisite check and then running the real upgrade.

    UPDATE:

    Downloaded completed normally (I didn't even have to restart SMS_Executive again), Prerequisite check passed without issues. I've got to run the upgrade through our CAB process now before I can actually run the real update, but so far things are looking good!


    • Edited by Tom W Brisby Wednesday, March 30, 2016 11:15 PM
    • Proposed as answer by Motorhead85 Thursday, March 31, 2016 12:53 AM
    • Marked as answer by urmasv Friday, April 01, 2016 11:53 AM
    Wednesday, March 30, 2016 11:01 PM
  • I can confirm the same has worked for me, just changed the package id to the hotfix 10BE05BB-BE45-4D65-8C3D-D12BAC995233. Will report back how the install goes.

    Update:

    Pre Req has passed though after selecting install the status has not changed and I see the below in CMUpdate.log

    Update package will not install as it is marked for prereq check only.    CONFIGURATION_MANAGER_UPDATE    31/03/2016 11:00:34 AM    11536 (0x2D10)

    Will continue to monitor

    Further Update:

    Install has now started (No intervention needed) and looking good

    Final Update:

    Install was successful, that SQL Query looks like the fix, great work!

    • Edited by Motorhead85 Thursday, March 31, 2016 12:53 AM
    Wednesday, March 30, 2016 11:18 PM
  • Hi Motorhead85, Hotfix 3122637 is relatively much smaller than 1602. you may not need to force redownload of the content.

    If in Admin console, it is still showing "Checking Pre-requisites", please double check two log files. Hman.log, distmgr.log

    • Please check hman.log on site server to see if it has successfully created the software distribution package.

    Easy setup package hash = C55151F8B8E3FB70C39416E1D80D7F612E38BFB77D5E5B0DCCB8AF800EBFD8DC               

    Creating easy setup package... 

    Updating easy setup settings with EXEC sp_UpdateEasySetupSettings N'P0100006','1',N'C55151F8B8E3FB70C39416E1D80D7F612E38BFB77D5E5B0DCCB8AF800EBFD8DC'               

    P0100006 in this case is the package ID

    • Please check distmgr.log regarding the package, distmgr is supposed to copy the content from the source to the content library on the site server.

    STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=R31309497.R31309497DOM.net SITE=P01 PID=2264 TID=2884 GMTDATE=Sat Mar 19 01:26:40.659 2016 ISTR0="Configuration Manager Easy Setup Package" ISTR1="P0100006" ISTR2="" ISTR3="" ISTR4=""

    Exiting package processing thread for package P0100006.             

    If there is not enough disk space on the site server, or other problem that hman/distmgr can not access the \\<Service Connection Point>\EasySetupPayloader folder, you will see what you are seeing in CM Admin Console. (We are trying to improve the UI monitoring experience in future release)

    The other common problem is antivirus software. Make sure content library and CM install dirs are in the exclusion list

    If everything in hman.log/distmgr.log shows the package is processed, then check cmupdate.log


    --Richard This posting is provided “AS IS” with no warranties and confers no rights.

    Thursday, March 31, 2016 4:41 PM
  • Great success :) Works like a charm!

    Thanks!


    UV

    Friday, April 01, 2016 11:56 AM
  • Hi, this also worked for me. 1602 was stuck in checjing prereqs until running this delete.

    After restarting sms_executive the update was rediscovered and downloaded.

    Wednesday, April 06, 2016 3:05 AM
  • I may have made some headway on my instance of the issue. First I ran a query on my SCCM SQL instance:

    SELECT *
      FROM <Database Name>.dbo.CM_UpdatePackages
     where PackageGuid='037CD17E-4D7B-40E1-802B-14BB682364C7' or PackageGuid='609F1263-04E0-49A8-940B-09E0E34DE2D2';

    This returned results showing that my database had records of those upgrade packages (I believe the first one was the GUID back before the update was released to GA, and the second is the new package GUID).

    Next, I ran:

    DELETE FROM <Database Name>.dbo.CM_UpdatePackages
     where PackageGuid = '037CD17E-4D7B-40E1-802B-14BB682364C7' or PackageGuid = '609F1263-04E0-49A8-940B-09E0E34DE2D2';


    This is something that you should not do in production, because altering SQL is not supported by MS, when you are talking about CM. Just a side comment :)
    Wednesday, April 06, 2016 11:47 AM
  • Hi Yannara, I was working with Microsoft Support to resolve the issue, so it is supported in this scenario.

    Obviously this was performed after a site backup.

    Thursday, April 07, 2016 3:32 AM
  • I´m just thinking, should we use the precheck or not? During the upgrade from 1511 to 1602, there is an option to ignore any precheck warnings. Since there seems to be some "bugs" or issues with the content, guid missmatch or something, I might prefer to ignore these warnings and go with the upgrade. Only critical part is to precheck the database first. Se still use vmware snapshots in production, so if it blows, we revert. How does it sounds?

    With first upgrade, which was a clean CM 1511 installation, I fought 3 evenings to do it, then I took first old CM enviroment, did 1511 upgrade and then did 1602 upgrade ignoring warnings, works as a charm...

    Monday, April 11, 2016 6:49 AM
  • Not sure what to do here. the console has 1602 and 1511 hotfix. I can right click and install the hotfix. However i cannot do the same with 1602. all choices are greyed out. My easysetuppayload folder has both GUIDS 609f1263-04e0-49a8-940b-09e0e34de2d2 and 10be05bb-be45-4d65-8c3d-d12bac995233

    the 1602 is complete based on 1.72 gigs of data, and folder and file structure look intact. its been like this for 4 days

    CMupdate log:

    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 4/11/2016 7:08:15 PM 1820 (0x071C)
    There is no redist version. Use default redist version 112015 CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:18:15 PM 1820 (0x071C)
    This is running against 1511 RTM or 1512 TP. Use default publisher flag 0x2 CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:18:15 PM 1820 (0x071C)
    INFO: setup type: 1, top level: 1. CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:18:15 PM 1820 (0x071C)
    Update package will not install as it is marked for prereq check only. CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:18:15 PM 1820 (0x071C)
    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 4/11/2016 7:18:15 PM 1820 (0x071C)
    There is no redist version. Use default redist version 112015 CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:28:16 PM 1820 (0x071C)
    This is running against 1511 RTM or 1512 TP. Use default publisher flag 0x2 CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:28:16 PM 1820 (0x071C)
    INFO: setup type: 1, top level: 1. CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:28:16 PM 1820 (0x071C)
    Update package will not install as it is marked for prereq check only. CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:28:16 PM 1820 (0x071C)
    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 4/11/2016 7:28:16 PM 1820 (0x071C)
    There is no redist version. Use default redist version 112015 CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:38:16 PM 1820 (0x071C)
    This is running against 1511 RTM or 1512 TP. Use default publisher flag 0x2 CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:38:16 PM 1820 (0x071C)
    INFO: setup type: 1, top level: 1. CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:38:16 PM 1820 (0x071C)
    Update package will not install as it is marked for prereq check only. CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:38:16 PM 1820 (0x071C)
    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 4/11/2016 7:38:16 PM 1820 (0x071C)
    There is no redist version. Use default redist version 112015 CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:48:16 PM 1820 (0x071C)
    This is running against 1511 RTM or 1512 TP. Use default publisher flag 0x2 CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:48:16 PM 1820 (0x071C)
    INFO: setup type: 1, top level: 1. CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:48:16 PM 1820 (0x071C)
    Update package will not install as it is marked for prereq check only. CONFIGURATION_MANAGER_UPDATE 4/11/2016 7:48:16 PM 1820 (0x071C)
    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 4/11/2016 7:48:16 PM 1820 (0x071C)

    how can i kick the install off?  thanks

    Monday, April 11, 2016 11:58 PM
  • Se still use vmware snapshots in production, so if it blows, we revert. How does it sounds?


    Not good, because snapshot are not supported to restore a site (especially true when there are more sites involved).

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, April 12, 2016 6:05 AM
  • how can i kick the install off?  thanks

    Have you already restarted SMS Executive?

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, April 12, 2016 6:06 AM
  • restarted SMSEXEC and rebooted several times. still all options greyed out
    Wednesday, April 13, 2016 2:32 AM
  • restarted SMSEXEC and rebooted several times. still all options greyed out

    How about removing that Connector role from site server, restart, re-add it and launch the pre-checker again? That helped me out.
    • Proposed as answer by yannara Thursday, April 28, 2016 8:48 AM
    Wednesday, April 13, 2016 6:00 AM
  • removed service connection point, rebooted, and 1602 still shows all options as greyed out. it does say prerequisites check passed for 1602, but right clicking shows all options as greyed out
    Wednesday, April 13, 2016 11:59 PM
  • I had done all the above said activities, but still it says Checking prerequisites.

     i tried restarting SMS_Executive, Removed the package from SQl DB, removed and readded Service connection point but with no luck.  I also tried running pre req check manually on all servers 1 cas, 3 primary out of which 2 primary gives warning message for backlogged inbox.

    So current state on all servers is Checking prerequisites..... :(

    Friday, April 22, 2016 9:35 AM
  • Finding myself in the same boat, after only about 30 min. into my R2>1511 upgrade. I have the full EasySetupPayload download. I can't get the SMS_Executive Service to restart w/o timing out. Manual prereq check passes just fine. Going to try removing and re-adding the service connection point role and see where I'm at.

    ETA: That worked! Thx.



    • Edited by JackalAR Saturday, April 23, 2016 3:54 AM
    Friday, April 22, 2016 10:17 PM
  • This is awesome! solve mine too!
    Thursday, April 28, 2016 1:56 AM
  • I'm stuck at installing actually. I have a thread started here: https://social.technet.microsoft.com/Forums/en-US/f8f3127e-a4b5-43b1-aa6e-25cd12c3e38a/1602-updates-stuck-installing?forum=ConfigMgrCompliance
    Thursday, April 28, 2016 3:06 PM
  • This is normal, in my case it did this for about 1.5 hours. Monitor the CMUpdate.log I think it is. I accidentally rebooted about 10 min. into it, but it recovered just fine on its own.
    Thursday, April 28, 2016 3:18 PM
  • This is normal, in my case it did this for about 1.5 hours. Monitor the CMUpdate.log I think it is. I accidentally rebooted about 10 min. into it, but it recovered just fine on its own.
    It was like that for a week actually. Do you think I should just keep waiting? Is there something it might be waiting for before it starts?
    Thursday, April 28, 2016 3:20 PM
  • Oh dang, I doubt it, check the logs and/or try removing and re-adding the service connection point role again...??? If that doesn't work, I think you're possibly looking at opening a case with MS and having them walk you through hacking the DB.

    • Edited by JackalAR Thursday, April 28, 2016 3:32 PM
    Thursday, April 28, 2016 3:31 PM
  • Oh dang, I doubt it, check the logs and/or try removing and re-adding the service connection point role again...??? If that doesn't work, I think you're possibly looking at opening a case with MS and having them walk you through hacking the DB.

    I've done that a few times now, and going to try it again. I can successfully reset the Update status by deleting from the DB, with the query in this post. Anyone else have any suggestions? I could rebuild the entire Site but I would rather not have to. 
    Thursday, April 28, 2016 3:36 PM
  • Oh dang, I doubt it, check the logs and/or try removing and re-adding the service connection point role again...??? If that doesn't work, I think you're possibly looking at opening a case with MS and having them walk you through hacking the DB.

    I've done that a few times now, and going to try it again. I can successfully reset the Update status by deleting from the DB, with the query in this post. Anyone else have any suggestions? I could rebuild the entire Site but I would rather not have to. 

    Did you ever resolve this?
    Monday, June 06, 2016 5:41 AM
  • Definitive fix. Cleared hung process on 2 servers.

    Many Kudo's

    Monday, June 20, 2016 1:30 PM
  • I may have made some headway on my instance of the issue. First I ran a query on my SCCM SQL instance:

    SELECT *
      FROM <Database Name>.dbo.CM_UpdatePackages
     where PackageGuid='037CD17E-4D7B-40E1-802B-14BB682364C7' or PackageGuid='609F1263-04E0-49A8-940B-09E0E34DE2D2';

    This returned results showing that my database had records of those upgrade packages (I believe the first one was the GUID back before the update was released to GA, and the second is the new package GUID).

    Next, I ran:

    DELETE FROM <Database Name>.dbo.CM_UpdatePackages
     where PackageGuid = '037CD17E-4D7B-40E1-802B-14BB682364C7' or PackageGuid = '609F1263-04E0-49A8-940B-09E0E34DE2D2';

    That sucessfully removed the records. I refreshed my Updates and Servicing pane in the Configuration Manager Console and sure enough, the 1602 record that had been stuck there was finally gone!

    After that I restarted the SMS_Executive service, and the 1602 update magically reappeared in my Updates and Servicing pane - it is currently in the downloading process and I can see that is it finally populating the EasySetupPayload folder (2.10GB so far).

    I'll report back when that download has finished on how the rest of the process goes - hopefully no more issues running the prerequisite check and then running the real upgrade.

    UPDATE:

    Downloaded completed normally (I didn't even have to restart SMS_Executive again), Prerequisite check passed without issues. I've got to run the upgrade through our CAB process now before I can actually run the real update, but so far things are looking good!



    PLEASE, DO NOT, DO NOT, AND DO NOT do this unless you know for sure what is going on.
    There are a few tables behind the scene. Without finding the root cause in your environment, and following this could get environment into a even worse state.

    --Richard This posting is provided “AS IS” with no warranties and confers no rights.

    Thursday, August 04, 2016 7:05 PM
  • How I can ignore the precheck warning?
    Friday, August 12, 2016 12:34 PM
  • You can select an Option to ignore Prerequiste Check it when you start the Install Update Pack Wizard.
    • Proposed as answer by tacks2211 Tuesday, April 04, 2017 8:53 PM
    Friday, August 12, 2016 1:18 PM
    • Proposed as answer by ajaytoon Friday, August 26, 2016 12:28 PM
    Friday, August 26, 2016 12:21 PM
  • This worked for me, thanks! 
    Sunday, October 23, 2016 3:13 AM
  • I faced same issue, just changing the state in cm_updatespackages didnt help.

    I noticed a .EFC file in hman\CFD inbox folder (dated 4 months back). this file is typically processed quickly as soon as hman sees the package as applicable and instructs distmgr to create package for easysetuppayload content.

    After deleting this file and again changing state to make package status 'Available ' again, the pre-req checker ran fine.

    Tuesday, February 07, 2017 8:31 PM