Failed Asynchronous Messages still processing

Hi,
Scenario: Asynchronous
QoS: EO
SAP > PI > 3rd Party
I have an almost 1500 failed messages in my SXI_MONITOR SAP PI with an error of 'No Receiver Determination'. I have already solved the issue and the future messages were successful. However, the 1500 failed messages are still being pushed/processed, which is taking up too much memory.
How do you stop these failed messages in processing?
Is there a way that when a failed message already fails, it would stop pushing/processing in SAP PI?
thank you.

Hi,
I think your team mates or BASIS team might have already set a background job for re triggering failed messages in ABAP stack .
If you don't want those messages then you can cancel those in SMQ2/SXMB_MONI.
Regards
Venkat

Similar Messages

SAP Blog XI Asynchronous Message Processing: Understanding XI Queues

Hi,
I was not able to access this blog anymore.
It was at this link before : XI Asynchronous Message Processing: Understanding XI Queues -Part I
Can someone please send me a copy if you've saved before? Thanks.
Please email to yuanyuanlin2001 at yahoo.com

hi,
the link is working and you can still access that - I've just tried
Regards,
Michal Krawczyk

Synchronous message interface processes as Asynchronous

I have a message interface define as Outbound - Synchronous. But when it processes it shows it being an Asynchronous message. My response message mapping never executes.
Thanks,
Jim

Priyanka,
Here is the situation. This process works in XI 2.0 and I am trying to convert it to XI 3.0 The message interface is defined as outbound-synchronous. This automatically forces me to define the Output message and the input message. Because of this definition, the message mapping allows me to define the request message mapping and the response message mapping.
Basically the scenario is I receive an XML file that is mapped to an RFC that is sent to SAP R/3. This RFC creates a sales order.
When the scenario is executed, the request message mapping executes because the sales order is created in R/3. However the response message mapping never seems to executes.
The message interface is defined as Synchronous, but it shows in the message monitor as Asynchronous.
So I do not understand your question about "Do I have a corresponding inbound sync message interface".
The fact that the message interface is marked as synchronous and it has the output and input message types defined, I would have to say that this is the corresponding inbound message interface. This is how I have defined it in XI 2.0 and it works. Is there something different with XI 3.0 that maybe I am missing?
Thanks,
Jim

BPM :: Messages not processed at outbound side

Hi Experts,
We have 1000+ synchronous messages with BPM for only two days in July which havent processed fully. Now oncoming messages are getting processed fine, but the messages which were waiting for outbound processing from July are still waiting.
inbound side there is a success flag and outbound side it is showing a clock symbol(looks like scenario is collecting / waiting)... cant see any failed/waiting messages iin queues .. when I checked the workflow logs few are showing workflow manually edited and processed after exception.
The date messages were triggered are 10/Jun and seems one or more messages were edited on 17/jun later.
Now we would like to know which workflow thrown the exception and what they have done during manual operation.
And how to process the remaining holding messages.
Thanks in advance for you ideas and suggestions.

Hi,
As you pointed out in your post that
"inbound side there is a success flag and outbound side it is showing a clock symbol(looks like scenario is collecting / waiting)... "
Now you have not explained your scenario completely. Still from the problem statement I can say that The BPM is waiting for some messages. There are three possible scenarios where you can see the clock symbol.
You have the option of collecting multiple messages for an interface and bundling them into one message, for example, individual sales order items into one sales order. To do so, you need to define a receiver step within a loop. The loop can finish in a variety of ways.
Payload-Dependent => The loop finishes when the number of messages received matches the number specified in the payload of the messages.
Time-Dependent => The loop finishes at a specified point in time.
Message-Dependent => The loop finishes when a specific message is received.
Once all the messages have been received, a transformation step bundles the messages collected in the container element and from them creates a message in the container element .This message is then sent by a subsequent send step.
The processes use one of the abstract interfaces as an inbound interface, and the other as an outbound interface.
Your BPM cannot be time dependant, otherwise it would have completed processing by now.
Either your BPM is message dependant or payload dependant. You need to find this out.
Check out the correlation (if) used in BPM, and the condition in BPM which stops the message collection.
Plesae check SXMB_MONI and study the messages which have been succesfully processed by the BPM, so if your BPM is message dependant you have to find out what message it needs to stop collecting the message, this you can do by studying the successful message processed by the BPM. In this case your BPM will contain a FORK step. In one branch of FORK step there will be a receive step, this is the step where you can find the message required to complete waiting stage of the BPM.
Check if this message has arrived or not.
If your BPM is Payload dependant, find out whether number of messages received by the BPM matches the expected count or not. In this case the BPM must have a container operation to count the messages received. If the count is less than required value, the BPM will remain in waiting state.
regards
Anupam

