on 03-31-2008 2:30 PM
Hi all,
I have the following Scenario r3 send to an intgration process and this process send to a
fileadapter.
Sometimes I have the problem that the step process to file will be stopped (I see it in the
message display tool)
Does someone know whats the reason for this?
Thanks for help in advance.
Alex
Alexander:
You can check what error cause the problem first:
SXMB_MONI, get the queue number. e.g.
XBTR0008
Run T-Code: SMQ2, locate the stucked queue name, double click on it, you probably see the error, e.g. SYSFAIL or other error.
Click on the error, you will know the detailed error description.
If the error is caused by race condition (e.g. database access issue due to load), then you can click on the queue name, you will see all the messages stucked in the queue, just click on the first message on the queue (usually the message block the queue), re-start the message, usually the race condition does not exist, you will see message processed.
If the message is caused by non race condition, you might need to fixed it first and restart the message again.
Also check the XI : How to Re-Process failed XI Messages Automatically
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
and
SAP Note 1118927
Liang
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi
check the queue . because if the number of message in the queue then it somtime not forwarding the file
refresh the queue ather wise delete all the messages which are in queue
i hope its helpful for you
thanks
Regards
vijay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Alex,
Stopped means-Does it got stucked in the queue?
raj.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> the message is insert in the queue and then it get the status hold!
Hi,
If it is in hold state then try to find out if any old message for your scenario is in system error under RWB ---> Message Monitoring. If yes then cancel all message which are in system error state and try to resend the hold message again from message monitoring.
Regards,
Sarvesh
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.