Sxmb_moni system error

Hi Experts ,
I found this error in SXMB_MONI.please help me what would be the error.I have checked in SMQ1,SMQ2 also but the queues are not strucked.

<Trace level="1" type="T">User: PIECC</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="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">Docnum 0000000000881605</Trace>
<Trace level="1" type="T">Get the Metadata for port SAPR3D</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_STRUCTURE_GET Details</Trace>
<Trace level="2" type="T">Port : SAPR3D</Trace>
<Trace level="2" type="T">IDoctyp : /AFS/ORDERS06</Trace>
<Trace level="2" type="T">Cimtyp : ZIMPOINFO</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 current IDoc</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_SYNTAX_CHECK</Trace>
<Trace level="2" type="T">Port : SAPR3D</Trace>
<Trace level="2" type="T">IDoctyp : /AFS/ORDERS06</Trace>
<Trace level="2" type="T">Cimtyp : ZIMPOINFO</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>
<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">Message ID = 005056A961341EE189D58C5E5FB798DC</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="2" type="T">system-ID = PID</Trace>
<Trace level="2" type="T">client = 300</Trace>
<Trace level="2" type="T">language = E</Trace>
<Trace level="2" type="T">user = PIECC</Trace>
<Trace level="1" type="Timestamp">2011-12-14T23:36:04Z PST</Trace>
<Trace level="1" type="T">ACL Check is performed</Trace>
<Trace level="1" type="T">XML validation is executed</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC">
<Trace level="1" type="T">Queue name : XBTL0000</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
</Trace>
<Trace level="1" type="T">Generated prefixed queue name =</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface ZPOMSG./AFS/ORDERS06.ZIMPOINFO</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="2" type="T">system-ID = PID</Trace>
<Trace level="2" type="T">client = 300</Trace>
<Trace level="2" type="T">language = E</Trace>
<Trace level="2" type="T">user = PIECC</Trace>
<Trace level="1" type="Timestamp">2011-12-14T23:36:04Z PST</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>
- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
<Trace level="1" type="T">Reading sender agreement</Trace>
<Trace level="1" type="T">Message does not contain a sender agreement</Trace>
<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <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">Using Receiver Determination AC49C10FD6A33945A771DAA45DC95E91</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: - BC_HighJump</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 2</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - BC_CheckPoint</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:2</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <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) BC_CheckPoint SIIA_PO_Creation_CheckPoint</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: SIIA_PO_Creation_CheckPoint</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) BC_HighJump SI_PO_Creation_WS_I_Async</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: SI_PO_Creation_WS_I_Async</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:2</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT2->ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 2</Trace>
<Trace level="1" type="T">Multi-receiver split case</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Splitting loop start</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="2" type="T">child 1</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTM0000</Trace>
<Trace level="1" type="T">Persisting split kid = 005056A961341EE189D58C508D91B8DC</Trace>
<Trace level="1" type="T">Generated prefixed queue name =</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface ZPOMSG./AFS/ORDERS06.ZIMPOINFO</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface SIIA_PO_Creation_CheckPoint</Trace>
<Trace level="1" type="T">select interface namespace urn:foxhead.com/highjump/INF008/PO_Creation</Trace>
<Trace level="1" type="T">--no interface action for sender or receiver found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="2" type="T">system-ID = PID</Trace>
<Trace level="2" type="T">client = 300</Trace>
<Trace level="2" type="T">language = E</Trace>
<Trace level="2" type="T">user = PIECC</Trace>
<Trace level="1" type="Timestamp">2011-12-14T23:36:04Z PST</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
<Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
- 
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="1" type="T">Interface mapping missing in cache</Trace>
</Trace>
<Trace level="2" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
Regards,
Shaju

Hi,
pease see this thread,
Posting XML via HTTP post returns "Envelope missing in SOAP message header"
regrads,
ganesh.

Similar Messages

SXMB_MONI-system error occured during persist

Hi Friends
While running the SXMB_MONI tcode in my XI system i am getting this error:
"system error occured during persist"
I am on a production system please reply ASAP.
Thanks

Hi Aquarin,
then it is really strange.........
in RWB, see the status of Integration Engine - is it green or not...........i think it will not be green..........if it is not green, then see in the below messages, if you get any error message....................
just go to SICF and check all the services are running or not..........
in RWB, see in message monitoring what is happening to messages during the last 2 hours.............
Regards,
Rajeev Gupta

Application Error, System Error and Error in SXMB_Moni

Dear PI Gurus,
I am kinda new to PI(XI) environment, and my self confused when I try to search failed messages in XI. I saw in Status group, there is Application Error, system Error and Error under SXMB_MONI. And I am wondering what is the different between these errors. Worst to come it all errors, Why we do have this separated errors? Can anyone tell me, what is the difference between this errors?
Thank You
Regards
Ramesh

