"Failed to Run Task Sequence" in OSD

[lindevang]

The Setup

Very simple: One Primary Site server named server132 that is also my Distribution Point in the site BAL .

 

The Problem

I’m having some strange ”Failed to Run Task Sequence” errors when starting OSD Task Sequences.

Following part is written in the smsts.log file:

 

<![LOG[Found location: http://SERVER132.nclan.netcompany.dk/SMS_DP_SMSPKG$/BAL00002]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="1" thread="1048" file="libsmsmessaging.cpp:3761">
<![LOG[Local=0]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="1" thread="1048" file="libsmsmessaging.cpp:3798">
<![LOG[Processing 1 locations.]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="1" thread="1048" file="resolvesource.cpp:2029">
<![LOG[Not processing remote location:]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="1" thread="1048" file="resolvesource.cpp:2076">
<![LOG[ Flags: 01000000]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="1" thread="1048" file="resolvesource.cpp:2077">
<![LOG[ URLs : 1]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="1" thread="1048" file="resolvesource.cpp:2078">
<![LOG[ SMB : ]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="1" thread="1048" file="resolvesource.cpp:2079">
<![LOG[ MCS : ]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="1" thread="1048" file="resolvesource.cpp:2080">
<![LOG[LocationsList.size() > 0, HRESULT=80040102 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,2139)]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="0" thread="1048" file="resolvesource.cpp:2139">
<![LOG[FALSE, HRESULT=80040102 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,1815)]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="0" thread="1048" file="tspolicy.cpp:1815">
<![LOG[Content location request for BAL00002:2 failed. (Code 0x80040102)]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="3" thread="1048" file="tspolicy.cpp:1815">
<![LOG[hr, HRESULT=80040102 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,2578)]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="0" thread="1048" file="tspolicy.cpp:2578">
<![LOG[Failed to resolve PackageID=]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="3" thread="1048" file="tspolicy.cpp:2578">
<![LOG[(*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040102 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,3341)]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="0" thread="1048" file="tspolicy.cpp:3341">
<![LOG[m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040102 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1480)]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="0" thread="1048" file="tsmediawizardcontrol.cpp:1480">
<![LOG[Failed to resolve selected task sequence dependencies. Code(0x80040102)]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="3" thread="1048" file="tsmediawizardcontrol.cpp:1480">
<![LOG[hrReturn, HRESULT=80040102 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediaresolveprogresspage.cpp,408)]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="0" thread="1048" file="tsmediaresolveprogresspage.cpp:408">
<![LOG[ThreadToResolveAndExecuteTaskSequence failed. Code(0x80040102)]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="3" thread="1048" file="tsmediaresolveprogresspage.cpp:408">
<![LOG[ThreadToResolveAndExecuteTaskSequence returned code 0x80040102]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="1" thread="260" file="tsmediaresolveprogresspage.cpp:221">
<![LOG[setting wizard error: This task sequence cannot be run because the program files for BAL00002 cannot be located on a distribution point. For more information, contact your system administrator or helpdesk operator.]LOG]!><time="11:34:35.336-120" date="07-26-2012" component="TSPxe" context="" type="0" thread="260" file="tsmediawizardcontrol.cpp:1504">

 

I have googled 0x80040102 and every solution points that the distribution of package is not completed or that the option “Copy the content in this package to a package share on distribution points” in the package is not checked.

 

The package BAL00002 is distributed to the DP.

Screenshot.

 

BAL00002 is the Configuration Manager Client Package and the “Copy the content”-option is greyed out so I can't do anything about that.

Screenshot.

 

I’ve then copied the content of Configuration Manager Client Package and created a new Package, which gets the ID BAL00007, distributed it to my DP and checked the “Copy content” property. I also have changed the Configuration Manager Client Package in my OSD Task Sequence to BAL00007.

 

Now I get the exact same “Failed to Run Task Sequence” but with BAL0004 instead. I suppose that the Task Sequence loads in a name order.

 

BAL00004 is Boot image (x64) and it is also distributed.

 

Please help!

[Iroqouiz]

Have you set up boundaries and boundary groups and made sure you've added your server in the Content location box?

 

[Rocket Man]

This is because you have not made a copy of the configuration manager client...the default one can not be edited nor can it be used to be deployed...as a matter of fact it serves no purpose really at all, only other than been the first package to be distributed to a newly created remote DP, which it can not be removed from either.

 

 

in the snippet above you can see the default client package and the created one. the manually created on should have 5.0 All after it and this is the one you use when deploying

 

How did you copy the original client package did you create a pacakge from definition??

 

 

You also need to distribute both boot.wims, the x86 and x64 regardless whether you are using x86 or x64 OS version

 

Rocket Man

[lindevang]

Iroquiz> Thank you man! It works like a charm after setting up the boundary groups correct

 

Rocket Man> I copied the content of the original folder to a new folder and created the package.