Failed to Resolve Task Sequence Dependencies 0X80040102

During OSD, if you see failed to resolve selected task sequence dependencies with error 0x80040102, surely there are packages missing on the SCCM distribution point. Let me show you how to fix this issue.

While performing operating system deployment, the task sequence fails if any of it’s dependencies are missing on the SCCM distribution point server. It usually fails and also shows the package ID that’s missing on the distribution point.

When you know a package is missing on a distribution point, it is easy to re-distribute the failed package from SCCM console. However when you don’t see the package ID, you might have to do some extra work to find out the package name.

Failed to Resolve Task Sequence Dependencies 0X80040102

When the SCCM task sequence fails with error 0x80040102, you don’t see any package ID for failed deployment. What you see is the Application CI Unique ID. The error 0x80040102 can be found when you examine the smsts.log file.

There is a way to convert an Application CI Unique ID to Display Name. I had used it long back but now I don’t remember the commands. I will update the post once I find it.

Here is the error that you see on the screen :-

Failed to Run Task Sequence

This task sequence cannot be run because the program files for ScopeId_AA5DBF4A-0002-4D92-BD93-8972BED9C201/Application_64aad461-0a72-4a4a-bd9c-644331b0b4a2 cannot be located on distribution point.

When you examine the smsts.log file, you will notice the following lines.

• Failed to resolve application
• Failed to resolve selected task sequence dependencies. Code(0x80040102)
• Content location request for application model:ScopeId_AA5DBF4A-0002-4D92-BD93-8972BED9C201/Application_64aad461-0a72-4a4a-bd9c-644331b0b4a2 failed. Code 0x80040102.

Now that you know one of the package that is part of task sequence is missing, it is easy to find out that package.

• In the SCCM console go to Software Library > Operating Systems > Task Sequences.
• Select the Task Sequence and at the bottom click References tab.
• Add the Object ID column if you don’t see it.
• Look for the exact ScopeId/Application_ and make a note of Software (in my case it’s .Net Framework 4.7.2).
• Redistribute the application to distribution point.

Test the OSD now and you shouldn’t see the same error again.