Skip to end of metadata
Go to start of metadata

Introduction

With SAP ECTR 5.1.16.0 and SAP ECTR 5.2.3.0 the new JCo 3.1 is used. In earlier versions JCo 3.0 has been used.  


Question or Problem

During start of ECTR using BackendConfig you get this error:

EN:

  • E00549 - Error when transferring from SAP system.
  • E00206 - The process has been canceled: Error at 'execute' transaction '/DSCSAG/DOC_CHECKOUT_URL2': Error while parsing bASXML document.
  • Error while parsing bASXML document
  • Unexpected token in parameter %_RFC_DELTA1 of the current BXML document: 'R' at position 460
    E02501 = No original available for document '...' . - Please check if the DTypes have been uploaded to SAP system.


DE:

  • E00549 - Fehler beim Übertragen aus dem SAP-System.
  • E00206 - Der Prozess wurde abgebrochen: Fehler beim 'execute' Transaktion '/DSCSAG/DOC_CHECKOUT_URL2': Error while parsing bASXML document.
  • Error while parsing bASXML document
  • Unexpected token in parameter %_RFC_DELTA1 of the current BXML document: 'R' at position 459
  • E02501 - Es ist kein Original für das Dokument '...' verfügbar. – Bitte prüfen Sie ob die DTypes ins SAP-System hochgeladen wurden.


Stack Trace in Log:

[E02990 - Document cannot be opened.]
  13:00:00  
    [Stack Trace]
    plm.omf.OmfDocOpenFast.openDocument(OmfDocOpenFast.java:980, C:\Program Files (x86)\SAP\ECTR\basis\classes\plm.jar)
...
      E00549 - Error when transferring from SAP system.
      [Stack Trace]
      cadagent.proc.doc.ProcessDocMultiCheckOutFast2._execute(ProcessDocMultiCheckOutFast2.java:201, C:\Program Files (x86)\SAP\ECTR\basis\classes\sapbase.jar)
...
        E00549 - Error when transferring from SAP system.
        [Stack Trace]
        cadagent.proc.doc.ProcessDocGetUrls._execute(ProcessDocGetUrls.java:157, C:\Program Files (x86)\SAP\ECTR\basis\classes\sapbase.jar)
        cadagent.proc.PLMProcess.execute(PLMProcess.java:517, C:\Program Files (x86)\SAP\ECTR\basis\classes\sapbase.jar)
...
          E00206 - The process has been canceled: Error at 'execute' transaction '/DSCSAG/DOC_CHECKOUT_URL2': Error while parsing bASXML document.
          [Stack Trace]
          cadagent.sap.conn.jco.tm.JcoSapManager.genericFunction(JcoSapManager.java:359, C:\Program Files (x86)\SAP\ECTR\basis\classes\sapbase.jar)
...
            E00206 - The process has been canceled: Error at 'execute' transaction '/DSCSAG/DOC_CHECKOUT_URL2': Error while parsing bASXML document.
            [Stack Trace]
            cadagent.func.jco.FuncGeneric.intern_execute(FuncGeneric.java:349, C:\Program Files (x86)\SAP\ECTR\basis\classes\sapbase.jar)
            cadagent.func.jco.FuncGeneric.execute(FuncGeneric.java:157, C:\Program Files (x86)\SAP\ECTR\basis\classes\sapbase.jar)
...
              E00508 - Error at 'execute' transaction '/DSCSAG/DOC_CHECKOUT_URL2': Error while parsing bASXML document.
              [Stack Trace]
              cadagent.sap.conn.jco.tm.JCOTransaction.execute(JCOTransaction.java:395, C:\Program Files (x86)\SAP\ECTR\basis\classes\sapbase.jar)
              cadagent.func.jco.FuncGeneric.intern_execute(FuncGeneric.java:311, C:\Program Files (x86)\SAP\ECTR\basis\classes\sapbase.jar)
              cadagent.func.jco.FuncGeneric.execute(FuncGeneric.java:157, C:\Program Files (x86)\SAP\ECTR\basis\classes\sapbase.jar)
...
                Error while parsing bASXML document
                [Stack Trace]
                com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:437, C:\Program Files (x86)\SAP\ECTR\basis\libraries\sapjco3.jar)
                com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.execute(MiddlewareJavaRfc.java:1814, C:\Program Files (x86)\SAP\ECTR\basis\libraries\sapjco3.jar)
...
                  Error while parsing bASXML document
                  [Stack Trace]
                  com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcReceive(RfcIoOpenCntl.java:2057, C:\Program Files (x86)\SAP\ECTR\basis\libraries\sapjco3.jar)
                  com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcReceive(RfcIoOpenCntl.java:2008, C:\Program Files (x86)\SAP\ECTR\basis\libraries\sapjco3.jar)
...
                    Error while parsing bASXML document
                    [Stack Trace]
                    com.sap.conn.rfc.engine.RfcImp.receiveBasXMLCompressedData(RfcImp.java:384, C:\Program Files (x86)\SAP\ECTR\basis\libraries\sapjco3.jar)
                    com.sap.conn.rfc.engine.RfcGet.ab_rfcget(RfcGet.java:363, C:\Program Files (x86)\SAP\ECTR\basis\libraries\sapjco3.jar)
...
                      Unexpected token in parameter %_RFC_DELTA1 of the current BXML document: 'R' at position 460
                      [Stack Trace]
                      com.sap.conn.jco.rt.BasXMLParser.parse(BasXMLParser.java:433, C:\Program Files (x86)\SAP\ECTR\basis\libraries\sapjco3.jar)
                      com.sap.conn.jco.rt.BasXMLParser.setCompressedBytes(BasXMLParser.java:1582, C:\Program Files (x86)\SAP\ECTR\basis\libraries\sapjco3.jar)
...


During work with ECTR you get this error:

[11:45:15.312] COM1T   [E02501 - Es ist kein Original für das Dokument '...' verfügbar. – Bitte prüfen Sie ob die DTypes ins SAP-System hochgeladen wurden.]
[11:45:15.312] COM1T     11:45:14  
[11:45:15.312] COM1T       [Stack Trace]
[11:45:15.312] COM1T       plm.proc.doc.checkout.PlmProcessCacheUpdate.checkAndRenameMasterFiles(PlmProcessCacheUpdate.java:694, D:\PDM\ECTR\basis\classes\plm.jar)
[11:45:15.312] COM1T       plm.proc.doc.checkout.PlmProcessCacheUpdate.performTransferDirect(PlmProcessCacheUpdate.java:521, D:\PDM\ECTR\basis\classes\plm.jar)
[11:45:15.312] COM1T       plm.proc.doc.checkout.PlmProcessCacheUpdate.performTransfer(PlmProcessCacheUpdate.java:470, D:\PDM\ECTR\basis\classes\plm.jar)





Causes

There exists an issue with the basXML delta manager of JCo 3.1.2 (See note 2947370 symptom 3).


Known Errors and Solutions

Switch off delta manager for JCo

Add this switch in file customize/config/saplogon.txt:

sap.transaction.deltaManagerEnabled=false

Apart from hardly noticeable performance losses when calling RFC function modules, this will have no other effects. Try this solution first.

Use JCo 3.0

You can replace JCo 3.1 with JCo 3.0 then the error should not occur. 

Use 5.2.3.1 / 5.1.16.2 (as soon as they are available)

These versions use JCo 3.1.3, where this problem is solved. (See note 2947370)




See Also