locked
SCCM Task Sequence Fails with 0x80004005 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm getting a failure while doing OSD in a SCCM 2007 R2 site. Everytime the task sequence gets to "Resolving Task Sequence Dependencies" it failes with an error code of 0x80004005. Looking at the SMSTS.log file on the system, it is saying that the "content location request failed".

    I've verified through both the SCCM console and the actual fileshare that the package its looking for is available. It always fails on the first package that it tries to resolve, I've played around with the task sequence to see if it had any effect.






    Any ideas on what I should try?


    Last bit of the SMSTS.log file is below:
    Executing content location request for HSG0005C:2 as GUID:4D8A8CF6-AF1D-462B-966C-356E49830CA1 TSPxe 8/10/2009 1:52:36 PM 1632 (0x0660)
    Sending RequestContentLocations TSPxe 8/10/2009 1:52:36 PM 1632 (0x0660)
    Formatted header: TSPxe 8/10/2009 1:52:36 PM 1632 (0x0660)
    <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:4D8A8CF6-AF1D-462B-966C-356E49830CA1</SourceID><SourceHost/><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2009-08-10T18:52:36Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="618"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
     TSPxe 8/10/2009 1:52:36 PM 1632 (0x0660)
    CLibSMSMessageWinHttpTransport::Send: URL: sccm-mp-1.housing.wisc.edu:80  CCM_POST /ccm_system/request TSPxe 8/10/2009 1:52:36 PM 1632 (0x0660)
    The request has succeeded. 200 OK TSPxe 8/10/2009 1:53:31 PM 1632 (0x0660)
    reply from server is 'NoReply' TSPxe 8/10/2009 1:53:31 PM 1632 (0x0660)
    DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,3396) TSPxe 8/10/2009 1:53:31 PM 1632 (0x0660)
    ContentLocations.RequestContentLocations(), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,8232) TSPxe 8/10/2009 1:53:31 PM 1632 (0x0660)
    content location request failed TSPxe 8/10/2009 1:53:31 PM 1632 (0x0660)
    CCM::SMSMessaging::GetContentLocation( pszPackageID, pszPackageType, lSourceVersion, pszSiteCode, pszServer, pTransport, pszClientGUID, NULL, true, NULL, lSMSCLRList ), HRESULT=80004005 (c:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,1870) TSPxe 8/10/2009 1:53:31 PM 1632 (0x0660)
    Content location request for HSG0005C:2 failed. (Code 0x80004005) TSPxe 8/10/2009 1:53:31 PM 1632 (0x0660)
    FALSE, HRESULT=80004005 (c:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,1635) TSPxe 8/10/2009 1:53:31 PM 1632 (0x0660)
    Content location request for HSG0005C:2 failed. (Code 0x80004005) TSPxe 8/10/2009 1:53:31 PM 1632 (0x0660)
    pTSPolicyManager->GetContentLocations( m_sPackageID, m_lSourceVersion, m_dwContentSourceFlags, slistContentLocations, slistHttpContentLocations, slistMulticastContentLocations, m_dwContentPackageFlags ), HRESULT=80004005 (c:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2330) TSPxe 8/10/2009 1:53:31 PM 1632 (0x0660)
    (*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80004005 (c:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2862) TSPxe 8/10/2009 1:53:31 PM 1632 (0x0660)
    m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1207) TSPxe 8/10/2009 1:53:31 PM 1632 (0x0660)
    Failed to resolve selected task sequence dependencies. Code(0x80004005) TSPxe 8/10/2009 1:53:31 PM 1632 (0x0660)
    hrReturn, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediaresolveprogresspage.cpp,408) TSPxe 8/10/2009 1:53:31 PM 1632 (0x0660)
    ThreadToResolveAndExecuteTaskSequence failed. Code(0x80004005) TSPxe 8/10/2009 1:53:31 PM 1632 (0x0660)
    ThreadToResolveAndExecuteTaskSequence returned code 0x80004005 TSPxe 8/10/2009 1:53:31 PM 1428 (0x0594)
    Setting wizard error: An error occurred while resolving dependencies for the selected task sequence (0x80004005). For more information, please contact your system administrator or helpdesk operator. TSPxe 8/10/2009 1:53:31 PM 1428 (0x0594)

    Somthing
    Monday, August 10, 2009 7:18 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    We finally resolved the issue. First I deleted some orphaned DPs from the site database using SQL manager. That got us to a point where we were recieveing a new error message in the OSD. The installation of http://support.microsoft.com/kb/959812 resolved it.

    Somthing
    • Marked as answer by chuckwastell Thursday, August 13, 2009 9:28 PM
    Thursday, August 13, 2009 9:28 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Before an OSD task sequence kicks off it checks that all packages called by the task sequence are available/accessible. This means you should verify all settings in each task in your task sequence to make sure the content is accessible.
    Monday, August 10, 2009 7:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I've verified that the package in question: HSG0005C:2 is available on all of our DPs. It's actually the PXE Boot image that is being used by the OSD to actually boot.
    Somthing
    Monday, August 10, 2009 7:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Is the package/boot image distributed to both ordinary and pxe distribution point?
    Monday, August 10, 2009 10:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Do you have a network access account set up?
    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    • Proposed as answer by Jamitupya Tuesday, August 11, 2009 4:18 AM
    Monday, August 10, 2009 10:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Sorry, mis-click ... not my thread
    Tuesday, August 11, 2009 4:19 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    1) Verify that the Driver Package is already on the DP by checking the Package Status of the Driver Package.

    2) Under the Driver Package, right click Distribution Points and choose "Manage Distribution Points".

    3) In the Manage Distribution Points Wizard, click Next, and then choose "Update all distribution points with a new package source version", then click Next, Next again, and then Close.

    4) Monitor the Package Status for the Driver Package and verify that the DP updates.

    5) Once the DP updates, try the OSD Task Sequence deployment again
    Tuesday, August 11, 2009 9:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Housing,

    A lot of times this error occurs when your packages have not been updated on the DPs or your task sequencer is using a different version of one your packages. 

    If it is the PXE Boot image in question, RC on the TS, go to properties, go to Advanced tab.  Verify you are using the correct boot image.

    Hope this helps.
    BR
    Tuesday, August 11, 2009 2:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yep, network access account is setup.
    Somthing
    Tuesday, August 11, 2009 3:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Did this for all packages involved in the Task Sequence, as well as all of the Driver Packages in our Site, didn't change anything.
    Somthing
    Tuesday, August 11, 2009 4:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yep, and I just tested and we get the same problem when using Boot Media.
    Somthing
    Tuesday, August 11, 2009 4:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Housing,

    My next step would be to delete packages from their DPs, verify they have been removed from the SMSPKG share and add them back.  You can do this one at a time to identify the package or all at once.
    BR
    Wednesday, August 12, 2009 2:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    My lab partner and I have been seeing a lot of this. Specifically on Windows 7 deployments using ConfigMgr 07 RC1. I have read numerous times about Win7 WAIK maybe having something to do with it. Are you trying to deploying Win7?

    Wednesday, August 12, 2009 9:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We finally resolved the issue. First I deleted some orphaned DPs from the site database using SQL manager. That got us to a point where we were recieveing a new error message in the OSD. The installation of http://support.microsoft.com/kb/959812 resolved it.

    Somthing
    • Marked as answer by chuckwastell Thursday, August 13, 2009 9:28 PM
    Thursday, August 13, 2009 9:28 PM