Deserialization error: XML parsing error: Illegal XML character

Hi All,
Anybody knows what caused this? This error occured at the client side when the server returned an object that contains other objects to client during a jaxrpc call. It worked before, something is definitely changed, I reversed my changes but still the same.
Please help, thanx a lot.
[java] java.rmi.RemoteException: Runtime exception; nested exception is:
[java] deserialization error: deserialization error: deserialization error: XML parsing error: com.sun.xml.rpc.sp.ParseException:2: Illegal XML character:
[java] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:234)
[java] at com.ummq.ME_Stub.getMsg(MsgExpertIF_Stub.java:1333)
[java] at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1764)
[java] at javax.swing.AbstractButton$ForwardActionEvents.actionPerforme
d(AbstractButton.java:1817)
[java] at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:419)
[java] at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:257)
[java] at javax.swing.AbstractButton.doClick(AbstractButton.java:289)
[java] at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1109)
[java] at javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mous
eReleased(BasicMenuItemUI.java:943)
[java] at java.awt.Component.processMouseEvent(Component.java:5093)
[java] at java.awt.Component.processEvent(Component.java:4890)
[java] at java.awt.Container.processEvent(Container.java:1566)
[java] at java.awt.Component.dispatchEventImpl(Component.java:3598)
[java] at java.awt.Container.dispatchEventImpl(Container.java:1623)
[java] at java.awt.Component.dispatchEvent(Component.java:3439)
[java] at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3450)
[java] at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3165)
[java] at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3095)
[java] at java.awt.Container.dispatchEventImpl(Container.java:1609)
[java] at java.awt.Window.dispatchEventImpl(Window.java:1585)
[java] at java.awt.Component.dispatchEvent(Component.java:3439)
[java] at java.awt.EventQueue.dispatchEvent(EventQueue.java:450)
[java] at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:197)
[java] at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
[java] at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:144)
[java] at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:136)
[java] at java.awt.EventDispatchThread.run(EventDispatchThread.java:99)
[java] Caused by: deserialization error: deserialization error: deserialization error: XML parsing error: com.sun.xml.rpc.sp.ParseException:2: Illegal XML character:
[java] at com.sun.xml.rpc.encoding.SOAPDeserializationContext.deseriali
zeMultiRefObjects(SOAPDeserializationContext.java:65)
[java] before getMsg
[java] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:175)
[java] ... 30 more
[java] java.rmi.RemoteException: Runtime exception; nested exception is:
[java] deserialization error: deserialization error: deserialization error: XML parsing error: com.sun.xml.rpc.sp.ParseException:2: Illegal XML character:
[java] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:234)
[java] at javax.swing.JComboBox.fireItemStateChanged(JComboBox.java:1161)
[java] at javax.swing.JComboBox.selectedItemChanged(JComboBox.java:1218)
[java] at javax.swing.JComboBox.contentsChanged(JComboBox.java:1265)
[java] at javax.swing.AbstractListModel.fireContentsChanged(AbstractListModel.java:100)
[java] at javax.swing.DefaultComboBoxModel.setSelectedItem(DefaultComboBoxModel.java:88)
[java] at javax.swing.JComboBox.setSelectedItem(JComboBox.java:551)
[java] at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1764)
[java] at javax.swing.AbstractButton$ForwardActionEvents.actionPerforme
d(AbstractButton.java:1817)
[java] at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:419)
[java] at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:257)
[java] at javax.swing.AbstractButton.doClick(AbstractButton.java:289)
[java] at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1109)
[java] at javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mous
eReleased(BasicMenuItemUI.java:943)
[java] at java.awt.Component.processMouseEvent(Component.java:5093)
[java] at java.awt.Component.processEvent(Component.java:4890)
[java] at java.awt.Container.processEvent(Container.java:1566)
[java] at java.awt.Component.dispatchEventImpl(Component.java:3598)
[java] at java.awt.Container.dispatchEventImpl(Container.java:1623)
[java] at java.awt.Component.dispatchEvent(Component.java:3439)
[java] at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3450)
[java] at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3165)
[java] at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3095)
[java] at java.awt.Container.dispatchEventImpl(Container.java:1609)
[java] at java.awt.Window.dispatchEventImpl(Window.java:1585)
[java] at java.awt.Component.dispatchEvent(Component.java:3439)
[java] at java.awt.EventQueue.dispatchEvent(EventQueue.java:450)
[java] at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:197)
[java] at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
[java] at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:144)
[java] at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:136)
[java] at java.awt.EventDispatchThread.run(EventDispatchThread.java:99)
[java] Caused by: deserialization error: deserialization error: deserializa
tion error: XML parsing error: com.sun.xml.rpc.sp.ParseException:2: Illegal XML character:
[java] at com.sun.xml.rpc.encoding.SOAPDeserializationContext.deseriali
zeMultiRefObjects(SOAPDeserializationContext.java:65)
[java] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:175)
[java] ... 39 more