Windows 7 64bit has an MTP USB Device Failed error message when I attach my Ipad1

I keep getting an MTP USB Device Failed error message when I plug in my USB cable into my Ipad1. Can someone help?

This is NOT resolved. The "Upper..."Key in the registry editor doesn't exist as you can see below in the image I am providing. This is still an OUTSTANDING issue, can someone please help with resolving this issue, super frustrating.
This is not just an iPAD issue, I get the same problem with my iPhone as well, both (iPhone and iPad) have the latest iOS 6.1.3 installed as well.

Assembly failed error message

Hello Experts,
We are getting "Assemble failed" error message when we tried to assemble components. I have attached a CMS log file. You help and feedback is greatly appreciated.
David
Info:Starting Step Repository-export at 2008-10-08 05:34:02.0206 -4:00
Info:Component:alleghenyenergy/AE_IMPORTED_OBJECTS
Info:Version :JD1_XD1IR01_C.20081008093400
Info:1. PR is of type TCSSoftwareComponent
Info:the workspace will be read from XI
Info:OK   : workspacedata added.
Info:Component:ivara.com/IVARA_EXP_ENTERPRISE
Info:Version :JD1_XD1IR01_C.20081008093401
Info:2. PR is of type TCSSoftwareComponent
Info:the workspace will be read from XI
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: Exception received:
ClientServerException exception:Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
com.sap.aii.utilxi.misc.api.ResourceException: Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
     at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.checkSwcvExistence(InternalRepTransportServiceImpl.java:316)
     at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.createSupportPackage(InternalRepTransportServiceImpl.java:283)
     at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.createSupportPackage(TransportServiceImpl.java:362)
     at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:206)
     at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
     at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
     at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
     at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
     at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
:communication error: Exception received:
ClientServerException exception:Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
com.sap.aii.utilxi.misc.api.ResourceException: Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
     at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.checkSwcvExistence(InternalRepTransportServiceImpl.java:316)
     at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.createSupportPackage(InternalRepTransportServiceImpl.java:283)
     at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.createSupportPackage(TransportServiceImpl.java:362)
     at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:206)
     at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
     at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
     at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
     at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
     at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: Exception received:
