Getting error hash value is not correct during application installation.
Question
Same application installation on machine from other dp properly.
1.removed package from dp and redistributed.
2.removed filed from cache folder
3.reinstall sccm client.
But same issue . please help on this.
Answers ( 13 )
As per Karthik incorrect hash updated into DB due to such issue come sometime
I don’t think the hash value details are stored in DB
As per Karthik incorrect hash updated into DB due to such issue come sometime
Hi,
Sometimes this will happens because of incorrect hast value updated in DB. better you can create the new application with same source then distribute the content to dp then create the deployment finally see the result on client machine.
Thanks
Karthikeyan
Thank you , this issue for only 3 applications only and on one another one dp and on another two machines same application working fine .
Is same behaviour if incorrect value updated into DB.
Hi,
First you can try one one package. If that solution works then try same on other 2 packages.
Thanks
Karthikeyan
Ok we will try this option.
I have one query here if incorrect hash value updated into database it should not install other machin .
Any logic on this.
Ok I will check and revert on same.
How to enable classic package share ,any link for this.
I mean the older versions of content share folders instead of the content library.
I couldn’t find the option for the application model in SCCM.
It might be there for classic package Data access – Package share settings – https://snipboard.io/gnmvAa.jpg
I don’t recommend this method at all
As I mentioned above:
– The best way is to use the EXE mentioned above to validate
– Use Content Library Explorer – https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/the-content-library
It’s always a bit tricky
Have you enabled content validation on your DP on a schedule https://snipboard.io/q3rbH7.jpg
I had a post long back but it’s not much valid for a new content library
https://www.anoopcnair.com/configmgr-sccm-hash-mismatch-issue/
Don’t try HashDIR.exe, that won’t work for CB version…
smsdpusage.exe is the one you can use with SCCM CB https://snipboard.io/1PQHnC.jpg
Content validate is not enable.
Any way to compare with working dp and not working dp…
Any others steps for this.
Only way is enable classic package share and
compare the size of the source and DP folder …
it should be absolutely equal .
I recommend the tool mentioned above