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

Similar Messages

Error: XML parser (in SXMB_MONI)

Dear Friends,
I'm doing file to IDoc scenario. The file is picked from source directory and functional acknowledgement is coming for that picked file. Then next process is purchase order creation. In this I used java mapping. In SXMB_MONI I got the error as follows:
<?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_IDOC_RUNTIME</SAP:Code>
<SAP:P1>XML parser: Error in row 1 column 1, error unexpectedend-of-file</SAP:P1>
<SAP:P2/>
<SAP:P3/>
<SAP:P4/>
<SAP:AdditionalText/>
<SAP:ApplicationFaultMessage namespace=""/>
<SAP:Stack>Error: XML parser: Error in row 1 column 1, error unexpectedend-of-file</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Here upto Message Branch step payload contains xml file and the following steps having payload without any xml.
Please give me the solution for this problem.
Regards,
Jagan.

that means that the structure defined in MT is diferent that the one which arrive to PI.
check whehter the inbound strcture has the namespace in main segment or not. please paste the inbound strcture you get from SXI_monitor and the inbound structure in your MM
Thanks
Rodrigo

Error during parsing of SOAP header

Hi all,
I have configured the j-meter to send an http request to inegration engine of PI.
The request xml that I am sending is as follows:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
<SOAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30"
versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1">
</SOAP:Main>
</SOAP:Header>
<SOAP:Body>
<ns1:UnitOfMeasure xmlns:ns1="urn:sapappl:mdm:cp:eame:masterdata:uom:620">
<Record>
<FinishedMaterialCode>000000000000000233</FinishedMaterialCode>
<BaseUOM>KG</BaseUOM>
<AlternateUOM>GEB</AlternateUOM>
<UnitsInAlternateUOM>100</UnitsInAlternateUOM>
<UnitsInBaseUOM>2268</UnitsInBaseUOM>
<Active_Deleted></Active_Deleted>
</Record>
</ns1:UnitOfMeasure>
</SOAP:Body>
</SOAP:Envelope>
I am getting the following response from the XI:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during parsing of SOAP header</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="PARSER"/><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>System error in parser
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Any idea as to why PI is not able to parse the request header?
Thanks,
Amit

Hi,
Better to take WSDL from PI(ID window) and try.

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.

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

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

System config network error while parsing /etc/hosts

I am configuring RAC on Oracle Linux,i have configured /etc/hosts on both nodes,when ever i opened network, its displaying error message.
system config network error while parsing /etc/hosts
wrong ip on line 25
wrong ip on line 26
wrong ip on line 27
here is my host entries.
node1
====
[root@racnode1 ~]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
#::1 localhost6.localdomain6 localhost
#####Public#####
192.168.1.101 racnode1.reg.com racnode1
192.168.1.102 racnode2.reg.com racnode2
192.168.1.103 racnode3.reg.com racnode3
192.168.1.104 racnode4.reg.com racnode4
####Private######
10.10.1.1 racnode1-priv.reg.com racnode1-priv
10.10.1.2 racnode2-priv.reg.com racnode2-priv
10.10.1.3 racnode3-priv.reg.com racnode3-priv
10.10.1.4 racnode4-priv.reg.com racnode4-priv
#####Virtual#####
192.168.1.201 racnode1-vip.reg.com racnode1-vip
192.168.1.202 racnode2-vip.reg.com racnode2-vip
192.168.1.203 racnode3-vip.reg.com racnode3-vip
192.168.1.204 racnode4-vip.reg.com racnode4-vip
#SCAN
#192.168.1.301 racdb-scan.reg.com racdb-scan
#SCAN
192.168.1.301 racnode1-scan.reg.com racnode1-scan
192.168.1.302 racnode2-scan.reg.com racnode2-scan
192.168.1.303 racnode3-scan.reg.com racnode3-scan
[root@racnode1 ~]# hostname
racnode1.reg.com
[root@racnode1 ~]#
node2 host entries
===========
[root@racnode2 ~]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
#::1 localhost6.localdomain6 localhost
#####Public#####
192.168.1.101 racnode1.reg.com racnode1
192.168.1.102 racnode2.reg.com racnode2
192.168.1.103 racnode3.reg.com racnode3
192.168.1.104 racnode4.reg.com racnode4
####Private######
10.10.1.1 racnode1-priv.reg.com racnode1-priv
10.10.1.2 racnode2-priv.reg.com racnode2-priv
10.10.1.3 racnode3-priv.reg.com racnode3-priv
10.10.1.4 racnode4-priv.reg.com racnode4-priv
#####Virtual#####
192.168.1.201 racnode1-vip.reg.com racnode1-vip
192.168.1.202 racnode2-vip.reg.com racnode2-vip
192.168.1.203 racnode3-vip.reg.com racnode3-vip
192.168.1.204 racnode4-vip.reg.com racnode4-vip
#SCAN
#192.168.1.301 racdb-scan.reg.com racdb-scan
#SCAN
192.168.1.301 racnode1-scan.reg.com racnode1-scan
192.168.1.302 racnode2-scan.reg.com racnode2-scan
192.168.1.303 racnode3-scan.reg.com racnode3-scan
[root@racnode2 ~]#
i am not able to ping racnode1-priv or racnode2-priv.
from node1:
========
[root@racnode1 ~]# ping racnode2-priv
PING racnode2-priv.reg.com (10.10.1.2) 56(84) bytes of data.
From racnode1-priv.reg.com (10.10.1.1) icmp_seq=2 Destination Host Unreachable
From racnode1-priv.reg.com (10.10.1.1) icmp_seq=3 Destination Host Unreachable
From racnode1-priv.reg.com (10.10.1.1) icmp_seq=4 Destination Host Unreachable
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4002ms
, pipe 3
[root@racnode1 ~]#
from node2:
=======
[root@racnode2 ~]# ping racnode1-priv
PING racnode1-priv.reg.com (10.10.1.1) 56(84) bytes of data.
From racnode2-priv.reg.com (10.10.1.2) icmp_seq=2 Destination Host Unreachable
From racnode2-priv.reg.com (10.10.1.2) icmp_seq=3 Destination Host Unreachable
From racnode2-priv.reg.com (10.10.1.2) icmp_seq=4 Destination Host Unreachable
--- racnode1-priv.reg.com ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms
, pipe 3
[root@racnode2 ~]#
any idea where configuration went wrong.
Thanks

