http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2777615&SiteID=17
Error when boot Winpe: Failed to resolve selected task sequence dependencies. Code(0x80040102)
I can boot with the image, the DHCP is working and with the F8 option I can connect to the DP to copy the smsts.log.
But if I do not start the F8 console the Image will loading and after a while it just reboots.
Annalysing the smsts.log shows that the MP will properly detected but no DP is discovered:
Failed to resolve selected task sequence dependencies. Code(0x80040102)
Reason that may causes this problem:
A boot image asks the MP where the DPs are. But it doesn't ask about DPs in general -- it asks about DPs that have a particular package. So you may get a different answer about what DPs are present depending on what package is being asked about. If you have not replicated one of your packages to a DP, then you could get the above error where no DPs (i.e., no DPs containing that package) are found. In this case, the package in question is ZMH0001A.
This problem could also occur if the package has been updated and has a new version, but the DPs have not yet received the new version. You can use "Update Distribution Points" and then check the package status to make sure the new version has gotten out to the DPs. Then try your task sequence again.
In my case, a software package has been created from task sequence but it has not been add to any distribution point. To fix it:
go to Software distribution ->packages->right click "microsoft configuration manager client upgrade 4.0 all->add it to both distribution point.
Subscribe to:
Post Comments (Atom)
Posts
3 comments:
how does one determine WHAT specific dependency was not able to be located?
You can determine which dependency wasn't located by looking at the full line in the SMSTSlog, for example.
Failed to find CCM_SoftwareDistribution object for AdvertID="ATL200E7", PackageID="ATL000AB", ProgramID="*"
Go to SCCM->Computer Management->Advertisements, then use the "Look For" search box at the top to search for the Advertisement ID, i.e. "ATL200E7".
Normally you just need to update the distribution point because of some changes you made.
You can determine which dependency wasn't located by looking at the full line in the SMSTSlog, for example.
Failed to find CCM_SoftwareDistribution object for AdvertID="ATL200E7", PackageID="ATL000AB", ProgramID="*"
Go to SCCM->Computer Management->Advertisements, then use the "Look For" search box at the top to search for the Advertisement ID, i.e. "ATL200E7".
Normally you just need to update the distribution point because of some changes you made.
Post a Comment