SAP Knowledge Base Article - Preview

3197511 - Payload reaching the PI/PO Receiver Mail Adapter must be in a specific format for startTLS

Symptom

  • You are using the startTLS functionality in your Process Integration (PI) or Process Orchestration (PO) Receiver Mail Adapter.
  • You see your email is either blank or the attachments do not come up. 
  • The splitMainPayload parameter is also enabled as per SAP Note 2863754 Attachments are missing or corrupted when startTLS is enabled in Mail Receiver Adapter. 
  • You may find an error similar to below in the Communication Channel Monitor:
    Transmitting the message to endpoint <local> using connection AFW failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.sdk.xi.srt.BubbleException: Failed to call the endpoint  [null "null"]; nested exception caused by: com.sap.aii.af.sdk.xi.srt.BubbleException: Failed to call the endpoint  [null "null"]; nested exception caused by: com.sap.aii.af.sdk.xi.lang.BinaryIndexOutOfBoundsException: Binary index out of range: -1 


Read more...

Environment

  • SAP Netweaver 7.5.
  • SAP Process Integration.

Product

SAP NetWeaver 7.5

Keywords

Process Integration, PI, Process Orchestration, PO, NetWeaver, XI, AEX, startTLS, email receiver, attachment, payload, no attachment, not working, missing attachment, security, Office 365, SMTP , KBA , BC-XI-CON-MAI , Mail Adapter , 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.