here is output, i can see lot of additional characters.
[root@racnode1 ~]# cat -vet /etc/hosts
# Do not remove the following line, or various programs$
# that require network functionality will fail.$
127.0.0.1 localhost.localdomain localhost$
#::1^I^Ilocalhost6.localdomain6 localhost$
$
#####Public#####$
192.168.1.101 racnode1.reg.com racnode1$
192.168.1.102 racnode2.reg.com racnode2$
192.168.1.103 racnode3.reg.com racnode3$
192.168.1.104 racnode4.reg.com racnode4$
####Private######$
10.10.1.1 racnode1-priv.reg.com racnode1-priv$
10.10.1.2 racnode2-priv.reg.com racnode2-priv$
10.10.1.3 racnode3-priv.reg.com racnode3-priv$
10.10.1.4 racnode4-priv.reg.com racnode4-priv$
#####Virtual#####$
192.168.1.201 racnode1-vip.reg.com racnode1-vip$
192.168.1.202 racnode2-vip.reg.com racnode2-vip$
192.168.1.203 racnode3-vip.reg.com racnode3-vip$
192.168.1.204 racnode4-vip.reg.com racnode4-vip$
#SCAN$
#192.168.1.301 racdb-scan.reg.com racdb-scan$
#SCAN$
192.168.1.301^Iracnode1-scan.reg.com^Iracnode1-scan$
192.168.1.302^Iracnode2-scan.reg.com^Iracnode2-scan$
192.168.1.303^Iracnode3-scan.reg.com^Iracnode3-scan$
[root@racnode1 ~]#
from node2:
========
[root@racnode2 ~]# cat -vet /etc/hosts
# Do not remove the following line, or various programs$
# that require network functionality will fail.$
127.0.0.1 localhost.localdomain localhost$
#::1^I^Ilocalhost6.localdomain6 localhost$
$
#####Public#####$
192.168.1.101 racnode1.reg.com racnode1$
192.168.1.102 racnode2.reg.com racnode2$
192.168.1.103 racnode3.reg.com racnode3$
192.168.1.104 racnode4.reg.com racnode4$
####Private######$
10.10.1.1 racnode1-priv.reg.com racnode1-priv$
10.10.1.2 racnode2-priv.reg.com racnode2-priv$
10.10.1.3 racnode3-priv.reg.com racnode3-priv$
10.10.1.4 racnode4-priv.reg.com racnode4-priv$
#####Virtual#####$
192.168.1.201 racnode1-vip.reg.com racnode1-vip$
192.168.1.202 racnode2-vip.reg.com racnode2-vip$
192.168.1.203 racnode3-vip.reg.com racnode3-vip$
192.168.1.204 racnode4-vip.reg.com racnode4-vip$
#SCAN$
#192.168.1.301 racdb-scan.reg.com racdb-scan$
#SCAN$
$
192.168.1.301^Iracnode1-scan.reg.com^Iracnode1-scan$
192.168.1.302^Iracnode2-scan.reg.com^Iracnode2-scan$
192.168.1.303^Iracnode3-scan.reg.com^Iracnode3-scan$
Edited by: Endeca on Apr 7, 2013 10:13 AM

Error while parsing or executing XML-SQL document attribute "action" missin

