Skip to Content

Crystal Reports crashes when displaying reports - 32-bit runtime was wrong.

I just downloaded and installed the latest version of Crystal Reports for VS 2010 vs 22. I did this because Visual Studio was hanging, so I ended up deleting the SUO files. Once this was done, Visual Studio no longer hangs, but all of my settings were gone. I restored the settings but DataSets no longer were editable as it claimed that it was unable to initialize the Windows CE SQL Server Driver or the MySQL driver, neither of which I am using. Deleting those from the registry of Data Providers seemed to fix the problem.

However, Visual Studio no longer recognized .rpt files as editable, so I installed the latest version of the designer. After re-installing the latest version of Crystal Reports I was no longer able to view reports - Visual Studio crashed. I finally figured out that the re-installation had installed a 64-bit version of the run-time but not the 32-bit version. Re-installing that fixed the problem, although for some reason, all of my database connections in the Database Expert now need to be reloaded.

Suggestion for product development, when installing VS design environment, also install 32-bit run-time for debugging support.

Thanks, Neil

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Apr 23, 2018 at 10:15 PM

    Hi Neil,

    You did it all wrong, CR for VS .exe installs the 32 bit runtime then you get an option after it's installed to install the 64 bit runtime.

    I think what you need to do is first uninstall the 32 bit runtime MSI package, then repair Visual Studio and then repair CR for VS.

    Also read the info for SP 21 on the download WIKI page, make sure all your CR references are 13.0.3500.0

    If that doesn't work need more info on the OS you are using.

    Does a new Project work, add CR viewer 3500 version to the Tool bar.


    Add comment
    10|10000 characters needed characters exceeded

    • Hi Don, viewing a report in VS 2010 is working now, after I upgraded the 32 bit version to the latest release. I think the mis-match was causing the problem.