Jump to content


  • 0
Zebwen

Task Sequence Failure on Downloading Updates: 0x80004005

Asked by Zebwen

Question

Zebwen Newbie

Zebwen

Posted
Posted

Hi all! First post so I apologise if I miss important stuff!

 

I am having an issue with my deployment of Windows 7 (this has previously worked correctly, although I haven't used it in a couple of months, I am now trying to set it all up for mass deployment). I'll start with a bit of background, and what I have done so far to try and correct this issue:

  • Server is Windows Server Standard 2008 R2.
  • SCCM 2007 R3.
  • Issue first manifested as task sequence freezing at "Downloading Updates 0% Complete" and not progressing any further.
  • After some google-fu I noticed there was a hotfix I had not yet applied (KB2509007), although there was one hotfix that WAS applied (KB977384).
  • Went through steps to add the new hotfix, installed to server and added to task sequence properties, my ConfigMgr installation properties now reads:
    Patch="C:\_SMSTaskSequence\OSD\EQW0006F\i386\hotfix\KB977384\sccm2007ac-sp2-kb977384-x86-enu.msp";"C:\_SMSTaskSequence\OSD\EQW0006F\i386\hotfix\KB2509007\sccm2007ac-sp2-kb2509007-x86-enu.msp" SMSCACHESIZE=8000
  • Next install of task sequence, I actually get an error (0x80004005) at the same point it was previously freezing at 0%. The new patch is installing correctly and SCCM client version is now: 4.00.6487.2188
  • Decided ro re-capture a reference machine. New capture is sysprepped and tested, new image without updates being applied in the TS works correctly.
  • Further google-fu suggests this could be permissions, I check (and re-flood) permissions on updates DIR and Share, they were (but now definitely ARE) correct.
  • Task sequence still fails.
  • Another suggestion was to remove the KMS code from task sequence, tried this but TS still fails.
  • Checked boundaries, but they are the same as they have always been (only one, AD site).
  • Tried one last suggestion which was adding a reboot event before the updates event. Tried this, reboot occurs as expected, TS still fails as before when attempting updates.

Here is an excerpt from the smsts.log on a machine after the TS fails:

 

Set a local default variable SMSInstallUpdateTarget TSManager 09/01/2013 16:47:06 252 (0x00FC)
Set a global environment variable _SMSTSLogPath=C:\WINDOWS\system32\CCM\Logs\SMSTSLog TSManager 09/01/2013 16:47:06 252 (0x00FC)
Expand a string: TSInstallSWUpdate.exe /target:%SMSInstallUpdateTarget% TSManager 09/01/2013 16:47:06 252 (0x00FC)
Expand a string: TSManager 09/01/2013 16:47:06 252 (0x00FC)
Command line for extension .exe is "%1" %* TSManager 09/01/2013 16:47:06 252 (0x00FC)
Set command line: TSInstallSWUpdate.exe /target:%SMSInstallUpdateTarget% TSManager 09/01/2013 16:47:06 252 (0x00FC)
Start executing the command line: TSInstallSWUpdate.exe /target:%SMSInstallUpdateTarget% TSManager 09/01/2013 16:47:06 252 (0x00FC)
!--------------------------------------------------------------------------------------------! TSManager 09/01/2013 16:47:06 252 (0x00FC)
Expand a string: FullOS TSManager 09/01/2013 16:47:06 252 (0x00FC)
Executing command line: TSInstallSWUpdate.exe /target:%SMSInstallUpdateTarget% TSManager 09/01/2013 16:47:06 252 (0x00FC)
=======================[ OSDInstallSWUpdate.exe ] ======================= InstallSWUpdate 09/01/2013 16:47:06 2964 (0x0B94)
Running "TSInstallSWUpdate.exe" /target:All InstallSWUpdate 09/01/2013 16:47:06 2964 (0x0B94)
(spBuf.size() > 0), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\installswupdate\main.cpp,140) InstallSWUpdate 09/01/2013 16:47:06 2964 (0x0B94)
Updates paused cookie is null InstallSWUpdate 09/01/2013 16:47:06 2964 (0x0B94)
GetPausedCookie(ulCookie), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\installswupdate\main.cpp,277) InstallSWUpdate 09/01/2013 16:47:06 2964 (0x0B94)
Setting TSEnv variable SMSTSInstallUpdateJobGUID= InstallSWUpdate 09/01/2013 16:47:06 2964 (0x0B94)
Process(pInstallUpdate, tType), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\installswupdate\main.cpp,349) InstallSWUpdate 09/01/2013 16:47:06 2964 (0x0B94)
Process completed with exit code 2147500037 TSManager 09/01/2013 16:47:06 252 (0x00FC)
!--------------------------------------------------------------------------------------------! TSManager 09/01/2013 16:47:06 252 (0x00FC)
Failed to run the action: Install Software Updates.
Unspecified error (Error: 80004005; Source: Windows) TSManager 09/01/2013 16:47:06 252 (0x00FC)
Sending status message . . . TSManager 09/01/2013 16:47:06 252 (0x00FC)
Send a task execution status message SMS_TSExecution_ActionFailError TSManager 09/01/2013 16:47:06 252 (0x00FC)
MP server HYPNOS.COMPANY.COM and port 80. SSL=false. CRL=false. TSManager 09/01/2013 16:47:06 252 (0x00FC)
Site code: EQW TSManager 09/01/2013 16:47:06 252 (0x00FC)
Client machine name: MININT-L7QPTIN TSManager 09/01/2013 16:47:06 252 (0x00FC)
Client Identity: GUID:08537e34-50e4-443c-a09e-88c4782fc46d TSManager 09/01/2013 16:47:06 252 (0x00FC)
Advertisement ID: EQW2015E TSManager 09/01/2013 16:47:06 252 (0x00FC)
Package ID: EQW00149 TSManager 09/01/2013 16:47:06 252 (0x00FC)
Sending StatusMessage TSManager 09/01/2013 16:47:06 252 (0x00FC)
Formatted header: TSManager 09/01/2013 16:47:06 252 (0x00FC)
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>bcf455e3-b1a8-4144-bd43-6ac27a2315ec</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2013-01-09T16:47:06Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="3302"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
TSManager 09/01/2013 16:47:06 252 (0x00FC)
CLibSMSMessageWinHttpTransport::Send: URL: HYPNOS.COMPANY.COM:80 CCM_POST /ccm_system/request TSManager 09/01/2013 16:47:06 252 (0x00FC)
The request has succeeded. 200 OK TSManager 09/01/2013 16:47:06 252 (0x00FC)
Set a global environment variable _SMSTSLastActionRetCode=-2147467259 TSManager 09/01/2013 16:47:06 252 (0x00FC)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 09/01/2013 16:47:06 252 (0x00FC)
Clear local default environment TSManager 09/01/2013 16:47:06 252 (0x00FC)
Let the parent group (Install Software) decides whether to continue execution TSManager 09/01/2013 16:47:06 252 (0x00FC)
Let the parent group (Setup Operating System) decide whether to continue execution TSManager 09/01/2013 16:47:06 252 (0x00FC)
The execution of the group (Setup Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 09/01/2013 16:47:06 252 (0x00FC)
Failed to run the last action: Install Software Updates. Execution of task sequence failed.
Unspecified error (Error: 80004005; Source: Windows) TSManager 09/01/2013 16:47:06 252 (0x00FC)
Sending status message . . . TSManager 09/01/2013 16:47:06 252 (0x00FC)
Send a task execution status message SMS_TSExecution_TaskSequenceFailError TSManager 09/01/2013 16:47:06 252 (0x00FC)
MP server HYPNOS.COMPANY.COM and port 80. SSL=false. CRL=false. TSManager 09/01/2013 16:47:06 252 (0x00FC)
Site code: EQW TSManager 09/01/2013 16:47:06 252 (0x00FC)
Client machine name: MININT-L7QPTIN TSManager 09/01/2013 16:47:06 252 (0x00FC)
Client Identity: GUID:08537e34-50e4-443c-a09e-88c4782fc46d TSManager 09/01/2013 16:47:06 252 (0x00FC)
Advertisement ID: EQW2015E TSManager 09/01/2013 16:47:06 252 (0x00FC)
Package ID: EQW00149 TSManager 09/01/2013 16:47:06 252 (0x00FC)
Sending StatusMessage TSManager 09/01/2013 16:47:06 252 (0x00FC)
Formatted header: TSManager 09/01/2013 16:47:06 252 (0x00FC)
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>bcf455e3-b1a8-4144-bd43-6ac27a2315ec</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2013-01-09T16:47:06Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="2138"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
TSManager 09/01/2013 16:47:06 252 (0x00FC)
CLibSMSMessageWinHttpTransport::Send: URL: HYPNOS.COMPANY.COM:80 CCM_POST /ccm_system/request TSManager 09/01/2013 16:47:06 252 (0x00FC)
The request has succeeded. 200 OK TSManager 09/01/2013 16:47:07 252 (0x00FC)
Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767) TSManager 09/01/2013 16:55:11 252 (0x00FC)
Task Sequence Engine failed! Code: enExecutionFail TSManager 09/01/2013 16:55:11 252 (0x00FC)
**************************************************************************** TSManager 09/01/2013 16:55:11 252 (0x00FC)
Task sequence execution failed with error code 80004005 TSManager 09/01/2013 16:55:11 252 (0x00FC)
Cleaning Up. Removing Authenticator TSManager 09/01/2013 16:55:11 252 (0x00FC)
Cleaning up task sequence folder TSManager 09/01/2013 16:55:11 252 (0x00FC)
DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508) TSManager 09/01/2013 16:55:11 252 (0x00FC)
Successfully unregistered Task Sequencing Environment COM Interface. TSManager 09/01/2013 16:55:11 252 (0x00FC)
Command line for extension .exe is "%1" %* TSManager 09/01/2013 16:55:11 252 (0x00FC)
Set command line: "C:\WINDOWS\system32\CCM\TsProgressUI.exe" /Unregister TSManager 09/01/2013 16:55:11 252 (0x00FC)
Executing command line: "C:\WINDOWS\system32\CCM\TsProgressUI.exe" /Unregister TSManager 09/01/2013 16:55:11 252 (0x00FC)
==========[ TsProgressUI started in process 3136 ]========== TsProgressUI 09/01/2013 16:55:11 1660 (0x067C)
Command line: "C:\WINDOWS\system32\CCM\TsProgressUI.exe" /Unregister TsProgressUI 09/01/2013 16:55:11 1660 (0x067C)
Unregistering COM classes TsProgressUI 09/01/2013 16:55:11 1660 (0x067C)
Unregistering class objects TsProgressUI 09/01/2013 16:55:11 1660 (0x067C)
Shutdown complete. TsProgressUI 09/01/2013 16:55:11 1660 (0x067C)
Process completed with exit code 0 TSManager 09/01/2013 16:55:11 252 (0x00FC)
Successfully unregistered TS Progress UI. TSManager 09/01/2013 16:55:11 252 (0x00FC)
Setting program history for EQW00149:* TSManager 09/01/2013 16:55:11 252 (0x00FC)
Opening the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence TSManager 09/01/2013 16:55:11 252 (0x00FC)
Deleting the package ID from registry key HKLM\Software\Microsoft\SMS\Task Sequence\Package TSManager 09/01/2013 16:55:11 252 (0x00FC)
kTaskSequence.DeleteValue(L"Package"), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\utils.cpp,3099) TSManager 09/01/2013 16:55:11 252 (0x00FC)
Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002 TSManager 09/01/2013 16:55:11 252 (0x00FC)
Start to cleanup TS policy TSManager 09/01/2013 16:55:11 252 (0x00FC)

 

Full file is attached.

 

Updates deployment to existing XP and 7 clients is working correctly. This only appears to be affecting the imaging of new machines during the TS.

 

Been banging my head against this for two days, any suggestions would be greatly appreciated!

 

Thanks,

 

Rich

smsts-20130109-165515-Company.log

Share this post

Link to post
Share on other sites

1 answer to this question

Recommended Posts

  • 0
Zebwen Newbie

Zebwen

Posted
Posted

Fixed!

 

Stupidly, this appears to be a driver issue. In the Apply Device Drivers stage of the Task Sequence, I previously had "Consider drivers from all categories" selected. I have now changed this to "Limit driver matching to only consider drivers in the selected category" and specifically selected the category I created for Windows 7 x86 Drivers". I still have "Do unattended installation of unsigned drivers on versions of Windows where this is allowed" checked, as it was previously.

 

For crazypants reasons, this has now fixed the issue. My thoughts are that the task sequence was incorrectly choosing to use drivers from older operating systems (I also have all the equivalent drivers in a separate category for XP).

 

Just doing a few test images to confirm, but this certainly looks like it was a driver issue. Hope this helps someone else!

 

Rich

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
Answer this question...

×   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...
×
Go to question listing
×
×
  • 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.