Hi All,
I am doing a scenario for IDOC to JDBC, When I push IDOC from R/3 , IDOC sent to XI System successfully,
I have also checked in SXMB_MONI it is showing the successful staus without any errors, and I have also copied the xml structure from main document of payloads and tested the mapping in Integration Designer, and it is showing successfull message.
here is the xml structure from payloads of Request Message Mapping ........
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:RTACOGRP_RECEIVER_MT xmlns:ns0="http://prospecta.com/wsorta/cosmas/idoc2jdbc">
- <COGRP_TMP_PROC action="EXECUTE">
<IDOCNUMBER isInput="TRUE" type="CHAR">1000001</IDOCNUMBER>
<E1COGH_NUMBER isInput="TRUE" type="CHAR">1</E1COGH_NUMBER>
<E1COGH_HIGHERSEGMENT isInput="TRUE" type="CHAR">1</E1COGH_HIGHERSEGMENT>
<E1COGH_MSGFN isInput="TRUE" type="CHAR">1</E1COGH_MSGFN>
<E1COGH_GROUPTYPE isInput="TRUE" type="CHAR">1</E1COGH_GROUPTYPE>
<E1COGH_GROUPNAME isInput="TRUE" type="CHAR">1</E1COGH_GROUPNAME>
<E1COGH_KOKRS isInput="TRUE" type="CHAR">1</E1COGH_KOKRS>
<E1COGHT_NUMBER isInput="TRUE" type="CHAR">1</E1COGHT_NUMBER>
<E1COGHT_HIGHERSEGMENT isInput="TRUE" type="CHAR">2</E1COGHT_HIGHERSEGMENT>
<E1COGHT_LANGU isInput="TRUE" type="CHAR">2</E1COGHT_LANGU>
<E1COGHT_DESCRIPT isInput="TRUE" type="CHAR">2</E1COGHT_DESCRIPT>
<E1COGHT_LANGU_ISO isInput="TRUE" type="CHAR">2</E1COGHT_LANGU_ISO>
<E1COGV_NUMBER isInput="TRUE" type="CHAR">1</E1COGV_NUMBER>
<E1COGV_HIGHERSEGMENT isInput="TRUE" type="CHAR">3</E1COGV_HIGHERSEGMENT>
<E1COGV_FROMVALUE isInput="TRUE" type="CHAR">6</E1COGV_FROMVALUE>
<E1COGV_TOVALUE isInput="TRUE" type="CHAR">6</E1COGV_TOVALUE>
<E1COGS_NUMBER isInput="TRUE" type="CHAR">1</E1COGS_NUMBER>
<E1COGS_HIGHERSEGMENT isInput="TRUE" type="CHAR">5</E1COGS_HIGHERSEGMENT>
<E1COGS_SUBGROUP isInput="TRUE" type="CHAR">4</E1COGS_SUBGROUP>
<E1COGHR_NUMBER isInput="TRUE" type="CHAR">1</E1COGHR_NUMBER>
<E1COGHR_HIGHERSEGMENT isInput="TRUE" type="CHAR">6</E1COGHR_HIGHERSEGMENT>
<E1COGHR_SNAME isInput="TRUE" type="CHAR">3</E1COGHR_SNAME>
<E1COGHR_PRTCLASS isInput="TRUE" type="CHAR">3</E1COGHR_PRTCLASS>
<E1COGHR_AUTHGR isInput="TRUE" type="CHAR">3</E1COGHR_AUTHGR>
<E1COGSR_NUMBER isInput="TRUE" type="CHAR">1</E1COGSR_NUMBER>
<E1COGSR_HIGHERSEGMENT isInput="TRUE" type="CHAR">7</E1COGSR_HIGHERSEGMENT>
<E1COGSR_XSUPPRESS isInput="TRUE" type="CHAR">5</E1COGSR_XSUPPRESS>
<E1COGSR_PRTCLASS isInput="TRUE" type="CHAR">5</E1COGSR_PRTCLASS>
<E1COGSR_LNAME isInput="TRUE" type="CHAR">5</E1COGSR_LNAME>
<E1COGVT_NUMBER isInput="TRUE" type="CHAR">1</E1COGVT_NUMBER>
<E1COGVT_HIGHERSEGMENT isInput="TRUE" type="CHAR">9</E1COGVT_HIGHERSEGMENT>
<E1COGVT_LANGU isInput="TRUE" type="CHAR">7</E1COGVT_LANGU>
<E1COGVT_DESCRIPT isInput="TRUE" type="CHAR">7</E1COGVT_DESCRIPT>
<E1COGVT_LANGU_ISO isInput="TRUE" type="CHAR">7</E1COGVT_LANGU_ISO>
<E1COGVR_NUMBER isInput="TRUE" type="CHAR">1</E1COGVR_NUMBER>
<E1COGVR_HIGHERSEGMENT isInput="TRUE" type="CHAR">12</E1COGVR_HIGHERSEGMENT>
<E1COGVR_XSUPPRESS isInput="TRUE" type="CHAR">8</E1COGVR_XSUPPRESS>
<E1COGVR_PRTCLASS isInput="TRUE" type="CHAR">8</E1COGVR_PRTCLASS>
<E1COGVR_LNAME isInput="TRUE" type="CHAR">8</E1COGVR_LNAME>
</COGRP_TMP_PROC>
</ns0:RTACOGRP_RECEIVER_MT>
When I checked for component monitoring in runtime workbench....
these are the messages........
Error while parsing or executing XML-SQL document: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
Here are the messages from message monitoring ......
2007-06-07 12:42:17 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2007-06-07 12:42:17 Success JDBC adapter receiver channel RTACOGRP_COM_Chan: processing started; party , service WSORTABS
2007-06-07 12:42:17 Error No "action" attribute found in XML document ("action" attribute missing or wrong XML structure)
2007-06-07 12:42:17 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
2007-06-07 12:42:17 Error Exception caught by adapter framework: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
2007-06-07 12:42:17 Error Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure).
2007-06-07 12:42:17 Error The message status set to NDLV.
Can any body please resolve the problem.....
Thanks in Advance
Murthy

