Notifications of XI-mgs in status 'System Error - Manual Restart Possible'

Dear colleagues,
I'm using a simple communication channel of type 'GeneratedReceiverChannel_XI' in order to push XML-messages from the intergration engine into the ABAP-Backend using an ABAP server proxy. Many of these messages, however, show an error status in the XI-monitor (Notifications of XI-mgs in status 'System Error - Manual Restart Possible'). The indication of the system error is OK, since the XML-parser correctly detects a character in a field which shall be mapped to a field of type 'DEC' in the ABAP backend.
Is there any possibility to configure some type of alerting in the ABAP-backend to track especially the appearence of XML-messages in the XI-monitor with status 'System Error'?
Thanks a lot and kind regards
Stefan

HI,
As its mentioned in above postes, you can configure the Alert notification in XI which can give you the alerts about this kind of errors.
If the exception is raised after reaching to ABAP backend R/3 Side, then you may trace it in t-code SXMB_MONI of R/3.
Refer -- ALERT MANAGMENT
http://help.sap.com/saphelp_nw04/helpdata/en/3f/81023cfa699508e10000000a11402f/content.htm
Thanks
Swarup

Similar Messages

Set Message in BPM to System Error - Manual Restart Possible ?

Hello,
I'm working on a scenario where two idocs are merged in a BPM. The next step is sending the message in a synchronous RFC (BAPI) to a SAP R/3. Is it possible to set the merged message to the message status 'System Error - Manual Restart Possible' in the SXMB_MONI, when the BAPI returns an Error message?
When it's not possible, is there an othe possibility to sent the message again, without involving the source system?
Thanks in advance
Matthias

Hi,
It would be better i think if you use the concept of raising an exception in your response mapping
please refer:
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
/people/michal.krawczyk2/blog/2007/04/26/xipi-throwing-generic-exceptions-from-any-type-of-mapping
in the response mapping you can check the condition for the responce code from RFC.
Ranjit

URGENT: system error - Maual restart possible

Hi Experts,
I'm facing a problem in Xi prodoction. Both inbound and outbound are throwing system error - Maual restart possible. The user is restarting manually in order to post the invoice.
Basically this is retail project, from POS s/w to Xi to SAP R/3. The scenario is file to idoc(inbound) and idoc to file (outbound).
The error is :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="PERSIST">MESSAGE_NOT_FOUND</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XML message not found</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The acknowledgement error is :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert the sender service to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have gone throw the sdn post and blogs but i'm uable to trace the problem.
Kindly suggest me ASAP as this is business critical and posting have been stoped.
Regards,
Pawan

