Custom Crystal Report Error when launching from Sage 300 Desktop

[vbdbcoder]

Hello,

I have a custom Crystal Report for Sage 300 v2018. It has been working in v2016. We just did an upgrade.

The report works in Crystal Report Designer on the same App server as the Sage 300. Once I tried to launch the report directly within Sage desktop, I got an error message of "Crystal Report Windows Forms Viewer: Unspecified error".

I look at C:\Windows\Assembly\ folder, I see 3 versions of CrystalDecisions.CrystalReports.Engine file: 1)11.0.3300.0; 2)13.0.2000.0; 3)13.0.3500.0. I know for a fact that Sage 300 is using 13.0.2000.0. And I have a customization that requires 13.2.3500.0. Sage Crystal Report can print and the customization can print. Now only the Crystal report file launched within Sage Desktop does not print.

Any pointer is highly appreciated.

Regards,

 

[DjangMan]

It would be possible to create a manifest file for Sage to force it to use a particular version of Crystal. Misys is finding that they have to do this due to Sage 2019 and HRMS also uses a different version of Crystal and so a manifest is required, I believe.