Bhavesh,
Now I have changed the data structure , and the resultant structure is like this...
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:RTACOGRP_RECEIVER_MT xmlns:ns0="http://prospecta.com/wsorta/cosmas/idoc2jdbc">
- <Statement>
- <COGRP_TMP_PROC action="EXECUTE">
<IDOCNUMBER isInput="TRUE" type="CHAR">100002223</IDOCNUMBER>
<E1COGH_NUMBER isInput="TRUE" type="CHAR">1</E1COGH_NUMBER>
<E1COGH_HIGHERSEGMENT isInput="TRUE" type="CHAR">1</E1COGH_HIGHERSEGMENT>
<E1COGH_MSGFN isInput="TRUE" type="CHAR">H</E1COGH_MSGFN>
<E1COGH_GROUPTYPE isInput="TRUE" type="CHAR">H</E1COGH_GROUPTYPE>
<E1COGH_GROUPNAME isInput="TRUE" type="CHAR">H</E1COGH_GROUPNAME>
<E1COGH_KOKRS isInput="TRUE" type="CHAR">H</E1COGH_KOKRS>
<E1COGHT_NUMBER isInput="TRUE" type="CHAR">1</E1COGHT_NUMBER>
<E1COGHT_HIGHERSEGMENT isInput="TRUE" type="CHAR">2</E1COGHT_HIGHERSEGMENT>
<E1COGHT_LANGU isInput="TRUE" type="CHAR">T</E1COGHT_LANGU>
<E1COGHT_DESCRIPT isInput="TRUE" type="CHAR">T</E1COGHT_DESCRIPT>
<E1COGHT_LANGU_ISO isInput="TRUE" type="CHAR">T</E1COGHT_LANGU_ISO>
<E1COGV_NUMBER isInput="TRUE" type="CHAR">1</E1COGV_NUMBER>
<E1COGV_HIGHERSEGMENT isInput="TRUE" type="CHAR">3</E1COGV_HIGHERSEGMENT>
<E1COGV_FROMVALUE isInput="TRUE" type="CHAR">V</E1COGV_FROMVALUE>
<E1COGV_TOVALUE isInput="TRUE" type="CHAR">V</E1COGV_TOVALUE>
<E1COGS_NUMBER isInput="TRUE" type="CHAR">1</E1COGS_NUMBER>
<E1COGS_HIGHERSEGMENT isInput="TRUE" type="CHAR">5</E1COGS_HIGHERSEGMENT>
<E1COGS_SUBGROUP isInput="TRUE" type="CHAR">S</E1COGS_SUBGROUP>
<E1COGHR_NUMBER isInput="TRUE" type="CHAR">1</E1COGHR_NUMBER>
<E1COGHR_HIGHERSEGMENT isInput="TRUE" type="CHAR">7</E1COGHR_HIGHERSEGMENT>
<E1COGHR_SNAME isInput="TRUE" type="CHAR">R</E1COGHR_SNAME>
<E1COGHR_PRTCLASS isInput="TRUE" type="CHAR">R</E1COGHR_PRTCLASS>
<E1COGHR_AUTHGR isInput="TRUE" type="CHAR">R</E1COGHR_AUTHGR>
<E1COGSR_NUMBER isInput="TRUE" type="CHAR">1</E1COGSR_NUMBER>
<E1COGSR_HIGHERSEGMENT isInput="TRUE" type="CHAR">8</E1COGSR_HIGHERSEGMENT>
<E1COGSR_XSUPPRESS isInput="TRUE" type="CHAR">S</E1COGSR_XSUPPRESS>
<E1COGSR_PRTCLASS isInput="TRUE" type="CHAR">S</E1COGSR_PRTCLASS>
<E1COGSR_LNAME isInput="TRUE" type="CHAR">S</E1COGSR_LNAME>
<E1COGVT_NUMBER isInput="TRUE" type="CHAR">1</E1COGVT_NUMBER>
<E1COGVT_HIGHERSEGMENT isInput="TRUE" type="CHAR">10</E1COGVT_HIGHERSEGMENT>
<E1COGVT_LANGU isInput="TRUE" type="CHAR">T</E1COGVT_LANGU>
<E1COGVT_DESCRIPT isInput="TRUE" type="CHAR">T</E1COGVT_DESCRIPT>
<E1COGVT_LANGU_ISO isInput="TRUE" type="CHAR">T</E1COGVT_LANGU_ISO>
<E1COGVR_NUMBER isInput="TRUE" type="CHAR">1</E1COGVR_NUMBER>
<E1COGVR_HIGHERSEGMENT isInput="TRUE" type="CHAR">11</E1COGVR_HIGHERSEGMENT>
<E1COGVR_XSUPPRESS isInput="TRUE" type="CHAR">E</E1COGVR_XSUPPRESS>
<E1COGVR_PRTCLASS isInput="TRUE" type="CHAR">E</E1COGVR_PRTCLASS>
<E1COGVR_LNAME isInput="TRUE" type="CHAR">E</E1COGVR_LNAME>
</COGRP_TMP_PROC>
</Statement>
</ns0:RTACOGRP_RECEIVER_MT>
Now in message monitoring error is showing like this...
Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'COGRP_TMP_PROC' (structure 'Statement'): java.sql.SQLException: General error
Now in Component Monitoring error is showing like this....
Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'COGRP_TMP_PROC' (structure 'Statement'): java.sql.SQLException: General error
I have tested the stored procedure in sql by giving the same values , it was successfully executed..
Can you please tell me where is the error still in structure ...
Thanks in Advance,
Murthy.

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' 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>

Error while parsing or executing XML-SQL document

