/build/static/layout/Breadcrumb_cap_w.png

hashing mismatch error with SCCM 2007

Can someone tell me why a software package in SCCM 2007 doesn`t install when it`s part of a task sequence but when i deploy it individually to running PC`s it works fine.  I get hashing mismatch errors.

Any input would be apreciated.  Thanks


0 Comments   [ + ] Show comments

Answers (2)

Posted by: dunnpy 11 years ago
Red Belt
2

I think that the solution might be found here, it would seem you have extended ASCII characters in a file name:

http://social.technet.microsoft.com/wiki/contents/articles/6562.aspx

4. SMSTS error “Hash could not be matched for the downloaded content”. When deploying a software package in SCCM 2007 via a Task Sequence, and that package contains files with names containing extended ASCII characters, the Task Sequence may fail with an error code 80004005. An example would be something like the Spanish word año where there’s a tilde over the ‘n.’

I've seen a similar issue when a file name has a '+' in it. I've had to rename the file and then use a vbscript to rename it back to the correct name and launch the msiexec  commands once it's down in the client cache of the target machine.

Hope that helps,

Dunnpy

Posted by: KevinViolette 11 years ago
5th Degree Black Belt
1

We were not able to pinpoint the probleme but we did find a solution.  Instead of copying the files from the DP to the client we ran the installation from the DP, therefore eliminating the hash checking alltogether.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