Restart Queue in PI 7.1

hello everybody,
i have a silly question.
in my XI projects i scheduled jobs for restart messages locked using following report:
RSARFCEX
RSQIWEK
now i'm working with PI 7.1 but i don't find these reports.
Are there other solutions for restart messages?
Or Report's name is different?
thanks
Alex

I am also working on PI 7.1.
I am able to see in my system first program
RSARFCEX --> Execute Calls Not Yet Executed
Second program name should be :
RSQOWKEX --> QOUT Scheduler: Execution of Registered Outbound Queues
OR
RSQIWKEX - -> Standard QIN Scheduler: Execution of Registered Inbound Queue
These are available in PI 7.1.

Similar Messages

Restarting Queue not allowed in PI

Hi Felix,
You can use
RSQOWKEX --> QOUT Scheduler: Execution of Registered Outbound Queues
OR
RSQIWKEX - -> Standard QIN Scheduler: Execution of Registered Inbound Queue
These are available in PI 7.1.
Please see this Blog
/people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i
http://help.sap.com/saphelp_nw04/helpdata/en/25/bcfa40badbf46fe10000000a1550b0/content.htm

HI Felix,
If you double click on any Queue entry then you can see all the message entry inside that queue.
now click on the sysfail entry then it will take you to SXMB_MONI particular corresponding faile message.
then cancel the message.
Automatic Cancel:
Here you GO:
If in case of bulk error messages, all these error messages can either be cancel them manually by selecting these set of messages in SXMB_MONI and then cancel them by pressing button "Cancel Processing of Messages With Error" (CTRL+F8). or report RSXMB_CANCEL_MESSAGES is the tool of choice for mass data handling, i.e. for canceling a large set of messages. This report handles message that already are in error state.
SE38 -
>RSXMB_CANCEL_MESSAGES
If you cancel the message using RSXMB_CANCEL_MESSAGES then it will be removed from the QUeUE.
RSXMB_CANCEL_NOT_REST_MESSAGES Cancel XI Messages With Errors That Cannot Be Restarted
we cannot cancel the messages which are in pending status. But there is a way by which we can bypass holding messages. For this, we need to go to SMQ2, select the queue, select holding message LUW and select the option to save LUW. We can restore these LUWs back from tcode SMQ3.
Also You may be find interesest in this Blog
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
URLs of help.sap.com
1) http://help.sap.com/saphelp_nw04s/helpdata/en/f5/d347ddec72274ca2abb0d7682c800b/frameset.htm
2) http://help.sap.com/saphelp_nw04s/helpdata/en/41/b715015ffc11d5b3ea0050da403d6a/frameset.htm
3) http://help.sap.com/saphelp_nw04s/helpdata/en/0e/80553b4d53273de10000000a114084/frameset.htm
Edited by: Debashish Roy on Jul 19, 2011 6:44 PM
Edited by: Debashish Roy on Jul 19, 2011 6:47 PM

ABAP Report to restart queues automatically

Hello,
We are facing the issue of needing to restart the smq1,smq2 and trfc queues to restart messages failed in PI. We really appreciate if anyone could provide us with an ABAP program which restarts these failed messages automatically. We wanted to know if anyone has implemented a solution to deal with this issue.
Thanks.
Kiran

Hi Kiran,
As per as my knowledge, When ever queues are struck in SMQ1& SMQ2 , first we need to check the error, the error its shows the queues (or) any particular message is failed in queue, the remaining messages(processing after error message queue) are also in struck in queue.
In this time first u need to check the error and depends upon the priority of the message is important we will wait for some time (or) prirority is low first u delete the particular error queue and processing the remaining messages.
for this particular error queue we can process again in SXI_MONITOR,in SXI_monitor we check the particular error queue and select the 'Restart' option, again the message is processing.
Regards,
Sateesh n

XI restart in qRFC not allowed

I am new in XI. Have prior experience in debugging BW related queues or CIF queue (APO) but not XI qRFC.
In our XI system's inbound queue is having stuck queue with large no. of LUWs from mdm system with SYSFAIL error. Opening the qRFC for details show the first LUW contains message "XI restart in qRFC not allowed".
What this indicates ? qRFC queue restart not possible here ? Double clicking on the queue status message shows a xml message with 'red flag' with information 'System error - manual restart possible' - where and how to restart queues like this ?

