none
OSD Task Sequence fails on first attempt in Software Center RRS feed

  • Question

  • Will I have been facing an issue with OS deployments via Software Center in my test SCCM server. OS Deployment always fails on first attempt but on retry which happens after 10 minutes the deployment starts successfully.

    This happens with Windows 7, 8, 10 TS. I have seen this in a production environment also.

    Now I think to find out the solution for this problem. Where should I start?

    I have the following:

    • Server1: Windows Server 2012 R2 (Active Directory)
    • Server2: Windows Server 2012 R2 (SCCM 1602)

    • Edited by Hamnawa Wednesday, April 20, 2016 12:42 PM Add extra info
    Wednesday, April 20, 2016 12:25 PM

Answers

  • This is an issue with the product.

    The client downloads policy from the MP using two channels - BITS and raw HTTP. In the past, all policies were downloaded using only a single channel. However, a change was made to "optimize" the policy download to use different channels depending on the policy size. This caused some policies to arrive in a different order. This is normally harmless. But, in the case of task sequence policies, this is harmful because task sequence policies have dependencies.

    The effect is that the main task sequence policy gets downloaded and software center thinks that it is OK to display and run it. But, in reality, the dependent policies have yet to be downloaded, and so it fails. After a few minutes, the dependent policies eventually get downloaded, and the retry succeeds.

    Thursday, September 29, 2016 12:39 AM