What type of encoding are you using? Do you transform a string in an array of bytes or viceversa?
Marco

Similar Messages

Xml parsing error: invalid character

We started receving below error while opening PDF forms in the browser , its started happening from today for several users. They were using IE and Adobe Reader 10.1
Any one saw this error before?
xml parsing error: invalid character number (error code 14), line 3 , column 264 of file....

We can see this issue only in Adobe Reader XI (11.0.01), X (10.1.5) And 9.5.3 in OS Win XP and 7.0. This happens only in IE. Fire Fox it works fine.
We rolled back to Adobe Reader 10.1.3 , works perfect.

XML parsing error registering a JSR168 portlet

Hi, I'm trying to register a deployed application as a portlet provider, and I'm getting an XML parsing error (full details below). Basically, when I complete the Register Provider wizard, it falls over with "Illegal Namespace prefix: xml".
I'm guessing this is coming from the service description: the response from WSRPServiceDescriptionService.getServiceDescription contains xml:lang="en" attributes on many of the elements.
Anyone have any ideas how to fix this? Should these attributes not be present, or should the portal be able to parse them?
I'm using the following versions:
JDeveloper Studio Edition 10.1.3.2.0.4066
Oracle Application Server 10.1.2.0.2
Oracle Portal 10.1.4
Oracle Java Portlet Container 10.1.4 (wsrp-install.jar from Portlet PDK)
ADF Runtime 10.1.3.40.66
Thanks,
Full exception details:
An error occurred when attempting to call the providers register function. (WWC-43134)
An error occurred during the call to the WSRP Provider: java.rmi.RemoteException: Runtime exception; nested exception is:
deserialization error: deserialization error: XML parsing error: com.sun.xml.rpc.sp.ParseException:1: com.sun.xml.rpc.sp/Illegal Namespace prefix: xml
com.sun.xml.rpc.encoding.DeserializationException: deserialization error: deserialization error: XML parsing error: com.sun.xml.rpc.sp.ParseException:1: com.sun.xml.rpc.sp/Illegal Namespace prefix: xml
com.sun.xml.rpc.encoding.DeserializationException: deserialization error: XML parsing error: com.sun.xml.rpc.sp.ParseException:1: com.sun.xml.rpc.sp/Illegal Namespace prefix: xml
com.sun.xml.rpc.streaming.XMLReaderException: XML parsing error: com.sun.xml.rpc.sp.ParseException:1: com.sun.xml.rpc.sp/Illegal Namespace prefix: xml
Java stack trace from root exception:
com.sun.xml.rpc.sp.ParseException:1: com.sun.xml.rpc.sp/Illegal Namespace prefix: xml
at com.sun.xml.rpc.sp.Parser2.fatal(Parser2.java:2015)
at com.sun.xml.rpc.sp.Parser2.fatal(Parser2.java:2000)
at com.sun.xml.rpc.sp.Parser2.processStartElement(Parser2.java:2794)
at com.sun.xml.rpc.sp.Parser2.parseContent(Parser2.java:3036)
at com.sun.xml.rpc.sp.Parser2.parse(Parser2.java:2360)
at com.sun.xml.rpc.streaming.XMLReaderImpl.next(XMLReaderImpl.java:105)
at com.sun.xml.rpc.streaming.XMLReaderBase.nextContent(XMLReaderBase.java:23)
at com.sun.xml.rpc.streaming.XMLReaderBase.nextElementContent(XMLReaderBase.java:41)
at oracle.webdb.wsrp.PortletDescription_LiteralSerializer.doDeserialize(PortletDescription_LiteralSerializer.java:94)
at com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalDeserialize(LiteralObjectSerializerBase.java:174)
at com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.deserialize(LiteralObjectSerializerBase.java:84)
at oracle.webdb.wsrp.ServiceDescription_LiteralSerializer.doDeserialize(ServiceDescription_LiteralSerializer.java:88)
at com.sun.xml.rpc.encoding.literal. (WWC-43273)