ClientServerException exception:Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
com.sap.aii.utilxi.misc.api.ResourceException: Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
     at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.checkSwcvExistence(InternalRepTransportServiceImpl.java:316)
     at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.createSupportPackage(InternalRepTransportServiceImpl.java:283)
     at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.createSupportPackage(TransportServiceImpl.java:362)
     at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:206)
     at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
     at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
     at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
     at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
     at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
     at com.sap.cms.tcs.client.XICommunicator.readWorkspaceData(XICommunicator.java:228)
     at com.sap.cms.tcs.core.RepositoryExportTask.processRepositoryExport(RepositoryExportTask.java:226)
     at com.sap.cms.tcs.core.RepositoryExportTask.process(RepositoryExportTask.java:324)
     at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
     at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:197)
     at com.sap.cms.tcs.core.TCSManager.assemblePropagationRequests(TCSManager.java:677)
     at com.sap.cms.pcs.assembly.manager.AssemblyManager.assemble(AssemblyManager.java:1510)
     at com.sap.cms.pcs.assembly.AssemblyQueueHandler.execAssembly(AssemblyQueueHandler.java:818)
     at com.sap.cms.pcs.assembly.AssemblyQueueHandler.startAssembly(AssemblyQueueHandler.java:133)
     at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startAssembly(CmsTransportProxyBean.java:829)
     at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl20.startAssembly(LocalCmsTransportProxyLocalObjectImpl20.java:1836)
     at com.sap.cms.ui.wl.Custom1.startComponetAssembly(Custom1.java:14080)
     at com.sap.cms.ui.wl.Custom1.assembleQueue(Custom1.java:4685)
     at com.sap.cms.ui.wl.wdp.InternalCustom1.assembleQueue(InternalCustom1.java:2303)
     at com.sap.cms.ui.wl.Worklist.handleAssemblyOptionsEvent(Worklist.java:1487)
     at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2520)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Component.fireEvent(Component.java:283)
     at com.sap.cms.ui.wl.wdp.InternalWorklists.wdFireEventAssemblyOptionsEvent(InternalWorklists.java:388)
     at com.sap.cms.ui.wl.Worklists.fireAssemblyOptionsEvent(Worklists.java:247)
     at com.sap.cms.ui.wl.wdp.InternalWorklists.fireAssemblyOptionsEvent(InternalWorklists.java:328)
     at com.sap.cms.ui.wl.AssemblyOptions.onActionStartAssembly(AssemblyOptions.java:276)
     at com.sap.cms.ui.wl.wdp.InternalAssemblyOptions.wdInvokeEventHandler(InternalAssemblyOptions.java:339)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Info:Step Repository-export ended with result 'fatal error' ,stopping execution at 2008-10-08 05:36:32.0376 -4:00

Hi,
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: Exception received:
ClientServerException exception:Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
The error is saying that there might a communication issue with CBS to CMS. That's the reson the imported SCA version is not available in the current system to assemble. The NWDI restart may work some times.
Thanks
Krishna

Load fails while running a Process Chain even before loading to the PSA.

Hi Experts,
We are working on BI 7.0 and ECC 6.0 on an IS-U Project.
We are loading Transaction Data using Process Chains. Data load is failing even before loading to the PSA and the error message is as below:
Error message during processing in BI
Diagnosis
An error occurred in BI while processing the data. The error is documented in an error message.
System Response
A caller 01, 02 or equal to or greater than 20 contains an error meesage.
Further analysis:
The error message(s) was (were) sent by:
Inbound Processing
Procedure
Check the error message (pushbutton below the text).
Select the message in the message dialog box, and look at the long text for further information.
Follow the instructions in the message.
Had anyone come across this type of error, if so, what could be the reason of failure and probable solution.
Your time is very much appreciated.
Thanks in Advance.
Best Regards,
Chandu.

Hi,
It might be a network connection between the source system and BW? Can you get your Basis colleague to look into the connection?
Hope this helps.
Cheers,
Gimmo

Dreaded "Operations Manager failed to start a process" error (2012 R2)

