cancel
Showing results for 
Search instead for 
Did you mean: 

SMQ2 Error SYSFAIL

Former Member
0 Kudos

Hello experts

I have moved all the XI developments into Production and wanted to test one of the scenario , when i sent an IDOC to XU production

In SXMB_MONI i get a green flag , but has error in queue , when i checked SMQ2 it has SYSFAIL error .

The excat ERROR is "prefix number: entry missing for system XIP client 200."

It is a new XI installation , Is there any thing missing ?

You help is much appriciated.

Sudheer

Accepted Solutions (0)

Answers (8)

Answers (8)

Former Member
0 Kudos

Thank you

Former Member
0 Kudos

Hey,

You can set this value.

IS configuration parameter

MONITOR QRFC_RESTART_ALLOWED to value 1 in transaction SXMB_ADM

You can efer to this note: 987143

You can refer to this link.

/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

This will surely help you.

Former Member
0 Kudos

Hello,

Still you are facing the same problem or is it resolved..?

If you are facing same problem. As per the log prefix number for the client 200 was not maintained in XI system.

We can maintain prefix number in SWF_XI_CUSTOMIZING ,Here we can maintain prefix numbers for the client prefix numbers should be greater than 900.

This will resolves the problem.

Regards,

Ravi.

Former Member
0 Kudos

Double click on the SYSFAIL in the queue monitoring and check for the error message. you can activate the queue also for reprocessing. Also in ST22 you should able to see some abap dumps.

if u are getting "XI restart in qRFC not allowed"

In integration server administration SXMB_ADM, Integration engine configuration->specific configuration->there is a parameter for QRFC restart allowed or not.

and also

Refer to this thread:

note:reward points if solution found helpfull

regards

chandrakanth.k

vijay_b4
Active Contributor
0 Kudos

Hi Sudheer,

a) qRFC Errors

Often in asynchronous scenarios where inbound queues are used, the queues are set to SYSFAIL status and all the messages in the inbound queue are stuck (not processed). Depending on the status of XI processing queues, we can reset a queueu2019s status and trigger processing of messages.

Manual Resend of messages: Use transaction SMQR or SMQ2 to reset the status of queues. As you can see in the following figure, the queue has been marked with a status sysfail.

b) tRFC Errors

Like qRFC errors one can either manually or automatically initiated processing of messages hanged tRFC calls.

Manual Resend of messages: Use transaction SM58 and check through the list. If necessary, start hanging tRFC calls

under the Edit menu by choosing Execute LUWs.

For automatic tRfC failure recover, schedule the report RSARFCEX for periodic execution.

c) Other Errors

All the errors generated and captured in Integration engine can be viewed using transaction SXMB_MONI. Message that were sent asynchronously and had failed due transient system/configuration failures can be manually restarted in SXMB_MONI.

Reward points if this helps

Regards

Vani.

Former Member
0 Kudos

Hi,

Check this

/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

Regards

Seshagiri

Former Member
0 Kudos

Hi

Pls find the answer in above links.

Thanks,

RamuV

GabrielSagaya
Active Contributor
0 Kudos

1) You can use transaction codes SMQR and SXMB_ADM for queue status resetting.

2) use transaction codes SMQ1 and SMQ2 for deleting SYSFAIL files, and manually resending messages in the queues.(For activating queues in SMQ1 and SMQ2, you would need to first deregister them in SMQR or SXMB_ADM).

3)As a pre-requisite, the IS configuration parameter MONITOR QRFC_RESTART_ALLOWED should be set to 1.

/people/prashanth.azharuddin/blog/2006/11/24/some-errors-in-an-xi-production-environment