Hi,
Please find the interface determination trace. Hope this will help you to provide some suggestion.
<?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: XIBGUSER</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="2" type="T">Tunneling needed?</Trace>
<Trace level="2" type="T">Partytype = LS fallback to logical system</Trace>
<Trace level="3" type="T">Sender Interface</Trace>
<Trace level="3" type="T">WP_PLU.WP_PLU03 urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</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 SAPRT2</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_STRUCTURE_GET Details</Trace>
<Trace level="2" type="T">Port : SAPRT2</Trace>
<Trace level="2" type="T">IDoctyp : WP_PLU03</Trace>
<Trace level="2" type="T">Cimtyp :</Trace>
<Trace level="2" type="T">RFCDest :</Trace>
<Trace level="2" type="T">Release : 700</Trace>
<Trace level="2" type="T">Version : 3</Trace>
<Trace level="2" type="T">Direct : 1</Trace>
<Trace level="2" type="T">SAPREL : 700</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_SYNTAX_CHECK</Trace>
<Trace level="2" type="T">Port : SAPRT2</Trace>
<Trace level="2" type="T">IDoctyp : WP_PLU03</Trace>
<Trace level="2" type="T">Cimtyp :</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">Create XML-Control Record</Trace>
<Trace level="2" type="T">Create XML-Data Records</Trace>
<Trace level="3" type="T">Create data Record E1WPA01</Trace>
<Trace level="3" type="T">Create data Record E1WPA02</Trace>
<Trace level="3" type="T">Create data Record E1WPA03</Trace>
<Trace level="3" type="T">Create data Record E1WPA04</Trace>
<Trace level="3" type="T">Create data Record E1WPA05</Trace>
<Trace level="3" type="T">Create data Record E1WPA01</Trace>
<Trace level="3" type="T">Create data Record E1WPA02</Trace>
<Trace level="3" type="T">Create data Record E1WPA03</Trace>
<Trace level="3" type="T">Create data Record E1WPA04</Trace>
<Trace level="3" type="T">Create data Record E1WPA05</Trace>
<Trace level="3" type="T">Create data Record E1WPA01</Trace>
<Trace level="3" type="T">Create data Record E1WPA02</Trace>
<Trace level="3" type="T">Create data Record E1WPA03</Trace>
<Trace level="3" type="T">Create data Record E1WPA04</Trace>
<Trace level="3" type="T">Create data Record E1WPA05</Trace>
<Trace level="3" type="T">Create data Record E1WPA01</Trace>
<Trace level="3" type="T">Create data Record E1WPA02</Trace>
<Trace level="3" type="T">Create data Record E1WPA03</Trace>
<Trace level="3" type="T">Create data Record E1WPA04</Trace>
<Trace level="3" type="T">Create data Record E1WPA05</Trace>
</Trace>
<Trace level="2" type="T">Partytype = LS fallback to logical system</Trace>
<Trace level="2" type="T">Set Sender Routing-object</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="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="3" type="T">system-ID = XIP</Trace>
<Trace level="3" type="T">client = 600</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIBGUSER</Trace>
<Trace level="1" type="Timestamp">2008-03-27T06:35:02Z UTC-7</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = DCFBC7EA238100F1B64A00145EDC94EF</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="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = DCFBC7EA238100F1B64A00145EDC94EF</Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTI0001</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0001</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = DCFBC7EA238100F1B64A00145EDC94EF</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">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 level="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface WP_PLU.WP_PLU03*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XIP</Trace>
<Trace level="3" type="T">client = 600</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIBGUSER</Trace>
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - e_solutionsPOS</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 2</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) e_solutionsPOS WP_PLU.WP_PLU03</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: WP_PLU.WP_PLU03</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Thanks,
Pavan

How to cancel automatically messages stated 17 (Application error - manual restart possible) in SAP ECC

Hi people. I need to create a job to cancel automatically the messages with the status 17 (Application error - manual restart possible) in SAP ECC.
In SXI_MONITOR I can retrieve these messages filtering just for "Application Error". I can cancel them here, however I need for a Job to do it.
I appreciate your help.
Regards
Arturo Santos

Hi,
>Is there any way we can make this automatic
In RWB-Component Montoring-Adapter Engine-Communication Channel Montoring- Select the Adapter- Go to Settings and change as per your Business Requirement.
Regards
Agasthuri Doss

System error and restart not possible

Hi
I have developed the Proxy to SOAP scenario and it used to work normally as designed, But suddenly it started giving the System error and restart not possible,
I see the following error in the Runtime work bench on the Receiver CC
SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Can anyone let me know what the error is
Thanks
PR

Hii
If this channel was in working state earlier, then this error would mean that the receiver webserver hosting the webservice has some problem. You may contact the receiver system for checking out if they have problem at their end and if they agree resend the messages and it should pass through.
It may be problem with certificates even.
Best Regards

Music pauses on my iPhone 5C when switching between apps or when receiving alerts/notifications sometimes (not always) and I have to manually restart the song. I'm running the latest 7.0.1 software. It's a bit annoying.

Music pauses on my iPhone 5C when switching between apps or when receiving alerts/notifications sometimes (not always) and I have to manually restart the song. I'm running the latest 7.0.1 software. It's a bit annoying.

