2002903 - Some objects fail with No SAX Parser is available error during UMT migration | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2002903 - Some objects fail with No SAX Parser is available error during UMT migration

Symptom

  • During migration with the upgrade management tool (UMT), some of the objects, mostly seen of the type " universe connections " fail with an "No SAX Parser is available" error.
  • While several other objects in the same batch migrate successfully from the BOE XI 3.1 system to BI 4.0 SP6 system, universe connections seem to fail with this error
  • The issue is seen to occurs on one of the BI servers running the UMT while it seems to be working on another BI server.
  • The object log simply indicates the failure detail as "No SAX parser is available" as shown in the snapshot below -

    UMT_sax_error.png
  • The UMT traces indicate the following error for each failure -

    com.crystaldecisions.xml.serialization.XMLObjectSerializer||No SAX parser is available
    org.xml.sax.SAXException: Can't create default XMLReader; is system property org.xml.sax.driver set?
     at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:156)
     at com.crystaldecisions.xml.serialization.XMLObjectSerializer.<init>(XMLObjectSerializer.java:101)
     at com.crystaldecisions.xml.serialization.XMLObjectSerializer.<init>(XMLObjectSerializer.java:65)
     at com.businessobjects.sdk.plugin.desktop.DataConnection.internal.DataConnection.getConnectionAttributesXMLString(DataConnection.java:88)
     at com.businessobjects.sdk.plugin.desktop.DataConnection.internal.DataConnection.prepareForSerialization(DataConnection.java:125)
     at com.crystaldecisions.sdk.occa.infostore.internal.InfoObject.writeReplace(InfoObject.java:2628)
     at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:1027)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1115)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at com.businessobjects.sdk.biar.om.internal.db.ObjectRecord.toByteArray(ObjectRecord.java:361)
     at com.businessobjects.sdk.biar.om.internal.db.ObjectRecord.setObject(ObjectRecord.java:155)
     at com.businessobjects.sdk.biar.om.internal.db.AnnotatedObjectStore.newRecord(AnnotatedObjectStore.java:700)
     at com.businessobjects.sdk.biar.om.internal.db.AnnotatedObjectStore.newRecord(AnnotatedObjectStore.java:684)
     at com.businessobjects.sdk.biar.om.internal.ObjectManager.packRecord(ObjectManager.java:628)
     at com.businessobjects.sdk.biar.om.internal.ObjectManager.update(ObjectManager.java:548)
     at com.businessobjects.sdk.biar.om.internal.ObjectManagerAdaptor.update(ObjectManagerAdaptor.java:316)
     at com.businessobjects.sdk.plugin.desktop.common.internal.migration.MigrationDestination.update(MigrationDestination.java:122)
     at com.businessobjects.migration.engine.internal.MigrationEngine$WorkerFactory$Worker.performUpdate(MigrationEngine.java:801)
     at com.businessobjects.migration.engine.internal.MigrationEngine$WorkerFactory$Worker.performUpdate(MigrationEngine.java:687)
     at com.businessobjects.migration.engine.internal.MigrationEngine$WorkerFactory$Worker.performUpdate(MigrationEngine.java:677)
     at com.businessobjects.migration.engine.internal.scheduling.Scheduler$Engine.run(Scheduler.java:296)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:662)
  • The UMT generated .CSV file does not have any significant log entries on the failed objects

 


Read more...

Environment

SAP BusinessObjects BI Platform 4 and above  [ Upgrade Management Tool ]
Windows Server 2008 R2

Product

SAP BusinessObjects Business Intelligence platform 4.0 ; SAP BusinessObjects Business Intelligence platform 4.0, feature pack 3 ; SAP BusinessObjects Business Intelligence platform 4.1

Keywords

BI 4.0 4.1 4.x  3.1 UMT upgrade migration move universe conn connections error failure fail , KBA , BI-BIP-UMT , Upgrade management tool , BI-BIP-INS , Enterprise (BI platform) installation, upgrade, patching , Problem

About this page

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

Search for additional results

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