MoritzCSA
asked on
SCCM OS deployment error (0x80091007)
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\framew ork\tscore \resolveso urce.cpp,3 130)
ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0),
HRESULT=80091007
(e:\nts_sms_fre\sms\framew ork\tscore \resolveso urce.cpp,3 031)
TS::Utility::ResolveSource ( this->packageID, this->packagePath,
TS::Utility::ResolveSource Flags::Per sistConten ts ),
HRESULT=80091007
(e:\nts_sms_fre\sms\client \osdeploym ent\applyo s\installs cripted.cp p,
160)
installer.install(), HRESULT=80091007
(e:\nts_sms_fre\sms\client \osdeploym ent\applyo s\installs cripted.cp p,
632)
Entering ReleaseSource() for
C:\_SMSTaskSequence\Packag es\GID0000 4
The user tries to
release a source directory
C:\_SMSTaskSequence\Packag es\GID0000 4 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 \osdeploym ent\applyo s\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
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\framew
ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0),
HRESULT=80091007
(e:\nts_sms_fre\sms\framew
TS::Utility::ResolveSource
TS::Utility::ResolveSource
HRESULT=80091007
(e:\nts_sms_fre\sms\client
160)
installer.install(), HRESULT=80091007
(e:\nts_sms_fre\sms\client
632)
Entering ReleaseSource() for
C:\_SMSTaskSequence\Packag
The user tries to
release a source directory
C:\_SMSTaskSequence\Packag
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
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
ASKER
Hi,
Its not the Boot image what has problems. Its one single OS package as others workjust fine
Its not the Boot image what has problems. Its one single OS package as others workjust fine
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.
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.
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.
ASKER
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
smsts.log
I have the log file from the F8 boot atached
smsts-20100210-001651.log
smsts.log
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 = A9173DC49D149170C0F7F55261 54AC4381ED 0DC0, Downloaded ContentHash = 88601C0BA124401EA13790D2F3 18AF04CB28 3DD1 ApplyOperatingSystem 9/02/2010 3:29:21 PM 1680 (0x0690)
Hash could not be matched for the downloded content. Original ContentHash = A9173DC49D149170C0F7F55261
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Update the distribution points of the package that was failing. I have had this same problem and a distribution point update will fix it.
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