2386821 - Error Cannot configure XML parser when loading Crystal report

SAP Knowledge Base Article - Public

2386821 - Error Cannot configure XML parser when loading Crystal report

Symptom

When attempting to load a report using RAS, the following error is thrown:

java.lang.RuntimeException: Cannot configure XML parser
at com.crystaldecisions.xml.serialization.XMLObjectSerializer.logAndReturnRuntimeException(XMLObjectSerializer.java:134)
at com.crystaldecisions.xml.serialization.XMLObjectSerializer.initSaxParser(XMLObjectSerializer.java:167)
at com.crystaldecisions.xml.serialization.XMLObjectSerializer.<init>(XMLObjectSerializer.java:125)
at com.crystaldecisions.xml.serialization.XMLObjectSerializer.<init>(XMLObjectSerializer.java:65)
at com.crystaldecisions.proxy.remoteagent.TCPIPCommunicationAdapter.connect(TCPIPCommunicationAdapter.java:181)
at com.crystaldecisions.proxy.remoteagent.CommunicationAdapterFactory.createCommunicationAdapter(CommunicationAdapterFactory.java:101)
at com.crystaldecisions.sdk.occa.report.application.ReportAppSession.createCommunicationAdapter(ReportAppSession.java:118)
at com.crystaldecisions.sdk.occa.report.application.ReportAppSession.initialize(ReportAppSession.java:328)
at com.crystaldecisions.sdk.occa.report.application.ClientDocument.initializeServerConnectionAdapter(ClientDocument.java:636)
at com.crystaldecisions.sdk.occa.report.application.ClientDocument.initializeServerConnection(ClientDocument.java:667)
at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.initializeServerConnection(ReportClientDocument.java:1417)
at com.crystaldecisions.sdk.occa.report.application.ClientDocument.open(ClientDocument.java:1011)
at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.open(ReportClientDocument.java:223)

Environment

  • SAP BusinessObjects Business Intelligence platform 4.0
  • SAP BusinessObjects Business Intelligence platform 4.1
  • SAP BusinessObjects Business Intelligence platform 4.2

Cause

This issue occurs when an incompatible version of the saxparser class is loaded by the JVM being used to run the application.

Resolution

To resolve this issue, ensure that the only jar files with the saxparser class in them are the supported SAP BusinessObjects jar files.  Specifically xercesImpl.jar and xml-apis.jar.   On a default windows installation of BOE Enterprise, they can be found in the folder:

<Install Folder>\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\lib\external\xercesImpl.jar
<Install Folder>\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\lib\external\xml-apis.jar

NOTE: Older versions of the SDK had the saxparser class contained in xerces.jar  When upgrading an application from a previous version, you should remove all jar files from the previous version and copy new ones in.  Just copying the jar files with the same name is insufficient.

Keywords

saxparser xml parser tcip serialize RAS OEM , KBA , BI-DEV-JAV , BI Software Development Kits (SDKs) - Java , Problem

Product

SAP Crystal Reports 2013