I have had a similar problem with my system. I just recently (within a week of this post) built a brand new desktop. I installed Windows 7 64-bit Home and had a clean install, no problems. Using IE downloaded an anti-virus program, and then, because it was the latest version, downloaded and installed Firefox 4.0. As I began to search the internet for other programs to install after about maybe 10-15 minutes my computer crashes. Blank screen (yet monitor was still receiving a signal from computer) and completely frozen (couldn't even change the caps and num lock on keyboard). I thought I perhaps forgot to reboot after an update so I did a manual reboot and it started up fine.
When ever I got on the internet (still using firefox) it would crash after anywhere between 5-15 minutes. Since I've had good experience with FF in the past I thought it must be either the drivers or a hardware problem. So in-between crashes I updated all the drivers. Still had the same problem. Took the computer to a friend who knows more about computers than I do, made sure all the drivers were updated, same problem. We thought that it might be a hardware problem (bad video card, chipset, overheating issues, etc.), but after my friend played around with my computer for a day he found that when he didn't start FF at all it worked fine, even after watching a movie, or going through a playlist on Youtube.
At the time of this posting I'm going to try to uninstall FF 4.0 and download and install FF 3.6.16 which is currently on my laptop and works like a dream. Hopefully that will do the trick, because I love using FF and would hate to have to switch to another browser. Hopefully Mozilla will work out the kinks with FF 4 so I can continue to use it.
I apologize for the lengthy post. Any feedback would be appreciated, but is not necessary. I will try and post back after I try FF 3.16.6.

How to CANCEL/RESEND messages in Adapter with status system error in bulk?

Hello all,
I d like to know how can I CANCEL or RESEND messages with status error SYSTEM ERROR in adapter framework.
Messages failed because of receiver system un-availability. Now, we have more than 50.000 messages stuck, waiting for being resent or cancelled.
But from the Message Monitoring Tool at Runtime Workbench Monitoring, I can only process up to 200 messages each time.
So, its practically imposible to do it manually.
My question is how can I deal with that amount of messages? Is there a way to process them in bulk and get them cancelled in only one step/action?
Many Thanks in advance.

Hello, I hope you are doing fine!!
The most common way to cancel these messages is through the Runtime Workbench as you have mentioned youu2019ve tried.
Just one note: Once you are on the Message Monitoring screen -> Filter (where you can select the dates, message status, etcu2026), there is a Dropdown box menu at center of the screen called u201Cmaximum Numberu201D where I believe you said you can only see 200 messages.
You may try to select u201C10.000u201D there and then cancel these messages from there.
However, if you prefer doing this in one go, you can do this by changing the status of the messages from u201Cerroru201D to status u201Cdeliveredu201D by executing following SQL statement at the database level:
UPDATE <DB Schema>.XI_AF_MSG SET STATUS='DLVD' WHERE MSG_ID='<MSG ID>
AND DIRECTION='<INBOUND OUTBOUND>'
Cheers,
Jorge Eidelwein

System Error u0096 Restart is Not Possible!

Hi guys,
I have a sync scenario that calls an http service. When the http service is not available (down) the message in the monitor has a sys error status and the restart is not possible. With an identical scenario, but async, the status is also system error but Manual Restart is possible.
My question is: this is a typical behavior for sync http scenarios? I would like to be able to restart this message, is it possible?
Thanks in advance,
Ricardo.

Hi Michal
Thanks for your quick response.
Im using these sync calls under a BPM and I found a way to reprocess this messages in system error. So, in Message Monitor open the PE and over the task in error (ex. send step) open the work item and go to EDIT menu, in EDIT menu press change and you will see on the left side Services for Administration and something like reprocess after error, press the execute button and the sync calls is restarted.
I believe without BPM is not possible restart sync calls, but with BPM it is
Thanks Michal.
Regards,
Ricardo.
Message was edited by: Ricardo Quintino
Message was edited by: Ricardo Quintino

Cancel System Error Messages from RWB

Hi All,
I have nearly 3000 messages those were got System Error in Integration Engine process, but when i check messages in SXMB_MONI all are success and written to target folders also.There is no problem absolutely.
Now i just want to cancel those System Error messages from RWB--Message Monitor to keep system green and do not want to see those system error messages again.
Iam not able to cancel those messages from RWM, it is saying that User and pwd incorrect but iam providing correct one only.
I went to details of that system error message from Message Monitor, i took message id and filtered with that in SXMB_MONI. i got the message with error state.Iam able to cancel that from MONI but not from RWB which is fine and disappearing from RWB list.
the thing is i can't copy each and every message id by opening details button for every message
How can i proceed for this. please advice me
REgards

Hi Ravi,
For example iam able to see system error message in RWB--Message Monitor under Integration Engine at 9:30
when i execute SXMB_MONI for the same time and see, there is no error message for that able to see success.
When i took message id from RWB--message monitor and filter that in MONI means it is showing me the error message.
I can able to cancel it from MONI which is fine. but this way i have 3000 messages in RWB--Message monitor under IE.
How to copy and paste then filter those error messages in MONI???this is pain process to copy each and every one by one
Iam not able to get those if i filter with the status group as System Error manual Restart Possible criteria
Regards

System error when send file with Sender File Adapter

Hi all,
I have configured a "File To ABAP Proxy" scenario. After configuring, i executed a "Test Configuration" in Integration Directory and it's all OK. But this file unable to reach into ABAP Proxy Target. In the Runtime WorkBench\Message Monitoring, I get an error message in below:
Engine: Adapter Engine
Status: *System Error     *
Start: 15.08.2008 14:04:01
End: 15.08.2008 14:19:01
Sender Service: BS_XI_SERVER
Interface Servic: urn://FILE_TO_PROXY
MI_EMPLOYEE_OB
In this case, I don't know why my Sender File Adapter is error and why status is "System Error" and why it can't reach into Target System. Can it concern a role user?
( For more clearly: I configured the source file and the path correctly. And i used the xml file with the content and the document name correctly. In general, the Sender Adapter File don't convert the sender file and its content is same as the Payload in the "Test Configuration", i think it is all OK.)
Could anyone please help me to resolve this problem, anyone can explain this error, how can i resolve this error?
Thanks a lot in advance,
Vinh Vo

Hi Chirag,
1.I source structure is very simple as below:
<ns0:MT_MATERIAL xmlns:ns0="urn://FILE_TO_PROXY">
   <MATERIAL>
      <WERKS>1000</WERKS>
      <MATNR>MAT00001</MATNR>
      <MAKTX>Chemical Material</MAKTX>
   </MATERIAL>
</ns0:MT_MATERIAL>
2. the Communication Channel Monitoring in Runtim WorkBench\Adapter Engine is OK for my Sender File Communication Channel, it's in Blue Light.
However, i don't know what's FCC?
Thanks and best regards,
Vinh Vo

E75 MfE: System error. Try again later.

When configuring my work Exchange account on my cell, I can't establish a connection to the server (I think). It attempts to connect and says it's connected, but no messages are displayed. In place is just (no messages). If I go to that mailbox's Mailbox Settings and hit Options -> View log, I get the follow info:
Time: <time>
Status: System error. Try again later.
Is there another log file somewhere on the phone that will give a more detailed description of what's happening than this file does? Or does anyone know what could be causing my issue? The info I'm using for the Exchange server details came from our IT department, and a fair number of Blackberries are used successfully by our employees with the same connection info the IT department gave me.
Thanks!
Message Edited by richmix on 07-Aug-2009 03:47 PM

Hi Nokia Team!
i have the same Problem with 3 different E75 phone. How can i solve this problems.
thanks

E72 System Error on Start up

I have just updated my E72 to the latest software and now I get a 'system error' on restarting my phone.
I am unable to do anything on it so cannot restore to previous version I am also unable to input the reset number!
Please HELP URGENTLY

I've not heard this problem before, but the only explanation I can think of is that something has trashed/deleted the shared runtime DLLs.
To fix the problem, please download this zip. There are 2 files inside it, copy them both into the "C:\windows\syswow64" folder.
Reboot, and then let me know if the problem is solved.

'System Error' status at Message Monitoring( HTTP to FILE )

I have created a scenario HTTP to FTP. I sent message to XI server using the HTTP Client.
After sending the message I am getting the response at browser.
Result:
http-Status: 200 Message accepted
Payload:
But when I look in to the Message monitoring at RWB, I am getting the message status as
System error. while going to the details i can see below error category.
Error Category MAPPING
Error Code EXCEPTION_DURING_EXECUTE
(Is the password different for port 50000 and 8000)
Please help me to solve this issue.
Thanks in Advance,
John

This is the trace message that I got for this error
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:70) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:231) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:63) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) 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:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_HTTP2File_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46)</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_HTTP2File_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:72) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) 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:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:46) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:41) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:70) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:231) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:63) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:77) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:88) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:63) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:80) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy24.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171) 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:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)</Trace>

