- You find that the communication channels like IDoc_AAE/File/SOAP fail with the following error in Communication Channel Monitoring:
"Processing error = Connection IDoc_AAE_http://sap.com/xi/XI/System is currently not started."
- Moreover, the log like Connection IDoc_AAE_http://sap.com/xi/XI/System is currently not started could be found in default trace.
- In addition, as per KBA 1662269 How to Monitor the PI Adapter Framework queues, you find that some queues in Additional Data Tab of Engine Status are missing, for example:
IDoc_AAE_http://sap.com/xi/XI/SystemRecv -> Missing
IDoc_AAE_http://sap.com/xi/XI/SystemRqst -> Missing
- You have also checked the KBA 1890225 "Connection xxx is currently not started" error in Channel Monitoring, but it still doesn't work.
- PI Release Independent
- SAP NetWeaver
- SAP Process Integration
Communication Channel monitoring, Engine Status, Safe mode, messaging.connectionDefinition, queue, Additional Data Tab, Engine Status, Process Integration 7.0, PI 7.0, PI 7.01, PI 7.02, Process Integration 7.10, PI 7.10, Process Integration 7.11, PI 7.11, Process Integration 7.30, PI 7.30, Process Integration 7.31, PI 7.31, Process Orchestration 7.40, PI 7.40, PO 7.40, Process Orchestration 7.50, PI 7.50, PO 7.50, NetWeaver, XI , KBA , BC-XI-CON , Connectivity , Problem
About this pageThis 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.