SYSFAIL in SMQ2 in Device Reassignment Queues

Dear SUP developers,
Device Reassignment Queues(Pattern: DOE_Q_*) got failed in SMQ2 with error
"Exception occurred due to http communication failure"
in Function module "SDOE_ESDMA_EXECUTEQOS".
I didn't find any related dump in ST22.
Please help me to resolve the issue.
lakshman balanagu.

SUP server is not reachable from DOE.
Please check following things.
1. Check whether address provided while deployment of the bundle in SUP is correct or not? The information will be in sup-db.xml file.
2. If yes, Then check whether IP is reachable or not?
3. If yes, check whether port provided is reachable or not?
Regards,
Siva.

Similar Messages

Sysfail locks smq2 queue

Hi,
We are live with our PI7.1 system as of 11/6 and are seeing serious issues when a data error causes a sysfail for a SMQ2 queue. At this point the queue is locked for further processing. We have monitors setup which page us for this situation. However, we really need to prevent the queue from locking so other messages are sent even when one item is in sysfail status.
Notes 813209 and 1118297 do not seem to offer any help is this situation.
Is there a way to prevent the queue from locking due to sysfail status messages?
Any help is greatly appreciated.
Regards,
Rick Taylor

Rick,
Check out this blog..
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417500)ID1371322850DB11715461650132929943End?blog=/pub/wlg/2728
"For automatic qRfc failure recovery, schedule the report RSQIWKEX to run periodically. This report enables automatically resets the queues. "
I remember there is a way to put error messages in different queue so that current queue wont b lock anymore...I'll check and let you know.
Hope this will help.
Thanks,
Nilesh

How to debug XI--- R/3 (abap server proxy) code, SYSFAIL in SMQ2

Hi
i have a XI (BPM) to R/3 (ABAP server proxy) scenario,
when the data goes from XI to R/3, it is getting stuck at R/3 inbound queue (SMQ2), with status : SYSFAIL and error text: "No roll storage space of length
3391496 available for internal storage",
we tried activating the queue/ reexecute the LUW, but it still shows the same error status after running for some time,
how can i debug the ABAP server proxy,
pls tell me how can i debug the ABAP proxy code in the R/3
very critical issue

Have a look at SAP Note 17965 - No storage space available
Regards,
Prateek

Why i can't use SMQ2 to monitor inbound queue?

i modified BP data in ECC. There should be R3AD_CUSTOMExxxxxxx(BP number) in inbound queue, but i can't find that.

Helo,
There would be queue entry waiting in R3AD_CUSTOME* queue only if you have de-registered this queue in txn:SMQR.
Or else this queue entry would get processed automatically.
Have you checked the BDoc in txn:SMW01to see whether detla changes from ECC is coming to CRM?
Best Regards,
Shanthala Kudva.

SYSFAIL error SMQ2 during initial load of PLANTs

Hello Everyone,
We are on CRM50 and during the process of the initial download of plants not all plants were replicated. Now we are attempting another load using DNL_PLANT and getting the following error:
Business partner ##1 does not exist. I have not seen this error before and I am not sure how to proceed.
Thanks in advance for your help.
Cheers
Wiktor

Hello Tiest,
That did not seem to be the issue. I went through and validated the load objects and there was some new configuration in the sales area which I moved over. All other objects loaded correctly.
When I executed DNL_PLANT got:
Not all address numbers have yet been issued.
More confused then before. Any other thoughts?
Thanks for the help!
Cheers
Wiktor

How to work with SYSFAIL in Queues

Hi
I am working on monitoring part, when the messages are sturcked in the queue with a queue status of SYSFAIL.
How can we handle this. How to process the failed message as well as blocked messages in the queues.
Thanks,
Ram

Hi Ram,
You can do one simple thing...jus goto SMQ2-> click on the queue-> select the queue name with sysfail error--> unlock it and refresh.
if it not works for you thn do the following....
1. To be able to initiate processing of messages stuck in the queue, make sure to set following IS configuration parameter
MONITOR QRFC_RESTART_ALLOWED to value 1
2. For automatic failure recovery, schedule the report RSQIWKEX to run periodically. This report enables automatically resets the queues.
Regds,
Pinangshuk.

Sysfail queue: queue stopped

i have some scenarios runnnig in my system, some scenarios are failing due to queue STOP,
when i click the queue name from the MONI, it shows that three queues namely XBTI007, XBTI003, XBTI004 are in SYSFAIL status,
when i cllick those queues, i find some 1000 entries in each of the queue,
the topmost entry shows that qRFC SXMS_ASYNC_EXEC failed due to
reason: COMMIT/ROLLBACK error on "DEFAULT" database connection...
there are many scenarios getiing stuck but i could find that the a particular scenarios qRFC execution lead to the error,
but since all the scenarios are getting stuck ....
wat action can i take....
if i select the entry with sysfail status and activate the queue, will it hamper something...
will data loss happen??
pls help...its in production system

