Symptom
When connecting an SAP Java Connector(JCo) to an SAP AS ABAP system, following error is perceived:
com.sap.conn.jco.JCoException: (180) JCO_ERROR_DESTINATION_DATA_INVALID: Destination <Destination Name> was changed. Refresh the destination instance with the JCoDestinationManager |
Note: As a consequence, the client process has to be restarted every time, so it gets processed in SAP ABAP system.
Read more...
Environment
-
SAP Netweaver AS ABAP release independent;
- Java application using standalone SAP JCo 3 library.
Product
Keywords
DestinationDataProvider, JCO_ERROR_DESTINATION_DATA_INVALID, JCO, Java conector, Standalone JCo, Refresh the destination instance, com.sap.conn.jco.JCoException, (180), JCO_ERROR_DESTINATION_DATA_INVALID, Destination <Destination Name> was changed, Refresh the destination instance, JCoDestinationManager, connector, standalone, JCoDestination.isValid, , KBA , BC-MID-CON-JCO , Java-Connector , 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.