SAP Knowledge Base Article - Public

3108674 - xerces-x_3_2.dll uses char16_t to represent the wide characters (XMLCh) in Crystal Reports for Visual Studio does not use it.

Symptom

We need to migtare our product from Crystal Runtime for .NET framework from SP21 to the lattest SP 31.

So I downloaded the latest runtime for 32 bit from SAP, but it doesn't work for us and I will tell you why:

Looks like from SP26 Crystal runtime was migrated to use xerces-x_3_2.dll, it was using 3_1 previously.

The problem is that in our windows process we use also another third party that loads a build of Xerces that uses char16_t to represent the wide characters (XMLCh) used in Xerces. So whicheverer tool loads xeces first(Crystal or the other TP) will be able to wirk with it, and the second will fail.

We need CR runtime and the other TP in the same process, we can not create new processes.

The other TP claims that they need char16_t and we agree with them, char16_t is also the default way that Xerces build is done.

Environment

SAP Crystal Reports, Developer for Microsoft Visual Studio

Cause

This component is used by core components and requires a rewite of those dependencies

Resolution

This issue has beed escalate to R&D for a fix possibly in CR for VS SP 33, no release date set for this SP.

Keywords

cr for vs, xerces-x_3_2.dll, char16_t , KBA , BI-DEV-NET , BI Software Development Kits (SDKs) - .NET or Other , Problem

Product

SAP Crystal Reports, developer version for Microsoft Visual Studio