Check the required settings here: /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
From the blog:
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
Update:
The parameter needs to be set in SAP GUI --> tcode SXMB_ADM -> Integration Engine Configuration-> Configuration
Regards,
Abhishek.
Edited by: abhishek salvi on Aug 3, 2009 4:31 PM

XI Error ERROR_OBJECT.INTERNAL: Queue stopped

Hi All,
In our Integration system there are lot of ques stopped in SMQ2. When we checked the status is SYSFAIL and we are getting message as "XI Error ERROR_OBJECT.INTERNAL: Queue stopped"
Not sure how to solve this problem and what are the things that i should check.
"XI Error ERROR_OBJECT.INTERNAL: Queue stopped
Message no. SR053
In SM37 i can check that the job named "80144F3A76E71DDFAF9B420D2A9B8456" is created by user PISUPER and running and active since 86000 secs.
Can anyone help in this
Thanks

hi,
need to restart Queue..
->double click on Quue
->it will show you status of the Q....number of messages in the Q...
-> double-click on the number of entries
-> you will see a detailed report
-> double click on the first entry
-> you will see the message processing due to which the Q got blocked
-> on the toolbar above (in the same page) you will find the option of Restart...click it....select the tracing level as retain....
this will cause the message processing to restart and all the messages blocked in the Q will get processed....
please refer below blog:
Internal Server Error in PI 7.1
thanks,

Idocs in inbound queue

Hi,
We have a very critical issue wherein many a times in actual production system idocs are going into status 75 and hence into Inbound Queue.
So user currently has to go transaction WEINBQUEUE and restart queue details.
Just to give more technical details as only these type of idocs are going into queue's:
Basic type: WMTOID02
Message type :WMTORD
Please help asap.Issue is very critical here.
Thanks,
Vikram

Hi Ravi,
Thanks for your quick response.
As you have explained I see that from the Message Mapping I must mapping a timestamp in SERIAL field of the Control Record. This implies that the IDOC Receiver Communication Channel should not mark the checkbox "Queue Processing" (I get the feeling that this does nothing) and I have to mark the checkbox "Apply Control Record Values from Payload '.
In conclusion, I understand that the IDOC Adapter for queued processing on a target system such as SAP adds nothing as standard. That is, I've mapping identifiers as timestamp to ensure the execution sequence in SAP and this will be done through a program in background. As is done with ALE...
Furthermore, I can not avoid a "delay" in processing these messages. In my client does not allow me to schedule the job in less than 5 minutes.
Is not there another solution where PI contribute just over? Any ideas?
Thanks in advance,
Jose.

Frequently getting issue in queues

Hi Gurus,
Can any body tell me the resolution for one of the issue which we are currently facing is 'object is locked by this user xxxxx" we are getting in smq2 of
ecc system so we are resolving this issue by resetting the status of queue so it is working fine when we do this activity so again after few hours again
we are getting so whom do we contact to resolve this issue as a pi consultant im manually processisng all these activities for every hour , can any body give the suggestion for this.

Hi,
A temp solution that might help you while you try and sort out the problem. Is to schedule these jobs to restart the queues every 15min or 60min so it can start processing again. Please also have a look in SM12 when to see what locks there are.
How to use SAP's WebAS J2EE's JMS Queue in Exchange Infrastructure
how to restart queues in smq2 automatically
Messages Stuck in ECC SMQ2
Regards,
Jannus Botha

R3AD_BUPA_KNVH queue Error

Hie guys,
I have a strange error coming when system tries to replicate hierarchy to CRM.
Error says "Customer XXXXXXX in sales area O 50006277 0008 has no data in the customer hierarchy"
does any one know what caused this error?
I tried to debug and found that system is looking in table CRMM_BUT_BUHI_1 for an entry... but i dont know how to have this table updated!!!!
Any bdy had this error b4?
BR,
Dinesh.