"waiting" and "system error" status cannot be resent in rwb?

Hi,gurus:
In RWB->MESSAGE MONITORING,I can't resend or cancel the messages with the status " waiting" and "system error".
when I clicked "resend" button,it asked for user and password.After I was authentificated,the system didn't resend a message. Have you ever met this issue?
By the way,I could resend the error messages before.
Thanks in advance.

Hi,
I checked the note 1233918,and it talked about the same issue.
But the solution is as follows,which I don't know what to do.(Our PI version is PI7.0 SR3 SP14)
Symptom
When the first message for a managed system is cancelled or resent, after pressing ok in the logon pop-up nothing happens - message is not resent or cancelled. The logon data is correct, since subsequent resend/ cancel works without further logon request. Another symptom is cancelling or resending a wrong message, when using the filter mechanism in the table. E.g. the table displays messages A, B, C, D. If message C is selected and after that the filter is set so that message C is hidden from the filter selection, when selecting message D and trying to resend/cancel it, message C is cancelled/resent (the hidden one, previously selected) and nothing is happening with message D.
Other terms
NWA, PI, Message monitoring, resend, cancel
Reason and Prerequisites
The UI Proxy connection was not obtained properly. Another reason - TableAccessories was not invalidating the nodes properly. Also after filtering the result list, resend/cancel was taking wrong message Ids.
Solution
For SP5 install LMNWABASICCOMP05P_1.SCA or higher patch level.
For SP6 install LMNWABASICCOMP06P_1.SCA or higher patch level.

Resend XI Message RWD Status as System Error

Hi All,
The Message failed is due to FTP connection, In SXMB_Moni the status of the message was succesfully processed. Where as when i check in Runtime Workbench, the status shows as "System Error" and Adapter Engine Status says the same as connection failed.
When i tried to send the message from SXMB_MONI, it gives error message as " You cannot restart XML message DE43EEDA9B73E7F19797001F29E544F6 with this status/type"
I tried from RWD by selecting the message & click on Resend again the same sort of error message
Please let me know how to reprocess/resend the message, as the message was not send to the FTP.
Thanks
Bala L

You cannot restart XML message DE43EEDA9B73E7F19797001F29E544F6 with this status/type
check this blog to know how to solve the above problem:
/people/michal.krawczyk2/blog/2005/11/09/xi-restarting-successfully-processed-messages
Please note that the suggestion mentioned in above blog is to be applied only if you are in Development Environment
For some more reading: /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Regards,
Abhishek.

Notifications of XI-mgs in status 'System Error - Manual Restart Possible'

Similar Messages

Maybe you are looking for