Skip to Content
avatar image
Former Member

CRRedist2008_x86 - no longer downloadable by PRQ (prerequisites) file?

FYI - I'm reposting this query from the original conversation thread at CRRedist2008_x86 - no longer downloadable by PRQ (prerequisites) file? (in case anyone wants the history).

We've just encountered a problem with downloading CRRedist2008_x86 as a setup prerequisite.

Our product includes CRRedist2008_x86.msi as a setup prerequisite downloadable from the web. We haven't had an issue with this previously, and probably haven't exercised it in some time. However, yesterday we did and it fails to download via Windows Installer, or directly from InstallShield via the prerequisites definition (i.e., .PRQ) file. I manually followed the URL in the prerequisities file and I was able to download it successfully that way (so the file is still there), but I noticed that the file size does NOT agree with that info in the prerequisites file.

Here is a snippet from the PRQ file we have been using:

<file LocalFile="C:Program FilesMicrosoft SDKsWindowsv6.0ABootstrapperPackagesCrystalReports10_5CRRedist2008_x86.msi" URL="" CheckSum="C931B3CBA27BA9289F502CB98CB2A5C8" FileSize="0,17964544"></file>


The above URL still exists and the MSI file is still there - but what is there now no longer agrees with the file info in the PRQ file - I don't know about the checksum, but I downloaded the file at the above URL and its size is different.

Please note that I am NOT simply looking for a URL to obtain the MSI file. The file at the above URL was a vendor provided download location, and I am using an associated prerequisites file which was tightly bound to the contents of that location (checksum and file size). Apparently the contents of the URL has changed and that is going to break every product installer previously built and distributed which references this URL via Windows Installer setup prerequisites; this should never have been changed.

So, options:

a) can the Vendor (now SAP) correct whatever has gone wrong with the contents at the above URL (i.e., restore the previous file which matched the prerequisites file specifications); or

b) provide a new prerequisites file (or file info) for the above URL; or

c) provide a new official download location and matching prerequisites file.

Option (a) is obviously the only one that will work for all existing product installers referencing the "old" location, and thus is preferable. Going forward (for new product installers) Option (c) gives the Vendor an opportunity to transition everyone to a new location - but it needs to be a permanent unchanging location (you can't changes things like this without breaking things for everyone who has already used it).


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Sep 23, 2008 at 11:04 PM

    Try this -

    - Backup your original MSI file from here C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\CrystalReports10_5\CRRedist2008_x86.msi

    - Download the file

    - Replace the C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\CrystalReports10_5\CRRedist2008_x86.msi

    - Rebuild your ClickOnce deployment package

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 23, 2008 at 11:26 PM

    That won't help - this is a setup prerequisite downloadable from the web at installation time. InstallShield builds a Setup.exe which includes references to setup prerequisites. This setup prerequisite is a download from the vendor web site. While the file is still located at the historical location (as specified in the PRQ file I have), it no longers matches the details in the PRQ file.

    Okay, one way I can "workaround" this is to not use the download from the web site and simply carry the file around in / with our installation package - at a cost of 18 MB for every copy of our installer 😔 . I'm loathe to do that.

    Another way I can "workaround" this is to revise my PRQ file to match the file at the download site. My issues with that are I'm not sure at the moment how to generate a checksum for the downloaded file, and if the download site has changed the file once it could be done again and I'm back in this boat again.

    I really would like Crystal (now SAP) to give us a guaranteed location (URL) for this type of download, along with the assoicated PRQ file, and guarantee it won't be changed again (assuming that is what has happened this time).

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 24, 2008 at 12:05 AM

    I think the reason to download it and place it in the directory Dave suggests is so that your local matches what is on the web.

    As for guarenteeing that this file will never change, this is something I do not think we can do as I believe it will be updated for service packs and hotfixes.


    Add comment
    10|10000 characters needed characters exceeded

    • Former Member David Hilton

      It looks as though the prerequisites file we have been using may be homegrown here. Since we are using the download location URL as a target for setup prequisites in our product installers, the file size/checksum info in the prerequisites file has to agree with the file at the download location. Since the contents of the download location have changed (in what manner I'm not even sure), in order to resolve this issue for our current development I have revised our prerequisites file to match the current version of the file at the download location.

      However, any existing product installers (built who knows how long ago) are all going to continue to fail. Hopefully, now that I have synched up our current development to the current contents of the download location, this won't change anymore.