none
OSD Task Sequence Fails with Error 0x80091007

    Question

  • Hello Everyone,

    I have a bit of a weird hash mismatch problem.  The issue is only occuring on one laptop.  The laptop was imaged successfully, new out of the box.  Computer started "acting craptacular" according to the tech, so he tried to reimage it, assuming one of the applications he put on the computer while setting it up for the user may have messed it up.

    From that point forward, the computer couldn't image anymore.  I can image the same model, TS, and even other models without issue.  The error logs are pointing to a hash value mismatch on the OS WIM. 

    Here are the log files - I wish there was a way to make them cleaner.  I ran some hardware tests with IBM's PCDoctor, and it came back clean.  I'm starting to run out of ideas.

    Thanks in advance!

    Log: (SMSTS.LOG)

    ------------------------------------------------------

    Download done setting progress bar to 100 ApplyOperatingSystem 5/14/2010 4:09:31 PM 840 (0x0348)

    Hash could not be matched for the downloded content. Original ContentHash = A6170DC8CFC5A443636828F093C45377B5FE2A62, Downloaded ContentHash = 7DEBC67B90C2326031EF8727238176C92A02006C ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

    0L == TS::Utility::VerifyPackageHash(pszContentID, sDestination), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2901) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

    DownloadContentAndVerifyHash(pszPackageID, L"SMSPackage", saHttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L"", 0, dwPackageFlags, pszUserName, pszUserPassword ), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3000) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

    DownloadContentLocally(pszSource, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3128) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

    ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3029) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

    TS::Utility::ResolveSource( this->packageID, this->packagePath, TS::Utility::ResolveSourceFlags::PersistContents ), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1255) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
    resolvePkgSource(), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1299) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

    Installation of image 1 in package RH1000DD failed to complete..

    The hash value is not correct. (Error: 80091007; Source: Windows) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

    installer.install(), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1373) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

    Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\RH1000DD ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

    The user tries to release a source directory C:\_SMSTaskSequence\Packages\RH1000DD that is either already released or we have not connected to it ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

    InstallImage( g_InstallPackageID, g_ImageIndex, targetVolume, ImageType_OS, g_ConfigPackageID, g_ConfigFileName ), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,360) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

    Process completed with exit code 2148077575 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    !--------------------------------------------------------------------------------------------! TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Failed to run the action: XP SP3 - Multi-HAL.

    The hash value is not correct. (Error: 80091007; Source: Windows) TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Sending status message . . . TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Send a task execution status message SMS_TSExecution_ActionFailError TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    MP server rh1-sccm.ritehite.com and port 80. SSL=false. CRL=false. TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Site code: RH1 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Client machine name: R842AEYa TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Client Identity: GUID:428CFC8B-1BE1-4E11-B2C4-21E31EA71572 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Advertisement ID: RH1200C2 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Package ID: RH1000DF TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Sending StatusMessage TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Formatted header: TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>56d444c9-6bf0-4ed2-86a9-5f199c90924c</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2010-05-14T21:09:53Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="4246"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
     TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    CLibSMSMessageWinHttpTransport::Send: URL: sccmserver.x.com:80  CCM_POST /ccm_system/request TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    The request has succeeded. 200 OK TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Set a global environment variable _SMSTSLastActionRetCode=-2146889721 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Clear local default environment TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Let the parent group (Apply Operating System) decides whether to continue execution TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Let the parent group (Install Operating System) decide whether to continue execution TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    The execution of the group (Install Operating System) has failed and the execution has been aborted. An action failed.

    Operation aborted (Error: 80004004; Source: Windows) TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Failed to run the last action: XP SP3 - Multi-HAL. Execution of task sequence failed.

    The hash value is not correct. (Error: 80091007; Source: Windows) TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Sending status message . . . TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Send a task execution status message SMS_TSExecution_TaskSequenceFailError TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

    Friday, May 14, 2010 9:27 PM

Answers

  • Sorry, forgot to answer on this one.

    Turns out the computer had bad memory!  It was a completely obscure issue where the symptom had no implication as to what the true problem was.

    Thanks,

    Sean

    • Marked as answer by seanka79 Wednesday, July 14, 2010 7:42 PM
    Wednesday, July 14, 2010 7:42 PM

