We are looking into this and will provide an update shortly.

I tried installing Crystal Reports 2016 SP5 and it did not cause any problems with Report Commander. I'm not able to install Business One to see if that's the issue. Perhaps Business One is installing an older version of the Crystal Reports runtime; that would break Report Commander.

The quick solution is to uninstall and reinstall Report Commander, then make sure that doesn't break your Crystal Reports or Business One installation.

Otherwise:

Look in "C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\dotnet". If CrystalDecisions.CrystalReports.Engine.dll that's there, what's the file version?

If it's not there, look in "C:\Windows\assembly". What version is there?

Please save the attached "projecteditor.txt" to the Report Commander program folder and rename it to "ProjectEditor.exe.config". Then start the Project Editor and see if it works. This should tell it to use the newer version of the runtime that's installed--though that should already be happening automatically, so I'm not sure what's going on.

Thanks. That fixed it :-)

I will save that file in case I need it again. Do you think this will be included in a future build?

You'll need to copy the file to "projectrunner.exe.config", "adcrutil.exe.config", and "commandlinebuilder.exe.config" as well; otherwise those programs will have the same problem.

The issue here is that either Crystal Reports or Business One installed a newer version of the Crystal Reports runtime than what Report Commander is expecting. Because of the way the runtime pieces fit together it may not be possible for us to deal with the problem other than through the config files, which we can't push out to everyone because we can't know what version of the runtime any user will have. We will be looking into this further though.

Bill wrote:

You'll need to copy the file to "projectrunner.exe.config", "adcrutil.exe.config", and "commandlinebuilder.exe.config" as well; otherwise those programs will have the same problem.

Make that "adrcexec.exe.config", not "projectrunner.exe.config".

I made all of the above changes but I still get this when trying to run the report:

I also tried reloading the report within the project and got this:

Another weird thing is the preview button is missing from the output group properties screen:

The Preview button is missing because the Project Editor detected that Crystal Reports isn't available to run the report (due to the other problems).

We're going to have to do some more research on how to resolve the version mismatch issues.

Please go to Control Panel > Programs and Features. What version(s) of the SAP Crystal Reports runtime engine are listed? 32-bit or 64-bit?

32-bit:

 

I've installed the same CR runtime version that you had (13.0.22) and reproduced your original problem. On my test computer the updated config files solved the problem and allowed the export to work.

(Actually the config file needed one change to make the Preview work within the Project Editor--new version is attached.)

The error message you're getting now indicates that there's a problem with the runtime component installation, so let's try reinstalling that: uninstall "SAP Crystal Reports runtime engine", then download the installer here and reinstall it.

 

I replaced the file but the preview button was still missing, but after reinstalling the runtime it seems to be working now. Thanks so much for all your help!