The ECC will still send create queues if disconnected. But the queues would go into SYSFAIL. It could be that a job is scheduled on the ECC to try to restart queues stuck queues. Either that, or someone manually started the old queues. The queues MUST be coming from the ECC side.
Normally, if you're disconnecting or shutting down either system for a short time, note 764081 should be followed.
In htis case, it makes no snese to process queues dating from several years ago. I would suggest deleting them by scheduling one of background jobs RSTRFCID or RSTRFCIDS to run in the background. With RSTRFCIDS you can speicfy a timeframe and ensure only old queues are deleted. Afterwards, you can sue DIMa to check for data inonsistencies (see note 531217). In a worst case scenario you could repeat the initial laod but this shouldn't really be necessary.

QRFC list of inbound queues

Hi Friends,
can anyone help me to know which function module should I use to get the list of qRFC queue names available in R/3 for a particular application server user/ or for all users?
Thanks

http://help.sap.com/saphelp_470/helpdata/en/ee/fa5f3c90de2d73e10000000a114084/frameset.htm
RSTRFCT0
Outbound queue
One outbound queue and one destination, but multiple qRFC calls in a LUW, and a variable number of LUWs.
RSTRFCT1
Outbound queue
Works with tRFC and qRFC in "mixed mode" with different outbound queues and different destinations for one LUW.
RSTRFCT2
Send queue
Different outbound queues and different destinations for one LUW.
RSTRFCT3
Send queue
Different outbound queues and different LUWs. Some of these LUWs are dependent on other LUWs, to show how the qRFC Manager works.
RSTRFCT9
Send queue
Receiver list in qRFC: Process one LUW with different destinations, and the qRFC Manager stores the LUW data in the database only once.
RSTRFCTA
Send queue
STOP/RESTART queues (different RESTART conditions)
RSTRFCTB
Send queue
Obtaining qRFC LUWs from an outbound queue that is in the local or the remote system, and processing them in the current R/3 system.
RSTRFCTD
Send queue
qRFC in a dialog task and an update task in a LUW (from the application point of view)
RSTRFCTE
Send queue
List of queue names in qRFC: A qRFC call is assigned to more than one queue.
RSTRFCTF
Send queue
Performance test with and without receiver list for the current qRFC: Different calls/LUWs/queues/destinations.
RSTRFCTG
Send queue
"Multi-stage" STOP/RESTARTs (at different times)
Message was edited by:
Roberto Tagliento

SCEP 2012 Definitions only updating 50% of servers

Hiya,
We have SCCM 2012 R2 installed with a SUP and use an ADR to deliver Definitions 3 times a day. We're gradually migrating servers from our existing WSUS infrastructure to SCCM for monthly patching/AV defs.
Since 27.04.14 about half the servers (around 200) have failed to update their AV definitions and are stuck on version 1.173.658.0 (the majority, but not all). I've been comparing servers with up to date defs and those without but I can't see why they're
not working. In C:\Windows\CCMcache I just see a folder created for 28.04.14 for the next def but no file in there.
The non-working servers have;
1. The same AM policies applied
2. The same client settings applied
3. They're in the same site/use same DP
4. The same SCEP version (4.3.220.0)
5. The same SCCM client (5.00.7958.1000 - SP2 client)
6. Checked they're in the collection the ADR applies to
7. Log files show they're pointing to SCCM server and have same GPO settings as working servers
8. WUAgent is the same version
I've trawled through the SCCM client logs, used MpCmdRun.exe
-getfiles and looked through those but can't see any errors.
Of note, the WUAHandler.log shows the last update getting installed but then subsequent scans run, complete and there are no further "Update (Missing): Definition Update for Microsoft Endpoint Protection" entries.
Any help gratefully received!
Thanks