All replies

  • Hi,

    Have you tried to use "update distribution point" to refresh source version and wim file on distribution points ?
    Have you tried to reimport Wim files and change TS with the reimported WIM ?

    Best Regards


    Jean-Sébastien DUCHÊNE - www.windowstouch.fr - Microsoft Student Partner (MSP), MCITP Enterprise Desktop Support Technician 7/Enterprise Desktop Administrator 7, MCTS Configuration Manager/MDOP
    Saturday, May 15, 2010 9:16 PM
  • Does the file larger than 4 GB?

    If so, it's a known bug on SCCM, please refer to the following KB to resolve the problem:

    Multicast OS deployments fail with a hash value error when the Windows OS WIM file size is larger than 4 GB in System Center Configuration Manager 2007
    http://support.microsoft.com/kb/971413

    Hope it helps.

    Monday, May 17, 2010 8:01 AM
  • Hi Guys,

    My WIM is currently sitting at 1.8 GB, so I'm not sure it is the 4 GB bug you were referring to.

    I haven't tried a re-import/update DP yet mainly because the problem is occuring on only one computer at this moment.  In fact, I have deployed several computers already with the same DP, same WIM and even the same model of computer.  That makes me think it isn't an issue with the WIM as much as it is an issue with the computer itself.

    Can you guys think of anything on the computer that would cause the failure?

    Thanks again,

    Sean

    Monday, May 17, 2010 1:56 PM
  • I encountered the same 0x80091007 when attempting to build and capture Windows XP Pro with SP3.  I resolved it by modifying the task sequence to "Access content directly from distribution point when needed...." option.
    Wednesday, July 14, 2010 7:38 PM
  • Sorry, forgot to answer on this one.

    Turns out the computer had bad memory!  It was a completely obscure issue where the symptom had no implication as to what the true problem was.

    Thanks,

    Sean

    • Marked as answer by seanka79 Wednesday, July 14, 2010 7:42 PM
    Wednesday, July 14, 2010 7:42 PM
  • Ts error Code 0x80091007 will encounter due to Bad memory.I have faced the similar issue in recent Past and replaced Memory.

    Problem gets Solved.

     

    Thanks,

    K Arun

    Friday, January 07, 2011 2:45 AM
  • Sean, thanks for the post. I had the same problem today (Yeah, I know the thread has been dead for a year), and wouldnt have known without Google and your answer.
    Wednesday, May 25, 2011 7:25 PM
  • Nice!  Just ran into this...indeed, SCCM will fail it on applying the OS image and you would NEVER know!
    • Proposed as answer by sanjay.s Friday, January 27, 2012 5:00 AM
    Friday, June 24, 2011 8:02 PM
  • hi people..!!! I'm facing the same problem..please help out..


    Friday, January 27, 2012 5:02 AM
  • The memory fix did it for me too.  Good thing Google still sees this.  I was tearing my hair out trying to figure it out by checking the logs.
    Tuesday, November 12, 2013 10:49 PM
  • Would it matter matter if the memory was built-in vs a removable chip?  Reason I bring this up is I am experiencing the same error.  The removable memory chip (tested as bad) was removed and I tried to image again with the same error code (0x80091007).  Laptop has still had 4GB of built-in RAM.
    Friday, September 12, 2014 7:04 PM
  • I was receiving the same error.  Turns out the problem was binary differential replication.  Refreshing the distribution point was not helping.  I had to turn off binary differential replication and redistribute to the distribution point.  BDR was causing the hash error.
    Wednesday, October 22, 2014 10:10 PM
  • Sorry, forgot to answer on this one.

    Turns out the computer had bad memory!  It was a completely obscure issue where the symptom had no implication as to what the true problem was.

    Thanks,

    Sean

    Thanks, this was the issue for me as well. I was imaging a room of 20 identical machines and only 1 had this issue. Replacing the memory did the trick.

    Thanks

    Thursday, April 23, 2015 11:24 AM