Jump to content


burnzdog

SCCM2012 task sequence fails. Error: Failed to run task sequence (0x80004005)

Recommended Posts

HI all,

Recently migrated to SCCM 2012. All task sequences have been running without a problem but just today all task sequences fail promptly when choosing the task through the sccm boot option screen.

 

(0x80004005) An error occurred while resolving dependencies

 

I have recreated a new task and chose an existing image and same problem occurs. I have also readvertised the exisiting tasks but no joy.

Any advice appreciated as im still getting to grips with this new version.

Share this post


Link to post
Share on other sites

Below are the locations the log file will be in depending on what stage the TS is at:

 

 

During OS Deployment

 

Before your hard drive is formatted and partitioned

X:\windows\temp\smstslog\

 

After your hard drive is partitioned formatted

X:\smstslog\ and then is in C:\_SMSTaskSequence\logs\smstslog\

 

Within Windows

Within Windows before the SCCM agent is installed:

C:\_SMSTaskSequence\logs\smstslog\

 

Within Windows after the SCCM agent installed:

C:\windows\system32\ccm\logs\smstslog\

 

When the Task Sequence completes on a x86

C:\windows\system32\ccm\logs\

 

For x64 Systems

C:\windows\SysWOW64\ccm\logs\

 

You will need to enable your boot.wim with f8 support to retrieve the log if it bombs out before apply OS stage so that you can bring up the command prompt and copy the log to a share on the network.

Share this post


Link to post
Share on other sites

<![LOG[CLibSMSMessageWinHttpTransport::Send: URL:server.local:80 CCM_POST /ccm_system/request]LOG]!><time="14:28:08.791-60" date="07-15-2013" component="TSPxe" context="" type="1" thread="1040" file="libsmsmessaging.cpp:8621">
<![LOG[Request was succesful.]LOG]!><time="14:28:08.807-60" date="07-15-2013" component="TSPxe" context="" type="0" thread="1040" file="libsmsmessaging.cpp:8956">
<![LOG[reply from server is 'NoReply']LOG]!><time="14:28:08.807-60" date="07-15-2013" component="TSPxe" context="" type="3" thread="1040" file="libsmsmessaging.cpp:2048">
<![LOG[DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,3489)]LOG]!><time="14:28:08.807-60" date="07-15-2013" component="TSPxe" context="" type="0" thread="1040" file="libsmsmessaging.cpp:3489">
<![LOG[ContentLocations.RequestContentLocations(), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9281)]LOG]!><time="14:28:08.807-60" date="07-15-2013" component="TSPxe" context="" type="0" thread="1040" file="libsmsmessaging.cpp:9281">
<![LOG[content location request failed]LOG]!><time="14:28:08.807-60" date="07-15-2013" component="TSPxe" context="" type="3" thread="1040" file="libsmsmessaging.cpp:9281">

Share this post


Link to post
Share on other sites

content location request failed

 

 

verify that you've configured the network access account with the correct password, that you can ping the FQDN of the managent point and that the content it's referring to has actually been distributed to your dp's

Share this post


Link to post
Share on other sites

![LOG[Content location request failed for ESC00042:2. (Code 0x80004005)]LOG]!><time="14:28:08.807-60" date="07-15-2013" component="TSPxe" context="" type="3" thread="1040" file="resolvesource.cpp:2021">

<![LOG[FALSE, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,1863)]LOG]!><time="14:28:08.807-60" date="07-15-2013" component="TSPxe" context="" type="0" thread="1040" file="tspolicy.cpp:1863">

<![LOG[Content location request for ESC00042:2 failed. (Code 0x80004005)]LOG]!><time="14:28:08.807-60" date="07-15-2013" component="TSPxe" context="" type="3" thread="1040" file="tspolicy.cpp:1863">

 

 

 

check that package, is the second version of it really on the dp?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.