All replies

  • Which failure is that? Any details available?

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

    Wednesday, April 20, 2016 1:02 PM
  • Dear Sir,

         Also have you checked the smsts.log? Are there any errors in it?

    Best regards,

    Jimmy


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Thursday, April 21, 2016 6:23 AM
    Moderator
  • In the software center the status shows as failed and Retry after 10 minutes.

    And in the second attempt it deploys the OS.

    There is no log entry in smsts.log file on the client. What log files on the SCCM server should I look for trace of the error?

    Friday, April 22, 2016 8:30 AM
  • Dear Sir,

        So if you click the "failed", what error/error code you will see?

    Best regards,

    Jimmy


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, April 25, 2016 3:35 AM
    Moderator
  • I am not seeing any error code there. It only displays the following text:

    Unable to make changes to your software

    There was a problem applying changes to the software.

    Click OK to return to Software Center.

    My account is not verified therefore I can not attach the screenshot.

    Monday, April 25, 2016 11:00 AM
  • Hi,

       1. Press F5 to refresh the software center and retry.

       2. Also check the execmgr.log on your client (PATH:%systemroot%\CCM\logs)  

    Best regards,

    Jimmy


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, April 26, 2016 2:14 AM
    Moderator
  • I did try a refresh and it does not help.

    The TS retry automatic after 10 minute from first attempt and always goes without problem in second attempt.

    I am trying to figure out why it fails on first attempt.

    Here is the log from execmgr.log

    Mandatory execution requested for program * and advertisement XXX2003E	execmgr	2016-04-26 12:12:53	2784 (0x0AE0)
    Creating mandatory request for advert XXX2003E, program *, package XXX0001A	execmgr	2016-04-26 12:12:53	2784 (0x0AE0)
    The created request is a Task Sequence request	execmgr	2016-04-26 12:12:53	2784 (0x0AE0)
    GetSWDistPolicy - Could not find the policy in WMI for advertisement XXX2003E package XXX00006 program *	execmgr	2016-04-26 12:12:54	2784 (0x0AE0)
    Unable to find member policy for [advertisement: XXX2003E program: *]	execmgr	2016-04-26 12:12:54	2784 (0x0AE0)
    Fail to initialize TS member info, error 0x87d02004	execmgr	2016-04-26 12:12:54	2784 (0x0AE0)
    Child policy does not exist for program *. This program will retry.	execmgr	2016-04-26 12:12:54	2784 (0x0AE0)
    Program * has been tried 0 times, will retry later	execmgr	2016-04-26 12:12:54	2784 (0x0AE0)
    Execution Request for advert XXX2003E package XXX0001A program * state change from NotExist to WaitingRetry	execmgr	2016-04-26 12:12:54	2784 (0x0AE0)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="XXX0001A",ProgramID="*", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	2016-04-26 12:12:54	2784 (0x0AE0)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="XXX0001A",ProgramID="*", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	2016-04-26 12:12:54	2784 (0x0AE0)
    Policy arrived for child program *	execmgr	2016-04-26 12:12:54	2544 (0x09F0)
    Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	2016-04-26 12:12:55	2544 (0x09F0)
    Raising client SDK event for class NULL, instance NULL, actionType 6l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	2016-04-26 12:12:55	2544 (0x09F0)
    Policy arrived for child program *	execmgr	2016-04-26 12:12:55	3392 (0x0D40)
    Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	2016-04-26 12:12:55	3392 (0x0D40)
    Raising client SDK event for class NULL, instance NULL, actionType 6l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	2016-04-26 12:12:55	3392 (0x0D40)
    Policy arrived for child program *	execmgr	2016-04-26 12:12:55	3392 (0x0D40)
    Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	2016-04-26 12:12:55	3392 (0x0D40)
    Raising client SDK event for class NULL, instance NULL, actionType 6l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	2016-04-26 12:12:55	3392 (0x0D40)
    Policy arrived for child program *	execmgr	2016-04-26 12:12:55	3392 (0x0D40)
    Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	2016-04-26 12:12:55	3392 (0x0D40)
    Raising client SDK event for class NULL, instance NULL, actionType 6l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	2016-04-26 12:12:55	3392 (0x0D40)
    Policy arrived for child program *	execmgr	2016-04-26 12:12:55	3392 (0x0D40)
    Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	2016-04-26 12:12:55	3392 (0x0D40)
    Raising client SDK event for class NULL, instance NULL, actionType 6l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	2016-04-26 12:12:55	3392 (0x0D40)
    Policy arrived for child program *	execmgr	2016-04-26 12:12:55	3392 (0x0D40)
    Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	2016-04-26 12:12:55	3392 (0x0D40)
    Raising client SDK event for class NULL, instance NULL, actionType 6l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	2016-04-26 12:12:55	3392 (0x0D40)
    

    Tuesday, April 26, 2016 10:22 AM
  • Dear Sir,

         "GetSWDistPolicy - Could not find the policy in WMI for advertisement XXX2003E package XXX00006 program * "

        Check these two packages first (XXX2003E, XXX00006), and make sure update the DP at least once. Take a look at this thread please:

        https://social.technet.microsoft.com/Forums/en-US/8245384f-5442-428c-8d51-3cc04c07a12b/could-not-find-the-policy-in-wmi-for-package-xxx00057-program-?forum=configmanagerosd

    Best regards,

    Jimmy 


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, April 27, 2016 1:47 AM
    Moderator
    • XXX00006 is Configuration Manager Client Upgrade which I validate and redistribute it.
    •  XXX2003E is the Windows 7 OS tasksequence which is deployed to the Device Collection.

      I even updated the distribution point (I only have one DP) which did not help.
    • What should I check on the packages?
    • What else could I look at?
    Wednesday, April 27, 2016 5:58 PM
  • We have the same problem here when trying to install a software via tasksquence: SCCM 1602

    No Errors aside of:

    • Could not find the policy in WMI for advertisement ....
    • Fail to initialize TS member info, error 0x87d02004

    The second attempt works but the first always fails, so it can't be a problem with the distribution points not being up to date. Also this problem happens with every advertised tasksequence, so it can't be a problem in the ts either. The datatransfer.log says the download was started and completed into c:\windows\ccm\temp\xx but the folder is empty.

    @Hamnawa, did you find a solution for the problem? Looks like Microsoft doesn't acknowledge this as an error different then the one mentioned in the post from 2013 where the dp was not up to date.



    Wednesday, May 11, 2016 2:33 PM
  • @TS1984asdfasdf, I have not found a solution yet.

    Someone from Microsoft Support should take a look at this issue.

    Sunday, May 15, 2016 1:18 PM
  • Just thinking, could you make sure your client is really healthy? How about installing some apps or updates to ensure this first.
    Monday, May 16, 2016 5:41 AM
  • hae? client healthy? the client works, its just the first attempt at running the deployment that fails everytime.

    @hamnawa, i have opened a ticket at microsoft support. if we find the problem ill make sure to post it here.

    Tuesday, May 17, 2016 7:04 AM
  • We are also having the same issue. Everything else is healthy. We have talked to our TAM, they are not aware of the issue at this point but are digging deeper for us. Will post if I get any useful information.
    Tuesday, May 17, 2016 7:16 AM
  • Any news according this behaviour? We came across exactly the same issue after Upgrading to 1511.
    Friday, June 10, 2016 11:05 AM
  • My organization also just started having this issue.  We also recently upgraded to SCCM 1511.  

    The Task Sequence worked fine before the upgrade.  It has not changed since, nor have the packages.  I've also been through validating the DPs as well.  The TS always executes fine 10 minutes later on the 2d attempt.  

    It appears to potentially be a timing issue looking at the execmgr.log where it notes the "Could not find the policy...", fails with "Fail to initialize TS member info", and a second or so later I'll see "policy arrived" relating to the package in the TS that was indicating prior having problems finding the policy.

    Monday, June 27, 2016 8:19 PM
  • Hi, I stumbled across the answer today.

    I'm in the process of rolling out the new Adobe Suite, (35gb worth of apps) and about 2 months after a 1602 upgrade I decided to put them all in a task sequence which immediately started to fail. I've NEVER had this happen before. This TS would fail immediately as soon as it started and then in 10 minutes on retry would start running, however random applications would fail and I just couldn't understand why.

    I spent two solid days on everything from WMI validation checks to indepth task sequence debugging and consistently had this issue fail. The problem was that my SCCM cache was too small (5gb) in the control panel client settings. Immediately after increasing my cache from 5.gb to 20+ it worked consistently and immediately.

    There is a powershell script you can run to set the cache during the TS and then set it back at the end if you need to revert. I will be doing this tomorrow as I only figured this problem out at the end of the day, but so far so good.

    In my desperation to resolve this issue I saw this thread and thought this might be helpful to you guys.

    Best of luck, its cache...

    • Proposed as answer by Liam Mulligan Friday, July 8, 2016 12:28 PM
    Thursday, July 7, 2016 12:16 PM
  • Confirming today that indeed the cache fixed the issue :)

    Every task sequence that I ran would continuously fail, immediately set the cache and it would work instantly. I ended up setting cache to 50gb with a compliance baseline. Once the cache setting was right, I was able to create a collection, deploy 28 apps to the collection as required (using powershell + csv) and add a group of devices, the application model detected if the apps were already installed and installed 32gb's without a hitch. The task sequence model also worked perfectly without the immediate fail and wait 10 mins errors.

    I was receiving the same errors noted above (policy errors etc). The giveaway was when I switched the TS to "Download all content before starting the task sequence" it finally generated an error "download failed". I immediately knew it was a download issue and not policy related and thought of cache.

    hope this helps somebody, please let me know if it does :)

    regards

    L.Mulligan

    • Proposed as answer by Liam Mulligan Friday, July 8, 2016 12:28 PM
    Friday, July 8, 2016 12:27 PM
  • We've actually opened a support ticket with Microsoft and they have confirmed this to be an open bug. No hotfix is available, and appears to affect both 1511 and 1602.

    "Thank you for your patience while we investigated this issue. During our investigation we actually came across an open bug on this issue. In other words it is a known issue. The issue has been fully investigated. The basic problem is that sometimes PCs receive a parent policy for the Task Sequence before all child policies are received. This is why you see the Task Sequence as available but when you try to run it, it fails and you see the following messages in execmgr.log:

    07-01-2016 13:47:46.617    execmgr    GetSWDistPolicy - Could not find the policy in WMI for advertisement DS120029 package DS100034 program *

    07-01-2016 13:47:46.639    execmgr    Unable to find member policy for [advertisement: DS120029 program: *]

    07-01-2016 13:47:46.639    execmgr    Fail to initialize TS member info, error 0x87d02004"

    Jeff

    Friday, July 15, 2016 3:46 PM
  • was there any update on this issue? Seems to have hit us aswell with 1602 and the latest hotfixes.
    Tuesday, August 2, 2016 2:56 AM
  • The cache fix did not work for us.

    Tested even with SCCM 1606 same.

    Monday, August 8, 2016 4:56 PM
  • Opened a ticket with Microsoft Premier Support and this has been confirmed as an open bug with 1511 and above, so don't kill yourself trying to fix it.
    Friday, August 12, 2016 5:27 PM
  • Yes, we've seen this behavior too, seems timing related and frankly the cache fix makes no sense as it works again if you re-try, there is either room in the cache or not...

    Jack

    Friday, August 12, 2016 6:12 PM
  • In our testing, it seems to impact only Task Sequences (both Application and OS Deployment) with Required deployments
    Wednesday, August 24, 2016 2:08 PM
  • seeing the same thing on 1606 but need to install the role up, will retest later with the very latest flavour.

    Available is always fine, required deployment on rerun it fails then always works on the 10 minute retry. Will do some digging when I get more time.

    Thursday, September 15, 2016 9:18 AM
  • Same here.

    I saw it with 1511 and now with 1606 and the hotfix.  

    My CAS.log shows nothing regarding cache size (or anything) until the second attempt 10 minutes later

    "Not enough space in Cache"

    But like everyone else the second attempt is successful.

    Originally I was thinking 1E Nomad was my issue but nothing in logs to indicate any of that.

    Thursday, September 15, 2016 4:48 PM
  • Just moved to a new 1606 server and getting this same issue. Logs are also showing the same errors as above.

    Unfortunately the cache size fix doesn't seem to make much difference.

    Is there a way to suppress the error balloon for application installs deployed as a task sequence?

    Wednesday, September 21, 2016 8:08 AM
  • Just to add to this thread...

    We too opened up a case with MS a few months ago. They have stated, as above, that it is a known bug. THe reasons as exactly as Jeff states above - Child policy not arriving before/along with parent policy for the TS.

    Microsoft has stated that this WILL BE fixed in 1610. Slated to be released in LATE October (but most likely November).

    Hope it helps.

    Wednesday, September 28, 2016 5:19 PM
  • This is an issue with the product.

    The client downloads policy from the MP using two channels - BITS and raw HTTP. In the past, all policies were downloaded using only a single channel. However, a change was made to "optimize" the policy download to use different channels depending on the policy size. This caused some policies to arrive in a different order. This is normally harmless. But, in the case of task sequence policies, this is harmful because task sequence policies have dependencies.

    The effect is that the main task sequence policy gets downloaded and software center thinks that it is OK to display and run it. But, in reality, the dependent policies have yet to be downloaded, and so it fails. After a few minutes, the dependent policies eventually get downloaded, and the retry succeeds.

    Thursday, September 29, 2016 12:39 AM
  • This is an issue with the product.


    Which versions are affected? Is there a hotfix on the way?

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

    Thursday, September 29, 2016 6:19 AM
  • I was told by the owners that this issue started in the 1511 release.

    I cannot comment on any hotfix. You need to contact support for that.

    • Proposed as answer by gkdrcflyer1 Thursday, December 15, 2016 9:27 PM
    • Unproposed as answer by gkdrcflyer1 Thursday, December 15, 2016 9:27 PM
    Thursday, September 29, 2016 11:05 PM
  • I can confirm we're also seeing this on both the production and non production environments.

    Both environments are running 1606 and am seeing exactly the same symptoms. Task sequence starts then immediately fails with 0x87d02004.

    10 minutes later it just starts up and runs just fine.

    Setting a larger cache does not make a difference (TS is set up to run from Distribution Point Anyway)

    Will log a support case with Microsoft and come back with any updates.


    Monday, February 13, 2017 7:13 PM
  • I can confirm we're also seeing this on both the production and non production environments.

    Both environments are running 1606 and am seeing exactly the same symptoms. Task sequence starts then immediately fails with 0x87d02004.

    10 minutes later it just starts up and runs just fine.

    Setting a larger cache does not make a difference (TS is set up to run from Distribution Point Anyway)

    Will log a support case with Microsoft and come back with any updates.


    Hi,

    I'm experiencing this EXACT issue. Any luck with a response from Microsoft?


    Thursday, February 23, 2017 9:51 PM
  • Is also ConfigMgr 1610 affeced?

    Wednesday, March 15, 2017 10:20 AM
  • We have 1610 and got the problem.

    We deployed a TS on 8 computers, and got the problem for 1 of them.

    

    • Could not find the Policy in WMI for advertisement   xyz
    • OnPolicyActivation - Unable to find member Policy.  Advanced download failed: 0x87d02004
    • Unable to find a member Policy.  Will setup a re-activation

    

    
    • Edited by edrouin Tuesday, March 21, 2017 2:51 PM
    Tuesday, March 21, 2017 2:50 PM
  • Hi All,

    Any news on this issue,

    We're on 1610 and have this same issue

    Cheers


    Thanks Waco

    Tuesday, June 19, 2018 8:01 AM
  • TO CLEAR THE CONTINOUS RUNNING TASK SEQUENCE:

    Cause:

    The dependencies SMSTSMgr.exe , ConfigMgr Task Sequence Agent

    service was not set for ccmexec and winmgmt.

    Solution:

    Adding the dependency for SMSTSMgr.exe

    Run the script for dependency of cmstsmgr to be include both Winmgmt and ccmexec

    # Get Service Details 

    $service = get-service smstsmgr

     

    # Check ServiceDependedOn Array 

    if (($service.ServicesDependedOn).name -notcontains "ccmexec") 

    { 

     write-host "Not present...Configuring Service" 

     start-process sc.exe -ArgumentList "config smstsmgr depend= winmgmt/ccmexec" -wait 

    } 

    else 

    { 

     write-host "Present..Taking no action" 

    }

    # Stop Task Manager process named TaskSequenceManager

    Get-process  

    Go to Task Manager and end task TS Manager, ConfigMgr Task Sequence Agent

    Get-process TSManager.exe | stop-process -force

    Restart SMS Host Agent who will start  ccmexec and make smstsmgr.exe ready for starting again.

    Restart-service -Name “SMS Agent Host”

    When all done,

    sc config smstsmgr depend="/"

    To make TS been able to run again

    Tuesday, July 3, 2018 3:59 AM
  • Hello,

    I know it is an old post ,but i have the exact issue in my environment (CM 1802 )   "OnPolicyActivation - Unable to find member policy. Advanced download failed: 0x87d02004." After 10 min the same deployment pass with no issue.

    In our environment the start time is very critical and i've never saw the issue before the migration (from SCCM 2012 R2 CU4)

    Is there any available WA for that?

    Thanks

    Tuesday, January 8, 2019 3:44 PM
  • Having this issue as well. Fails initially but will run on the next try
    Friday, January 25, 2019 5:17 PM
  • Hey Again,

    Now on CM 1810, WIndows Upgrade TS deployed having this issue.

    Any wa or resolution?

    CHeers


    Thanks Waco

    Tuesday, March 19, 2019 6:39 AM
  • Hi,

    We are on SCCM 1810 and having same issues with required Task sequence. TS would fail first attempt and start after 10 minutes or so..

    Cache on computer has been set to 25 Gb and client is healthy..

    Here are errors from Execmgr.log

    [ABC20382 * ABC00268] OnPolicyActivation - Unable to find member policy. Advanced download failed: 0x87d02004 execmgr 5/28/2019 10:19:36 AM 2804 (0x0AF4)

    [ABC20382 * ABC00268] - Unable to find a member policy. Will setup a re-activate. execmgr 5/28/2019 10:19:36 AM 2804 (0x0AF4)
    Mandatory execution requested for program * and advertisement ABC20382 execmgr 5/28/2019 10:19:36 AM 5884 (0x16FC)
    Creating mandatory request for advert ABC20382, program *, package ABC00268 execmgr 5/28/2019 10:19:36 AM 5884 (0x16FC)
    GetSWDistPolicy - Could not find the policy in WMI for advertisement ABC20382 package ABC00003 program * execmgr 5/28/2019 10:19:36 AM 5884 (0x16FC)
    Unable to find member policy for [advertisement: ABC20382 program: *] execmgr 5/28/2019 10:19:36 AM 5884 (0x16FC)
    Fail to initialize TS member info, error 0x87d02004 execmgr 5/28/2019 10:19:36 AM 5884 (0x16FC)

    Did someone find a solution for this issue yet?

    Thanks

    RJ


    RJ09

    Tuesday, May 28, 2019 3:36 PM
  • We are also impacted by this issue, all of our in-place upgrade task sequences are affected. We're on the latest SCCM v1902. We see this error in the execmgr.log

    [PBC20527 * PBC00C0C] OnPolicyActivation - Unable to find member policy. Advanced download failed: 0x87d02004

    Fail to initialize TS member info, error 0x87d02004

    Child policy does not exist for program *. This program will retry.

    Program * has been tried 0 times, will retry later

    Sometimes it displays an error in Software Center, other times it does not. We have the TS set to download all content locally before starting the TS. I've spent a lot of time troubleshooting this, only to find out it has been a known issue for over 3 years now!

    @Kerwin Medina - Can we an update on when this will be fixed?

    Monday, June 24, 2019 10:09 PM