headershadow

Monitor ERROR MESSAGES IN SOST (incoming and outgoing emails in SAP)

Print Friendly

If you have access to the transaction code SOST you can monitor incoming and outgoing emails in SAP.

Alternatively you could also use the following transaction codes:

  • SOIN      BCS: Inbound Send Requests (SMTP)
  • SOSG     Send Request Overview (Groups)
  • SOSB     Send Request Overview (Users)

By default SAP shows you the “outgoing emails” sent from SAP.

In the first tab “Period” you can define the period that you want to monitor.

In the Second tab “Send Status” you can choose to only show “Errors”.

If you take a look at such outgoing emails containing an error you will probably see many different error message types.

If you select such an email and press the “glasses”, you see more details:

On the tab “Recipient list” you’ll see the addressee and further below you will see the error messages:

If you click on the error message “No Delivery to xxx as recipient unknown” itself you see more technical details:

If we take a look at the most frequent error messages in our system we identify the following ones:

1. Message no. XS802

No delivery to xxx, as recipient unknown

This means the email address that was used in the field “TO” (recipient) is incorrect.

Potential causes:

  • The person you tried to email no longer works at a particular company and therefore the email address is no longer valid
  • You made a typo when manually entering the email address (and as such the email address is not valid)

Check: You can use free online services to check whether an email address is a valid one or not. Just do a simple Google search on “Email Validation

2. Message no. XS838

No delivery XXX due to problems with system resources

Cause: as far as I could see once again an invalid email address entered (wrong domain, or non-existing email address)

3. Message no. XS806

No delivery to XXX, invalid recipient address

Cause: Again, using the email validation tool I only could notice that the email addresses used were BAD (not valid).

4. Message no. XS812

No delivery to XXXX

As far as I could verify, most of the email addresses used were actually valid.

Actually you will see different “subtype errors” if you look at the details, such as:

  • 557 Syntax error
  • _550 Requested action not taken: mailbox unavailable550 responses typically mean either the users mailbox was unavailable at the time the message delivery was attempted or the mailbox doesn't exist. Try sending the message to the recipient again and see if you get a 550 error. If you receive a 550 message the second time then I would double check with the recipient to make certain that particular mailbox is still active and go from there
  • 554 delivery error: dd This user doesn't have a yahoo.com accountThis error message seems to be related to “auto forwarding” to a Yahoo account or the fact that there is a problem at that time with a Yahoo account itself.If someone registered with it before but hasn't used it for a while, yahoo disables that account and bounces back all emails sent there.
  • 554 5.4.6 Hop count exceeded - possible mail loopI found back some technical information about this, but rather technical:
    http://supportweb.ciaops.net.au/blog/archive/2012/06/29/hop-count-exceeded-possible-mail-loop.aspx

Other info found back was:

Why am I getting an "Exceeded Hop count" failure email?

Question Background:

Sometimes I get an exceeded hop count message when I send mail to external email addresses. I have looked at the headers of the message, and it seems to be looping on my mail server, why might this be?

Answer:
if the domain that you are sending the mail to has an incorrect MX record configured, this can cause the problem - specifically if they have an MX record configured to point to the IP address 127.0.0.1

In these circumstances, GMS will look up the address, and then connect to the 127.0.0.1 address to deliver the mail. Because this is the local host IP address, GMS connects to itself and delivers the email. This then results in the mail loop, and the error message "Exceeded hop count".

The problem does not lie with GMS, but rather with the remote server, and as such, you will need to contact the administrator of the remote server to inform them of the problem.

  • message size xxx exceeds size limit xxx of serverThis depends on the max message size in SMTP. This is in the System Admin settings under Protocol Settings
  • 510 5.1.0 User unknown.

5. Message no. XS802

The message from the node could not be delivered to recipient xxx as the recipient is unknown.

As far as I could verify, this message is also triggered for invalid email addresses that were defined as recipient address.

6. Message no. XS610

Currently no delivery to xxx, as transfer attempt failed

In these cases for some reason the mail could not be sent out yet. I have done several cases where I did perform a “Repeat Send” in SOST.

And then manually triggered the sending

In some cases the email get’s send out correct, in other cases the email will receive another error message (as this time the sending did work, and the feedback error message could be that the email address used is invalid).

7. Message no. XS612

Currently no delivery to XXX

I only had 1 error of this type, but was able to reprocess it, using the “Repeat send” option, and then trigger the sending manually.

8. Message no. XS832

Message in node cannot be processed due to authorization problem

Diagnosis

The node refused message processing.

Procedure

Use the troubleshooting programs of the node to examine the precise cause of the authorization problem. You may need to consult the SAP Hotline or the contact person for the communication system (node) you are using.

At this point I also managed to reprocess those emails, using the “Repeat send” option, and then trigger the sending manually. However, as the actual sending only takes place using the repeat send, once again you might encounter another error message.

 

9. Message No. XS722

Message could not be delivered, will try again later

Diagnosis

Despite several attempts, the message could not be sent to the recipient xxx@xxxx.

Further attempts will be made to send the message. Further status messages may be generated indicating whether the message was delivered or not.

System Response

Processing was completed as normal.

Additional information about the node used (in the system language of the node, if available):

Procedure

No action is necessary.

 

Remark:

you will see that the status sign is "grey" and looks like below:

 

What we have noticed in several cases, is that by performing a "repeat send" the issue got solved. HOWEVER; in several cases we have noticed that AFTER performing the repeat send was done, the status of the "send request" got changed into "XS073 communication send". Some time after this change, the status automatically got reset to "XS722" and in several cases the customer (receiver of the email) complained that he has received that particular email multiple times (I am talking about 20 up-to more than 100 times). We still face this issue at this point in some cases and are looking with SAP OSS Support into this matter.