friends,
my scenario is based on file to jdbc.i am facing an error in receiver CC in RWB.
The error states that '
Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'MATMAS' (structure 'STATEMENT'): java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]String or binary data would be truncated.'
My SOAP xml message is
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Header>
- <sap:Main xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3" versionMinor="0" SOAP:mustUnderstand="1" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
<sap:TimeSent>2008-02-06T22:30:21Z</sap:TimeSent>
- <sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<sap:Service>ECC</sap:Service>
</sap:Sender>
- <sap:Receiver>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<sap:Service>BS_JDBC</sap:Service>
</sap:Receiver>
<sap:Interface namespace="http://file_to_jdbc">MI_JDBC_RECEIVER</sap:Interface>
</sap:Main>
- <sap:ReliableMessaging xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:QualityOfService>ExactlyOnce</sap:QualityOfService>
</sap:ReliableMessaging>
- <sap:DynamicConfiguration xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="Directory">
sapecc50\sapmnt\trans</sap:Record>
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="FileEncoding">UTF-8</sap:Record>
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="FileType">txt</sap:Record>
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="FileName">matmas1.txt</sap:Record>
</sap:DynamicConfiguration>
- <sap:HopList xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
- <sap:Hop timeStamp="2008-02-06T22:30:21Z" wasRead="false">
<sap:Engine type="AE">af.e6e.sapecc6eval</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XIRA</sap:Adapter>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
<sap:Info />
</sap:Hop>
- <sap:Hop timeStamp="2008-02-06T22:30:21Z" wasRead="false">
<sap:Engine type="IS">is.01.sapecc6eval</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XI</sap:Adapter>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
<sap:Info>3.0</sap:Info>
</sap:Hop>
- <sap:Hop timeStamp="2008-02-06T22:30:22Z" wasRead="false">
<sap:Engine type="AE">af.e6e.sapecc6eval</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XIRA</sap:Adapter>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
</sap:Hop>
</sap:HopList>
- <sap:Diagnostic xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:TraceLevel>Information</sap:TraceLevel>
<sap:Logging>Off</sap:Logging>
</sap:Diagnostic>
</SOAP:Header>
- <SOAP:Body>
- <sap:Manifest xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <sap:Payload xlink:type="simple" xlink:href="cid:[email protected]">
<sap:Name>MainDocument</sap:Name>
<sap:Description />
<sap:Type>Application</sap:Type>
</sap:Payload>
</sap:Manifest>
</SOAP:Body>
</SOAP:Envelope>
and payload message is
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_JDBC_RECEIVER xmlns:ns0="http://file_to_jdbc">
- <STATEMENT>
- <ROW action="INSERT">
<TABLE>MATMAS</TABLE>
- <access>
<MATNR>38</MATNR>
<MTART>HALB</MTART>
<MATKL>00107</MATKL>
<MEINS>pc</MEINS>
<ERSDA>2008.04.05</ERSDA>
<BRGEW>10</BRGEW>
<NTGEW>12</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>88</MATNR>
<MTART>FERT</MTART>
<MATKL>02004</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2008.04.05</ERSDA>
<BRGEW>12</BRGEW>
<NTGEW>13</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>89</MATNR>
<MTART>FERT</MTART>
<MATKL>02004</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2008.03.02</ERSDA>
<BRGEW>12</BRGEW>
<NTGEW>14</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>98</MATNR>
<MTART>HALB</MTART>
<MATKL>2</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2006.09.01</ERSDA>
<BRGEW>12</BRGEW>
<NTGEW>12</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>170</MATNR>
<MTART>NLAG</MTART>
<MATKL>4</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2005.03.02</ERSDA>
<BRGEW>2</BRGEW>
<NTGEW>3</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>178</MATNR>
<MTART>NLAG</MTART>
<MATKL>4</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.03.06</ERSDA>
<BRGEW>3</BRGEW>
<NTGEW>4</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>188</MATNR>
<MTART>NLAG</MTART>
<MATKL>5</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.05.02</ERSDA>
<BRGEW>2</BRGEW>
<NTGEW>3</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>288</MATNR>
<MTART>HALB</MTART>
<MATKL>101</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2006.02.11</ERSDA>
<BRGEW>5</BRGEW>
<NTGEW>4</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>358</MATNR>
<MTART>HAWA</MTART>
<MATKL>2</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.09.09</ERSDA>
<BRGEW>500</BRGEW>
<NTGEW>500</NTGEW>
<GEWEI>G</GEWEI>
</access>
- <access>
<MATNR>359</MATNR>
<MTART>HAWA</MTART>
<MATKL>2</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.08.01</ERSDA>
<BRGEW>20</BRGEW>
<NTGEW>10</NTGEW>
<GEWEI>G</GEWEI>
</access>
</ROW>
</STATEMENT>
</ns0:MT_JDBC_RECEIVER>
Could anybody help me in sorting out this issue.My advance thanks

hi,
ypur structure is bad defined.
if you want to do an insert, the DT should be
<ns0:MT_JDBC_RECEIVER xmlns:ns0="http://file_to_jdbc">
___<StatementName>
______<dbTableName action=INSERT>
_____<table>MATMAS</table>
_______ <access>
___________<MATNR>38</MATNR>
___________<MTART>HALB</MTART>
___________<MATKL>00107</MATKL>
___________<MEINS>pc</MEINS>
___________<ERSDA>2008.04.05</ERSDA>
___________<BRGEW>10</BRGEW>
___________<NTGEW>12</NTGEW>
___________<GEWEI>KG</GEWEI>
______</access>
_____</dbTableName>
__ </StatementName>
</ns0:MT_JDBC_RECEIVER>
the ROW field is used when you wait receive data from DB for example you execute and SQL Query from Sender communication channel "SELECT name FROM TABLE Names"
so, the result of this query would be, for example:
<row>
____<name>joge</name>
</row>
<row>
____<name>pepe</name>
</row>
<row>
____<name>nicola</name>
</row>
See this link
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/frameset.htm
Thanks
Rodrigo
Edited by: Rodrigo Pertierra on Feb 8, 2008 8:40 AM
Edited by: Rodrigo Pertierra on Feb 8, 2008 8:42 AM

IMAP error messages "Error while parsing IMAP response"

I'm getting thousands of IMAP errors every hour, can I shut those off?
My console log is flooded with them and it keeps me from seeing anything else
in the system log. The IMAP errors happen continuously while Mail.app is running.
It looks like debug output from Mail.app !?!
IMAP server is Beehive Server -- it's my company email so I need to use it.
Windows Outlook (Windows 7) shows no errors, possibly they're silently ignored
on Windows. My disk is writing almost continuously when Mail.appo is running.
Sample error: (thousands are generated per hour)
Apr 8 10:29:18 Js-Coolio-iMac.local Mail[22903]: Error while parsing IMAP response (null): Incomplete response
 Remaining text: < Gian Luigi >
 Full text: < Gian Luigi >