Ok still no joy unfortunately.
Checked the CAS/ContentAccess/ContentTransferManager/DataTransferService logs on an updated server and non-updated server and the only difference I see is this on the non-updated server;
DataTransferService.log
QUEUE: Error restarting queued DTS job {0A28D485-63C0-4C43-B942-7ECD4BFAE938}. Code 0x87d00215
QUEUE: Error evaluating DTS job queue. Code 0x87d00215
Error sending callback notification for DTS job {76FF03FC-D576-4F1D-9F6E-0EB7F187A2B7}
Comparing the WUAHandler.logs shows below;
Working;
Successfully completed synchronous searching of updates.
1. Update: 0a5fbcd9-e403-44cd-9fd0-38a2a942d394, 200 BundledUpdates: 1
Update: fa5965dd-4c94-4564-982b-6d1d1dd6e688, 200 BundledUpdates: 0
1. Update (Missing): Definition Update for Microsoft Endpoint Protection - KB2461484 (Definition 1.173.646.0) (0a5fbcd9-e403-44cd-9fd0-38a2a942d394, 200)
Async installation of updates started.
Update 1 (0a5fbcd9-e403-44cd-9fd0-38a2a942d394) finished installing (0x00000000), Reboot Required? No
Async install completed.
Installation of updates completed.
Non-working;
Successfully completed synchronous searching of updates.
1. Update: 0a5fbcd9-e403-44cd-9fd0-38a2a942d394, 200 BundledUpdates: 2
Update: fa5965dd-4c94-4564-982b-6d1d1dd6e688, 200 BundledUpdates: 0
Update: 484f6b32-9a1f-41b8-9044-d6da29c13279, 200 BundledUpdates: 0
1. Update (Missing): Definition Update for Microsoft Endpoint Protection - KB2461484 (Definition 1.173.646.0) (0a5fbcd9-e403-44cd-9fd0-38a2a942d394, 200)
Failed to find update (fa5965dd-4c94-4564-982b-6d1d1dd6e688) with binary in update collection from WUA. Continuing with download.
Async installation of updates started.
Update 1 (0a5fbcd9-e403-44cd-9fd0-38a2a942d394) finished installing (0x00000000), Reboot Required? No
Async install completed. Installation of updates completed.
I Couldn't find much on the "Failed to find update" error but from this point i don't see any "1. Update (Missing): Definition Update.." entries since 26.04.14 for the non-updating servers, but it does show the async searching and scans
completing.
Also, working machines have 2 or 3 folders per ADR deployment in the C:\Windows\CCMcache containing files called AM_Delta_Patch_1.173.1491.0.exe etc. but non-working ones have folders with one AM_Delta.exe and 5 or 6 empty folders with the same date.
Was thinking i'd locate the old defs in All Software Updates but they only go back as far as defs released on 30.04.14 so am a bit stumped!
Thanks

Project Server jobs going to "Waiting to be processed" state after resolving Error:1053 in virtual environment.

Hi all,
I am using project server 2007 in virtual environment. Before some time, my project server queue service was not starting & it gave Error: 1053. Then server team made some small changes in registry & resolved the problem. After that queue service
was in running condition. But when any job goes into queue, it processed the job first, then after some processing, it goes into "waiting to be processed", and after some time it again starts processing. So, the project server queue is working very
very slow. I restarted queue, event, sql, timer services, but no benefit.
In log it is showing "Queue unable to interact with SQL.".
Please Help....
Thanks.
Thanks & Regards Pradeep Gangwar

