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
Action output: zSource, sSourceDirectory, dwFlags, hUserToken,
pszUserName, pszUserPassword), HRESULT=80091007
ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0),
TS::Utility::ResolveSource( this->packageID, this->packagePath,
Entering ReleaseSource() for
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
The operating system reported error 2148077575: The hash value is
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
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
appreciate any help
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
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
by: MoritzCSAPosted on 2010-02-05 at 05:39:33ID: 26494871
Its not the Boot image what has problems. Its one single OS package as others workjust fine
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.
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.
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
by: TheLearnedOnePosted on 2010-03-03 at 18:54:29ID: 27299334
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
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.
Experts-Exchange Cleanup Volunteer
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)
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.
Save to Personal Knowledgebase
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.