search

rainforestnet / CrystalReportsNinja

A small Windows Console App that loads external Crystal Reports file, takes parameter inputs and export to various format or even print to printer
http://www.rainforestnet.com
96 stars 78 forks source link

CrystalReportsNinja Error #57

Open Boem1 opened 3 years ago

Boem1 commented 3 years ago

Hi, I'm using an application that requires a newer runtime version: 13.0.26.3348, so when I'm trying to install the version 13_0_20, the installer asks to uninstall the existing version. As I cannot do this, I tried to launch the CrystalReportsNinja, but I got the attached error: "Could not load file or assembly Crystaldecisions.CrystalReports.Engine Version 13.0.2000.0 ..." Did this error appear due to the incorrect CR runtime version ? If so, is there a way to solve it ? Thanks a lot for your support. Error

mhertzfeld commented 3 years ago

Regarding the application you are using. Could you use a newer version of the runtime than 13.0.26.3348? Most of the time the runtimes are backwards compatible with the apps that use them (not always). If so, my fork uses version 13.0.28. You could try that by uninstalling the version 26 runtimes and installing 28 or later.

Or download the rainforestnet source and compile it with version 26. I don't think you'd get any errors when compiling.

Boem1 commented 3 years ago

Ok, I'll ask the application provider to confirm that 13.0.28 will work. If not, I'll compile with version 26. Thanks a lot for your support !

Mr-JakeMan commented 3 years ago

Regarding the application you are using. Could you use a newer version of the runtime than 13.0.26.3348? Most of the time the runtimes are backwards compatible with the apps that use them (not always). If so, my fork uses version 13.0.28. You could try that by uninstalling the version 26 runtimes and installing 28 or later.

Or download the rainforestnet source and compile it with version 26. I don't think you'd get any errors when compiling.

I am having the same problem as @Boem1 When editing the version number in the xml and then replacing the DLL's it asks for the enterprise DLL's, then once compiled it fails to work with a NO_INTERFACE error when we try to run it. I have tried your build but the version is too new (we are on crystal runtime 13.0.2500, our app is incompatible with new versions) Am I changing the version number incorrectly?

mhertzfeld commented 3 years ago

You need to uninstall CR for VS and the runtimes, install the version of CR for VS and the runtimes you want. then on whatever computer your running from make sure the correct version of the runtimes are installed. also pay attention if you are using x86 or x64 as they have separate runtime installs.

no need to remove the DLLs or mess with the XML as VS should recognize whatever version you have installed on your build machine.

Mr-JakeMan commented 3 years ago

You need to uninstall CR for VS and the runtimes, install the version of CR for VS and the runtimes you want. then on whatever computer your running from make sure the correct version of the runtimes are installed. also pay attention if you are using x86 or x64 as they have separate runtime installs.

no need to remove the DLLs or mess with the XML as VS should recognize whatever version you have installed on your build machine.

I gave this a try on a fresh machine however without dll pointing the references are not found despite the correct runtime being installed, when manually pointing to the CrystalDecisions DLL files without XML edits it returns :

1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2123,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "CrystalDecisions.CrystalReports.Engine, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. So it is still looking for 13.0.2000.0 without the XML edits, VS doesn't seem to recognize the build at all automatically.