Dhar,
SMQ2 is for outbound queue and SMQ1 is inbound queue. If you are getting the messages into XI then check in SMQ1 for any errors in XI and if you are sending out from XI then see SMQ2. Check this help for some more information on this:
http://help.sap.com/saphelp_nw04/helpdata/en/76/e12041c877f623e10000000a155106/content.htm
Regards,
---Satish

Message Stuck in Queues SMQ2

Hi All.
    We are having a production issue where now and then, we have message accumulation which is visible in SMQ2. Messages accumulates upto 10000 in the queues. Most of the times the queues are outbound queues XBTO* and the status of the message is in "Scheduled for outbound processing".
    There are no regular patterns in them, in terms of, when it occurs.
   Any clue could be of great help.
Thanks
Vedavyas

Hi,
Regarding your error you just follw the below points:
if you face Blocked Queues (SYSFAIL), Incoming Messages are blocked then follow the steps
1.)     Go to SMQ2 (qRFC monitor) and 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.
If CACHE is already up to date as seen above, proceed to next steps.
3.)     Then, go back to SMQ2. Unlock the queue that is in SYSFAIL. To do this:
a.)     Choose the queue that is in SYSFAIL.
b.)     Click unlock icon
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 see if the message will be processed successful.
If error text is due to JCo failure (Java connector)
-     When J2EE is already up, do the following:
1.)     Just go inside the queue in error til you go to the user.
2.)     Double click on the user to go to the message in error.
3.)     Click/Choose the message in error (just going to the right for the error message, it is JCo failure related)
4.)     Restart   the message (retaining the trace level)
6.)     Check for the status of the XML if it is now processed.
7.)     Then, click F3 or back   til you go back to the queue in SYSFAIL.
8.)     Then, reset status of the LUW of the queue in SYSFAIL.
After that, it could be seen that queues are now in RUNNING status.
If helpful reward points pls
Thanks & Regards,
Venkata Nagesh B

Inbound-Queue SYSFAIL: SQL error in the database when accessing a table

Hi,
we send around 80 IDoc simultaneously, there 15 are stuck.
They all have SYSFAIL in SMQ2 with message: SQL error in the database when accessing a table
I already unlocked the queues and try to resend. Nothing happend!
I ran RSQIWKEX for the single queus but now there are new queues in Status SYSFAIL.
I already checked some entries in forum and blogs, but nothing worked out yet!
Can someone help?! it's urgent!!
br

Hi, well as mentioned i searched and found this already.
But in ST22 i got error concerning
Laufzeitfehler DBIF_RSQL_SQL_ERROR
Ausnahme CX_SY_OPEN_SQL_DB
So i guess it's something more serious.
Any more ideas?!
Can i simply delete the stucked queues and reporcess them?!
br

Running smq2 queues in debug mode

Hi,
Can anyone tell me how to successfully run an inbound queue in debug mode.
Following are the steps undertaken.
I locked the queue in SMQ1. The Queue is set to STOP state.
I then triggered an sBdoc flow into CRM.
I am expecting the sBdoc to be in an intermediate state, but to my surprise it is coming as Fully Processed.
At this point, setting Debug mode in smq2 and Unlocking the queue does not help me analyse the bdoc/process flow as the bdoc is allready processed.
Any inputs in this regard would be helpful.
Thanks & Regards
Ron.

Hi Ron,
Please check below blog, hope it helps u.
Regards,
Deven
/people/lokesh.aggarwal/blog/2008/02/27/debugging-crm-middleware--sales-document

In Bound queue status in SMQ2

Hi All,
i've created a customer in CRM and saved it.
i've filled all the mandatory fields and it should replicate to ECC.
i've checked in SMW01, BUPA_MAIN BDoc is in intermediate state ,then i went to SMQ2 in CRM to check the queue status it is in READY status then upon unlocking the queue and refreshing it moved to RUNNING status and cleared from the inbound queue.....then upon refreshing the SMW01 ,BDoc BUPA_MAIN moved from intermediate state to send to receiver status and customer replicated to ECC.
My query is whenever i create any CUSTOMER/LEAD the queue in SMQ2 should go to RUNNING status and get processed automatically, every time i'm clearing the queue in SMQ2 and refreshing the SMW01 to reliacate the customer to ECC.
Please suggest me if any configuration change i've to do for the automatic queue clearence.
i've cleared all the queues in SMQ2 , there are no queues in wait/failed Status.
Thanks,
Syam

