/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
Sudden halt in the generation of Inbound IDocs. The issue persists despite a restart of the Message Broker component and the use of the latest version. Additionally, the following lines can be found in the Message Broker's log file:
|
{TIMESTAMP} ERROR [proaxia.e4c.msgbrkr.CloudTransporter.Impl.TransporterAdapter] <{FSM_ACCOUNT_NAME}> Exception while starting cloud transporter, transporter will not operate Transporter.Exceptions.TransporterException The SSL connection could not be established, see inner exception. ... caused by IOException Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. |
Read more...
Environment
SAP Field Service Management
Product
Keywords
FSM, Proaxia, Inbound idocs, idocs not generated, message broker, ERP, PACG , KBA , CEC-SRV-FSM-ERP , FSM Connector for SAP ERP , 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.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)