I’ve booted off a USB key and selected the Task Sequence I want to run but I then get a screen titled “Failed to Run Task Sequence” which states:
This task sequence cannot be run because the program files for <package_ID> are inaccessible on the distribution point. Please make sure the the packages are available, and the distribution points are accessible, and the appropriate network access account is configured if needed. For more information, please contact your system administrator or helpdesk operator.
Click Finish to reboot the computer.“
Take a look in the “X:\Windows\Temp\SMSTSLog\smsts.log” which will show the following lines:
dwErr, HRESULT=80070037 (e:\nts_sms_fre\sms\framework\tscore\tsconnection.cpp,517)
Failed to connect to "\\<dp_fqdn>\SMSPKGC$\<package_ID>" (55)
!slistSMBPaths.empty(), HRESULT=80040103 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2163)
FALSE, HRESULT=80040103 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,1635)
Content location request for <package_name>:2 failed. (Code 0x80040103)
pTSPolicyManager->GetContentLocations( m_sPackageID, m_lSourceVersion, m_dwContentSourceFlags, slistContentLocations, slistHttpContentLocations, slistMulticastContentLocations, m_dwContentPackageFlags ), HRESULT=80040103 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2330)
(*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040103 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2862)
m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040103 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1208)
Failed to resolve selected task sequence dependencies. Code(0x80040103)
hrReturn, HRESULT=80040103 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediaresolveprogresspage.cpp,408)
ThreadToResolveAndExecuteTaskSequence failed. Code(0x80040103)
ThreadToResolveAndExecuteTaskSequence returned code 0x80040103
In this case the Package was being hosted on a Branch Distribution Point (BDP). Looking under “Package Status” for the affected Package the BDP was not listed.
Looking in “PeerDPAgent.log” showed the following for the package:
Package <package_name> in state 'HostingIncomplete'.
Removing the Package from the BDP and re-adding it resolved the issue (after doing this the “PeerDPAgent.log” showed “Package <package_name> in state ‘Succeeded’.“)