So to be continued :-(

 

Davy has been working as an SAP Consultant since 2000 and started working in the SAP IS-U Module , but as of 2002 he has mainly worked as functional SAP CRM consultant and SAP Authorizations consultant.
More about

17 thoughts on “Monitor ERROR MESSAGES IN SOST (incoming and outgoing emails in SAP)


Comment author said

By Sunitha on 11 March 2013 at 14:11

Could you please let me know the reason for XS899 error msg in SOST

 

Comment author said

By Davy Pelssers on 11 March 2013 at 15:22

Hi,
the only thing I found back on this message type: XS899 - No information on delivery, status invalid - XS 899

Diagnosis
The message was processed successfully in the SAP system and transferred to the connected system. However, it was not possible to get information about the delivery to the recipient because the send status data that was returned had errors or was incomplete. It is not possible to tell from this data whether the message was delivered or not.

It really does not say much, but that's also the same for most of the other messages ...

 

Comment author said

By Manjunatha on 16 July 2013 at 23:58

The message has delivered to customer, but we got the message cannot be sent. how can we resolve this?

 

Comment author said

By Arun on 24 July 2014 at 15:27

I had encountered the error XS899 happens when multiple recipients (approvers) have the same email id maintained in their user master record (SU01)

I had initially maintained my only email id for multiple approvers for testing and got the error. Than I had maintained different email ids for all the approvers for the is mail notification and all of them now receive.
I realized the mail would only show once for this email id in the mail box. Also, the sap message give a vague hint in error --> "No information on delivery" may be for the same reason.

Just give a try from your end too.

Cheers
Arun

 

Comment author said

By Nilanjan on 26 June 2013 at 12:57

it seems that SAP is not able to smtp server . Please check the IP address of the SMTP server in SCOT .

 

Comment author said

By Vinay Biradar on 5 August 2013 at 12:57

Hi,

Could you please let me know if an email address entered has a typo or no longer valid, how do we delete or change the email address in the distribution list?

Thank you,
Vinay

 

Comment author said

By Davy Pelssers on 16 September 2013 at 20:52

hi
in SOST you can just delete the email (in error) that was send to that particular emailaddress...
but you can not change it...you will need to change the emailadres on the customer master record, and resend the email once again as far as I can tell.

 

Comment author said

By Bijoy Yohannan on 15 October 2013 at 09:33

Hello guys,

With regards to the message type 899, i went and saw the same technical documentation which was mentioned by davy.

This error could be happening because the recievers' server was busy or else(most likely) the outlook/lotus mailbox is full.

I tried reprocessing it after speaking with the end user and asked him to empty up his mailbox a bit, and this was transferred successfully.

 

Comment author said

By Monica Sanchez on 29 October 2013 at 18:38

Hi Bijoy,

How did you get to know that solution, did you search on a SAP Note or forum page?

I'm having the same issue and also I'm having this problem displayed in the status:

Internal error: SO_OBJECT_MIME_GET Excepción 2
Message no. XS829

Diagnosis
An error occurred in program SO_OBJECT_MIME_GET
Error text: Excepción
Additional information:
2

System Response
Message processing terminated.

Do you know what can cause this?

Regards,

Monica

 

Comment author said

By P Bansal on 18 March 2014 at 15:48

Hi Blogger,

It was an tremendously helpful document for day to day work.

We are trying to send email to vendors automatically, and built a program to support multiple scenarios. while doing that if email id is wrong, system technically fails the email with appropriate message in SOST. but in our dev client we have seen that if email is wrong system sends SBWP notification to the user who initiated the processing.
But it is not working in QA for while doing UAT.

Please advice how to activate it since non of our technical guys are able to support this issue.

Thanks in Advance.

 

Comment author said

By Sagata Das on 2 May 2014 at 16:31

Hi,

Please can you help me implemnet one of the scenarios.

We are monitoring SOST for the PO's that are send to vendor through fax. when there are failures we manually inform the BUyer that their PO has not been autofaxed to vendor by sending a mail to buyer.

Is there any way that this can be automated. That is when a faxing to vendor fails through SOST and automated mail will be sent to buyer notifying the buyer that the vendor has not recevied the fax.

 

Comment author said

By Davy Pelssers on 7 May 2014 at 11:49

Hi,
I am not sure if this is possible to be honest.
perhaps you can check with the BASIS consultant? They usually are pretty much aware of this kind of stuff like SOST.

cheers
D

 

Comment author said

By Arijit Dey on 8 May 2014 at 11:16

HI Davy,

Can we restrict the sender list to specific email id only for tcode SOST or SOSG?

if yes, how to do it?

 

Comment author said

By D on 19 June 2014 at 22:23

We currently monitor a job called ZSMTP_PRD_ALL for running time exceeding 90 minutes. The email is sent directly to our team, The threshold for alerting will be raised to 3600 minutes so jobs actually successfully run longer than that.

I have a requirement to monitor the number of errors being generated and I don't know if this can be done through Solution Manager

 

Comment author said

By vaishali on 6 June 2015 at 10:31

why msg incoming or outgoing not send or receive

 

Comment author said

By Vinod Tanwar on 27 April 2016 at 12:24

No delivery to email , invalid recipient address
Message no. XS806

Diagnosis
The recipient address Email was invalid or initial.

System Response
The action was terminated.

Additional information of the node used (in the system language of the node):
550 5.7.1 Unable to relay for Email id

Procedure
Specify a valid recipient of the object. The address 'email or address type '' you specified (no 'type' specification is equivalent to the SAP address) contains an error.

 

Leave a Reply


*