Any idea how to shut these off? I reinstalled Mavericks, no improvement as expected
since this seems to be Mail complaining about IMAP protocol issues.
Thanks in advance for any suggestions. And yes I've rebooted, reinstalled the IMAP account,
reinstalled Mavericks, etc.
Entrecheck follows...
Hardware Information:
 iMac (27-inch, Late 2009)
 iMac - model: iMac11,1
 1 2.8 GHz Intel Core i7 CPU: 4 cores
 12 GB RAM
Video Information:
 ATI Radeon HD 4850 - VRAM: 512 MB
System Software:
 OS X 10.9.2 (13C64) - Uptime: 9 days 20:39:45
Disk Information:
 ST31000528ASQ disk0 : (1 TB)
 EFI (disk0s1) <not mounted>: 209.7 MB
 Macintosh HD (disk0s2) / [Startup]: 999.35 GB (801.18 GB free)
 Recovery HD (disk0s3) <not mounted>: 650 MB
 OPTIARC DVD RW AD-5680H
USB Information:
 Seagate Backup+ Desk 3 TB
 disk1s1 (disk1s1) <not mounted>: 209.7 MB
 JOHN TM (disk1s2) /Volumes/JOHN TM: 2 TB (1.81 TB free)
 LIU TM (disk1s3) /Volumes/LIU TM: 500 GB (203.45 GB free)
 Untitled 3 (disk1s4) /Volumes/Untitled 3: 499.39 GB (498.94 GB free)
 Apple Inc. BRCM2046 Hub
 Apple Inc. Bluetooth USB Host Controller
 Apple Internal Memory Card Reader
 Griffin Technology, Inc iMic USB audio system
 Apple, Inc. Keyboard Hub
 Logitech USB Trackball
 Apple, Inc Apple Keyboard
 Apple Computer, Inc. IR Receiver
 Apple Inc. Built-in iSight
FireWire Information:
Thunderbolt Information:
Configuration files:
 /etc/hosts - Count: 4
Kernel Extensions:
 com.seagate.driver.PowSecDriverCore (5.2.4 - SDK 10.4)
 com.seagate.driver.PowSecLeafDriver_10_5 (5.2.4 - SDK 10.5)
Launch Daemons:
 [System] com.adobe.fpsaud.plist 3rd-Party support link
 [System] com.barebones.textwrangler.plist 3rd-Party support link
 [System] com.oracle.java.Helper-Tool.plist 3rd-Party support link
Launch Agents:
 [System] com.oracle.java.Java-Updater.plist 3rd-Party support link
 [System] net.culater.SIMBL.Agent.plist 3rd-Party support link
User Launch Agents:
 [not loaded] com.adobe.ARM.[...].plist 3rd-Party support link
 [not loaded] com.google.keystone.agent.plist 3rd-Party support link
 [not loaded] com.leadertech.PowerRegister.SEA1.7c77b2ab072a21a06107fccae868ff4b.plist 3rd-Party support link
 [not loaded] com.valvesoftware.steamclean.plist 3rd-Party support link
User Login Items:
 Flux
 smcFanControl
 SpeechSynthesisServer
 AdobeResourceSynchronizer
 Flux (13.0)
Internet Plug-ins:
 Default Browser: Version: 537 - SDK 10.9
 Flip4Mac WMV Plugin: Version: 3.1.0.24 - SDK 10.8 3rd-Party support link
 AmazonMP3DownloaderPlugin101750: Version: AmazonMP3DownloaderPlugin 1.0.17 - SDK 10.4 3rd-Party support link
 RealPlayer Plugin: Version: (null) 3rd-Party support link
 AdobePDFViewerNPAPI: Version: 10.1.3 3rd-Party support link
 FlashPlayer-10.6: Version: 12.0.0.77 - SDK 10.6 3rd-Party support link
 MRJPlugin: Version: 1.0-JEP-0.9.0 3rd-Party support link
 QuickTime Plugin: Version: 7.7.3
 Flash Player: Version: 12.0.0.77 - SDK 10.6 3rd-Party support link
 iPhotoPhotocast: Version: 7.0
 AdobePDFViewer: Version: 10.1.3 3rd-Party support link
 JavaAppletPlugin: Version: Java 7 Update 51 3rd-Party support link
Safari Extensions:
 Ghostery: Version: 5.1.0
 AdBlock: Version: 2.6.18
 Turn Off the Lights: Version: 2.3.0.5
Audio Plug-ins:
 BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
 AirPlay: Version: 2.0 - SDK 10.9
 AppleAVBAudio: Version: 203.2 - SDK 10.9
 iSightAudio: Version: 7.7.3 - SDK 10.9
iTunes Plug-ins:
 Quartz Composer Visualizer: Version: 1.4 - SDK 10.9
User Internet Plug-ins:
 WebEx: Version: 1.0 3rd-Party support link
 WebEx64: Version: 1.0 - SDK 10.5 3rd-Party support link
 Google Earth Web Plug-in: Version: 7.1 3rd-Party support link
3rd Party Preference Panes:
 RCDefaultApp
 Flash Player 3rd-Party support link
 Flip4Mac WMV 3rd-Party support link
 Java 3rd-Party support link
 MenuMeters 3rd-Party support link
