SAP Knowledge Base Article - Preview

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.


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 xerces first(Crystal or the other TP) will be able to work 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.



SAP Crystal Reports, Developer for Microsoft Visual Studio


SAP Crystal Reports, developer version for Microsoft Visual Studio


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

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.