xercesc_3_2::RuntimeException Error while loading SAP crystal report 2016

[#1]

Persistent xercesc_3_2::RuntimeException when Loading Crystal Reports 2016 (32-bit) in MFC C++/CLI App (VS2019 32-bit)

Hello everyone,

I'm encountering a stubborn xercesc_3_2::RuntimeException when trying to load a Crystal Report (.rpt file) in my MFC C++/CLI application developed with Visual Studio 2019. I've tried extensive troubleshooting, and I'm hoping for some fresh insights, especially regarding this specific exception with matching bitness.

Problem Summary: When my MFC application calls m_report->Load(reportPath); (where m_report is a CrystalDecisions::CrystalReports::Engine::ReportDocument^ instance), an immediate Microsoft C++ exception: xercesc_3_2::RuntimeException is thrown. The debugger shows the exception originating deep within Crystal Reports' native components, likely during the XML parsing of the .rpt file.

My Environment:

• Development IDE: Microsoft Visual Studio Professional 2019 (Version 16.11.x, latest updates applied).

• Application Type: MFC Dialog-based application (C++).

• Managed Code Bridge: C++/CLI Wrapper project (CrystalReportsWrapper.dll) exposing a System::Windows::Forms::Control-derived class (CrystalReportHostControl) to host the Crystal Report Viewer.

• Target Framework: .NET Framework 4.7.2 (consistent across both MFC and C++/CLI projects).

• Crystal Reports:

  • SAP Crystal Reports, version for Microsoft Visual Studio 2016 (design-time component).

  • SAP Crystal Reports runtime engine for .NET Framework (32-bit) (Crucial: confirmed 32-bit installation).

[DonWilliams · Accepted solution]

What SP of CR for VS are you using?

You can get the latest from here:

https://help.sap.com/docs/SUPPORT_CONTENT/crystalreports/3354091173.html

Check the platforms support info also for supported OS's etc.

See my blog on upgrading your project:

Upgrading a Visual Studio 2008->2022 .NET project with the latest CR .NET SDK packages

Also note CR for VS runtime will only be 64 at the end of this year, time to upgrade your project 64 bit.

[anilraj202 · Accepted solution]

Thank you, Don. My application is a legacy C++/MFC MDI application that heavily relies on DAO and Crystal Reports 8.5. Unfortunately, due to architectural constraints and dependencies, it cannot be migrated to 64-bit at this time. Given this, I'm currently limited to using the 32-bit Crystal Reports runtime, and I understand that support for it is expected to end in December 2025. I'm exploring options for maintaining compatibility in the short term while planning a longer-term migration strategy. Any suggestions or shared experiences from others in a similar situation would be greatly appreciated.

[DonWilliams · Accepted solution]

WOW, using 8.5, it's amazing its been working this long. Nothing you can do to get past that error since 8.5 has no concept of current Os's or anything else.... You can use the latest CR .NET in a Managed C++ app. We had a sample but no idea where it is now...