Hi
- Application Error related to SOAP
just look at tgis Blog
/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
also look at this Thread for SXMB_MONI-system error occured
SXMB_MONI-system error occured during persist
Regards
Abhishek
Edited by: Abhishek Agrahari on Jan 21, 2009 7:48 AM

PI 7.11 - How to create a System Error in SXMB_MONI using a Java Mapping

Hi
We ve go a Java Mapping in a File-to-HTTP Scenario. It works perfect except of one error case: if an empty source file or a source file with the wrong structure is delivered. In this case our Java Mapping forwards an empty payload to the HTTP channel. So, for PI is the mapping successful.
I'd like to recognize this case and invoke a system error in the SXMB_MONI, so that this mapping will be stopped and our alerting concept informs the users. I know, how to recognize the case in Java but need to know how to create the System Error Status in the PI System.
Thanks in advance
Michael

Hi Michael,
Please refer here for the mapping API description:
http://help.sap.com/javadocs/NW04S/SPS09/pi/com/sap/aii/mapping/api/package-summary.html
You can use the StreamTransformationException exception describet there to raise an error from your Java mapping. Direct link:
http://help.sap.com/javadocs/NW04S/SPS09/pi/com/sap/aii/mapping/api/StreamTransformationException.html
You might also consider using the "Empty-File Handling" option in sender file CC to avoid processing empty files by PI.
Hope this helps,
Greg

System Error in Message Monitoring while it shows checked flag in SXMB_MONI

Hia,
We are working on ABAP Proxy --> SAP PI 7.1 --> SOAP (Asynchronous Scenario).
(ECC -> PI -> Legacy CRM)
I have following queries:
1. While sending messge across to Legacy system, we can see CHECKED flag in SXMB_MONI but there is System Error in Message Monitoring. When checked legacy system is unable to receive any message. Cannot understand the issue.
2. Is there any way to check in PI system whether the message has reached Legacy System other than making scneario synchronous?
Regards

System is getting connected and able to send asynchronous messages to legacy system. But getting following error while sending synchronous error:
2010-05-10 13:15:05     Information     Delivering to channel: CC_SOAP_SOReject_Out
2010-05-10 13:15:05     Information     SOAP: request message entering the adapter with user J2EE_GUEST
2010-05-10 13:15:05     Information     SOAP: completed the processing
2010-05-10 13:15:05     Information     SOAP: continuing to response message f33caa90-5c07-11df-c659-96d147c2ff0f
2010-05-10 13:15:05     Error     SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.
2010-05-10 13:15:05     Error     Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.
2010-05-10 13:15:05     Error     Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.. Setting message to status failed.
2010-05-10 13:15:06     Error     The message status was set to FAIL.
I have already checked Data Structure and it is fine.
Regards
In this scenarios we are using XSLT mapping using CDATA.
Please suggest solution.

System Error in Parser in SXMB_MONI

Hello all,
For a File to XML scenario, when I check the tcode 'sxmb_moni'. If i click on any message it gives an error "System Error in parser".
It is not letting me get into the message.
Did anyone face this error. Please help me.
Thanks in advance.
Best Regards
Chakra and Somnath

Hello,
Thanks for ur Reply, but i guess you have got me wrong. I cannot even see the Mapping. Because the first screen where I see the messages in the 'sxmb_moni' (i.e. where the Flag marks are there , red, green, chequered), on clickin any message it gives me the "System Error in Parser ". I am not able to get into the second screen where we can see the inbound and the Outbound payloads.
What should I do for this.
Please help me out on this. Thanks in anticipation
Best regards
Chakra

How to capture System Error in XI?

Hello All,
1. Can any one tell me , How to capture the system error , Adapter Error and send the alert to make sure the guarenteed delivery from Source to Target via XI ?
2.I have done the configuration for to capture the mapping error in transaction ALRTCATDEF .But still i am not able to see any messages in my Alert Inbox???
I have checked with the two weblogs Alert step by step and Alert Trouble shooting guide.but still i am not getting any messages in Alert inbox .Any one can tell me how to fix this?
Thanks!

Hi,
You wrote:
<i>How to capture the system error , Adapter Error </i>
Errors are captures in many ways and at different stages,
like alert, sld errors or even sxmb_moni or even with visual administrator trace, I am not sure of your requirement but if you want a centrlished point to access all these error you may refer a good example as,
/people/michal.krawczyk2/blog/2005/09/07/xi-why-dont-start-searching-for-all-errors-from-one-place
<i>have checked with the two weblogs Alert step by step and Alert Trouble shooting guide.but still i am not getting any messages in Alert inbox .Any one can tell me how to fix this?</i>
The two weblogs are my favourite and best resources but still if you are missing, please elaborate if you are getting any errors or other fesible traces as to why your alerts are not coming in inbox.
Regards,
Anirban.

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