This might not be related at all, but...
Did you specify J2EE 1.3 (Servlet 2.3/JSP 1.2) when you created the portlet and did you compile the project with JDK 1.4.x...?
...'cause whenever I've forgotten to do the above and try to deploy to Portal 10.1.4 on OAS 10.1.2.0.2 (which is J2EE 1.3-based) all heck breaks loose...

XML parsing error, whitespace expected

I'm seeing this "XML parsing" error in the SSRS Logs once in a while and I don't know what is causing it. The weird thing is that the report doesn't get this error everytime, most of the time it will work. I originally thought that
it might be the data that is being returned but I don't know if this is the case. Usually when a user gets an error, they'll just run it again later and it'll work the 2nd time. I looked at the report parameters in the ExecutionLogStorage table and the same
parameters are passed in each time.
Does anyone have any ideas of where I can look to get to the bottom of this one? Any help is appreciated.
The actual error from the logs is below:
processing!ReportServer_0-26!fdc!05/08/2014-13:33:12:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'DataSet1'. ---> System.Data.SqlClient.SqlException: XML parsing: line 1, character 121, whitespace expected
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.DataExtensions.SqlCommandWrapperExtension.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.OnDemandProcessing.RuntimeDataSet.RunEmbeddedQuery(Boolean& readerExtensionsSupported, Boolean& readerFieldProperties, List`1 queryParams, Object[] paramValues)
Thanks,
-Song

Hi Song,
Sorry for the delay.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

XML parse error in IPS

I've setup IPS on 5515-X
In Cisco IDM in "Events" i see a lot of:
evError: eventId=6823483858390 vendor=Cisco severity=error
originator:
    hostId: ips5515
    appName: mainApp
    appInstanceId: 1232
time: avg 28, 2014 20:26:15 UTC offset=120 timeZone=GMT+01:00
errorMessage: XML Parser error at line: 1, at character: 0: no element found name=errInvalidDocument
version of sensor:
Mod SSM Application Name           Status           SSM Application Version
ips IPS                            Up               7.3(2)E4
Does anyone have similar problem?

Okay after further investigation this error shows up only when i connect with Cisco IDM. So i suspect there must be a bug in IDM 7.3.2.

R12 - Format Payment Instructions XML Parsing Error: not well-formed

We are going from 11.5.10 to R12,
We followed the Note : 562806.1 to generate the XML file but we are getting the following error?
XML Parsing Error: not well-formed
Location: http://XXXXXXXXXXXXXX.com:8030/OA_CGI/FNDWRR.exe?temp_id=3412576704
Line Number 1, Column 9:%PDF-1.4
--------^
Any help or suggestions would be great!
Thanks

Please see if the solution in (BI Publisher Reports End With Error When There Is An Ampersand Character ( & ) On The Xml Data File [ID 1081175.1]) is applicable.
Thanks,
Hussein

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

Since installing the latest update, Firefox will not load; it gives me the following error -- XML Parsing Error: not well formed.

since installing the latest update, Firefox first operated with some errors but now will not load at all; it gives me the following error --
XML Parsing Error: not well formed
locations chrome://browser/content/browser.xml
Line Number 1191, column 20:
utton id="back-forward-dropmarker" type="menu" chromedir="&locale.dir;"-------------------
please note that the words "utton ID" are exactly as the error message gives it; and at the end of the message there are exactly 19 hyphens.
I don't know why this faulty code is referencing things to do with "chrome"... the Chrome browser is not installed on this PC or anywhere on our network.
Also, this is not the first problem I had after clicking Firefox's prompt for the latest update. Before Firefox retreated into this error message, it was loading but running with some faults...
1. the bookmark symbol was not appearing on the right hand side of the URL line, so I had always to click on "bookmark this page", after which the bookmark symbol did appear; however I don't know if the bookmarking function worked properly.
2. the back and forward buttons were not highlighted, as if I had not come from a previous page; so once I clicked on a link to a new page I could not go back to where I came from because Fiefox thought I hadn't come from anywhere.
3. there may have been other errors, but I did not find them.
How do I reinstate my Firefox program to work properly please? do I have to download the latest version and reinstal? if so, do I have to remove the old version first? or is there a fix?
Even to write this message I have been forced to use (yuk -- I don't like to say this!!!) Internet Explorer. So please -- I need help urgently.
Thanks,
NOEL

Some how I solved my problem by opening a user account and downloading Firefox 4.0 beta and installing it, I did try it, worked fine, so I did close the user account and did go back to my own account(switched user), the main page that I had problem with Firefox which would not open, I dabble click on Firefox it start working again!! I hope that solves your problem too.
firefox will not open, it gives me this cod and would not turn off, Error on switching in renew: NS_ERROR_UNEXPECTED, Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref] id: none

I am recieving an xml parsing error message on a website I use for work. It used to work on firefox but now it has stopped. It works with other browsers though.

XML Parsing Error: XML or text declaration not at start of entity
Location: https://evalue.internationaldelivers.com/service/SVCDOCS/Navistar/isisxsl.xsl
Line Number 2, Column 1:<?xml version='1.0'?>
^
That is the error I receive the page loads and half the content appears but the other half is blank and I receive that instead. I can attach a screenshot if needed.

May be cookies issue try this
Reload the webpage while bypassing the cache
*Hold down the ''Shift'' key and click the ''Reload'' button with a left click.
*Press ''Ctrl'' + ''F5'' or ''Ctrl'' + ''Shift'' + ''R'' (Windows and Linux)
*Press ''Command'' + ''Shift'' + ''R'' (Mac)
Clear the cache and the cookies from sites that cause problems.
'''Clear the Cache''': Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
'''Remove Cookies''' from sites causing problems:
*Tools > Options > Privacy > Cookies: "Show Cookies"
*https://support.mozilla.org/en-US/kb/websites-say-cookies-are-blocked-unblock-them

XML Parser Error while creating Web service Client using JAX RPC

hello evryone,
Im facing XML Parser Error while creating web service client using JAX RPC. Im using Net Beans IDE for development purpose. I have wrote configuration file for client. Now i want to create Client stub. However i dont know how to do this in Net Beans. So i tried to do it from Command promt using command :
wscompile -gen:client -d build -classpath build config-wsdl.xml
here im getting Error:
error parsing configuration file: XML parsing error: com.sun.xml.rpc.sp.ParseException:10: XML declaration may only begin entities
Please help me out.
Many thanks in advance,
Kacee

Can i use the client generated using jdeveloper 11g to import into the oracle forms 10g, i.e., form builder 10g. Currently this is the version we have in our office.

XML parsing error: web-jsptaglibrary_1_1.dtd not found

I'm getting the following Exception while Tomcat is parsing my welcome jsp page:
exception
org.apache.jasper.JasperException: XML parsing error on file /WEB-INF/struts-template.tld: Internal Error: File /javax/servlet/jsp/resources/web-jsptaglibrary_1_1.dtd not found
     at org.apache.jasper.parser.ParserUtils.parseXMLDocument(ParserUtils.java:227)
     at org.apache.jasper.compiler.TagLibraryInfoImpl.parseTLD(TagLibraryInfoImpl.java:283)
     at org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:219)
     at org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:174)
     at org.apache.jasper.compiler.JspParseEventListener.processTaglibDirective(JspParseEventListener.java:1170)
     at org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspParseEventListener.java:765)
     at org.apache.jasper.compiler.DelegatingListener.handleDirective(DelegatingListener.java:125)
     at org.apache.jasper.compiler.Parser$Directive.accept(Parser.java:255)
     at org.apache.jasper.compiler.Parser.parse(Parser.java:1145)
     at org.apache.jasper.compiler.Parser.parse(Parser.java:1103)
     at org.apache.jasper.compiler.Parser.parse(Parser.java:1099)
     at org.apache.jasper.compiler.ParserController.parse(ParserController.java:214)
     at org.apache.jasper.compiler.Compiler.compile(Compiler.java:210)
     at org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:548)
     at org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(JspServlet.java:176)
     at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:188)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:98)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:176)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:172)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:475)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
     at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:458)
     at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551)
     at java.lang.Thread.run(Thread.java:534)
This is the reference to the dtd its not finding from the tld
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE taglib PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN" "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
Do you think this is a bug with the parser itself or an incompatablilty between it and the tag library?
Or am I missing something?
Thanks for any help..... Andy

Store the web-jsptaglibrary_1_1.dtd to a directory and specify the file url.
<!DOCTYPE taglib SYSTEM "file://C:/dtds/web-jsptaglibrary_1_1.dtd">

XML Parsing Error: no element found Location:Line Number 1, Column 1:

Hi,
i have a servlet code in which i am using bouncy castle encryption algorithm , if i tried to run that servlet on embeded weblogic server than my servlet works fine without error.
but if i deploy same Servlet code on SOA domain console than i get following error.
XML Parsing Error: no element found
Location: http://localhost:7001/Encryption-PGPEncrypt-context-root/pgpservlet
Line Number 1, Column 1:
Please help me friends...

Hi Chandra,
Based on my research, the error message is only generated by FireFox when the render page is blank in Internet. For some reason, .NET generates a response type of "application/xml" when it creates an empty page. Firefox parses the file as XML and finding
no root element, spits out the error message.
Also, based on your description, the other sites are opened correctly, the issue only happened in Central Administration(CA). This means the SharePoint services are working fine.
Since this issue only occurred in the CA, it might be due the application pool for the CA is corrupted. Please try to restart the application pool for the CA to resove the issue:
1. Open Internet Information Service(IIS)
2. List the application pools
3. Select the application pool used for the CA
4. Stop it, and then start it again.
Note, if the application pool is running in Classic mode, please change it to be Integrated mode.
Additionally, I found a similar thread, which may help you too:
http://social.msdn.microsoft.com/Forums/en/sharepoint2010general/thread/824d7dda-db03-452b-99c4-531c5c576396
If you have any more questions, please feel free to ask.
Thanks,
Jin Chen
Jin Chen - MSFT

XML Parsing Error: no element found Line Number 1, Column 1:

Hi All,
I have deployed EAR on my standalone server using JDEV 11.1.1.6.0. I am able to get the WSRP portlet producer page on
http://<server>:7001/contextRoot. But when i try to click on any of the WSDL URL it gives me "XML Parsing Error: no element found Line Number 1, Column 1:"
and from IE it gives me: XML document must have a top level element. Error processing resource
there can be a issue with the WSRPContainer.jar file. So i have remove it from my deployment profile, EAR and lib/classpath files.
Can you please suggest a workaround.
Regards,
ND
Edited by: ND on Dec 4, 2012 9:57 PM

Hi All,
this error normally comes when the WLS domain is not not properly created. if you get some exception for ./provesecurity.sh file while creating the domain, then the XML error comes.
I did not went into the depth but figured out a workaround: restart the VM/hosted box and then create the domain, remember to use diff port name while creating it from the domain creation script.
Regards,
ND

XML Parsing Error: no element found In BI Publisher

Hi Gurus,
I tried to get XML output for a Data Model which was based on SQL queries.
But I got the following error in Firefox
XML Parsing Error: no element found
Location: http://localhost:9704/xmlpserver/servlet/xdo
Line Number 4, Column 1:
In IE I got an other error:
There is no end tag for DATA_SET
Any ideas?
Many thanks
Laszlo

Hi,
I use 11g.
I tried to create element link when I got this error.
Now I am using groupink.
Without using bind variable I got result (Cartesian product)
However if i created and used bind variable I got the same error
this is a dept data set:
select     "DEPARTMENTS"."DEPARTMENT_ID" as DEPTNO,
     "DEPARTMENTS"."DEPARTMENT_NAME" as "DEPARTMENT_NAME",
     "DEPARTMENTS"."LOCATION_ID" as "LOCATION_ID",
     "DEPARTMENTS"."MANAGER_ID" as "MANAGER_ID"
from     "HR"."DEPARTMENTS" "DEPARTMENTS"
this is the emp data set:
select     "EMPLOYEES"."COMMISSION_PCT" as "COMMISSION_PCT",
     "EMPLOYEES"."DEPARTMENT_ID" as "DEPARTMENT_ID",
     "EMPLOYEES"."EMAIL" as "EMAIL",
     "EMPLOYEES"."EMPLOYEE_ID" as "EMPLOYEE_ID",
     "EMPLOYEES"."FIRST_NAME" as "FIRST_NAME",
     "EMPLOYEES"."HIRE_DATE" as "HIRE_DATE",
     "EMPLOYEES"."JOB_ID" as "JOB_ID",
     "EMPLOYEES"."LAST_NAME" as "LAST_NAME",
     "EMPLOYEES"."MANAGER_ID" as "MANAGER_ID"
from     "HR"."EMPLOYEES" "EMPLOYEES"
WHERE "EMPLOYEES"."DEPARTMENT_ID" =:DEPTNO
Thanks for any tip!
Laszlo

Xml parsing error while selecting whole result set for sql query

Hi All,
I am having xml parsing error while selecting whole query result set. The data is coming fine for default result set of 50 rows.
My exception is below.
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00234: namespace prefix "xsi" is not declared
Error at line 1
ORA-06512: at "SYS.XMLTYPE", line 254
ORA-06512: at line 1
*31011. 00000 - "XML parsing failed"*
**Cause: XML parser returned an error while trying to parse the document.*
**Action: Check if the document to be parsed is valid.*
My sql query is below that is giving results for default result set of 50 rows.
select extract(xmlType(clob_xml_colm_name), '//v2:node1//childnode/text()','xmlns:v2="namespace_url"').getStringVal() from table_name
My sql developer version is below.
Java(TM) Platform     1.7.0_04
Oracle IDE     3.1.07.42
Versioning Support     3.1.07.42
My database version is below.
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit
Please could any one help me urgently as the sql query is supposed to be correct as it is returning query results, but the problem happening when i try to select whole result set.
Thanks and regards,

What does the XML look like? It appears that some of the supposed XML stored as a CLOB is not really valid XML. Find the row in the table that is causing your issue and review the "XML" in it.

Deserialization error: XML parsing error: Illegal XML character

Similar Messages

Maybe you are looking for