Crystal Reports layout migration

[Former Member]

We are now trying to move a client to Win 10, and have a software package that will not load because of CR. I was unable to find a CR 13.0.35 Redist to allow it to load and a CR tech told me my old CR modules were not compatible with Win 10 anyway.

The desktop application was written in Visual Studio 17, and the last functioning CR version seems to be 13.0.35 (because there is a redirect in the config).

I knew I would have to upgrade the source code. I’m now using VS2019 but the source would not load to it! My client is in a hurry, so I downloaded Visual Studio 2017 and downloaded a new copy of CR designated for 2017 (hoping to get a compatible with Win 10 version and I did install “as admin”).I then pulled the source in.At least it runs, but I am having issues with CR.

Installed Version: Community

Visual C++ 201700369-60000-00001-AA815

Microsoft Visual C++ 2017

Application Insights Tools for Visual Studio Package8.14.20131.1

Application Insights Tools for Visual Studio

ASP.NET and Web Tools 201715.9.04012.0

ASP.NET and Web Tools 2017

First, there is a clause in the config file of the source that redirects from CR 13.0.20 to 13.0.35.That was causing “can’t resolve references to CR13.0.35”.

LOG: Redirect found in application configuration file: 13.0.2000.0 redirected to 13.0.3500.0.

LOG: Post-policy reference: CrystalDecisions.CrystalReports.Engine, Version=13.0.3500.0, Culture=neutral, PublicKeyToken=692fbea5521e1304

LOG: Attempting download of new URL file:///C:/Horizon/WSDC/WSDC_sm/WSDC_SM/bin/Debug/CrystalDecisions.CrystalReports.Engine.DLL.

WRN: Comparing the assembly name resulted in the mismatch: Build Number

ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.

I looked at the CR DLL’s and they are identified as 13.0.2600.

I altered the redirect clause in the config to:

<bindingRedirectoldVersion="13.0.2000.0"newVersion="13.0.2000.0"/>

(just removing the redirect doesn’t work!)

Once I made this change the code runs until I try to generate the report. The error is different.Now, it at least tries to pull in the CR report design file but promptly blows up.

LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.

LOG: Post-policy reference: CrystalDecisions.ReportAppServer.CommLayer, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304

LOG: Attempting download of new URL file:///C:/Horizon/WSDC/WSDC_sm/WSDC_SM/bin/Debug/CrystalDecisions.ReportAppServer.CommLayer.DLL.

LOG: Attempting download of new URL file:///C:/Horizon/WSDC/WSDC_sm/WSDC_SM/bin/Debug/CrystalDecisions.ReportAppServer.CommLayer/CrystalDecisions.ReportAppServer.CommLayer.DLL.

LOG: Attempting download of new URL file:///C:/Horizon/WSDC/WSDC_sm/WSDC_SM/bin/Debug/CrystalDecisions.ReportAppServer.CommLayer.EXE.

LOG: Attempting download of new URL file:///C:/Horizon/WSDC/WSDC_sm/WSDC_SM/bin/Debug/CrystalDecisions.ReportAppServer.CommLayer/CrystalDecisions.ReportAppServer.CommLayer.EXE.

A second clue:

In the VS design area, if I try to open the CR report layout, it can’t open it. I get the below.

Can someone clue me in to what I am facing here? How do I convert my old CR “stuff” to my new VS and CR environment? I have googled this and looked at CR forums, but solutions found have not shed light or worked.

[former_member11696 · Accepted solution]

Assembly version should be 13.0.4000.0

Remove and replace all of them in your project and update the web.config or app.config with the same 13.0.4000.0

[Former Member · Accepted solution]

THAT WORKED! Thank you so much. I can't tell you how grateful I am.

[Former Member · Accepted solution]

Another note: I had to do a lot of manual fixing to make this work. I removed the DLL's from the library manually. I then used "Add References" to reinstall the right ones. That didn't do it. I found that I had to manually edit the .proj file to set it to the right version, it still indicated the old one. That got rid of the new compile errors, but it still wouldn't render reports. I had to manually copy the CR DLL's from the bin/debug folder to the bin/release folder. Then, it worked.