why is the crystal runtime for 64 bit not working?

[former_member594930]

So we installed crystal runtime for 64 bit on our dev server, application is being run in 64 bit mode , the application is not working. why is that?

The app is referencing the old versions of the following dlls-

CrystalDecisions.Shared.dll,CrystalDecisions.Crystalreports.Engine, CystalDecisions.ReportSource

Do I need to add these in 64 bit on my dev machine , build and then deploy the new app or should the old app with new runtime work?

[DellSC · Accepted solution]

Pulling the .dll files from nuget won't get you what you need - they need to be installed because there are registry settings that need to be updated and COM objects that need to be registered. If you look at Control Panel >> Programs and Features on the server, which SP of the runtime is installed (look at the name to get the SP, not the version number!) If you to to the same place on the developer workstation, which SP of the SDK integration with Visual Studio is installed? These SP numbers must match - it has nothing to do with the "bit-ness" of the program.

Also, when you correctly install either the VS integration or the runtime, the assemblies are registered in the GAC so that your program can find them no matter where they are installed.

-Dell

[former_member594930 · Accepted solution]

Thanks. We tried adding reference to the version 13 .0 (Our current one was from 11.0) and it worked.

The runtime minor versions were different (runtime 13.0.23 and the DLLS from Developer version are from 13.0.0.35 - I know its far behind. But it worked, our pre-approved software repository has only old versions, I got the latest I could find). The dev version from SAP website matches no doubt , but has to go through official approval.

[DellSC]

"The app is referencing the old versions of the following dlls-"

This may be your problem. The version of the runtime that you're using MUST match the version of the SDK on the dev machine. Bit-ness doesn't matter, but the version/service pack of the SDK does, as does the OS that you're installing onto.

There is an option as part of the VS integration install on the dev machine to install the 64-bit version as well as the 32-bit version. DO NOT install any of the runtimes on the dev machine.

See https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads for more information about versions of the SDK and what they'll work with.

-Dell

[former_member594930]

Thanks, I believe that I had checked that our server o/s (2012) is matching the right runtime version. The 64 bit one, which we installed.

Since there are no folders containing the Crystaldecisions.engine.dll,etc. We copied these from a nuget package version 13.0.5 and added these as reference.

It still gave us the error.

The next step we'll try is install CR for VS 2017 in my dev machine and select the 64 bit versions. Will this give us the right library?

Once we get this we will try transferring these to the server - option 1, or rebuild and redeploy with the new assembly references- option 2. What do you think?