Hi Rohit Sharma,
Thanks for the help it solved my query.
I have one more query ,
Now the customer replicated to ECC without manual clearence of the queue.
even though the customer replicated to ECC i have the BDoc state of the BUPA_MAIN BDoc type as 'Sent to receivers (not all have confirmed)' with yellow light.
BDoc state should change to 'Confirmed (fully processed)' upon successful replication to ECC like BUS_TRANS_MSG for Lead.
Please suggest on any configuration change has to be done for the above query.
Thanks
Syam

[Windows8&8.1] Print queues-Root Print Queue device will appear after idle

Hi All,
I found the device Print queues will auto appear after idle on windows 8 or 8.1 OS.
Does anybody know why? or any Hotfix can reference, thanks.

Hi,
For end user issue about OS, please consult on this forum:
http://answers.microsoft.com/en-us/windows
Regards,
Barry Wang
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

IDOC to IDOC queue blockek status shows green flag

Hi i' m doin an iDOcto idoc scenario.. in sxmb_moni the status flag is green...queue is blocked.. i tried activating the queue
it still shows sysfail...
this is the trace message... any problem with my design or the message passed.. or is it a queue problem if so how to handle
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">User: PI_RM_USER</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="1" type="T">Syntax-Check-Flag</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPDEC</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">system-ID = DIN</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PI_RM_USER</Trace>
<Trace level="1" type="Timestamp">2009-08-07T09:08:38Z CST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 80144FDD6C661DEEA0E63CA33DA20911</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC">
<Trace level="1" type="T">Queue name : XBTI0008</Trace>
<Trace level="1" type="T">Generated prefixed queue name =</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface COELEM.COELEM01</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
</SAP:Trace>
Edited by: Indudhar P.G on Aug 7, 2009 11:22 AM
Edited by: Indudhar P.G on Aug 7, 2009 11:22 AM
Edited by: Indudhar P.G on Aug 7, 2009 11:22 AM
Edited by: Indudhar P.G on Aug 7, 2009 11:23 AM
Edited by: Indudhar P.G on Aug 7, 2009 11:24 AM

HI,
Correctly said by Abhishek, click on Queue Id and then further selct the Queue and Click on details to see all the messages in that Queue. Select the First Message in SYS FAIL and try to restat that. If that again Fails. Don't delete the whole Queue but delete the selected message from Queue in Error. Then go Back and Unlock the Queue and refresh. All messages behind this message will re-process automatically.
SMQ1 and SMQ2 are tcodes foe Queues.
REgards,
Anurag

Smq2 - Password logon no longer possible - too many failed attampts

Experts,
I was working on a data initial load from ECC to CRM. But the status remains "Running".
And in smq2 I saw the queue with "SYSFAIL" with info "Password logon no longer possible - too many failed attampts".
But my user's not locked in either CRM or ECC.
Any suggestions?
Thanks a lot
Shane

Hi Shane,
Whenever there is data transfer between R/3 and CRM it happens via a DIALOG user.
Henceforth, We have to maintain the dialog user in both the CRM and the R/3 systems.
To check whether the user is a dialog user , goto the Tx. SU01 and type in the User maintained in the SM59 Tx for the Data Transfer.
Check the User Type - It has to be Dialog User, else change the user to Dialog User.
Secondly, the User sepcified for the Destination in the CRM system has to exist in R/3 system also and vice-versa.
Henceforth, check the existance of the user in the respective system.
For Example. In Tx :SM59 ,for the R/3 destination QWC505, If the Dialog user specified was TESTER1. Then login to R/3, goto Tx: su01 and check the user exists in R/3.
Thirdly, In Tx:SM59, After sepcifying the LOGON details for the respective destination,Check the following :
1. Click on the REMOTE LOGON Button
2. click on the CONNECTION Test Button.
3. Click on the UNICODE Test Button.
If all the above criteria's are met, Then there should not be any problem WRT to "Password logon no longer possible error in the queues."
i faced the same problem some time back, I was to able to troubleshoot the problem with the above information. Hope You will also be able to fix the probelm.
Best Regards,
Vignesh Ravikumar

Materials and Services stucked in SRM SMQ2

Hi there!
When changing or creating services and materials on ECC they are automatically transferred to SRM but they get stucked in SRM in transaction SMQ2. If I enter SMQ2 and activate the queue, the products in SRM are correctly generated.
Queue names: SRMD_MATERIA0000000000 /   SRMD_SERVICE_MASTER
How can I do to let them automatically being created into SRM without having to activate the queue? Is there a job missing?
Thanks
Eze

Hello,
You can check and read the following note:
872533 - Follow the steps mentioned in this note especially question number 1.
In the same note also follow the question number 7 and refer all notes mentioned there.
1072160
1102001
1112879
1115992
1156748
Also delete all R3AD* entries which contain SYSFAIL errors in SMQ1, SMQ2.
Kind regards,
Ricardo

SYSFAIL in SMQ2 in Device Reassignment Queues

Similar Messages

Maybe you are looking for