Old Applications:
 asannotation2: Version: 10.21.26.0 - SDK 10.5 3rd-Party support link
 /Users/[redacted]/Library/Application Support/WebEx Folder/924/asannotation2.app
 convertpdf: Version: 1.2 - SDK 10.5 3rd-Party support link
 /Users/[redacted]/Library/Application Support/WebEx Folder/1224/convertpdf/convertpdf.app
 Neverwinter Nights 2: Version: 1.23.1765 - SDK 10.5 3rd-Party support link
 Amazon MP3 Downloader: Version: INFO_PLIST_VERSION - SDK 10.4 3rd-Party support link
 TurboTax Deluxe 2011: Version: 2011.r17.007 - SDK 10.4 3rd-Party support link
 Ventrilo: Version: 3.0.13 - SDK 10.5 3rd-Party support link
 /Users/[redacted]/Library/Application Support/WebEx Folder/1224
 Cisco WebEx Meeting Center: Version: 1207.04.2732.10 - SDK 10.5 3rd-Party support link
 asannotation2: Version: 8.25.31.0 - SDK 10.5 3rd-Party support link
 atmsupload: Version: 4.14.29.0 - SDK 10.5 3rd-Party support link
 convertpdf: Version: 1.2 - SDK 10.5 3rd-Party support link
Time Machine:
 Skip System Files: NO
 Auto backup: YES
 Volumes being backed up:
 Macintosh HD: Disk size: 930.71 GB Disk used: 184.55 GB
 Destinations:
 JOHN TM [Local] (Last used)
 Total size: 2
 Total number of backups: 51
 Oldest backup: 2014-01-09 05:11:53 +0000
 Last backup: 2014-04-04 08:40:29 +0000
 Size of backup disk: Adequate
 Backup size 2 > (Disk used 184.55 GB X 3)
 Time Machine details may not be accurate.
 All volumes being backed up may not be listed.
Top Processes by CPU:
 2% WindowServer
 1% EtreCheck
 0% SystemUIServer
 0% com.apple.WebKit.Networking
 0% softwareupdated
Top Processes by Memory:
 344 MB Safari
 258 MB mds_stores
 258 MB com.apple.IconServicesAgent
 172 MB softwareupdated
 172 MB soffice
Virtual Memory Information:
 3.05 GB Free RAM
 5.12 GB Active RAM
 2.71 GB Inactive RAM
 1.05 GB Wired RAM
 7.04 GB Page-ins
 15 MB Page-outs