Hi Hrishi,
ULS log is as below:
===========================================================
02/12/2013 10:19:20.99 OWSTIMER.EXE (0x0460)
0x089C
Windows SharePoint Services Timer
5uuf Monitorable
The previous instance of the timer job 'Shared Services Provider Synchronizing Job', id '{AD482C7A-A6D5-4313-A4B6-3F5A78730F61}' for service '{54B6D7E9-6F24-459E-92AC-E11FB157B119}' is still running, so the current instance will be skipped. Consider
increasing the interval between jobs.
02/12/2013 10:20:10.58 w3wp.exe (0x04C0)
0x13FC
Windows SharePoint Services General
8m90 Medium
105 heaps created, above warning threshold of 32. Check for excessive SPWeb or SPSite usage.
02/12/2013 10:20:29.99 OWSTIMER.EXE (0x0460)
0x089C
Windows SharePoint Services Timer
5uuf Monitorable
The previous instance of the timer job 'Config Refresh', id '{5BA90EA2-D960-4F00-BF99-2C9C96056FB1}' for service '{46CB2006-65AC-40C6-9B5D-E2924F18B8CD}' is still running, so the current instance will be skipped. Consider increasing the interval
between jobs.
==========================================================
And in Event Viewer, it is showing:
==========================================================
Log Name: Application
Source: Office SharePoint Server
Date: 12-02-2013 10:14:02
Event ID: 7761
Task Category: Project Server Queue
Level: Error
Keywords: Classic
User: N/A
Computer: xyz
Description:
Standard Information:PSI Entry Point:
Project User: domain\epmadmin
Correlation Id: a5e020df-ee43-417f-b47c-a1f1142fe2cf
PWA Site URL: http://xyz/PWA
SSP Name: SharedServices1
PSError: Success (0)
An unxpected exception occurred in the Project Server Queue. Queue type (Project Queue/Timesheet Queue): ProjectQ. Exception details: CompleteGroup failed.
===========================================================================================================================================================
Log Name: Application
Source: Office SharePoint Server
Date: 12-02-2013 10:14:02
Event ID: 7758
Task Category: Project Server Queue
Level: Error
Keywords: Classic
User: N/A
Computer: xyz
Description:
Standard Information:PSI Entry Point:
Project User: domain\epmadmin
Correlation Id: a5e020df-ee43-417f-b47c-a1f1142fe2cf
PWA Site URL: http://xyz/PWA
SSP Name: SharedServices1
PSError: Success (0)
Queue SQL call failed. Error: System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK_MSP_QUEUE_PROJECT_GROUP_ARCHIVE'.
Cannot insert duplicate key in object 'dbo.MSP_QUEUE_PROJECT_GROUP_ARCHIVE'.
===========================================================================================================================================================
Log Name: Application
Source: Office SharePoint Server
Date: 12-02-2013 10:14:02
Event ID: 7754
Task Category: Project Server Queue
Level: Error
Keywords: Classic
User: N/A
Computer: xyz
Description:
Standard Information:PSI Entry Point:
Project User: domain\epmadmin
Correlation Id: a5e020df-ee43-417f-b47c-a1f1142fe2cf
PWA Site URL: http://xyz/PWA
SSP Name: SharedServices1
PSError: Success (0)
Queue unable to interact with SQL. Queue type (Project Queue, Timesheet Queue etc):
ProjectQ Exception: Microsoft.Office.Project.Server.BusinessLayer.Queue.QueueSqlException: CompleteGroup failed --->
System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK_MSP_QUEUE_PROJECT_GROUP_ARCHIVE'.
Cannot insert duplicate key in object 'dbo.MSP_QUEUE_PROJECT_GROUP_ARCHIVE'.
==========================================================
Thanks & Regards Pradeep Gangwar

Q status -stop

hi,
I created file to idoc scenario. but in sxmb_moni its showing green flag and Q.status is STOP. what is means....
regards
manoj

Hi,
Try to de register and register your queue from SXMB_ADM .
Also, try deleting the entry in the queue by double clicking on the Queue ID in SXMB_MONI and restarting your message.
Also see the below threads....
Q.Status is "Queue stopped"
SXMB_MONI - Message Status - Automatic Restart
Queue Stopped
Q.Status Stopped
Regards
Chilla..

Printer not connected error in 10.10.3

I'm getting "Printer not connected" now since I've upgraded to 10.10.3 on my Epson WF-3540 on my MBPr. My two other Macs are not having this issue, one of which is also 10.10.3 and the other 10.10.2 (a MacPro and MBP respectfully).
I have tried the following on my MBPr:
Delete Jobs
Pause and restart queue
Restarting Mac
Restarting Printer
Resetting Printer
Delete and reinstall printer - Both via AirPrint and Epson drivers
Reinstall fresh downloaded drivers
Repeat 6 with new driver install
SMC and PRRAM reset
Printer can be seen easily in printer control panel for setup. Setup proceeds normally. Then when attempting to print, the queue displays "Printer not connected" error.

If the printer works with AirPrint, you don't need the EPSON software and you should remove it. Then see below:
OS X Yosemite: Reset the printing system

Disk full event although disk is not full

