none
SCCM 2012 - OSD Task Sequence Error 0x80091007

    Question

  • When deploying the OSD to a laptop model the TS is failing, see below from Status Message Viewer:

    The task sequence execution engine failed executing the action (Apply E6220 Driver Package) in the group (PostInstall) with the error code 2148077575
    Action output: urce, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3217)
    ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3122)
    TS::Utility::ResolveSource( pszPackageId, sSource ), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,472)
    pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,380)
    Exiting with return code 0x80091007
    Hash could not be matched for the downloded content. Original ContentHash = EB2A940227C7043DDDCE0985EB37CBB650245F47F12ACD48C936521F5CECAFED, Downloaded ContentHash = 6F4ED0BD9ECC46712E6160BF681ED3785097D95A43652424FB97E12EB1EAF8E3
    Failed to determine the driver source location. Code 0x80091007
    Failed to provision driver. Code 0x80091007. The operating system reported error 2148077575: The hash value is not correct. 

    I have redistributed the Driver packages to the DP's but still no luck - does anyone have any idea's?

    Thanks



    MCTS | MCITP | MCSA

    • Moved by Torsten [MVP]MVP Thursday, May 02, 2013 12:18 PM moved to OSD subforum
    Wednesday, May 01, 2013 3:56 PM

Answers

