ShockWave Player deployment fails error 0x80091007 RRS feed

  • Question

  • Hello,

    we are trying to deploy the last version of Adobe ShockWave (, using an Application in SCCM 2012 R2 CU3.

    We have previously done the same with versions, and (newer ones supersede the older), and we did never have a problem.

    On some workstations (W7SP1x64) the new application fails to install with the following Deployment Status:

    Category: "Failed to locate content"

    Error Code: 0x80091007

    Error Description: "The hash value is not correct."

    We are pretty sure that the content on the server is correct; moreover, if we launch manually, on the workstation, the MSI file from e.g. "C:\windows\ccmcache\x", the installation is successful.

    The problem happens on some, not all, the workstations, indipendently from the DP from where they get the content. All the workstations have (hopefully...) the same OS and software.

    It is noteworthy that the cache dir (in the example, "x"), is the same dir where there was the MSI file of the previous version: SCCM doesn't create a new dir as it does usually, but updates the old dir with the new content. In some cases, deleting/renaming the "x" dir causes SCCM to download again the MSI file and install it successfully.

    Is it, as we guess, a problem caused by the fact that the application, and its previous versions, use a MSI file with the same name ("sw_lic_full_installer.msi"), even if the content source dir is different? On this basis, we are trying to rename this file ("sw_lic_full_installer_12.1.4.154.msi") and update the DPs, and will post the result as soon as possible.

    In the meantime, any insight will be welcome and truly appreciated.

    Kind Regards

    Saturday, December 6, 2014 3:34 PM

All replies

  • Hello,

    as we guessed, SCCM now has created on the workstation a new cache folder for the new application,and then copied there the new MSI file, which installs correctly. This is the cache content as of now:


    06/12/2014  15:39    <DIR>          .
    06/12/2014  15:39    <DIR>          ..
    12/11/2014  17:15        24.253.952 sw_lic_full_installer.msi
                   1 File     24.253.952 byte


    06/12/2014  16:35    <DIR>          .
    06/12/2014  16:35    <DIR>          ..
    12/11/2014  17:15        24.253.952 sw_lic_full_installer_12.1.4.154.msi
                   1 File     24.253.952 byte

    Problem solved, it seems; but... was it our fault (some bad flag on the App wizard?), or is it a bug in SCCM?

    It seems that one can't make and deploy two distinct Applications where the MSI file name is the same... or maybe the problem is that one supersedes the other?

    Any clue will be appreciated.

    Kind Regards.

    Saturday, December 6, 2014 3:56 PM