Skip to end of metadata
Go to start of metadata

This page is part of the Sapconnect Interface Informations Guide

XS086 Function XCHGVERSION is not available

Solution:

Read SAP Note 308827 - Error message: XS086 Function XCHGVERSION is not available
As the message does not affect the SAP Internet Mail Gateway, you can ignore it.
In order to avoid the message in node maintenance deactivate the flag "Node supports: Connection test, status, trace".

XS612 Currently no delivery to RECIPIENT >> 452 4.3.1 Insufficient system resources

 >> 421 4.7.1 Recipient quota exceeded

Solution:

Read SAP Knowledge Base Article 2231130 - XS612 Currently no delivery to RECIPIENT
To resolve this issue please contact your mail server administrator and ask them to check the issue at mail server level.

XS702 "IN TRANSIT" status for fax

Solution:

Read SAP Note 821447 - Fax has 'in transit' status for XS 702
Implement the source code corrections using the Note Assistant.

XS806 No delivery to example@example.com, Invalid recipient address >> The recipient address example@example.com was invalid or initial (501 5.5.4 Invalid Address)

Solution:

Read SAP Knowledge Base Article 1955387 - Error XS806 "No delivery to ..., invalid recipient address" with long text message "501 5.5.4 Invalid Address" occurs while sending mail through SMTP

Please follow the detailed resolution steps.


XS816 
Message cannot be transferred to node SMTP due to connection error 

Solution:

Read SAP Knowledge Base Article 2547393 - Error message XS816 'Connection refused' for SMTP messages in SOST
Please follow the detailed resolution steps.

XS817 Error creating HTTP client object from URL

Solution:

Read SAP Knowledge Base Article 2238135 - XS817 error with text "Error creating HTTP client object from URL" occurs while sending SMS through HTTP node of SAPconnect interface

Maintain mandatory "Recipient Address" variable for the URL as follows:

  1. Call transaction SCON
  2. Under pager nodes (type PAG) double click on the used http node
  3. In the section "URL/Query" place the cursor on the place where recipient address should be entered (where SMS/Pager server requires it)
  4. Add missing SAPconnect variable by clicking on button "Recipient Address"

XS817 Cannot process message in SAP system >> No ESMTP is available for SAPconnect

>> SMTP Plug-In Not Available

Solution:

Read SAP Knowledge Base Article 1593121  Error XS817 with text "No ESMTP Plug-In is available for SAPconnect" occurs in transaction SOST while sending Mails through SMTP node
Please follow the detailed resolution steps.

XS826 Cannot process message; no node determined for RECIPIENT

Solution:

Read SAP Knowledge Base Article 2056291 - Error XS826 "Cannot process message; no node determined for..." occurs while sending in SAPConnect
Please follow the detailed resolution steps.

XS829 505 Authentication required

Solution:

Read SAP Knowledge Base Article 1829921 - Message no. XS829 505 Authentication required
To avoid this error message:

  1. In the Exchange Server / Connections / IMS properties page, there's a tab called Connections with a property called
    "accept connections". It is set to accept authenticated connections.
  2. On that tab - click on the "specify by host" button and create a specific definition for your Controller/Center node IP to be accepted
    without authentication.
  3. The scenario is for MS Exchange. If you are using Sendmail or any other mail server you will have to contact your mail adminstrator for instructions on how to setup anomymous connections from SAPConnect.

XS834 Message cannot be processed as it is not convertible

Solution:

Read SAP Knowledge Base Article 2312340 - XS834 - Sending email with ABAP list from job causes error in SOST
In order to solve this issue, assign the authorization objects S_SPO_DEV and S_DATASET to the job's user maintained.

XS835 Message cannot be edited, send data cannot be determined

Solution:

Read SAP Note 1614357 - Error XS 835 when sending SMS
Implement the corrections using the Note Assistant, or import the relevant Support Package.

XS848 No delivery to <Receiver> since message type is not supported

Solution:

Read SAP Note 1167588 - Status is not meaningful
Implement the corrections using the Note Assistant, or import the relevant Support Package.

SO004 Invalid combination of parameter values

Solution:

Read SAP Note 696215 - Cannot process message in SAP system
Implement the source code corrections in accordance with the correction instructions

SO596 Document changed due to security requirements

Solution:

Read SAP Knowledge Base Article 1813208 - Message "Document changed due to security requirements" (SO596) displayed and the HTML formatting ruined for an attachment
Switch off the filter function by changing the parameter HTML_FILTER_FOR_DISPLAY in the table SXPARAMS.

SO672 Still no entry in queue

Solution:

Read SAP Knowledge Base Article 1895298 - SO672 - Still no entry in queue
Check in the application you are using how e-mails are created.
It's mandatory to each application explicitly call COMMIT WORK, after the sending application has been called.

  • No labels