I know this error has been covered many times, and on many topics, but this time mine is slightly different.   It's
NOT the
"SCOMpercentageCPUTimeCounter" error covered by Kevin Holman.
Also, I am running SCOM 2012 R2 UR4 (7.1.10226.1046) and everything seems correctly patched (MS and agents), like
suggested by Nicole Welch and Kevin Holman as well.
So my environment is a fresh installation of SCOM 2012 R2, and I am transferring to this new Management Group, the monitored servers from our old SCOM 2012 "R1" (which I did not upgrade but rather made a brand new independent install). So
all servers aren't migrated yet, but I would like to solve this error before. This error did NOT happen in "R1", nor was it overridden (I imported the exact same Management Packs anyway).
On 2012 R2, it happens on almost all new monitored machines, mainly Read-Only Domain Controllers (RODCs).
Here is the kind of alert text I am getting:
Het om 10:10:15 gestarte proces is beëindigd als gevolg van een uitvoerverzamelfout als gevolg van fout 0x80070057 :
The parameter is incorrect.
; mogelijk zijn er gegevens verloren gegaan.
Opdracht die is uitgevoerd: "C:\Windows\system32\cscript.exe" //nologo "C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State\Monitoring Host Temporary Files 193\24788\AD_Global_Catalog_Search_Response.vbs"
RODC02.mydomain.be (objectCategory=DMD) false 4 {9E253FCB-8AAF-491F-CCA3-E632C6C2800C}
Werkmap: C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State\Monitoring Host Temporary Files 193\24788\
Dit is van invloed op een of meer werkstromen.
Werkstroomnaam: Microsoft.Windows.Server.2008.AD.DomainController.GCSearchTime.Monitor
Exemplaarnaam: RODC02
Our servers have Belgian (Dutch) regional settings, hence the language. But check out the highlighted info in bold.
The related event Number (in Alert Context) is 21404. Most other articles about this, mention 21402 or 21403. I suppose they all must be related but still, it's a new one here.
There you have the failing VBS file. I checked all alerts and there seem to be different files concerned overall. Other examples:
C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State\Monitoring Host Temporary Files 233\22737\AD_Database_and_Log.vbs    (from almost all RODCs)
C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State\Monitoring Host Temporary Files 196\19876\Microsoft.Windows.Server.Legacy.FreeSpace.vbs
(also from an RODC)
C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Health Service State\Monitoring Host Temporary Files 5891\338282\Microsoft.Windows.Server.CPUUtilization.Monitortype.vbs 95 15
SCOM02.mydomain.be 1.4119384288787842     (this one is from my second Management Server..)
Repeat count of the alert is 1 to 2 a day, so it's not nightmareish, but still, requires to be fixed. I suspect that even if there is a different VBS file concerned, since the eventID and the alert text are the same, the repeat count will just increase,
not showing the last actual VBS concerned.
I connect to each of these servers, and browse to the directory containing the file, and the folder is there, the file is there. The error text mentions incorrect parameters but they still seem OK to me.
I found something which might be worth noting: when browsing to the directory, be it on an RODC or on the SCOM server, I get a permission popup requiring some admin rights to do so - although I am using my domain admin (+SCOM+SQL+local
admin everywhere) account:
SCOM services use the Local System account to run, on every machine. I thought Local System shouldn't be concerned with these permissions popups, but normally the domain/local admins aren't either, yet I am.
The "Health service" folder is the only one from the "C:\Program Files\Microsoft Monitoring Agent\Agent" folder to be concerned with this; I can browse without trouble to any other directory there.
After a SCOM service stop, I renamed the "Health Service state" folder (as you can see on the screenshot, there is a "Health Service State bak" folder) and let the service recreate it after a restart, to ensure it was clean and with
appropriate permissions , but it doesn't help.
Might that be a clue?
Or else what? I'm getting confused and don't find a suitable solution.
dd
Bix

On Thu, 4 Dec 2014 14:20:22 +0000, Bixessss wrote:
I know this error has been covered many times, and on many topics, but this time mine is slightly different.   It's*NOT* the "SCOMpercentageCPUTimeCounter" error covered by Kevin Holman <http://blogs.technet.com/b/kevinholman/archive/2010/02/23/a-new-script-error-scompercentagecputimecounter-vbs-invalid-class.aspx>.
Also, I am running *SCOM 2012 R2 UR4* (7.1.10226.1046) and everything seems correctly patched (MS and agents), likesuggested by Nicole Welch <http://nicolewelchscom.wordpress.com/2013/10/01/operations-manager-failed-to-start-a-process/>
and Kevin Holman as well.
This forum is for security issues related to Windows Server and not for
System Center questions.
Post your question in one of the following forums:
https://social.technet.microsoft.com/Forums/systemcenter/en-US/home?category=systemcenteroperationsmanager
Thanks.
Paul Adare - FIM CM MVP
Never trust a computer you can't lift. - Stan Masor

I cant connect with my imessage and facetime in my iphone; i already upload de i os 7.02 but the message still have it; it said that they have problem with the network; i reset the network and doesnt work

I cant connect with my imessage and facetime in my iphone; i already upload de i os 7.02 but the message still have it; it said that they have problem with the network; i reset the network and doesnt work

