Andy Smith
asked on
Task sequence failed with the error code (0x80091007) - Usual fixes tried
Task sequence failed with the error code (0x80091007)
SCCM 2012 R2
We have a Primary Site and multiple distribution points.
Looking at the SMSTSLOG I can see:
Hash could not be matched for the downloded content. Original ContentHash = 00FC5D701C440E461503356D55 C5639CB184 7FED9AF3E7 5DC1C847BA 78F0830E, Downloaded ContentHash = AA80A09FC84DDF6E118348A120 C295FBB84C 160CAB7F10 FD400356B9 00AA15EF
Installation of image 1 in package SPS00158 failed to complete..
The hash value is not correct. (Error: 80091007; Source: Windows) ApplyOperatingSystem 24/02/2017 11:27:23 1784 (0x06F8)
This Image works on all our laptops/desktops even new/unknown ones, except this particular model:
HP Z Book 15 G3
I have removed the content from the distribution points and redistributed, same error.
I have re-imported the OS Image and distributed to the distributions points, same error.
I have captured a new OS image and imported, then distributed to distribution points, same error.
I am pulling my hair out over this one.
Any help/suggestions would be appreciated.
Andy.HFX1243---smsts.log
SCCM 2012 R2
We have a Primary Site and multiple distribution points.
Looking at the SMSTSLOG I can see:
Hash could not be matched for the downloded content. Original ContentHash = 00FC5D701C440E461503356D55
Installation of image 1 in package SPS00158 failed to complete..
The hash value is not correct. (Error: 80091007; Source: Windows) ApplyOperatingSystem 24/02/2017 11:27:23 1784 (0x06F8)
This Image works on all our laptops/desktops even new/unknown ones, except this particular model:
HP Z Book 15 G3
I have removed the content from the distribution points and redistributed, same error.
I have re-imported the OS Image and distributed to the distributions points, same error.
I have captured a new OS image and imported, then distributed to distribution points, same error.
I am pulling my hair out over this one.
Any help/suggestions would be appreciated.
Andy.HFX1243---smsts.log
Hi,
It's odd this only happens with one machine, which suggests it is the hardware. Have you tried booting with WinPE (or pausing the task-sequence) and then connecting to the CM source share manually and using copy/robocopy to transfer the WIM? This would just check that this machine can transfer a big file over the NIC. If that fails then updating the NIC driver would be the next step. I've no experience with that model I'm afraid. Updating the BIOS is always an option in cases like this too. Rule out the possibles.
I've not noticed nocert being in the logs before. Is that something you have or is it standard?
Mike
It's odd this only happens with one machine, which suggests it is the hardware. Have you tried booting with WinPE (or pausing the task-sequence) and then connecting to the CM source share manually and using copy/robocopy to transfer the WIM? This would just check that this machine can transfer a big file over the NIC. If that fails then updating the NIC driver would be the next step. I've no experience with that model I'm afraid. Updating the BIOS is always an option in cases like this too. Rule out the possibles.
I've not noticed nocert being in the logs before. Is that something you have or is it standard?
Mike
ASKER
HI, thanks for all your suggestions but none have worked.
I failed to mention that I initially thought it was hardware and replaced/tried different Memory/M.2 and HDD's. I even had the unit swapped out.
All of our other Laptops and Desktops build fine without issues.
Looks like I'll be raising support tickets with HP and MS
Andy
I failed to mention that I initially thought it was hardware and replaced/tried different Memory/M.2 and HDD's. I even had the unit swapped out.
All of our other Laptops and Desktops build fine without issues.
Looks like I'll be raising support tickets with HP and MS
Andy
Have the exact same issue(s).
Hash mis-match error
Dell 780, Win7 via SCCM CB running on a 2016 server.
Any updates on this?
Hash mis-match error
Dell 780, Win7 via SCCM CB running on a 2016 server.
Any updates on this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
http://HFX-SCCM-VM.siriusfs.com:443/NOCERT_SMS_DP_SMSPKG$/SPS00158/sccm?/Win7SP1Apps3005.wim
I wonder if the '?' in the file path following /sccm might be tripping things up. ? is an invalid file path character...Although it is a vaild character in a URL.
Make sure that you try an Update Distribution Points operation on your package as this will create a new hash
Also try this if the above fails to remove the hash error...its odd that you experience this only on a specific model but SCCM does weird things sometimes:
http://henkhoogendoorn.blogspot.ca/2014/04/hash-could-not-be-matched-for.html