adamf Posted March 21, 2011 Posted March 21, 2011 After wrestling with SCCM trying to be Adobe CS3 Master Collection to deploy silently, I have finally got it working from within the OS but when I included it as part of an OSD task it fails to install with error code 0x80091007 or "The hash value is not correct". The only fixes I have found from googling is to update the package in the DP, remove and re-add the package to the DP or completly remove the package from SCCM, re-create and re-add to the DP. None of these have worked. Does anybody have any ideas?
Theblacksheep Posted March 21, 2011 Posted March 21, 2011 After wrestling with SCCM trying to be Adobe CS3 Master Collection to deploy silently, I have finally got it working from within the OS but when I included it as part of an OSD task it fails to install with error code 0x80091007 or "The hash value is not correct". The only fixes I have found from googling is to update the package in the DP, remove and re-add the package to the DP or completly remove the package from SCCM, re-create and re-add to the DP. None of these have worked. Does anybody have any ideas? Are you waiting for the package to be removed (check status) before readding it?
adamf Posted March 21, 2011 Author Posted March 21, 2011 Yep. I waited until the package was removed and the re-added it.
tarquel Posted March 21, 2011 Posted March 21, 2011 Yep. I waited until the package was removed and the re-added it. Did u actually check that the directory on the DP(s) had gone? i.e. not just go by what SCCM was telling you. Have you queried the logs to see more detail on why its failing? either directly by using the F8 command line within the boot image [assuming u have enabled that] or by looking at the logs via the Advertisement of the OSD TS. Cheers
adamf Posted March 21, 2011 Author Posted March 21, 2011 Yep, checked to see if it had gone. This is what I am getting from the smsts.log The hash value is not correct. (Error: 80091007; Source: Windows)]LOG]!> I've just created a new task sequence in case something in that is not working.
adamf Posted March 21, 2011 Author Posted March 21, 2011 I created a new task and I am still getting the same error.
Theblacksheep Posted March 21, 2011 Posted March 21, 2011 Are the files downloaded locally and run from the client or run from the DP? running from the DP may prevent the files ending up mismatched when on client. The other trick is refrsh DP then immediatly update DP.
adamf Posted March 21, 2011 Author Posted March 21, 2011 Are the files downloaded locally and run from the client or run from the DP? running from the DP may prevent the files ending up mismatched when on client. The other trick is refrsh DP then immediatly update DP. Normally the content is downloaded, I am just about to try accessing it directly. I've already tried the refresh/update trick.
oxide54 Posted March 21, 2011 Posted March 21, 2011 are you following distmgr.log on the server when you refresh? be careful opening the DP directory in windows explorer, it may create desktop.ini files or thumbnail files which then make the hash invalid.
adamf Posted March 22, 2011 Author Posted March 22, 2011 I've refreshed/updated the package and you can see this happening in the distmgr.log on the server - everything complete fine. When running the task and having the content accessed directly I am still getting the same error. Are there any logs on the server that contain the hash of the package so I can cross reference it when the hash in the smsts.log on the client?
oxide54 Posted March 22, 2011 Posted March 22, 2011 have you checked this link? (iBoyd) » SCCM: Content downloaded to the client does not match the content specified in the content source Binary Differential Replication & Hidden files
adamf Posted March 22, 2011 Author Posted March 22, 2011 Just had a look run dir /s /a:h on the source directory that the files are copied from and there are no hidden files. Binary differential replication is not enabled on this package.
tarquel Posted March 22, 2011 Posted March 22, 2011 Just to get more info.... How are you deploying this as part of the OSD TS? via Collection Variables or via Install Software install in your TS? (or some other way) Are you running SCCM Natively or in Mixed Mode? Quite the puzzler tho... Also, is your DP the same or different server as your site server? Is BITS and associated services running correctly? I seem to recall that after a recent update - possibly R3 or some hotfixes - while everything was working correctly as far as current packages went, when i went to update them, things werent working as expected, for no apparent reason. Cant remember exactly what it was offhand, but I did have to remove the BITS Server Extensions (in the 2008 Features list) from the DP server (or might have been site server), reboot, install it again, reboot, and help / poke SCCM's services until things were working again. I did read that rarely, this can fail for no reason and something like the above is the cure, but take with a pinch of salt Nath
adamf Posted March 22, 2011 Author Posted March 22, 2011 Just to get more info.... How are you deploying this as part of the OSD TS? via Collection Variables or via Install Software install in your TS? (or some other way) Are you running SCCM Natively or in Mixed Mode? Quite the puzzler tho... Also, is your DP the same or different server as your site server? Is BITS and associated services running correctly? I seem to recall that after a recent update - possibly R3 or some hotfixes - while everything was working correctly as far as current packages went, when i went to update them, things werent working as expected, for no apparent reason. Cant remember exactly what it was offhand, but I did have to remove the BITS Server Extensions (in the 2008 Features list) from the DP server (or might have been site server), reboot, install it again, reboot, and help / poke SCCM's services until things were working again. I did read that rarely, this can fail for no reason and something like the above is the cure, but take with a pinch of salt Nath We are deploying the packages using the "Install Software" part of the TS. SCCM is running in Mixed Mode The DP is on the same server as the site server BITS appears to be running correctly as I can download and install the problem package from within the OS after advertising it. It's only when it is part of the OSD TS that it causes a problem. I haven't installed R3 yet.
hofsteda Posted March 25, 2011 Posted March 25, 2011 check the web server logs on the dp point for errors from that client. I've seen the appconfig in IIS cause some strangeness like this. I would expect all installs to fail though, not just osd ones.
adamf Posted March 28, 2011 Author Posted March 28, 2011 Am I looking for anything specific in the logs? Here are a few lines which look to me like everything is working as expected: 2011-03-24 10:19:32 10.59.100.47 GET /SMS_DP_SMSPKGC$/RC10006D/application.xml.override - 80 CURRICULUM\Administrator 10.59.99.109 SMS+TS 200 0 0 0 2011-03-24 10:19:32 10.59.100.47 GET /SMS_DP_SMSPKGC$/RC10006D/deployment/application.xml.override - 80 CURRICULUM\Administrator 10.59.99.109 SMS+TS 200 0 0 0 2011-03-24 10:19:32 10.59.100.47 GET /SMS_DP_SMSPKGC$/RC10006D/deployment/install.xml - 80 CURRICULUM\Administrator 10.59.99.109 SMS+TS 200 0 0 11 2011-03-24 10:19:32 10.59.100.47 GET /SMS_DP_SMSPKGC$/RC10006D/deployment/installtryout.xml - 80 CURRICULUM\Administrator 10.59.99.109 SMS+TS 200 0 0 7 2011-03-24 10:19:32 10.59.100.47 GET /SMS_DP_SMSPKGC$/RC10006D/deployment/uninstall.xml - 80 CURRICULUM\Administrator 10.59.99.109 SMS+TS 200 0 0 14 2011-03-24 10:19:32 10.59.100.47 GET /SMS_DP_SMSPKGC$/RC10006D/deployment/uninstalltryout.xml - 80 CURRICULUM\Administrator 10.59.99.109 SMS+TS 200 0 0 8 2011-03-24 10:19:32 10.59.100.47 GET /SMS_DP_SMSPKGC$/RC10006D/install.xml - 80 CURRICULUM\Administrator 10.59.99.109 SMS+TS 200 0 0 8 2011-03-24 10:19:32 10.59.100.47 GET /SMS_DP_SMSPKGC$/RC10006D/Media.cab - 80 CURRICULUM\Administrator 10.59.99.109 SMS+TS 200 0 0 238
adamf Posted March 31, 2011 Author Posted March 31, 2011 I've now tried changing the location of the source files (after deleting the current package from the DP and then completly removing it from SCCM) - this hasn't solved the problem either. I've got 2 support incidents from my technet subscription. Does anybody think it is worth using one, or are MS going to say it's a 3rd party problem..
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now