Skip to Content

the type initializer error while install the CRRuntime_64bit_13_0_21

Sep 24, 2017 at 06:51 PM


avatar image

I have installed CRRuntime_64bit_13_0_21 but I got error message "the type initializer for 'crystaldecisions.crystalreports.engine.reportdocument' threw an exception". To solve the problem, I uninstalled previous version of CR runtime. I had to delete the folder "SAP BusinessObjects". Again I installed the CRRuntime_64bit_13_0_21. This time report worked properly.

My system automatically install the CRRuntime. Due to this problem my system is not working properly. Is there any way to avoid uninstall previous CRRuntime and delete folder jobs. I want to just install the new version of CRRuntime that we did in previous versions?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Don Williams
Sep 25, 2017 at 02:26 PM

I changed the Tag to CR for VS.

No, you cannot have more than one version of CR for VS on the same PC.

The reason is SP 21 updated the CR assemblies to version 3500, minimum requirements is 3.5 Framework now.

With these updates the GUID's are new and the installer for some reason detects the change so it install SP 21 first and then uninstalls SP20 which of course removes all of the SP 21 files.

The only way to run the update is to first go into Programs and Features, uninstall any previous version of CR for VS and runtime packages and the run the CR for VS.exe on the DEV PC or the MSI on the work station PC.

Do NOT install the runtime on your DEV PC, no need to.

See the info in the download WIKI:


Show 2 Share
10 |10000 characters needed characters left characters exceeded

This is a huge issue for those that distribute the runtime with their application. End users should not have to uninstall previous version of the runtime before installing the application or have to repair after installation.

Also, stop blaming Windows Installer. The SAP employee(s) who created the installers really messed up. That is what it comes down to. SAP should re-release SP 21 after fixing these bugs in the installers.


Hi Eric,

I'm not blaming MS, Issue is new GUID's for the 3500 version changed the install order, MSIExec installs SP21 first because of the new GUIDS, then MSIExec uninstalls SP 20. I'm not sure if it's our issue or not...

Too late to update SP 21 now, Install team already said they would look into the issue in SP 22.

For Installation issues PLEASE see this KBA - 2536330 - In-place (FlexNet), MSI and Merge Modules upgrade from Crystal Reports for Visual Studio SP xx to SP 21 does not work

It's a huge platform change as well, no more dependency on VC 2005 C++ ATL runtime and now relies on VC 2015 C++ runtime. As everyone asked for and no more LegacyMode for crdb_net driver. Also updated usp10 to version 1.6 to fix some Ms updates for various fonts.

This Platform change will force all applications to be rebuilt, no way around it, possible work around is on the download WIKI page, use the CR viewer zip file attached, it redirects the old to new assemblies and should work for you.

Other option is don't upgrade to SP 21 and wait for SP 22.