Hello, Toro Silva.
Thank you for visiting Apple Support Communities.
The steps in the section labeled Unable to activate FaceTime or iMessage with phone number and Apple ID after waiting 24 hours (iPhone only) of the article below, should help resolve the issue. Make sure to create a current backup prior to processing these steps.
iOS: Troubleshooting FaceTime and iMessage activation
http://support.apple.com/kb/ts4268
Cheers,
Jason H

File-RFC_File Scenario - single message got processed twice.

Hi all,
I have a file-RFC-File scenario in which the reponse from ECC is written using adapter modules.Today one message got processed twice into SAP.When i checked FIle Receiver adapter in CC monitoring i could see the error given below:
2010-11-16 08:47:37 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2010-11-16 08:47:37 Success The XI response message for message 0fb0e660-f130-11df-a03d-00212816ab84(INBOUND) was successfully returned to the calling application.
2010-11-16 08:47:37 Success The message status set to DLVD.
2010-11-16 08:47:37 Success ROB: entering ResponseOnewayBean
2010-11-16 08:47:37 Success ROB: resuming the transaction
2010-11-16 08:47:37 Success ROB: calling the module processor ...
2010-11-16 08:47:37 Success MP: Entering module processor
2010-11-16 08:47:37 Success MP: Processing local module localejbs/CallSapAdapter
2010-11-16 08:47:37 Success File adapter receiver: processing started; QoS required: ExactlyOnce
2010-11-16 08:47:37 Success File adapter receiver channel File_Receiver_XXXX_CC: start processing: party " ", service "XXXX_BUSS"
2010-11-16 08:47:37 Success Connecting to FTP server "XX.XX.X.XXX"
2010-11-16 08:47:37 Success Write to FTP server "XX.XX.X.XXX", directory "/inbound", -> file "XXXResp20101116-084737-629.xml"
2010-11-16 08:47:37 Success Transfer: "BIN" mode, size 273 bytes, character encoding -
*2010-11-16 08:47:37 Error Attempt to process file failed with com.sap.aii.adapter.file.ftp.FTPEx: 550 XI_ftp_0fb0e660-f130-11df-a03d-00212816ab84.tmp: The system cannot find the file specified.
2010-11-16 08:47:37 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: XI_ftp_0fb0e660-f130-11df-a03d-00212816ab84.tmp: The system cannot find the file specified. : com.sap.aii.adapter.file.ftp.FTPEx: 550 XI_ftp_0fb0e660-f130-11df-a03d-00212816ab84.tmp: The system cannot find the file specified.
2010-11-16 08:47:37 Error ROB: error during processing: com.sap.aii.af.mp.module.ModuleException caused by: com.sap.aii.af.ra.ms.api.RecoverableException: XI_ftp_0fb0e660-f130-11df-a03d-00212816ab84.tmp: The system cannot find the file specified. : com.sap.aii.adapter.file.ftp.FTPEx: 550 XI_ftp_0fb0e660-f130-11df-a03d-00212816ab84.tmp: The system cannot find the file specified. *
The tmp file was picked by the client system and may be that disturbed the entire scenario.But instead of throwing an error how can this reprocess the message from beginning. In SXMB_MONI i can see the pipeline steps executed twice for this message. Since the interface is critical i had to manually delete the replicated data from ECC after taking clients permission which wont be allowed everytime.
Could somepne help me in resolving the issue.
Thanks & Regards,
Lekshmi.

Nisar,
Which program to re-run? Are you talking about activating the channel again? If so, then I have done it many times changing the file name.
I got below error in Communication Channel Monitoring:
2008-02-06 02:27:39 Error Received XI System Error. ErrorCode: MSGGUID_EXISTING ErrorText: ErrorStack: Message ID 83F8B0B0D48311DCA544DA01C52F0606 for pipeline CENTRAL, version already exists in system
2008-02-06 02:27:39 Error Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:.
2008-02-06 02:27:39 Error Transmitting the message using connection http://xibox:8000/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:.
2008-02-06 02:27:39 Error The message status set to FAIL.
2008-02-06 02:27:39 Error Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:
2008-02-06 02:27:39 Error Attempt to process file failed with com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:
2008-02-06 02:27:39 Error Attempt to process file failed with com.sap.aii.af.service.util.transaction.api.TxManagerException: Unable to roll back transaction: com.sap.engine.services.ts.exceptions.BaseIllegalStateException

