0x80091007 - The hash value is not correct

[AdamF]

Hi,

 

Whilst trying to apply a package as part of an OSD TS, the TS is consistantly failing with the same error 0x80091007 - The hash value is not correct. We have tried multiple different things to fix the problem but seem unable to. We have tried the following:

 

•Updated the package on the DP

•Removed and re-added the package to the DP

•Completly removed the package from SCCM, re-created and re-added to the DP

•Refreshed the package on the DP and updated the package immediately

•Applied the hotfix from KB2276865 to the client - I read on another forum this could be casuing an incorrect hash

•Changed the TS advertisment and set the option: Access content directly from a DP when needed by the running TS

•Checked for non ACSII characters in the file paths - I read that this could cause an incorrect hash

•Deleted the package from the DP, remove the package from SCCM, changed the location of the source files, re-created the package and re-added to the DP

•Checked for hidden files in the source directory - none exist

•Checked to see if Binary Differential Replication is enabled - it is not enabled.

 

None of these have fixed the issue. If we attempt to deploy the software using a normaly advertisment once Windows is installed this works fine, we only see this error when trying to deploy the package as part of an OSD TS.

 

A little environment information:

 

 

SCCCM is running in Mixed Mode

The DP is on the same server as the site server

Server is running Windows Server 2008 R2 Std (as a VM)

SCCM is 2007 SP2

We are not using multicast

 

 

I'm testing SCCM as a proof on concept on a single client.

 

I've been looking at this problem for a couple of week now and am just going round and round in circles.

 

Can anybody help me out?

[CorradoGuy]

I can't help you on this issue directly (because I don't know the exact details nor can I remember what others were saying about it) but this is a know issue and Microsoft is working on a correction. If you have Microsoft support you can ask them to help you but I believe the correction was to delete the package and re-create which you have done and this did correct it for some people. I think it has something to do with the version of SCCM you are using or something along this line. You can also try managing the distribution point and then 'update all distribution points with new package source version' instead of just updating the distribution point. I know this doesn't really help you but it is a problem that a number of people mentioned at MMS 2011 and there is not a direct fix for it so you are not alone. Have you tried posting this on the Microsoft forums to see if someone there knows what the problem may be? I wish I could help more but I just remember people mentioned it but I don't recall the exact details, sorry about that.

[Lucid]

What exactly is "the package"? If you can tell us that, if it's a mainstream application, maybe someone has already run across this problem. Also, when you update the DPs for that package, in the package status, does it say that it updated successfully?