All replies

  • Hi,

    Thank you for your response - I have validated and redistributed the Driver Package to the DP's. Still the same error!


    MCTS | MCITP | MCSA

    Thursday, May 02, 2013 11:54 AM
  • When you deploy your TS have you chosen to "Access content directly from a distribution point when needed by the running task sequence" ? Id give that a go.

    Blog: http://heinrichandsccm.blogspot.co.uk

    Thursday, May 02, 2013 12:20 PM
  • Hi

    The TS deployment options (in SCCM2012) is currently set to "Download content locally when needed by running task sequence".

    The strange issue is that we have 4 laptop models, 3 of which deploy successfully, 1 model fails (with the error on original post).

    Thanks


    MCTS | MCITP | MCSA

    Thursday, May 02, 2013 1:23 PM
  • I would suggest that you either remove and re-distribute the content, or create the package again. I did save a webpage that I used when I had the issue, for me updating the DP worked.

    Link: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Systems_Management_Server/Q_25117354.html


    Blog: http://heinrichandsccm.blogspot.co.uk

    • Marked as answer by Toffeenose81 Friday, July 12, 2013 10:33 AM
    Thursday, May 02, 2013 2:38 PM
  • Thank you - I have removed the content from the DP's and redistributed. I'm currently testing the TS again now, I'll let you know!

    MCTS | MCITP | MCSA

    Thursday, May 02, 2013 3:05 PM
  • Failed again - next step is to delete the driver package and re-create!

    MCTS | MCITP | MCSA

    Thursday, May 02, 2013 3:14 PM
  • good luck ! I hope it works

    Blog: http://heinrichandsccm.blogspot.co.uk

    Thursday, May 02, 2013 3:33 PM
  • Did you manage to resolve this?

    Blog: http://heinrichandsccm.blogspot.co.uk

    Friday, May 03, 2013 10:10 AM
  • Hi,

    Nope, haven't tried removing the Driver package and re-installing as yet! Hopefully I will get a chance in the next few days to test.

    I'll let you know the outcome!

    Cheers for all your help!


    MCTS | MCITP | MCSA

    Tuesday, May 07, 2013 9:45 AM
  • Do you still have access to all of the comments from your experts-exchange post? I'm unable to access the comments on your resolution, im intrigued to to a look before removing the driver package and re-creating?

    Thanks


    MCTS | MCITP | MCSA

    Wednesday, May 08, 2013 12:32 PM
  • I dont, it wasnt my post, I simply used it to help with my issue at the time.
    Wednesday, May 08, 2013 12:35 PM
  • Below is the whole thread from Expert-sex-change.com: 

    SCCM OS deployment error (0x80091007)

    Asked by: MoritzCSA

    We are getting Error on one of your Primary Child site when deploying a XP Install Package.

    In the Advertisment Status we are getting following errors:

    The task sequence execution engine failed executing the action

    (Apply Operating System Image) in the group () with the error code

    2148077575

    Action output: zSource, sSourceDirectory, dwFlags, hUserToken,

    pszUserName, pszUserPassword), HRESULT=80091007

    (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3130)

    ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0),

    HRESULT=80091007

    (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3031)

    TS::Utility::ResolveSource( this->packageID, this->packagePath,

    TS::Utility::ResolveSourceFlags::PersistContents ),

    HRESULT=80091007

    (e:\nts_sms_fre\sms\client\osdeployment\applyos\installscripted.cpp,

    160)

    installer.install(), HRESULT=80091007

    (e:\nts_sms_fre\sms\client\osdeployment\applyos\installscripted.cpp,

    632)

    Entering ReleaseSource() for

    C:\_SMSTaskSequence\Packages\GID00004

    The user tries to

    release a source directory

    C:\_SMSTaskSequence\Packages\GID00004 that is either already

    released or we have not connected to it InstallScripted(

    g_InstallPackageID, g_ImageIndex, targetVolume,

    g_ConfigPackageID, g_ConfigFileName ), HRESULT=80091007

    (e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,397).

    The operating system reported error 2148077575: The hash value is

    not correct.

    The task sequence execution engine aborted execution for a failure

    of the action (Apply Operating System Image) in the group (). The

    operating system reported error 2148077575: The hash value is not

    correct.

    The task sequence execution engine failed execution of a task

    sequence. The operating system reported error 2148077575: The

    hash value is not correct.

    The task sequence manager could not successfully complete

    execution of the task sequence. A failure exit code of 16389 was

    returned.

    appreciate any help

    IMAG0020.jpg

    747 KBscreenshot off error on Client Computer when deploying OS

    2010-02-05 at 04:39:43ID: 25117354TopicsMS System Center ,Deployment Software for DevelopmentParticipating Experts3Points0Comments9

    Request Attention

    Answers

    EXPERT COMMENT

    by: NJComputerNetworksPosted on 2010-02-05 at 05:29:05ID: 26494779

    1) enable f8 boot console on your boot image:  http://www.windows-noob.com/forums/index.php?/topic/546-how-can-i-troubleshoot-windows-pe-booting-in-sccm/  this will get you to a command prompt on the client

    2) look at the smsts.log for exactly why your client is failing osd:  http://blogs.technet.com/inside_osd/archive/2007/12/13/troubleshooting-tips.aspx

    3) also look at the reports for information as to why your OSD is failing:  http://blogs.technet.com/inside_osd/archive/2007/12/13/troubleshooting-tips.aspx

    AUTHOR COMMENT

    by: MoritzCSAPosted on 2010-02-05 at 05:39:33ID: 26494871

    Hi,

    Its not the Boot image what has problems. Its one single OS package as others workjust fine

    EXPERT COMMENT

    by: NJComputerNetworksPosted on 2010-02-05 at 06:01:11ID: 26495086

    lol... ok... but enabling F8 will allow you to get to the smsts.log which should contain some more information about why the single OS package is failing.

    EXPERT COMMENT

    by: JonLambertPosted on 2010-02-08 at 01:43:35ID: 26512090

    OK, it looks like (as descripted in the logs) that the Hash Value for the package GID00004 is not correct.

    I've seen this before with Boot WIMS, if GID00004 is a boot WIM package, then try creating a new Boot Wim, deploying it to the relevant DPs, assigning it to th TS and try again.

    If GID00004 is not a Boot WIM, then try updating the package, and keep an eye on DistMgr.log to ensure it get's distributed Ok.

    AUTHOR COMMENT

    by: MoritzCSAPosted on 2010-02-09 at 07:13:55ID: 26524885

    Hi have recreated the OS Install Packlage and have distributed it again to the Primary Child site. Still the same issue as for example the same OS in English is running fine. GID00004 was an OS Install Package.

    I have the log file from the F8 boot atached

    smsts-20100210-001651.log

    976 KBlog

    smsts.log

    391 KBlog2

    ADMINISTRATIVE COMMENT

    by: TheLearnedOnePosted on 2010-03-03 at 18:54:29ID: 27299334

    MoritzCSA,

    After 21 days without comment, it is time for you to finalize this old question -- accept an answer, split points, or get a refund.  Please be a responsible EE Member and maintain your open questions! Click here to see your options: http://www.experts-exchange.com/help.jsp#hi331

    EXPERTS,

    I need your help.  Please post your closing recommendations within a few days.  If you do not respond, I may need to assume that no correct answer was provided.

    TheLearnedOne

    Experts-Exchange Cleanup Volunteer

    EXPERT COMMENT

    by: JonLambertPosted on 2010-03-03 at 19:17:39ID: 27299526

    OK, now the package with an hash error is GID0002A .. which is the OS Install Package, Check the source directory for files with odd characters, or extremely long directory paths .. this can sometime cause a hash-check mismatch.

    Hash could not be matched for the downloded content. Original ContentHash = A9173DC49D149170C0F7F5526154AC4381ED0DC0, Downloaded ContentHash = 88601C0BA124401EA13790D2F318AF04CB283DD1      ApplyOperatingSystem      9/02/2010 3:29:21 PM      1680 (0x0690)

    ACCEPTED SOLUTION

    by: MoritzCSAPosted on 2010-03-04 at 00:23:07ID: 27300766

    I have change the OS installation to not download the package. After this change it works fine without issues.

    0

    excellent

    Save to Personal Knowledgebase

    EXPERT COMMENT

    by: DSS-RMPosted on 2010-10-17 at 07:14:56ID: 33923836

    Update the distribution points of the package that was failing. I have had this same problem and a distribution point update will fix it.

    Friday, July 05, 2013 8:43 PM
  • If you are using VMWare 5.1 it's probably in the NIC driver.
    When you use the E1000E driver on your Windows 2012 machines, change it to VMXNET3 and the problem will be solved.


    __________________________________________ Willemjan van Laarhoven | http://www.toolzz.com

    Thursday, July 18, 2013 9:27 AM
  • I can confirm that changing the VMware 5.1 NIC driver on the Windows Server 2012 machine to VMXNET3 resolved the issue for me as well.  I would get to the Applying Operating System step in the Task Sequence after downloading the WIM and I would get the hash value incorrect error.  I tried recreating the package, updating source version, etc. all to no avail.  Changing to the VMXNET3 driver resolved it completely for me.

    Also, I can confirm that some consultants we work with had set up a Windows Server 2012 VMware 5.1 host and were running MDT 2012 only (not a full SCCM 2012 infrastructure like I am) and had the same issue and once changing to the VMXNET3, it resolved the issue for them as well.

    Friday, July 26, 2013 3:29 PM
  • funny to say, but restart the server/distribution point solved the issue :)
    Wednesday, October 09, 2013 12:29 PM
  • Had the same issue. Server 2012 on VMWare 5.1. Changing to the 10g VMXNET3 adapter solved my issue as well.
    Tuesday, October 29, 2013 4:46 PM