Catching System Error Message in Abap Proxy.

Hi all,
I want to know whether it is possible to catch the system error message from SXMB_MONI in proxy scenario's.
The error i am getting 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="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>403</SAP:P1>
<SAP:P2>Forbidden</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>Service is not active</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 403 with the description Forbidden Error when sending by HTTP (error code: 403, error text: Forbidden)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Is it possble to catch the above message text.
Regards,
Keith

Hi Keith,
Check this forums also should be definitely help u..
Error message handling in Integration Process
and
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/content.htm
also refer
Check this weblog once ... sure it will give u an idea..
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
and also go through this
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
Regards,
Sridhar

Messages stuck in QRFC inbound and outbound queues by system error

Hi Experts,
We faced a big problem in our PI server which stopped all the traffic in the iDoc to File interface. Both the QRFC queues (inbound - SMQ1 as outbound - SMQ2) where stuck by a system error.
In IDX5 of PI we saw two inbound iDocs on exact the same date/time of creation. Both iDocs are displayed in SXMB_MONI with the status "Canceled - Since Already Processed". The output files of both iDocs are generetad on the outbound side.
The output files are genereted with a date/time stamp in filename exactly as: "pi_20101106-221812-437.dat" and "pi_20101106-221812-438.dat". So it seems that both processes where running on exact the same time.
When looking into the system error we see the following details:
com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id 00505697-181b-1ddf-babd-68f1ac208528(INBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: [200]: Duplicate key
This caused that the QRFC queues where both stuck in inbound as outbound with a SYSERROR, so PI stopped and the queues should be reactivated manually.
Does anybody have some idea of the real cause of this error. We really want to prevent such situation in the future.
Thanks in advance!
Best regards,
Joost

Hi Joost,
Are you using an adpater module to avoid the same file name processed by the receiver channel ???
If this is the case change the filename and retest flow otherwise remove the module (ex: localejbs/AF_Modules/MessageTransformBean - Local Enterprise Bean) from the channel check it whether the file getting processed or not...
OR...you have an incorrect module configuration in the receiver channel.
Do not remove the standard SAP module and make sure that you add additional modules before it.
cheers,
Ram.

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

SOAP adapter engine with system error, problem with fault message.

HI,
I have IDOC -> PI -> SOAP scenario.
Idoc to PI is async. I have no problem in receiving the idoc in PI. The message mapping is carried out and sent to the adapter engine. I can also see the technical routing payload. It is sucessful at XML monitoring in SXMB_MONI.
The error is at PI -> SOAP.
I have wsdl provided by the receiver webservice. Which I have imported.
And created a service interface against this wsdl. I tried changing it to both sync and async.
I have also provided fault message.
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap
action = processDocument. Also provided user id and password.
I have a
Sender Agreement
Receiver determination
Interface determination
Receiver Agreement
I check in RWB adapter engine, this message goes to system error. The error log is as shown at the bottom.
When I see the message content, the SOap document shows me the details about IDOC, Instead I feel it should match
with the wsdl, where they have specified the corresponding interface name and address location etc.Please correct me.
How does the receiver know which service interface is it? The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same? I see that the soap document in the adapter engine has the
Service interface name which I created in the ER. Where in the document the Reciever interface name is sent?
Where can I see the generated soap document for the receiver?
Is there some setting/configuration required in PI for this to work?
I tried using the tcpgw to see the error. If I dont provide the service interface name in the communication channel
then I get the following error in the TCPGW. "The service cannot be found for the endpoint reference"
When I provide the service interface name in the communication channel I get a valid fault message.
Similarly
When I use SOAPUI, I can see the fault exception being return. The adapter engine doesnot show an equivalent message
instead it goes into system error as shown at the bottom. I guess this is expected, if so what is the work around? (I found this weblog /people/alessandro.guarneri/blog/2011/01/10/soap-fault-in-sap-pi-hijack-it, do I need to implement this? Or use ALEAUD?
The fault message what I see in SOAPUI has the below format.
<soapenv:Fault xmlns:axis2ns1="http://schemas.xmlsoap.org/soap/envelope/">
         <faultcode>axis2ns1:Server</faultcode>
         <faultstring>nested exception is: psdi.util.MXApplicationException: BMXAA7136E - Validation failed when the
                            database default values were set. See the associated message for more information.
           BMXAA4190E - Country NZ is not in the value list.</faultstring>
         <detail>
            <Exception>org.apache.axis2.AxisFault: nested exception is: psdi.util.MXApplicationException: BMXAA7136E
                      - Validation failed when the database default values were set. See the associated message for more information.
     BMXAA4190E - Country NZ is not in the value list.
            /Exception>
         </detail>
</soapenv:Fault>
And the fault message in my ER service interface is stanadard datatype ExchangeFaultData, which is different from
the above. Is this the problem? Can I change the data type here to be the same as above?
Audit log in the RWB adapter engine.
Time Stamp Type Description
30.09.2011 15:10:57 Information MP: processing local module Localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
30.09.2011 15:10:57 Information SOAP: request message entering the adapter with user J2EE_GUEST
30.09.2011 15:10:57 Information SOAP: completed the processing
30.09.2011 15:10:57 Information SOAP: sending a delivery error ack ...
30.09.2011 15:10:57 Information SOAP: sent a delivery error ack
30.09.2011 15:10:57 Error MP: exception caught with cause
com.sap.engine.interfaces.messaging.api.exception.MessagingException
30.09.2011 15:10:57 Error Adapter Framework caught exception: null
30.09.2011 15:10:57 Error Delivering the message to the application using connection
SOAP_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException.
30.09.2011 15:10:57 Information The message status was set to WAIT.
30.09.2011 15:10:57 Information The asynchronous message was successfully scheduled to be delivered at Fri Sep 30
15:15:57 NZDT 2011.

I tried changing it to both sync and async.
I have also provided fault message.
dont feel that you need to do above steps.
I have a
Sender Agreement
ideally you dont need a sender agreement (and a channel) for IDOC --> PI flow.
When I see the message content, the SOap document shows me the details about IDOC
this is fine...you may see fields as seen in EDI_DC40 of the IDOC...
How does the receiver know which service interface is it?
receiver need not know about the SI created in PI.
The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same?
you should the WSDL (external definition) as the Request Message in your service interface.
Is there some setting/configuration required in PI for this to work?
nothing specific...AFAIK
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap action
can you open the URL from Internet explorer...from your machine or from the machine which is in the same network as your PI server?
Things to check:
WSDL structure in PI and in target system is exactly the same.
does the target system require mesage in SOAP format (SOAP envelope - SOAP Header + SOAP body)?
target system is up and running?

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

System error in MDT

Hi Experts,
we got Interface Proxy to JDBC. the bach ground runs in SAP every day in the night and send the data to XI, Then XI will write to database.
In SAP back ground job runs successfully and send to XI. in XI successfull in sxmb_moni also.
but the message end up with system error in adapter engine.
when i restart the message in the morning it went through successfully.
Audit log is like this:
Audit Log for Message: 72737178-bcf0-484a-8462-68c8a7e7f1b0
Time Stamp Status Description
2008-01-29 21:10:43 Success Message successfully received by messaging system. Profile: XI URL: http://sappxi:58000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2008-01-29 21:10:43 Success Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-01-29 21:10:44 Success The message was successfully retrieved from the receive queue.
2008-01-29 21:10:44 Success Message successfully put into the queue.
2008-01-29 21:10:44 Success The message status set to DLNG.
2008-01-29 21:10:44 Success Delivering to channel: ReceiverChannel_JDBC
2008-01-29 21:10:44 Success MP: entering
2008-01-29 21:10:44 Success MP: processing local module localejbs/CallSapAdapter
2008-01-29 21:10:44 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2008-01-29 21:31:22 Success JDBC adapter receiver channel ReceiverChannel_JDBC: processing started; party , service JUSTENOUGH
Can anyone tell me is there anything problem with network related problem.
Kind Regards,
kiran

Hi Prateek,
There is no information available in audit log. there is no page available in audit log only it contains one page only, i dont why the audit log stoping there.
any input is appreciated.
Kind Regards,
kiran

System Error- Restart Not Possible

Hi All,
I have Synchronous scenario.
I am trying to handle system error in BPM. so if system error comes i m cancelling process.
So in sxmb_moni, my scenario is successful as it is not getting stuck into queue.
But it is giving me error as "System Error - restart not possible" .
But I need to resend / restart this message again.
So can u please guide me for same
Regards,
Manisha

When your WS id down you are handling the esception in your BPM perfectly....what more you can do is in the exception branch throw an alert to the support team from SAP saying that the processing for a particluar IDOC failed as there was an error while connecting to the end system......in this case you can ask them to restart this particular process once the WS is up....
One option wil also be to increase the default retry attempts of AE while connecting to the end system....affects performance....maximum retry attempts is 10 (if i am not wrong).....so if your WS comes up during this time you can send the message......
We have a similar case wherein same logic has been applied in BPM...which asks the support team to restart the process if the process fails due to a communication error with the end system.
Regards,
Abhishek.

Sxmb_moni system error

Similar Messages

Maybe you are looking for