Abstract asynchronous message interface for fault (exception) messages

Hi,
Has anyone yet discovered how to create an abstract asynchronous message interface for a fault message so that said message can be referenced in an Integration Process? I am currently at a loss as to how to reference the exception message returned by a synchronous RFC call, and how to return the fault message of a synchronous MI from a BPM.
Thanks for any help you can provide on this issue - please do not refer me to existing blogs or forum messages if they do not specifically answer this question in a positive manner. I have just been through the SAP Notes and the SDN forum and Google and while I have seen many questions about this topic I have not seen any answers.
Stephen

hi stephen,
never worked on this but out ofcuriosity after seeing ur question i tried to create one:
but i found these:
fault message types will only be used in case of synchronous messages.....if it is asynchronous the fault message type radio button it self will not seen while creating message interface..just check.
you need to create a Fault message type to use it in an interface...u can add your own fields also if u want.
in your present case you mentioned you are using synchronous RFC...try creating a synchronous abstract interface there you can give fault message type also...just check by creating one...
correct me if i am wrong...
regards.

Failed to start essbase process: number of back up files exceeds limit

Can someone help to take a look at this?
More details is logged in bug 11887650
Failed to start essbase process, message in log file:
11/03/18 11:44:10 Start process
Info: Essbase is reducing the number of soft file descriptors because the 32K limit has been exceeded. Exceeding the limit may significantly increase application load time.
Environment variable [HYPERION_LOGHOME] is set - use it to define Log location folder.
Log location is [u01/APPLTOP/instance/BIInstance/diagnostics/logs/Essbase/essbaseserver3/essbase].
ODL log location is [u01/APPLTOP/instance/BIInstance/diagnostics/logs/Essbase/essbaseserver3/agent-log].
[Fri Mar 18 11:44:10 2011]Local/ESSBASE0///4072736080/Warning(1056807)
The number of back up files found on disk (40) exceeds the configured limit which is 2
[Fri Mar 18 11:44:10 2011]Local/ESSBASE0///4072736080/Info(1051283)
Retrieving License Information Please Wait...
[Fri Mar 18 11:44:10 2011]Local/ESSBASE0///4072736080/Info(1051286)
License information retrieved.
65535 Essbase user 65535 Planning user system
Logging configuration class "oracle.core.ojdl.logging.LoggingConfiguration" failed
oracle.core.ojdl.logging.LoggingConfigurationException: ODL-52050: unable to process file '/u01/APPLTOP/instance/BIInstance/Essbase/essbaseserver3/bin/logging.xml', XML parse exception (line: 5, column: 38): org.xml.sax.SAXParseException: Attribute "class" is required and must be specified for element type "log_handler".
Mar 18, 2011 11:44:14 AM oracle.security.jps.az.internal.common.scanner.PolicyChangeScannerThread run
INFO: Policy store cleanup thread started.
Mar 18, 2011 11:44:14 AM
INFO: EPMCSS-CSS Fusion system initialized successfully. : [2724 ms]
[Fri Mar 18 11:44:14 2011]Local/ESSBASE0///4072736080/Info(1051199)
Single Sign-On Initialization Succeeded !
[Fri Mar 18 11:44:14 2011]Local/ESSBASE0///4072736080/Info(1051639)
Info: Essbase is reducing the number of soft file descriptors because the 32K limit has been exceeded. Exceeding the limit may significantly increase application load time.
Essbase 64-bit - Release 11.1.2 (ESB11.1.2.1.0B154)

I am an infrastructure idiot (I have all kinds of other idiocy available as well -- I am versatile), but I found:
http://troubleshooot.wordpress.com/2010/05/26/essbase-login-is-not-working/
To my ignorant eyes, this looks like some kind of *nix-centric issue.
If the post doesn't help, perhaps one of the infrastructure guys will chime in.
Regards,
Cameron Lackpour

** Message being processed - Queue status green colour

