SCCM OSD - Failed to Run Task Sequence (0x80004005)
Hi Niall,
Thank you for the response and info.
I have pasted the smsts.log below of where it is failing. The content location request for BOS00348:3 is my package for the x64 Boot Image. I have distributed the boot image successfully. Any ideas?
October 23rd, 2012 10:21am
AFAIK this error 0x80004005 is quite a generic or common error. Looking from your log, it cant resolve some dependencies.
Few things you can try:
1. Check if all the dependencies that contain packages on the TS are available on your DP e.g. your MDT toolkit if you're using one, etc.
2. Failing that, I'd normally recreate the TS (clean start).
Let us know
Free Windows Admin Tool Kit Click here and download it now
October 23rd, 2012 6:34pm
Hi xmen11:
I had recreated one Task Sequence with only the SCCM WinPe Boot Image and a Reboot task and I am still getting the same error. Would a reboot of the SCCM server maybe resolve this issue?
October 23rd, 2012 9:00pm
Reboot may not do much, but feel free to try, at least it will clear few other things up. Have you checked all the packages in your TS whether they are all available from your DP? because your issue seems to lean towards that. You can also try updating
them on the DP to make sure you get all the latest update in case there has been any changes in your packages. Also, can you tell me if you have the TS advertised to download or run from DP? Multicast or unicast?
Free Windows Admin Tool Kit Click here and download it now
October 23rd, 2012 9:07pm
Reboot may not do much, but feel free to try, at least it will clear few other things up. Have you checked all the packages in your TS whether they are all available from your DP? because your issue seems to lean towards that. You can also try updating
them on the DP to make sure you get all the latest update in case there has been any changes in your packages. Also, can you tell me if you have the TS advertised to download or run from DP? Multicast or unicast?
October 23rd, 2012 9:07pm
We do not have multicast enabled. so we are using unicast. I have checked all of the packages in my TS and they are available from my DP. As a test, I only created on TS that only has the boot image a reboot and I am still getting this error.
Free Windows Admin Tool Kit Click here and download it now
October 23rd, 2012 10:22pm
you might want to create a TS with more than just a reboot. Can you try creating a basic standard Build TS with OS package from scratch? Also, can you confirm if the failure takes place when it's "resolving policy.... " ?
October 24th, 2012 3:27am
I think you should refresh that package on your DP.
Free Windows Admin Tool Kit Click here and download it now
October 24th, 2012 4:49am
Hi Everyone:
Thank you for all of your replies. We checked boudaries and redistributed of the packages in our Task Sequence. We had seen several errors with SQL under the Component Status. We restarted the SMS Executive service and this resolved the
issue.
October 25th, 2012 11:06pm
Hi Everyone:
Thank you for all of your replies. We checked boudaries and redistributed of the packages in our Task Sequence. We had seen several errors with SQL under the Component Status. We restarted the SMS Executive service and this resolved the
issue.
Free Windows Admin Tool Kit Click here and download it now
October 25th, 2012 11:06pm
Aside from refreshing the boot images and restarting the WDS service, I would check your boundaries and make sure that your client is within a configured boundary that does not overlap with any others. I've seen content location go awry before due
to boundary issues.
October 28th, 2012 8:08am
I am booting up from my SCCM 2007 - WinPE CD and after I select the Task Sequence Advertisement, it is showing the the following error:
Failed to Run Task Sequence
An error occurred while resolving dependencies for the selected task sequence (0x80004005).
My OSD Task Sequence was working correctly before this, however I had mistakingly opened the properties of the Task Sequence> Advanced> and unchecked the Use a Boot Image.
I have deleted the Boot Image (x64) that was there and re-added it, and then recreated a Boot Media ISO from the Task Sequence, however I am still receiving the same error.
Any ideas to how I can resolve this issue?
Free Windows Admin Tool Kit Click here and download it now
October 28th, 2012 7:17pm
what does your smsts.log file say about the missing dependancies ? when you added the boot image back did you remember to update it to the dps
have you verified that all packages referenced in the task sequence are present on distribution points ? the smsts.log file on the client will reveal what package(s) are missing.
Step by Step ConfigMgr 2007
Guides | Step by Step ConfigMgr 2012
Guides | I'm on Twitter > ncbrady
October 29th, 2012 2:55am