SCCM Deployment Failed to Resolve Task Sequence Dependencies 0X80040102

Let’s see how you can FIX Failed to Resolve Task Sequence Dependencies 0X80040102. You might encounter a prompt message “Failed to Run Task Sequence” while performing Operating System Deployment with SCCM Task Sequence. This usually happens when the associated Packages, Applications to the task sequence have not been properly distributed to the distribution point or groups.

When the device is booting up from deployed sccm task sequence, You receive the error – This task sequence cannot be run because the program files for ScopeId_E96F0A9E-8055-4B4D-998C-D6262BFF9B6C/ Application_f8557e96-714c-4bc6-b5b8-d1c8038e29f5 cannot be located on a distribution point.

Here you won’t be able to identify which Application it is shown with its CI Unique ID. However, you can use PowerShell to convert an Application CI Unique ID to Display Name. Let’s proceed next to perform troubleshooting.

Issue Summary : Failed to Run Task Sequence

To troubleshoot OSD-related problems, learning to read SMSTS.log is very important. Let’s examine the SMSTS.log to find the problematic package. It’s most important to be aware of the location of the SMSTS log during SCCM OSD, and More you can explore SCCM OSD Task Sequence Troubleshooting Steps by Step Ultimate Guide SMSTS.log.

In this scenario, Task Sequence terminated at the beginning. You will collect the logs at WinPE x:\windows\temp\smstslog\smsts.log. To get the command prompt window, you have to press F8 key. After reviewing the logs, you will clearly see the details –

Here are the highlights Failed to Resolve Task Sequence Dependencies 0X80040102 from the SMSTS.log. You can collect the ApplicationModel: ScopeId_/Application_ to check the reference package to task sequence from SCCM Console.

Content location request for ApplicationModel:ScopeId_E96F0A9E-8055-4B4D-998C-D6262BFF9B6C/Application_f8557e96-714c-4bc6-b5b8-d1c8038e29f5:1 failed. (Code 0x80040102)	TSMBootstrap	02-08-2021 11:59:52	616 (0x0268)
hr, HRESULT=80040102 (..\tspolicy.cpp,3672)	TSMBootstrap	02-08-2021 11:59:52	616 (0x0268)
Failed to resolve application 缐䅢Ǻ	TSMBootstrap	02-08-2021 11:59:52	616 (0x0268)
(*iTSAppReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040102 (..\tspolicy.cpp,4188)	TSMBootstrap	02-08-2021 11:59:52	616 (0x0268)
m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040102 (tsmediawizardcontrol.cpp,1615)	TSMBootstrap	02-08-2021 11:59:52	616 (0x0268)
Failed to resolve selected task sequence dependencies. Code(0x80040102)	TSMBootstrap	02-08-2021 11:59:52	616 (0x0268)
hrReturn, HRESULT=80040102 (tsmediaresolveprogresspage.cpp,445)	TSMBootstrap	02-08-2021 11:59:52	616 (0x0268)
ThreadToResolveAndExecuteTaskSequence failed. Code(0x80040102)	TSMBootstrap	02-08-2021 11:59:52	616 (0x0268)
ThreadToResolveAndExecuteTaskSequence returned code 0x80040102	TSMBootstrap	02-08-2021 11:59:52	1396 (0x0574)
Setting wizard error: This task sequence cannot be run because the program files for ScopeId_E96F0A9E-8055-4B4D-998C-D6262BFF9B6C/ Application_f8557e96-714c-4bc6-b5b8-d1c8038e29f5 cannot be located on a distribution point. For more information, contact your system administrator or helpdesk operator.	TSMBootstrap	02-08-2021 11:59:52	1396 (0x0574)

FIX : Failed to Resolve Task Sequence Dependencies 0X80040102

• Launch SCCM console. Navigate to Software Library > Operating Systems > Task Sequences.
• Select the deployed Task Sequence from the list and select References tab at bottom.

• In Task Sequence References tab, Locate to the Object ID column. Scroll down and check the ScopeId_/Application_, Match with the above shared details. As you can see here it’s identifying “Google Chrome” Software, Application Type.

Note – If you are not able to see the Object ID column. To add the Object ID column, Right-click on a column detail name and Select column.

• Since the above identified Google Chrome Software Type is Application. The next step would be to Navigate to Software Library\Application Management\Applications.
• Find and select the application from the list and Redistribute the application to the distribution point or group.

To avoid issues with the content distribution of SCCM packages. Let’s check how to Redistribute package or application content to Distribution Point.

Once the content distribution status indicates success, Reinitiate the task sequence deployment.

Resources

• SCCM OSD SMSTS Log File Reading Tips | ConfigMgr | MEMCM
• SCCM OSD Task Sequence Troubleshooting Steps by Step Ultimate Guide with SMSTS.log
• SCCM Logs Files | 5 Log File Reading Tips | ConfigMgr
• HTMD SCCM Archieve Posts