com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Invalid destination reference encountered (destination is null)

Oracle Community | User503744 | 1 year ago
  1. 0

    JCoIDocServer with own DestinationDataProvider not working

    Stack Overflow | 4 days ago | Peter
    com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Server SAP_DEST_TestSap_server does not exist
  2. 0

    Sap Input step invocation always creates *.jcoDestination property file in current working directory. This file contain all SAP connection properties (including plain password!). properties are written to output as buffered stream. Since it is buffered, after closing a stream it may happen, content is not physically written yet. In the code those properties are again read from that file. In case the file is not completely saved yet, you receive following exception: {noformat} com.sap.conn.jco.JCoException: (101) JCO_ERROR_CONFIGURATION: Initialization of repository destination SAP connector failed: Parameter ABAP application server host ('ashost') is missing at com.sap.conn.jco.rt.RfcDestination.getSystemID(RfcDestination.java:1018) at com.sap.conn.jco.rt.RepositoryManager.getRepository(RepositoryManager.java:29) at com.sap.conn.jco.rt.RfcDestination.initRepository(RfcDestination.java:968) at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:1079) at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:34) {noformat} It makes no sense to write those properties to a file and read them from the same file immediately, while you have them in memory already. It would be much more feasible to use data in memory instead. Current approach using file is creating another security issue, while saving plain passwords.

    Pentaho BI Platform Tracking | 1 year ago | Tomas Ganaj
    com.sap.conn.jco.JCoException: (101) JCO_ERROR_CONFIGURATION: Initialization of repository destination SAP connector failed: Parameter ABAP application server host ('ashost') is missing
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

  4. 0

    SAP Connector Troubleshooting // MuleSoft Documentation

    mulesoft.com | 2 days ago
    com.sap.conn.jco.JCoException: (101) JCO_ERROR_CONFIGURATION: Server configuration for sapavalara-1.0-SNAPSHOT-gettax is already used for a running server
  5. 0

    Sap Input step invocation always creates *.jcoDestination property file in current working directory. This file contain all SAP connection properties (including plain password!). properties are written to output as buffered stream. Since it is buffered, after closing a stream it may happen, content is not physically written yet. In the code those properties are again read from that file. In case the file is not completely saved yet, you receive following exception: {noformat} com.sap.conn.jco.JCoException: (101) JCO_ERROR_CONFIGURATION: Initialization of repository destination SAP connector failed: Parameter ABAP application server host ('ashost') is missing at com.sap.conn.jco.rt.RfcDestination.getSystemID(RfcDestination.java:1018) at com.sap.conn.jco.rt.RepositoryManager.getRepository(RepositoryManager.java:29) at com.sap.conn.jco.rt.RfcDestination.initRepository(RfcDestination.java:968) at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:1079) at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:34) {noformat} It makes no sense to write those properties to a file and read them from the same file immediately, while you have them in memory already. It would be much more feasible to use data in memory instead. Current approach using file is creating another security issue, while saving plain passwords.

    Pentaho BI Platform Tracking | 1 year ago | Tomas Ganaj
    com.sap.conn.jco.JCoException: (101) JCO_ERROR_CONFIGURATION: Initialization of repository destination SAP connector failed: Parameter ABAP application server host ('ashost') is missing

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.sap.conn.jco.JCoException

      (106) JCO_ERROR_RESOURCE: Invalid destination reference encountered (destination is null)

      at com.sap.conn.jco.rt.AbapRepository$DDICHelper.queryFunctionTemplate()
    2. com.sap.conn
      AbapRepository.getFunctionTemplate
      1. com.sap.conn.jco.rt.AbapRepository$DDICHelper.queryFunctionTemplate(AbapRepository.java:1826)
      2. com.sap.conn.jco.rt.AbapRepository.queryFunctionTemplate(AbapRepository.java:1033)
      3. com.sap.conn.jco.rt.AbapRepository.queryFunctionTemplate(AbapRepository.java:612)
      4. com.sap.conn.jco.rt.AbapRepository.getFunctionTemplate(AbapRepository.java:874)
      4 frames
    3. com.ibi.sap30
      SapAdapter20.process
      1. com.ibi.sap30.SapFunctionCacheManager.getFunctionTemplate(SapFunctionCacheManager.java:68)
      2. com.ibi.sap30.SapConnection.getFunctionTemplate(SapConnection.java:256)
      3. com.ibi.sap30.DocumentRunner.processIfrDocument(DocumentRunner.java:192)
      4. com.ibi.sap30.SapAdapter20.inProcess(SapAdapter20.java:384)
      5. com.ibi.sap30.SapAdapter20.process(SapAdapter20.java:292)
      5 frames
    4. com.iwaysoftware.af
      ProxyAdapter.process
      1. com.iwaysoftware.af.container.adapter.ProxyAdapter.process(ProxyAdapter.java:138)
      1 frame
    5. com.ibi.afjca
      IWAFInteraction.exec
      1. com.ibi.afjca.cci.IWAFInteraction.execProcess(IWAFInteraction.java:238)
      2. com.ibi.afjca.cci.IWAFInteraction.exec(IWAFInteraction.java:145)
      2 frames