none
Applications failing to install during task sequence RRS feed

  • Question

  • Hello All:

    I am having a major issue deploying applications through task sequence. The errors in the smsts.log are useless and every single one of my 7 applications I have assigned to the task sequence fail with the same error. Here is a snippet...

    Policy Evaluation failed, hr=0x87d00269 InstallApplication 12/5/2013 2:24:36 PM 1876 (0x0754)Setting TSEnv variable 'SMSTSAppPolicyEvaluationJobID__ScopeId_A8C9B482-A47E-433C-914C-DEDEE5465DFD/Application_72ba1d7c-710f-48e5-9295-bcdc07f5cdca'='' InstallApplication 12/5/2013 2:24:36 PM 1876 (0x0754)EvaluationJob complete InstallApplication 12/5/2013 2:24:36 PM 1876 (0x0754)MP list missing in WMI, sending message to location service to retrieve MP list and retrying. InstallApplication 12/5/2013 2:24:36 PM 1876 (0x0754)m_hResult, HRESULT=87d00269 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,1065) InstallApplication 12/5/2013 2:25:50 PM 1876 (0x0754)Step 4 out of 7 complete InstallApplication 12/5/2013 2:25:50 PM 1876 (0x0754)Install application action failed: 'GoToMeeting'. Error Code 0x87d00269 InstallApplication 12/5/2013 2:25:50 PM 1876 (0x0754)

    The OS deploys, the Config Mgr client deploys, everything else appears to work except the applications.

    All applications are silent installers that deploy perfectly through regular deployment.

    Here is a link to my smsts.log - http://sdrv.ms/1kg8fiP

    Any help on this is greatly appreciated.

    Brad


    -Brad



    Thursday, December 5, 2013 8:57 PM

Answers

  • I got this working by adding SMSMP=w2srvcm01.lab.lcl to the installation properties of my config/windows setup ts step. It also resolved the issue I had of auto deploying the client to workgroup machines. I can't believe something so simple was so hard to find. Credit goes to Jason Sandys.

    The article as a whole didn't really appy directly to my issue but the last paragraph did the trick.

    http://blogs.catapultsystems.com/jsandys/archive/2012/08/30/configmgr-2012-application-installation-failures.aspx

    • Marked as answer by Brad M Laszlo Wednesday, January 29, 2014 1:45 PM
    Friday, January 24, 2014 7:23 PM

