Problem
When PXE booting and deploying a task sequence you receive the error “Failed to resolve selected task sequence dependencies” and no dependency or package IDs are displayed.
Solution
1. Press F8 when in the WinPE environment to open the command prompt – Click here if you have not enabled the command support console.
2. You can view the SMSTS.log file on the live system, or move it to another machine to interrogate. To open the SMSTS.log which is responsible for deployment and task sequence log events type notepad X:\Windows\Temp\SMSTS\SMSTS.log (the task sequence dependency check happens prior to any formatting of the HDD, hence the location of the log file). At this stage you can also plug in a USB drive and copy/save the log onto it.
Image may be NSFW.
Clik here to view.
3. Open the log file with the Configuration Manager Trace Log Tool aka CMTrace.exe, this will make it a lot easier to view and find the offending errors. If you do not have CMTrace, you can grab it from the SCCM media under SMSSETUP\TOOLS. It’s a single executable so can be copied and moved around as necessary.
Image may be NSFW.
Clik here to view.
4. Near the bottom of the log file you should observe similar errors:
Failed to find CCM_ApplicationCIAssignment object for AdvertID=”12003A”, ModelName=”ScopeId_59CA012F-1C99-45CD-9184/Application_64ff713e-87d1-40dc-8d24-16961ccff5bb”
Failed to resolve selected task sequence dependencies. Code(0×80040104)
ThreadToResolveAndExecuteTaskSequence failed. Code(0×80040104)
The part we’re interested in is the second part of the ScopeId, in this case: Application_64ff713e-87d1-40dc-8d24-16961ccff5bb. To find out which application this refers to open the System Center 2012 configuration manager console. Browse to Software Library, Operating Systems, Task Sequences and select the required task sequence. At the bottom choose “References”, this will show you all applications assigned to the task sequence and their Object IDs. Match this up with the error found from the SMSTS.log.
Image may be NSFW.
Clik here to view.
In my case the offending application was Sage Accounts 2014. Things to check:
- Make sure the application has been distribution to the required distribution point(s).
- Try removing it from the distribution point(s) and re-distributing.
- If the above fails, simply remove the application from the task sequence and re-add it (this was my issue!).
The post SCCM 2012 – Failed to Resolve Selected Task Sequence Dependencies appeared first on The Sysadmins.
