on 07-13-2017 6:16 AM
Hi Experts,
There is a Proxy-to-File (Async) scenario.The data generated by the reports from SE38,the ABAP queue (XBTS*Table) status when checked from SXI_MONITOR is showing as stopped.
After referring various blogs and SDN questions we tried the following from the ABAP side:
1)De-register and register the queue from sxmb_adm.
2)Clearing the queues from SMQ2.
3)Dump check in ECC.
From the PI side we checked the RFC destination in SM59 ,which is working fine(200 OK)
also we have cross checked whether we are using the appropriate Business System.
After doing all the above steps the messages are reaching SAP PI and getting stuck in ABAP queue.
Kindly suggest us some solution to overcome this problem.
P.S : Attached are the screenshots for reference.
Hi All,
The problem got resolved after we cleared the queues in SMQ2.
Thanks you
Sreyas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
From your screenshot, the messages are struck in the queue. You can move the failed message to SMQ3 through "Save LUW" and unlock the queue to allow the rest of the messages to pass through.
Regards
Bhagya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sreyas,
Try executing the LUW again to see if the queue gets processed.
You can schedule the report RSQIWKEX this will pick all the stuck entries and re-process them.
Try to clear the queues and then re-register the queue.
You can also try to debug the queue if that helps. (save the queue SMQ3 and try to debug it)
Regards,
Prithviraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
you can click on the Queue name and check the error details for more information related to struck messages.
Regards
Bhagya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Following screenshots will give a glimpse of problem.. as there are no errors given by queue
Going into queue we see this,
error2.png
Following status with retry in the queue,
err0r3.png
Marked report is for our scenario as " transaction recorded" with any error.
err0r5.png
Last screenshot says transaction recorded for that particular executed report.
Help us find the error.
User | Count |
---|---|
92 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.