All replies

  • What version are you running (RTM/SP1/R2)?

    Jason | http://blog.configmgrftw.com

    Thursday, December 5, 2013 9:52 PM
  • We are using R2

    -Brad

    Friday, December 6, 2013 1:40 PM
  • Having the exact same issue here - any help would be great with this...

    For more SCCM tips and tricks please visit me at my SCCM Blog The Pheasant Plucker

    Monday, December 9, 2013 9:55 AM
  • Anybody please? This is a major PITA for us.

    -Brad

    Tuesday, December 10, 2013 6:21 PM
  • 0x87d00269 = "Required MP not found" ??

    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Tuesday, December 10, 2013 8:47 PM
  • Is that a question or...? If you're asking if we have a management point obviously the answer is yes. I am not sure how to even troubleshoot this.

    -Brad

    Tuesday, December 10, 2013 8:59 PM
  • No, Don is pointing out the meaning of that error code (which is from what you originally posted).

    Jason | http://blog.configmgrftw.com

    Tuesday, December 10, 2013 9:22 PM
  • OK - he had added a few question marks after... I see the error, I just have no idea whatsoever why it doesn't see our MP or how to even begin diagnosing and resolving this.

    -Brad

    Tuesday, December 10, 2013 9:31 PM
  • If it was a management point issue surely it wouldn't deploy via the conventional method?!

    I too have been trying to diagnose the issue for a while now and can't find anything - this is the closest thrad I've found and it still appears to be in its infancy.


    For more SCCM tips and tricks please visit me at my SCCM Blog The Pheasant Plucker

    • Proposed as answer by craigrs Tuesday, June 16, 2015 8:21 PM
    Thursday, December 12, 2013 9:21 AM
  • No one said it was an MP issue -- the error message indicates that it's a client (the target of the task sequence) issue: specifically that the client cannot find the MP. The error code is pretty unambiguous however, without more of the log file (logs files are about context, not single out-of-context lines), it's hard to say anything else.

    Note also that applications during task sequences have been quite problematic since RTM -- it's gotten better with SP1 and R2, but there are still issues.


    Jason | http://blog.configmgrftw.com

    Thursday, December 12, 2013 2:40 PM
  • Jason,

    The log file is not out of context at all - I have included the ENTIRE log file in my first post in this thread. Also, as stated earlier, I am using R2.


    -Brad


    Thursday, December 12, 2013 3:47 PM
  • Sorry, you are correct -- there are just no carriage returns so it looks like a single line got pasted. However, generally for troubleshooting any issues within a task sequence, smsts.log in the primary log to review.


    Jason | http://blog.configmgrftw.com

    Thursday, December 12, 2013 5:06 PM
  • Here is a link to my smsts.log - http://sdrv.ms/1kg8fiP

    Jason,

    Thanks for your replies. Yes, I've posted a quick snippet of the log showing what I thought was the error, but I also provided a link to the entire smsts.log for review. I quoted my original post for this question here...


    -Brad

    Thursday, December 12, 2013 7:23 PM
  • Sorry about that previous post, I probably got distracted by a cat meme or something shiny ;)

    I took at look at the full smsts logfile, and it seems to me that the detection method for the appmodel apps is failing. we aren't doing appmodel via TS as yet, so I don't know what "normal/expected" looks like when invoked via TS.

    but it looks to me, that the detection methods is returning 0x87d00215 "app failed to evaluate" (which I'd expect at the time of a refresh), but it then returns 0x87d00269 "required MP not found", which seems very out-of-context to me.

    are there appenforce.log and other appmodel logs that coincide with this smsts.log?

    I fear I'm misunderstanding what this log is saying, the language/terminology of DCM is still foreign to me.

    does "app failed to evaluate" mean, "the app detection markers were not found" (i.e. the app is not present), or, does it mean "the methods crashed so cannot determine if the app is present or absent" ?

    if all of this is based on generic DCM concepts, then we should be looking for a condition, and getting a present/absent or true/false or something plain like that.


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)


    • Edited by DonPick Thursday, December 12, 2013 8:45 PM
    Thursday, December 12, 2013 8:44 PM
  • Hey Brad,

    Did you ever get this sorted out? Having the same issue.

    Thanks,

    Mike

    Friday, January 24, 2014 2:19 PM
  • Mike,

    No, this was never resolved... I spent days tweaking this or changing that ort modifying this and no joy. It makes absolutely no sense at all. I had to put this task aside and work on something else for the time being or I would drive myself absolutely nuts. I considered opening a ticket with Microsoft, but I didn't want to burn through my 5-pack with something that seems so trivial. If anyone else has any suggestions, it'd be appreciated


    -Brad

    Friday, January 24, 2014 2:24 PM
  • I got this working by adding SMSMP=w2srvcm01.lab.lcl to the installation properties of my config/windows setup ts step. It also resolved the issue I had of auto deploying the client to workgroup machines. I can't believe something so simple was so hard to find. Credit goes to Jason Sandys.

    The article as a whole didn't really appy directly to my issue but the last paragraph did the trick.

    http://blogs.catapultsystems.com/jsandys/archive/2012/08/30/configmgr-2012-application-installation-failures.aspx

    • Marked as answer by Brad M Laszlo Wednesday, January 29, 2014 1:45 PM
    Friday, January 24, 2014 7:23 PM
  • If this works, I will give you a big fat digital kiss!!! I will post back soon.

    -Brad

    Friday, January 24, 2014 8:23 PM
  • I got this working by adding SMSMP=w2srvcm01.lab.lcl to the installation properties of my config/windows setup ts step. It also resolved the issue I had of auto deploying the client to workgroup machines. I can't believe something so simple was so hard to find. Credit goes to Jason Sandys.

    The article as a whole didn't really appy directly to my issue but the last paragraph did the trick.

    http://blogs.catapultsystems.com/jsandys/archive/2012/08/30/configmgr-2012-application-installation-failures.aspx

    Amazing, this worked! I also had an issue deploying the client to workgroup machines and it resolved that as well. Thanks!

    -Brad

    Wednesday, January 29, 2014 1:46 PM
  • What did you put in the SMSMP=?  Is this the domain name?

    -Tim

    Tuesday, June 2, 2015 10:17 PM
  • It's the FQDN of your Management Point Server.
    Wednesday, June 3, 2015 12:19 PM
  • Hi Brad,

    I think you owe Jason that digital kiss.


    MikeT


    • Edited by drmiket Tuesday, June 9, 2015 1:01 PM
    Tuesday, June 9, 2015 1:01 PM
  • J-Sizzle for the win!

    Matteo Barreo

    Tuesday, November 26, 2019 10:28 PM