on 03-25-2008 3:50 PM
Hello All,
My sender system is CRM system.
When I use smq2 Tx. I see many queues in sysfail state.
How to solve it
Thanks
Hi Rick
we face this problem everyday and this is a known problem for us
After transaction SMQ2
follow these steps
1) double click on the queue name which is in sysfail status. in the next screen under status text right click on the red field and in the pop down menu execute LUW or press F6
if you get a warning function module does not exist or any exception raised then double click on the red text which should be like "XI restart in qrfc not allowed "
then you will be directed to the message which would be in error and due to that message in error this inbound queue is in error
Now click on that message and restart that message after that message will be successful then your queue will be successful
some times message inside queues are in error due to CLIENT RECEIVED FAILED
check the service is up or not you may check this service by pinging in transaction SM49
hope this may solve your problem
regards
Sandeep
Ps if helpful kindly reward points
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check this
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
.
JAVA Stack:
Go to Runtime Workbench--->Message Monitoring. Select either Integration Server or Adapter Engine, give the appropriate Sender business system, Sender interface, Sender namespace, Receiver System, Receiver Interface, Receiver namespace and click Start.
All status messages display. Here you should select the error messages and click on 'Resend'.
2. ABAP Stack.
SXMB_MONI, should select error message. From Edit menu click on "Reschedule XML messages after Error" or "F6"
3. Report.
RSXMB_RESTART_MESSAGES is the report to resend the error messages automatically.
Edited by: Ashok Reddy Thatigutla on Apr 14, 2008 7:45 AM
Edited by: Ashok Reddy Thatigutla on Apr 14, 2008 7:46 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
When you find SYSFAIL follow the below procedure and you cal solve your problem:
Reprocessing Sysfial procedure here below:
Go to transaction SMQ2 and Just click Execute (F8).
In the normal situation, you should not see any entries at the inbound queues.
In an error situation, you will find entries at the screen, indicating at the message processing in the inbound queues is either slow or stopped.
Click on a specific queue and view the entries at this specific queue.
Click again at the queue name to see the entries of this queue.
Please take special note of the status text.By clicking at the queue name a third time, you will be forwarded to the actual message and can further investigate there.
Steps:
1.) Go to SMQ2 (qRFC monitor) and then execute
2.) If there is a queue not moving, double click on queues til you see the status. SYSFAIL due to error move to the right to see the error text
If error is due to cache not refreshed:
1.) Go to transaction SXI_CACHE and check if CACHE is not up to date. In this case, CACHE contents are up-to-date
2.) If CACHE is not up to date, click Refresh before refreshing the cache just in case someone else already did it. If still not up to date, click Start Delta Cache Refresh in XI Runtime Cache.
3.) Then, go back to SMQ2. Unlock the queue that is in SYSFAIL. To do this:
a.) Choose the queue that is in SYSFAIL.and then click unlock
4.) Then, double click in the queue name til you go to the user.
5.) Double click on the user to go to the message in error.
6.) Select the one in error
7) click restart and refresh to to see if the message will be processed successful.
8.) Then, click F3 or back til you go back to the queues. Now, the queues are running.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
try to release the queue and refresh it ....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Double click on the Queue name...and there u will find the Staus text that shows what is the error.....if u want to check in moni then double click on the status check.....it will take u to SXMB_MONI....check the error....if u want any help post it....
Regards,
Phani
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Rick:
If you press recycle symbol in SMQ2 is not really delete the queue, it only reset the queue, it is same as the running the report I posted.
The other option is that you can cancel the message that blocked your queue, check the weblog:
How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
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
Liang
Hi Rick,
no, you can't delete the messages (if it is a production system) unless you find out, what caused the problem and which data must be re-sent.
So first, go to SMQ2 and click everything you can (queues, items..) until you'll see an error message, which causeed the problem.
Did you find any?
Peter
hi
go to SM58 and see te error
if you can not solve it, post the error to help you
Thanks
Rodrigo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.