Hi Friends,
Many messages in our SXMB_MONI shows green color in the queue id column. It shows 'Message being processed'. All messages are in queue, still they are not delivered. Processing takes more hours. These messages are not EOIO queue. While we check this thru SMQ1 and SMQ2 it shows 'Running'. So, what could be the problem ...?
Kindly help friends, to solve this issue. (Points rewarded for helpful answer)
Kind Regards,
Jeg P.

HI,
QUEUE STATUS RUNNING BASICALLY MEANS THT
The first LUW of this queue is currently being processed. If a queue in this status hangs for more than 30 minutes, this may mean that the work process responsible for processing this LUW has been terminated. In this case you can activate this queue again. Note that activating a queue in status RUNNING may cause a LUW to be executed several times if this LUW is still being processed in the target system at that time. We therefore recommend a waiting time of at least 30 minutes before you reactivate the queue.
HOPE THIS WILL SOLVE THE PROBLEM
PLZ REWARDS POINTS
VIKAS

Sales Order status is CLSD, RA is still processed

We have been working on Closing old MTO sales orders to shorten the month-end processing time. Most have been successful. However, there are some order that we set the status to CLSD and the order still process through RA. Other order (those we see as working correctly) will return a message about the status not valid for RA.
I don't know what to check on order that are CLSD and doing RA??
thank you
Althea

Hi Preety
Thanks for ur kind reply, my problem is solved for sales order closed manully for Item B
Good
I have doubt is that is it system generate AR invoice automatically when AR downpayment invoice created with DTM 100% ?
it system does not generate AR invoice automatically when AR downpayment invoice created with DTM 50% ?
which i have been observed above.
AM I right?
Please tell me what are the difference between AR downpayment invoice and AR downpayment request?
Prasad
Hyd

How to check if Message already exists in the queue and if message is processing currently

Hi everyone
I am new to Azure and worked on adding messages to the queue through workerrole1. Worker role 2 pulls them out from queue and processing them and de-queing them.
Worker role1 runs method gets called after every 10 seconds and puts messages in queue
CloudQueueMessage
message = newCloudQueueMessage(oAzureWorker.WorkerInstanceOf
+ "_"+ oAzureWorker.AgentId.ToString()
+ "|"+ ExecutionId.ToString());
queue.AddMessage(message);
Worker role2 runs method gets called after every 10 seconds too and checks the queue like this
foreach
(CloudQueueMessagemessage
inqueue.GetMessages(20,
TimeSpan.FromMinutes(5)))
// Process all (20) messages in less than 5 minutes, deleting each message after processing.
// Process message
queue.DeleteMessage(message);
Following are my questions
1) How do I check in worker role1 if the message is already in queue, Because I don't want to queue it back again if its not yet processed and is in the queue already
2) How do I check in worker role1 if the message is currently processing. Because I don't want to queue it back again.
3) How do I make sure that ALL the messages get processed in the order they are inserted. I know Queue is FIFO, but I know if the message gets delayed in processing another instance can pick it up, even if it gets picked up by another instance, I want to
make sure that the order remains.
Right now the instances of both these worker roles are 1, in the future when we increase them, I don't want them to queue the same messages multiple times or queue them if the message is already in process mode.

Hi Sarah,
I agree to the Frank's suggestion. Why you need to burden the worker role 1 to check if the message really sits on the queue or not? You can do this simply in your code before pushing it on queue instead querying queue.
All you need to do on worker role 1 is - push the message on the queue and forget as the entire queue design in azure is designed from asynchronous processing.
About worker role 2 - Use the GetMessage method which hides retrieved message's from other clients and hence makes sure that only one client is processing it at a time. If processing is successful - delete the message. if it is not - the message will be
visible anyways after the mentioned time provided in the GetMessage method.
I agree that when you will increase number of instances of your worker role 1 which might insert duplicates in the queue - in that case - you might need to introduce the shared entity (like database) and let all instances communicate through it to avoid
the duplication of messages on queue.
Bhushan | http://www.passionatetechie.blogspot.com | http://twitter.com/BhushanGawale

Failed Asynchronous Messages still processing

Similar Messages

Maybe you are looking for