Skip to Content
0
Jul 08, 2020 at 06:38 PM

Getting error on Server but not on Development Machine

78 Views Last edit Jul 10, 2020 at 02:13 PM 3 rev

On my local development machine I am able to run my application just fine, whether in debug or running the executable from the command line. However, when I deploy the executable to the Server I get the following error:

CrystalDecisions.Shared.CrystalReportsException: Load report failed. ---> System.Runtime.InteropServices.COMException: The document has not been opened.

I have checked that all paths and permissions are good. Is this a version discrepancy issue?

On my local I have:

  • CrystalReports version for Visual Studio - version 13.0.24.2970
  • CrystalReports runtime engine for .NET Framework (64 bit) v. 13.0.24.2970
  • CrystalReports runtime engine for .NET Framework (32 bit) v 13.0.1.220

On the server I tried installing the same, but we do not have visual studio installed on the Prod server, so I can't use the same install tools I used on my local which have been provided by my company - the CR for VS install included the 64 for my local install: CRforVS_13_0_24.exe

So instead on my Server I have:

  • CrystalReports runtime engine for .NET Framework (32 bit) v 13.0.1.220 (same as local)
  • CrystalReports runtime engine for .NET Framework (64 bit) v. 13.0.5.891 (lower version than local)

Is this version difference with the 64 bit the source of my issue? How can I find the correct version to download the 13.0.24.2970 without Visual Studio ( I assume I don't need to install VS on the Server to get this to work). I have been going around in circles looking for the msi version for CrystalReports runtime engine for .NET Framework (64 bit) v. 13.0.24.2970. Any help or suggestions are much appreciated!

UPDATE: I was able to find the download for CRRuntime_64bit_13_0_24.msi Once I installed that on the machine I was able to run my application with no problem. It took me over a week to track down this issue, so for anyone else getting the error I had, best bet is a version descrepancy between your dev machine and the deployment server.