try Mail is not syncing an imap account correctly
(https://discussions.apple.com/message/21904088#21904088) , it just worked for me.

System Error in Message Monitoring -Proxy to SOAP async scenario

Hi All,
My scenario is ABAP Proxy---> SAP PI 7.1 ---> WEbService(Asynchronous SOAP ).
In Moni message is showing successful Flag, but message has got stuck in "system Error" at message monitoring.I can't see any Audit log in Message monitoring .
but in related Soap Receiver communication channel i can see the below Error
"2010-08-11 09:54:15 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005.
2010-08-11 09:54:15 Information SOAP: sending a delivery error ack ...
2010-08-11 09:54:15 Information SOAP: sent a delivery error ack
2010-08-11 09:54:15 Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005.
2010-08-11 09:54:15 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. ---> Retrieving the COM class factory for component with CLSID {00226D6E-6A57-44DB-9DDC-66FDCB2869B3} failed due to the following error: 80070005. "
Please help , what could be the problem.
Thanks in Advance.
Jyoti

Hi Jyoti,
>Is there any specific setup required at Provide side while moving to Acceptance system
I dont think so.
Please compare EXACTLY the settings of the two Comunication Channels, especially the server path. Please assure that you ve sent exactly the same message content from Acceptance system.
Regards,
Udo

Error in parsing: SAX2 driver class com.sun.xml.parser not found

Hi I have this exception
Error in parsing: SAX2 driver class com.sun.xml.parser not found
when I try to run the examples from the book xml and java
I have added the following jar files to the class path that i have download form java.sun.com
xml.jar
xalan.jar
jaxp.jar
crimson.jar
Please can anyone tell me what is missing or wrong..the code must be right since written by oreilly... please have u any ideA
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");//
I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..to com.sun.xml.parser
THIS IS THE ALL CODE
import java.io.IOException;
import org.xml.sax.Attributes;
import org.xml.sax.ContentHandler;
import org.xml.sax.ErrorHandler;
import org.xml.sax.Locator;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import org.xml.sax.XMLReader;
import org.xml.sax.helpers.XMLReaderFactory;
import org.xml.sax.*;
* <code>SAXParserDemo</code> will take an XML file and parse it using SAX,
* displaying the callbacks in the parsing lifecycle.
* @author Brett McLaughlin
* @version 1.0
public class SAXParserDemo {
* 
* This parses the file, using registered SAX handlers, and output
* the events in the parsing process cycle.
* 
* @param uri <code>String</code> URI of file to parse.
public void performDemo(String uri) {
System.out.println("Parsing XML File: " + uri + "\n\n");
// Get instances of our handlers
ContentHandler contentHandler = new MyContentHandler();
ErrorHandler errorHandler = new MyErrorHandler();
try {
// Instantiate a parser
XMLReader parser =
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");// I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..
// Register the content handler
parser.setContentHandler(contentHandler);
// Register the error handler
parser.setErrorHandler(errorHandler);
// Parse the document
parser.parse(uri);
} catch (IOException e) {
System.out.println("Error reading URI: " + e.getMessage());
} catch (SAXException e) {
System.out.println("Error in parsing: " + e.getMessage());
* 
* This provides a command line entry point for this demo.
* 
public static void main(String[] args) {
// if (args.length != 1) {
// System.out.println("Usage: java SAXParserDemo [XML URI]");
// System.exit(0);
//String uri = args[0];
SAXParserDemo parserDemo = new SAXParserDemo();
parserDemo.performDemo("content.xml");
* <code>MyContentHandler</code> implements the SAX
* <code>ContentHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's content.
class MyContentHandler implements ContentHandler {
/** Hold onto the locator for location information */
private Locator locator;
* 
* Provide reference to <code>Locator</code> which provides
* information about where in a document callbacks occur.
* 
* @param locator <code>Locator</code> object tied to callback
* process
public void setDocumentLocator(Locator locator) {
System.out.println(" * setDocumentLocator() called");
// We save this for later use if desired.
this.locator = locator;
* 
* This indicates the start of a Document parse - this precedes
* all callbacks in all SAX Handlers with the sole exception
* of <code>{@link #setDocumentLocator}</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void startDocument() throws SAXException {
System.out.println("Parsing begins...");
* 
* This indicates the end of a Document parse - this occurs after
* all callbacks in all SAX Handlers.</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void endDocument() throws SAXException {
System.out.println("...Parsing ends.");
* 
* This will indicate that a processing instruction (other than
* the XML declaration) has been encountered.
* 
* @param target <code>String</code> target of PI
* @param data <code>String</code containing all data sent to the PI.
* This typically looks like one or more attribute value
* pairs.
* @throws <code>SAXException</code> when things go wrong
public void processingInstruction(String target, String data)
throws SAXException {
System.out.println("PI: Target:" + target + " and Data:" + data);
* 
* This will indicate the beginning of an XML Namespace prefix
* mapping. Although this typically occur within the root element
* of an XML document, it can occur at any point within the
* document. Note that a prefix mapping on an element triggers
* this callback before the callback for the actual element
* itself (<code>{@link #startElement}</code>) occurs.
* 
* @param prefix <code>String</code> prefix used for the namespace
* being reported
* @param uri <code>String</code> URI for the namespace
* being reported
* @throws <code>SAXException</code> when things go wrong
public void startPrefixMapping(String prefix, String uri) {
System.out.println("Mapping starts for prefix " + prefix +
" mapped to URI " + uri);
* 
* This indicates the end of a prefix mapping, when the namespace
* reported in a <code>{@link #startPrefixMapping}</code> callback
* is no longer available.
* 
* @param prefix <code>String</code> of namespace being reported
* @throws <code>SAXException</code> when things go wrong
public void endPrefixMapping(String prefix) {
System.out.println("Mapping ends for prefix " + prefix);
* 
* This reports the occurrence of an actual element. It will include
* the element's attributes, with the exception of XML vocabulary
* specific attributes, such as
* <code>xmlns:[namespace prefix]</code> and
* <code>xsi:schemaLocation</code>.
* 
* @param namespaceURI <code>String</code> namespace URI this element
* is associated with, or an empty
* <code>String</code>
* @param localName <code>String</code> name of element (with no
* namespace prefix, if one is present)
* @param rawName <code>String</code> XML 1.0 version of element name:
* [namespace prefix]:[localName]
* @param atts <code>Attributes</code> list for this element
* @throws <code>SAXException</code> when things go wrong
public void startElement(String namespaceURI, String localName,
String rawName, Attributes atts)
throws SAXException {
System.out.print("startElement: " + localName);
if (!namespaceURI.equals("")) {
System.out.println(" in namespace " + namespaceURI +
" (" + rawName + ")");
} else {
System.out.println(" has no associated namespace");
for (int i=0; i<atts.getLength(); i++)
System.out.println(" Attribute: " + atts.getLocalName(i) +
"=" + atts.getValue(i));
* 
* Indicates the end of an element
* (<code></[element name]></code>) is reached. Note that
* the parser does not distinguish between empty
* elements and non-empty elements, so this will occur uniformly.
* 
* @param namespaceURI <code>String</code> URI of namespace this
* element is associated with
* @param localName <code>String</code> name of element without prefix
* @param rawName <code>String</code> name of element in XML 1.0 form
* @throws <code>SAXException</code> when things go wrong
public void endElement(String namespaceURI, String localName,
String rawName)
throws SAXException {
System.out.println("endElement: " + localName + "\n");
* 
* This will report character data (within an element).
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void characters(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("characters: " + s);
* 
* This will report whitespace that can be ignored in the
* originating document. This is typically only invoked when
* validation is ocurring in the parsing process.
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void ignorableWhitespace(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("ignorableWhitespace: [" + s + "]");
* 
* This will report an entity that is skipped by the parser. This
* should only occur for non-validating parsers, and then is still
* implementation-dependent behavior.
* 
* @param name <code>String</code> name of entity being skipped
* @throws <code>SAXException</code> when things go wrong
public void skippedEntity(String name) throws SAXException {
System.out.println("Skipping entity " + name);
* <code>MyErrorHandler</code> implements the SAX
* <code>ErrorHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's errors.
class MyErrorHandler implements ErrorHandler {
* 
* This will report a warning that has occurred; this indicates
* that while no XML rules were "broken", something appears
* to be incorrect or missing.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void warning(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Warning**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Warning encountered");
* 
* This will report an error that has occurred; this indicates
* that a rule was broken, typically in validation, but that
* parsing can reasonably continue.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void error(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Error encountered");
* 
* This will report a fatal error that has occurred; this indicates
* that a rule has been broken that makes continued parsing either
* impossible or an almost certain waste of time.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void fatalError(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Fatal Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Fatal Error encountered");

I have seen this error when I'm executing inside one of the (j2ee sun reference implementation) server containers (either web or ejb). I believe its caused by "something" having previously loaded the "sax 1 driver class". In my case, I think the container or server is loading the sax parser from a jar that contains a sax 1 version. If you can, ensure that nothing is loading the sax 1 parser from another jar on your system. Verify that you are loading the sax parser from a jar containing the latest version so that you get the sax 2 compliant parser. Good luck!

System Error in Parser in SXMB_MONI

Similar Messages

Maybe you are looking for