LoadSaveReportException with CRRuntime_32_bit_13_0_2 on Windows Server 2008R2/IIS 7.5

[Former Member]

Hi,

I have a problem displaying Crystal Reports 13 in our ASP application hosted by IIS on Windows 2008R2.   I installed CRRuntime_32_bit_13_0_2.msi but on a newly installed Windows Server 2008 R2 with IIS 7.5 I get the following exception:

TypeInitializationException: The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception.

LoadSaveReportException: An error has occurred while attempting to load the Crystal Reports runtime. Either the Crystal Reports
registry key permissions are insufficient, or the Crystal Reports runtime is not installed correctly. Please install the appropriate Crystal Reports
redistributable (CRRedist*.msi) containing the correct version of the Crystal Reports runtime (x86, x64, or Itanium) required. Please go to
http://www.businessobjects.com/support for more information.

The runtime as well as application was installed using Administrator account.  Also, the application is configured to use IIS application pool with support for 32 bit enabled and our application is compiled to run in 32 bit environment. I don’t see any obvious problems when using Process Monitor.  Any help would be appreciated.

Dariusz

[former_member183750 · Accepted solution]

Is the server 32 or 64 bit?

Do you see the CR assemblies in the GAC?

What directory do you see the CR runtime installed in?

C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86

or

C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win64_x64

- Ludek

[Former Member · Accepted solution]

Hi Ludek,

It is 64 bit Server and yes I can see Crystal assemblies in the GAC. The CR runtime got installed into

C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86.  Hope this helps.  Any ideas?

Dariusz

[former_member183750 · Accepted solution]

Ok. If we trust the error, it's either a runtime issue or a permissions issue. Does not look like a runtime issue, so let's take a look at permissions;

Download Process Monitor. Filter it for your process / app name and run the app. See what the Process Monitor logs tell you re permissions.

- Ludek