Hello,
we have a HANA database running with revision 62.
After the filesystem for the log backup was not available (fileserver restart and mount did not reconnect) the database log went full.
The nameserver now cannot start and tells:
[11282]{-1}[-1/-1] 2013-08-24 00:43:07.470082 i EventHandler     EventManagerImpl.cpp(00647) : handleEvents(1)
[11282]{-1}[-1/-1] 2013-08-24 00:43:07.470119 i EventHandler     EventManagerImpl.cpp(00650) : --handleEvent: DiskFullEvent[id= 1, path= /sapmnt/log/HA1/mnt00001/hdb00001/, state= NEW]
[11282]{-1}[-1/-1] 2013-08-24 00:43:07.470156 i EventHandler     LocalFileCallback.cpp(00437) : [DISKFULL] restarting queue with 1 requests
[11282]{-1}[-1/-1] 2013-08-24 00:43:07.471884 i EventHandler     EventManagerImpl.cpp(00653) : --event not handled: DiskFullEvent[id= 1, path= /sapmnt/log/HA1/mnt00001/hdb00001/, state= HANDLING]
But the filesystem is not full.
df tells me:
df -h /sapmnt/log/HA1/mnt00001/hdb00001/
Filesystem            Size Used Avail Use% Mounted on
/dev/sapmntdata       5.8T 947G 4.9T 17% /sapmnt
I already checked the note
Note 1679938 - Log Volume is full (log mode = legacy)
But this does not work for me, as the filesystem is not full.
Is there a chance to bring the system up ?
Do I need to change a parameter ?
Many thanks in advance.
Any help is really appreciated.
Andreas

Hi Domenico,
yes I found a solution.
The problem was that there was a disk full indeed.
But it could not be seen by standard unix df command as the HANA logs are on a GPFS fileset.
This GPFS fileset was full.
You can check this with the command "mmrepquota"
mmrepquota --block-size G -a
this gives an overview of all filesets
*** Report for USR GRP FILESET quotas on sapmntdata
                         Block Limits                                    |
Name       type             GB      quota      limit   in_doubt    grace |
root       USR             203          0          0          1     none |
ha1adm     USR              77          0          0          1     none |
ha2adm     USR             137          0          0          1     none |
ha3adm     USR              47          0          0          1     none |
ha4adm     USR             295          0          0          1     none |
ha5adm     USR              86          0          0          1     none |
110        USR               1          0          0          0     none |
root       GRP             198          0          0          1     none |
sapinst    GRP               2          0          0          0     none |
sapsys     GRP             643          0          0          1     none |
root       FILESET         499          0          0          1     none |
hanadata   FILESET         150        768        768          1     none |
hanalog    FILESET         193        256        256          1     none |
In the column "GB" where actually the value is 193 was the value 256 which is exactly the quota of this fileset. So not the filesystem was full but the fileset in there.
As You can see we are running more than one HANA DB on this server. That might be the reason why the hanalog fileset was full very quickly.
The solution was to run the following statement on each of the DB's:
ALTER SYSTEM RECLAIM LOG;
After that the filling went down to 22 GB which is far away from the quota.
We now check regularly that we do not reach the quota.
To solve the problem final we are planning to patch SLES to SP2 or at least do an upgrade on GPFS because the shown behaviour is a bug in our GPFS revision.
hope that helps
Andreas

AQ message with delay problem!!

Hi,
I am having problem a problem with posting an AQ message to a queue using the AQMessageProperty.setDelay(val)
function. If val is 0, everything is fine, the message gets through. When the delay is > 0, it looks like oracle adds a number to the delay (currently amounting to 15-16 minutes). The amount added seems to increase over time.
I can see this in the AQ queue table: The message is inserted immediately, but the DATE in the columns DELAY, TIME_MANAGER_INFO, and ENQ_TIME all have a value 16 minutes after SYSDATE.
I have double-checked that the parameters passed in are correct.
Has anyone seen this problem, and found a solution to it?
Thanks in advance,
Trond Hvoslef

To follow up, here is some more info about the environment:
- AQ is accessed from Java
- Oracle version is 9.2.0.3
- Restarting the application does not help
- Dropping and recreating the queue tables does not help
- Restarting queue manager does not help
What does help is to restart the Oracle instance.
However I suppose the problem will appear again after running the instance for a few weeks.
As far as I can understand this must be a bug in Oracle.
I am interested to hear from other people using this feature.
Thanks,
Trond Hvoslef

Restart Queue in PI 7.1

Similar Messages

Maybe you are looking for