I am getting a "Hash could not be matched for the downloded content. Original ContentHash =..." in smsts.log
Hi, I have a mixed SCCM and SMS hierarchy. I am doing OSD from SCCM 2007 R3 SP2 central site server. Things are working quite nicely except when I try to put the OSD package content on an SMS DP (that exists lower in the hierarchy). I am trying to leverage a WIM image that is 6.2GB's is size. (Note: when I perform OSD using smaller image files, it seems to work both on SMS DP's and with SCCM DP's.... so, it seems like size has something to do with my problem.) The error in the SMSTS.log is this "Hash could not be matched for the downloded content. Original ContentHash = 7334ABBF5399075E5AB71040F168C88622FF9533, Downloaded ContentHash = 719D6807E396C2D1CE4DBAF61E6ED7DBDC3DA95F" We are not using Multicast. I have removed this package and re-added the package several times...but I always get the HASH problem. Does anyone know what this means? We have discovered as per earlier results is that we consistently get the hash mis match error when the file has been distributed to the sms 2003 distribution point. This is independent of having the binary differential on or off as we have tested with both settings. Work Around: Marking the advertisement to NOT download and execute seems to work. (run over the network). However, we would like to use download and execute for these packages. Any thoughts?
October 5th, 2011 2:55pm

have you tried refreshing the package ? does it make any difference ? also check the following:- Task Sequence Fails Due to Hash Error Because of Extended Character in File Name An advertised task sequence can fail if a file name associated with that task sequence package contains extended characters (that is, characters with an umlaut or accent). When a task sequence advertisement is set to “Download content locally when needed by running task sequence,” the extended character in the file name can result in an error. The smsts.log file will state “Hash could not be matched for the downloaded content.” This issue can also affect task sequences not used for operating system deployment. Solution The issue can be resolved by renaming all files to names without extended characters. This issue can also be resolved by specifying that the task sequence advertisement should download all content locally before running the task sequence. For more information about log files for task sequences, see Log Files for Operating System Deployment. For more information about distributing advertisements for task sequences, see Advertised Task Sequence Properties - Distribution Points Tab. http://technet.microsoft.com/en-us/library/bb932192.aspx My step by step SCCM Guides I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2011 3:03pm

Thank you for the fast reply. "have you tried refreshing the package ? does it make any difference ?" <- yes, many many times. However, the problem continues. I have even deleted the package and readded the package fresh with no positive results. "Task Sequence Fails Due to Hash Error Because of Extended Character in File Name" Yes, I am aware of this issue too. And I don't think I am using any special chararcters. In fact, when the package is only distributed to SCCM DP's, the OSD works fine. It is only when I add the package to an SMS DP that the problem develops. (Most of our environment still uses SMS DP's.
October 5th, 2011 3:20pm

Hi I saw lot's of hash value failures if I had hidden files like thumbs.db in my packages. Good blog Post about hash value failures: http://marcusoh.blogspot.com/2011/04/sccm-content-hash-fails-to-match.html Greetings, Jürg
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2011 5:43pm

what is the package exactly ? just a wim file or somethign else ? My step by step SCCM Guides I'm on Twitter > ncbrady
October 6th, 2011 12:49pm

thank you so much for the replies... Juerge: I have checked the package and have confirmed that there are no HIDDEN files. Niall: The problematic package is just one single WIM file. (Operating system image)
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2011 2:51pm

as you are only seeing this on the sms distribution point is there anything strange about that dp ? any new/changed antivirus software/software rules on it ? My step by step SCCM Guides I'm on Twitter > ncbrady
October 6th, 2011 3:36pm

I will look into that a bit more. both SCCM and SMS DPs run the same version of Symantec AV. However, all SCCM DPs are Windows 2008 and all SMS DPs are Windows 2003. We have tested the issue on at least 3 different SMS DPs around the world and have run into this issue every time. Note: The download and execute of the WIM file works when our WIM file is smaller (like 2.9 GB's); however, only when we use our large WIM files do we see this issue (6.2GB) Also, when we set the advertisement to RUN OVER the NETWORK... and not download first, the packages run just fine (even when we use the 6.2GB wim).
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2011 3:41pm

Try disable antivirus for a short period, and distribute to DPs again. Recommend anyway for performance and functionality to exclude certain folders and files according to: http://systemcenterforefront.blogspot.com/2011/09/configmgr-2007-antivirus-scan-and.html Regards, NicolaiNicolai
October 7th, 2011 3:56am

I also would like to suggest that you turn off the "binary delta replication" option for the package.
Free Windows Admin Tool Kit Click here and download it now
October 7th, 2011 1:49pm

Thanks... we have experimented with both enabling and disabling binary replication. (with no change either way). Although, for the moment, we have disabled it.
October 7th, 2011 1:57pm

I remember there was a hashing issue in SCCM SP1, maybe the sms2003 DP is using old code that causes the hash mismatch? http://support.microsoft.com/kb/2000470 The problem is caused by a known bug in Configuration Manager 2007 SP1 R2 where the hash calculations are not performed correctly when going over the the 32bit barrier (approximately 4GB) and going into 64bit calculations. This occurs when the WIM file size is just over 4GB.
Free Windows Admin Tool Kit Click here and download it now
January 11th, 2012 12:08am

Have you tried to deinstall the AV? With Symantec AV I've noticed several times that only exclusion doesn't do the trick...Tim Nilimaa | IT Expert at Knowledge Factory | Please remember to mark this answer as helpful if it helped you.
January 11th, 2012 3:01am

I seem to have been able to narrow down the problem. As far as I can tell this is a limitation/bug in the ISAPI filter dll that the DP uses. It looks like the problem is the "smsfileisapi.dll" that is part of SMS 2003 SP3 (2.50.4253.3000). If I simply replace that dll with the SCCM 2007 version "4.0.6487.2000" then the problem seems to go away. Have reported this to MS. Waiting for a response now.
Free Windows Admin Tool Kit Click here and download it now
February 29th, 2012 8:04am

wow... how in the world did you figure that one out?
February 29th, 2012 9:50am

So, MS researched this further and confirmed that this is a bug with the older versions of this .dll (SMS 2003 SP3), that the ISAPI would have problems downloading packages over 4GB in size. This was resolved with Configuration Manager 2007 with the updated smsfileisapi.dll but there was no resolution offered for SMS 2003. Since SMS 2003 SP3 is now only in extended support, there would not be any additional hotfixes or changes offered for the product. Their recommendation is to upgrade the SMS 2003 DPs to Configuration Manager 2007.
Free Windows Admin Tool Kit Click here and download it now
March 1st, 2012 5:40am

So, MS researched this further and confirmed that this is a bug with the older versions of this .dll (SMS 2003 SP3), that the ISAPI would have problems downloading packages over 4GB in size. This was resolved with Configuration Manager 2007 with the updated smsfileisapi.dll but there was no resolution offered for SMS 2003. Since SMS 2003 SP3 is now only in extended support, there would not be any additional hotfixes or changes offered for the product. Their recommendation is to upgrade the SMS 2003 DPs to Configuration Manager 2007.
March 1st, 2012 5:40am

It figures... Thanks for the update. "If I simply replace that dll with the SCCM 2007 version "4.0.6487.2000" then the problem seems to go away." -- seems to be a good work around.
Free Windows Admin Tool Kit Click here and download it now
March 1st, 2012 6:47am

It's very much an unsupported workaround. Goes without saying that you're on your own then and can't expect any more support from MS.
March 1st, 2012 7:01am

fair enough....
Free Windows Admin Tool Kit Click here and download it now
March 1st, 2012 7:02am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics