Skip to end of metadata
Go to start of metadata

Purpose

The purpose of this wiki is to provide details on where to open a message if you are seeing outbound or inbound queues in SMQ1 or SMQ2.

Overview

This wiki will detail what status SYSFAIL means when used in outbound and inbound processing and how to find the correct component to help troubleshoot the issue.

Meaning of status SYSFAIL

Note 378903  provides details on status SYSFAIL.  

For Outbound:

SYSFAIL

A serious error occurred in the target system while the first LUW of

this queue was executed. The execution was interrupted. When you

double-click on this status, the system displays an error text. You can

find additional information on this error in the corresponding short

dump in the target system (transaction ST22). No batch job is scheduled

for a repetition and the queue is no longer processed. Information from

the affected application is required to solve the problem. Refer to note

335162 for the special error text "connection closed".

For inbound:

SYSFAIL

A serious error occurred in the target system while the first LUW of

this queue was executed. The execution was interrupted. When you

double-click on this status, the system displays an error text. You can

find additional information on this error in the corresponding short

dump in the target system (transaction ST22). No batch job is scheduled

for a repetition and the queue is no longer processed. Information from

the affected application is required to solve the problem. Refer to note

335162 for the special error text " connection closed".

 

How to find the relevant application?

So, as per note 378903  in both cases the application needs to be involved.

To find the relevant component area check the function module used in SMQ1 or SMQ2.

To do this, check the queue that is in status SYSFAIL: 



Double click on the Queue Name and the function module is shown:

You can then check the application component responsible for the function module  - in this example the function module is /WSCGMBH/C_ENGINEER_UPDATE_RFC.

To check the application responsible goto transaction SE37 and enter the function module used:


  

Choose "Goto" in the menu and then click Object Directory entry:

   
 

From the next screen click on the Package:



 
 
Afterwards you will see the Application Component responsible:
 
 

 
 
In this example the related Application component is CS-SE.

In some cases the function module may not exist on the sending side . In this case check the function on the target system (SE37  - Goto  - Object Directory entry).

If you need help from SAP as to why Queues are in status SYSFAIL please open a message with SAP using the component area found as per instructions above. 

Related Content

Related Documents

Related SAP Notes/KBA's

378903  Queue status in SMQ1, SMQ2 and table ARFCRSTATE

335162  Error "connection closed" in tRFC/qRFC monitors