IDOC_ERROR_PARSE_FAILURE: An IDocIllegalTypeException occurred while parsing IDocXML:state=READING_SEGMENT_STARTTAG

Hello Experts,
We are getting a strange issue while trying to post IDOC into ECC through PO 7.31 Single Stack.
We are having a custom segment in IDOC with a single field.If we don't create that segment in PO,i.e. if we don't map this segment the IDOC is getting posted.But if we map the custom segment(setting SEGMENT=1),we are getting error "com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.conn.idoc.IDocParseException: (7) IDOC_ERROR_PARSE_FAILURE: An IDocIllegalTypeException occurred while parsing IDocXML for type <*IDOC_NAME*>:
state=READING_SEGMENT_STARTTAG, charPosition=834, lineNumber=1, columnNumber=835".
I have gone through other discussion in scn related to this exception,but they are not similar to our problem.
Please suggest.
Regards,
Suman

Hi Sunil,
I have re-imported Idoc as many as 10 times,even created separate message and operation mapping,new Idoc receiver channel.But still no luck.
Regards,
Suman

Similar Messages

Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML

Hello Rescue Team,
I am facing the following error :\
16.06.2014 23:22:42.164
Error
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.166
Error
MP: exception caught with cause com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Exception caught by adapter framework: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Transmitting the message to endpoint <local> using connection EDISeparator_http://sap.com/xi/XI/EDISeparator failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
and the payload transferred is as attached in the attachment below.
I have refered various blogs, however I am still not able to understand how to get the exact location of the error location..According to me, the value that is giving trouble is OTH in <BSARK> however I have checked the permitted values for BSARK on ECC and OTH is maintained.
Can you please help how I can resolve this error.
Thanks
Saurabh

Hi Guys,
This is solved..I corrected the date format of the ZZTIME segment from 1157 to 115700.
Thanks
Saurabh

ORA-20100: Error occurred while parsing:Error opening external DTD ( Asap)

Hi I'm using domsample example. And I have written the program. The xml file at the starting has this string"<!DOCTYPE MobileInventoryResponse SYSTEM "MobileInventoryResponse.dtd">", from which I'm getting error -"ORA-20100: Error occurred while parsing: Error opening external DTD".
I'm new to xml could you please help me to solve this problem. I assume this is related to DTD for which I need to set base path. But I'm not sure how to do it? I'm getting this xml file through CLOB which I'm able to parse until an extent. where in between got this error.
Here is my partial code:
l_doc_id := rec_xml_data.id;
l_xml_parser := xmlparser.newParser;
xmlparser.setValidationMode(l_xml_parser, FALSE);
xmlparser.parseCLOB(l_xml_parser,rec_xml_data.l_xml_data);--PARSING THE CLOB WHICH CONTAINS XML FILE
l_xml_doc := xmlparser.getDocument(l_xml_parser);
xmlparser.freeParser(l_xml_parser);
l_nodelist := xmldom.getElementsByTagName(l_xml_doc, '*');
l_length := xmldom.getLength(l_nodelist);
-- loop through elements
FOR l_rec_xml in 0..l_length-1
LOOP
l_node := xmldom.item(l_nodelist, l_rec_xml);
-- dbms_output.put(xmldom.getNodeName(n) || ' ');
-- get the text node associated with the element node
l_nodename:=xmldom.getNodeName(l_node);
l_node := xmldom.getFirstChild(l_node);
IF (xmldom.isNull(l_node) = false) THEN
IF xmldom.getNodeType(l_node) = xmldom.TEXT_NODE THEN
IF l_nodename = 'purchase-order-number' THEN
l_po_num:=NULL;
l_po_num:= xmldom.getNodeValue(l_node);
-- dbms_output.put_line('Purchaser Order Num : '||l_po_num);
END IF;
from here onwards I get the string values
Now I don't know where to set the DTD basepath or baseurl. I need it asap.
Regards,
Naveen.

The version which I'm working on is 10.2.0.4.
XML File---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE MobileInventoryResponse SYSTEM "MobileInventoryResponse.dtd">
<MobileInventoryResponse>
<message>
<message-header>
<message-id>16244182</message-id>
<transaction-name>ship-advice</transaction-name>
<partner-name>cbeyond</partner-name>
<source-url>http://www.brightpoint.com</source-url>
<create-timestamp>20080826150709</create-timestamp>
<response-request>1</response-request>
</message-header>
<ship-advice>
<header>
<customer-id>297859</customer-id>
<shipment-information>
<ship-first-name>RA_13Aug_1</ship-first-name>
<ship-last-name>MIND</ship-last-name>
<ship-address1>test</ship-address1>
<ship-city>test</ship-city>
<ship-state>VA</ship-state>
<ship-post-code>22102-4931</ship-post-code>
<ship-country-code>US</ship-country-code>
<ship-phone1>0040726335068</ship-phone1>
<ship-email>[email protected]</ship-email>
<ship-via>FX01</ship-via>
<ship-request-date>20080826</ship-request-date>
<ship-request-warehouse>CBY1</ship-request-warehouse>
</shipment-information>
<purchase-order-information>
<purchase-order-number>380928</purchase-order-number>
<account-description />
<purchase-order-amount>0.0</purchase-order-amount>
<currency-code>USD</currency-code>
</purchase-order-information>
<order-header>
<customer-order-number>0002759</customer-order-number>
<customer-order-date>20080826</customer-order-date>
<order-sub-total>19.0</order-sub-total>
<order-discount>0.0</order-discount>
<order-tax1>0.0</order-tax1>
<order-tax2>0.0</order-tax2>
<order-tax3>0.0</order-tax3>
<order-shipment-charge>18.0</order-shipment-charge>
<order-total-net>0.0</order-total-net>
<order-status>Completed</order-status>
<order-type />
<brightpoint-order-number>35028788</brightpoint-order-number>
<warehouse-id>CBY1</warehouse-id>
<ship-date>20080826</ship-date>
</order-header>
</header>
<detail>
<line-item>
<line-no>1</line-no>
<item-code>SKU1</item-code>
<universal-product-code>0</universal-product-code>
<ship-quantity>1.0</ship-quantity>
<unit-of-measure>EA</unit-of-measure>
<serial-list>
<serial-numbers>
<esn>TIMI000013</esn>
</serial-numbers>
</serial-list>
<line-status />
<base-price>0.0</base-price>
<line-discount>0.0</line-discount>
<line-tax1>0.0</line-tax1>
<line-tax2>0.0</line-tax2>
<line-tax3>0.0</line-tax3>
<bill-of-lading>929406733828</bill-of-lading>
<scac>FX01</scac>
</line-item>
</detail>
</ship-advice>
<transactionInfo>
<eventID>16244182</eventID>
</transactionInfo>
</message>
</MobileInventoryResponse>
XML FILE END--------------------
MY PROGRAM IS AS BELOW---
get_eai_data_prc( x_ret_code OUT NUMBER
,p_debug_flag IN VARCHAR2
IS
--Local Variables
l_xml_parser xmlparser.Parser;
l_xml_doc xmldom.DOMDocument;
l_xml_data CLOB;
l_nodelist xmldom.DOMNodeList;
l_length NUMBER := 0;
l_num_cnt NUMBER := 0;
l_node xmldom.DOMNode;
l_docelem DBMS_XMLDOM.DOMElement; -- XML DOM element.
l_nodeValue VARCHAR2(30); -- Text value of the node.
l_nodename VARCHAR2(100);
l_po_num VARCHAR2(150);
l_account_desc VARCHAR2(150);
l_cust_ord VARCHAR2(150);
l_ship_date VARCHAR2(150);
l_item_code VARCHAR2(150);
l_ship_qty VARCHAR2(150);
l_esn VARCHAR2(150);
l_cust_channel_type VARCHAR2(150);
l_cust_grp_acct VARCHAR2(150);
l_max_doc_id NUMBER;
l_doc_id NUMBER;
l_market_id VARCHAR2(150);
l_record_id VARCHAR2(30);
TYPE l_esn_table IS TABLE OF VARCHAR2(30)
INDEX BY BINARY_INTEGER;
l_data l_esn_table;
--CURSOR TO GET XML DATA FROM EAI
CURSOR cur_xml_data(p_doc_id VARCHAR2)
IS
SELECT id
,document l_xml_data
FROM tds_xml_store_temp
WHERE id >= id ;
BEGIN
FOR rec_xml_data IN cur_xml_data(l_max_doc_id)
LOOP
l_doc_id := rec_xml_data.id;
l_xml_parser := xmlparser.newParser;
xmlparser.setValidationMode(l_xml_parser, FALSE);
xmlparser.parseCLOB(l_xml_parser,rec_xml_data.l_xml_data);
l_xml_doc := xmlparser.getDocument(l_xml_parser);
xmlparser.freeParser(l_xml_parser);
l_nodelist := xmldom.getElementsByTagName(l_xml_doc, '*');
l_length := xmldom.getLength(l_nodelist);
-- loop through elements
FOR l_rec_xml in 0..l_length-1
LOOP
l_node := xmldom.item(l_nodelist, l_rec_xml);
-- dbms_output.put(xmldom.getNodeName(n));
-- get the text node associated with the element node
l_nodename:=xmldom.getNodeName(l_node);
l_node := xmldom.getFirstChild(l_node);
IF (xmldom.isNull(l_node) = false) THEN
IF xmldom.getNodeType(l_node) = xmldom.TEXT_NODE THEN
IF l_nodename = 'purchase-order-number' THEN
l_po_num:=NULL;
l_po_num:= xmldom.getNodeValue(l_node);
-- dbms_output.put_line('Purchaser Order Num : '||l_po_num);
END IF;--purchase-order-number
IF l_nodename = 'account-description' THEN
l_account_desc :=NULL;
l_account_desc := xmldom.getNodeValue(l_node);
END IF;
IF l_nodename = 'customer-channel-type' THEN
l_cust_channel_type:=NULL;
l_cust_channel_type:= xmldom.getNodeValue(l_node);
END IF;
IF l_nodename = 'customer-group-account' THEN
l_cust_grp_acct := NULL;
l_cust_grp_acct := xmldom.getNodeValue(l_node);
END IF;
IF l_nodename = 'customer-order-number' THEN
l_cust_ord:=NULL;
l_cust_ord:= xmldom.getNodeValue(l_node);
-- dbms_output.put_line('Customer Order NUm : '||l_cust_ord);
END IF;--customer-order-number
IF l_nodename = 'ship-date' THEN
l_ship_date:=NULL;
l_ship_date:= xmldom.getNodeValue(l_node);
-- dbms_output.put_line('Ship Date : '||to_date(l_ship_date,'YYYY-mm-dd'));
END IF;--ship-date
IF l_nodename = 'item-code' THEN
l_item_code:=NULL;
l_item_code:= xmldom.getNodeValue(l_node);
-- dbms_output.put_line('Item Code : '||l_item_code);
END IF;--item-code
IF l_nodename = 'esn' THEN
l_esn:=NULL;
l_num_cnt := l_num_cnt + 1;
l_esn:=xmldom.getNodeValue(l_node);
l_data(l_num_cnt) := l_esn;
-- dbms_output.put_line('Serial Num : '||l_esn);
END IF;--esn
IF l_nodename = 'market-id' THEN
l_market_id := NULL;
l_market_id := xmldom.getNodeValue(l_node);
END IF;
IF l_nodename = 'ship-quantity' THEN
l_ship_qty:=NULL;
l_ship_qty:= xmldom.getNodeValue(l_node);
-- dbms_output.put_line('Ship Quantity : '||l_ship_qty);
END IF;--ship-quantity
END IF;--xmldom.TEXT_NODE
END IF;
END LOOP;--l_rec_xml
FOR j in l_data.first..l_data.last
LOOP
INSERT INTO cbey_shipment_int_stg( purchase_order_number
,account_description
,customer_order_number
,ship_date
,item_code
,ship_quantity
,esn
,customer_channel_type
,customer_group_account
,market_id
,eai_xml_doc_id
,record_status
,record_id
VALUES
( l_po_num
,l_account_desc
,l_cust_ord
,to_date(l_ship_date,'YYYY-mm-dd')
,l_item_code
,l_ship_qty
,l_data(j)
,l_cust_channel_type
,l_cust_grp_acct
,l_market_id
,l_max_doc_id
,'NEW'
,CBEY_RECORD_ID_SEQ_S.nextval
END LOOP;--j
UPDATE cbey_interface_run_log
SET request_id = l_conc_req_id
,lastrun_date = SYSDATE
,doc_id = rec_xml_data.id
WHERE program_id = 'SHIPMENT_INT'
AND doc_id =l_max_doc_id;
l_data.delete;
l_num_cnt :=0;
END LOOP; --rec_xml_data
COMMIT;
END of the Procedure--------------------------
Now if I load the xml file without the this :- <!DOCTYPE MobileInventoryResponse SYSTEM "MobileInventoryResponse.dtd">
it works well. But it gives error when this particular thing is there.
Regards,
Naveen
Edited by: MAN on Oct 17, 2008 7:28 AM

ORA-20100: Error occurred while parsing: Start of root element expected.

I've been searching everywhere for a reason to the following error message: ORA-20100: Error occurred while parsing: Start of root element expected.
I get this when attempting to parse an XML file stored as a CLOB using the xmlparser.parseClob procedure
Any help would be much appreciated.

I initially used US ASCII but then tried several unicode formats as created by XML Spy (UTF16, Unicode16, Unicode32). All had the exact same result.
Exactly what would be the most helpful output? The XML documents are varied, mostly very simple, but do you want the CLOB printed some other way?
--Joan Armstrong
null

An error occurred while parsing DA Hierarchy : Document is invalid: no gram

When logging in to Portal Administration, I am seeing the following error. Please help me resolve this problem. Many thanks.
An exception has been thrown while trying to render this page.
Exception Message:
An error occurred while parsing DA Hierarchy : Document is invalid: no grammar found.
---Begin Stack Trace---
com.bea.p13n.delegation.common.DelegationSystemException: An error occurred while parsing DA Hierarchy : Document is invalid: no grammar found. at com.bea.p13n.delegation.management.internal.DelegationHierarchyAbstractPersistenceManager.parseData(DelegationHierarchyAbstractPersistenceManager.java:209) at com.bea.p13n.delegation.management.internal.DelegationHierarchyAbstractPersistenceManager.get(DelegationHierarchyAbstractPersistenceManager.java:189) at com.bea.p13n.delegation.management.internal.DelegationHierarchyDelegate.getHierarchyRoot(DelegationHierarchyDelegate.java:123) at com.bea.p13n.delegation.management.DelegationRoleManager.getHierarchyRoot(DelegationRoleManager.java:63) at com.bea.jsptools.delegation.Pruner.isRootDARole(Pruner.java:145) at com.bea.jsptools.delegation.PortalNodePruner.isEnabled(PortalNodePruner.java:96) at com.bea.treeutils.PrunableTreeNode.checkEnabled(PrunableTreeNode.java:161) at com.bea.jsptools.portal.PortalHierarchyServlet.generateLibraryNodes(PortalHierarchyServlet.java:856) at com.bea.jsptools.portal.PortalHierarchyServlet.generateTopLevelNodes(PortalHierarchyServlet.java:231) at com.bea.jsptools.portal.PortalHierarchyServlet.generateTree(PortalHierarchyServlet.java:104) at jsp_servlet._portaltools.__portalmgmttree._jspService(__portalmgmttree.java:5784) at weblogic.servlet.jsp.JspBase.service(JspBase.java:33) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27) at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:293) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:644) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:423) at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:533) at com.bea.netuix.nf.ControlLifecycle$1.visit(ControlLifecycle.java:495) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:542) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:247) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:105) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:356) at com.bea.netuix.nf.UIControl.render(UIControl.java:536) at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:405) at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:123) at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:58) at jsp_servlet._framework._skeletons._beatools.__gridlayout_two_column._jspService(__gridlayout_two_column.java:423) at weblogic.servlet.jsp.JspBase.service(JspBase.java:33) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:638) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:423) at com.bea.netuix.servlets.controls.JspRenderer.renderAlt(JspRenderer.java:194) at com.bea.netuix.servlets.controls.JspRenderer.beginRender(JspRenderer.java:96) at com.bea.netuix.nf.ControlLifecycle$1.visit(ControlLifecycle.java:491) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:542) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:247) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:105) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:356) at com.bea.netuix.nf.UIControl.render(UIControl.java:536) at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:405) at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:123) at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:58) at jsp_servlet._framework._skeletons._beatools.__gridlayout._jspService(__gridlayout.java:193) at weblogic.servlet.jsp.JspBase.service(JspBase.java:33) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:638) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:423) at com.bea.netuix.servlets.controls.JspRenderer.renderAlt(JspRenderer.java:194) at com.bea.netuix.servlets.controls.JspRenderer.beginRender(JspRenderer.java:96) at com.bea.netuix.nf.ControlLifecycle$1.visit(ControlLifecycle.java:491) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:542) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:247) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:105) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:356) at com.bea.netuix.nf.UIControl.render(UIControl.java:536) at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:405) at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:123) at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:58) at jsp_servlet._framework._skeletons._beatools.__gridlayout_outermost._jspService(__gridlayout_outermost.java:285) at weblogic.servlet.jsp.JspBase.service(JspBase.java:33) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:638) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:423) at com.bea.netuix.servlets.controls.JspRenderer.renderAlt(JspRenderer.java:194) at com.bea.netuix.servlets.controls.JspRenderer.beginRender(JspRenderer.java:96) at com.bea.netuix.nf.ControlLifecycle$1.visit(ControlLifecycle.java:491) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:542) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:553) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:247) at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:204) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:153) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:333) at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:196) at com.bea.netuix.servlets.manager.PortalServlet.doPost(PortalServlet.java:772) at com.bea.netuix.servlets.manager.PortalServlet.doGet(PortalServlet.java:671) at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:147) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27) at com.bea.servlet.PortalSystemAdministratorFilter.doFilter(PortalSystemAdministratorFilter.java:83) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27) at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:293) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6987) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) Caused by: org.xml.sax.SAXParseException: Document is invalid: no grammar found. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(Unknown Source) at com.bea.p13n.delegation.management.internal.DelegationHierarchyParser.getDelegationHierarchy(DelegationHierarchyParser.java:102) at com.bea.p13n.delegation.management.internal.DelegationHierarchyAbstractPersistenceManager.parseData(DelegationHierarchyAbstractPersistenceManager.java:206) ... 129 more
---End Stack Trace---

I have the same problem with Weblogic 8.1 SP5 running on Itanium (the same appl. running on Xeon runs OK).

Error installing Azure SDK 2.2: An error occurred while parsing Entityname. Line 1031, position 71.

I am setting up a new machine for windows azure development. I have VS 2013 Ultimate with Team Explorer on Windows 7 Enterprise. When I launch the Web Installer for Azure SDK 2.2 I receive a dialog almost immediately with the message:
An error occurred while parsing EntityName. Line 1031, position 71.
I ran the same installer on another machine with similar configuration of VS2013 and Win 7, and it doesn't display this dialog.
Any help/guidance is appreciated.

Hi,
Based on your description, you install Azure SDK successful in a similar configuration machine, but it give "An error occurred while parsing EntityName. Line 1031, position 71" error in your target machine, from my research, this may be Microsoft
server-side error, refer to
http://stackoverflow.com/questions/14964634/wpi-4-5-error-after-upgrading fro more details. I would suggest you reinstall, if any further issue, please feel free to let e know.
Best Regards
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Error occurred while parsing: Start of root element expected.

This my code i use to try inserting xml data:
v_BFile := BFILENAME('XML_DIR',v_xmlfile);
DBMS_LOB.createTemporary(v_clob, cache=>false);
DBMS_LOB.open(v_bFile, DBMS_LOB.lob_readonly);
DBMS_LOB.loadFromFile(v_clob,v_BFile,DBMS_LOB.getLength(v_bfile));
DBMS_LOB.close(v_bfile);
v_parser := XMLPARSER.newParser;
XMLPARSER.parseClob(v_parser,v_clob);
On the parseClob is get the error message: Error occurred while parsing: Start of root element expected.
My xml is as follows
<?xml version="1.0" ?>
<EMPLOYEES>
<EMP>
<EMPNO>8000</EMPNO>
<ENAME>JONES</ENAME>
<JOB>DBA</JOB>
<MGR>7839</MGR>
<HIREDATE>07-MAY-2002</HIREDATE>
<SAL>100</SAL>
<COMM>10</COMM>
<DEPTNO>10</DEPTNO>
</EMP>
<EMP>
<EMPNO>8001</EMPNO>
<ENAME>SMITH</ENAME>
<JOB>PROG</JOB>
<MGR />
<HIREDATE>01-MAY-2002</HIREDATE>
<SAL>200</SAL>
<COMM>10</COMM>
<DEPTNO>10</DEPTNO>
</EMP>
</EMPLOYEES>
What do i do wrong. Can someone help me

Kurt
Can you answer the following questions
Which Release of the database are you using ?
What is the database character set ?
What is the character set encoding of the source document ?
Remember that the loadFromFile procedure is designed to load binary data, and does not convert data into the database character set. If the database character set is UTF8, then the CLOB data has to be UCS2.
Can you dump the contents of the CLOB
If you are using 9iR2 then you can use the new procedure GetCLOBFromFile which will perform the correct coversions.
Also in 9iR2 we would recommend the use of the DBMS_XMLPARSER package, rather than the XMLPARSER package. The reason for this is the DBMS_XMLPARSER makes use of a 'C' based parser, running as native compiled code, which XMLPARSER still uses the Java based version of the parser. Performance with DBMS_XMLPARSER is much better.
Hope this helps

An error occurred while parsing EntityName. Line 1, position 3224

Hi all...
We are implementing a SAP standard solution as per NOTE 1003730
we are facing problem while transferring data to Government Gateway and error generated as
"An error occurred while parsing EntityName. Line 1, position 3224"
tried counting the posiitons in payload....could get any luck....
any inputs around this will be of gr8 help.
Full error text as follows:
- <GovTalkErrors>
- <Error>
<RaisedBy>System</RaisedBy>
<Number>1001</Number>
<Type>fatal</Type>
<Text>An error occurred while parsing EntityName. Line 1, position 3224.</Text>
<Location />
</Error>
</GovTalkErrors>
Regards.

Hi,
Could tell us what EntityName's value is ? Or what's at this char position ?
Rgds
Chris

ORA-20100: Error occurred while parsing (from xml in custom schema)

Hi,
I am using xmlParser and xmlDom to extract information from xml document. My whole process works perfectly in the APPS schema on the Oracle e-Business Suite. The minute I move it to a custom schema (ie new User) I get this error.
ORA-20100: Error occurred while parsing: Element '' used but not declared.
This only occures at runtime. I am pretty sure I grant the correct SELECT and EXECUTE privileges to this Schema. If I hadn't then it would not compile. It compiles without errors on the Database.
Any help will be appreciated.
Thanks in advance.
Regards
Dave

I just tried this again. I have Oracle9i 9.0.1.1 on my Windows
2000 laptop.
I went to OTN and downloaded the XDK 9.0.2D for PL/SQL
I used loadjava to load the \oracle\ora90\rdbms\jlib\xdb_g.jar
file into the database (shouldn't have had to do this) into the
XMLBOOK account. Filed a bug for needing to do this by hand.
I ran "xdkload.bat" with xmlbook/xmlbook as the username/password
I made sure the proxy server name was set correctly in the
example (if you don't need a proxy server, comment out that line
in the parse_xml_news.sql example, or that could cause your
error!!)
I ran the parse_xml_news.sql script, and I get:
Top Stories on XML from Moreover.com on December 21st, 2001
( 1) CEO highlights Mercator Softwares single biggest opportunity
( 2) WWRE Chooses webMethods
( 3) WebMethods, retail exchange ink deal
( 4) Worldwide Retail Exchange Chooses webMethods
( 5) Worldwide Retail Exchange Chooses webMethods
( 6) WorldWide Retail Exchange choses webMethods for integration
( 7) XML: Wherever You Go, There You Are
( 8) Chap. 13: Metadata
( 9) Enterprise Adoption of XML Made Simple
(10) XML Databases
(11) Using CSS2 to display XML documents
(12) How XML could bring an end to all of your troubles
(13) Effort Launched To Bring Classic Macs Rich Metadata To Mac
(14) Sneak attack on Pearl Harbor roused publics anger, resolve
(15) Drug dogs whiff worth $230,000
(16) PORTLAND Police target
(17) 11-year-old cant seem to get out of jury duty
(18) Another casualty of war: Proposed waterfront museum
(19) webMethods Establishes Sales Operations in Brussels
(20) Using Emacs for XML documents
(21) Gates: XML could be everything we dreamed...
(22) XML: The end of all your troubles?
(23) Java XML
(24) Tool To Compare XML Files
(25) Fairfax County Sends webMethods to School
(26) webMethods Embraces Web Services
(27) WebMethods Supports Web Services
(28) Accessing metadata through Reflection
(29) When format is foremost
(30) Views from Abroad: XML Pipelines and Delta XML

Internal error occured while parsing heap dump.

Hello,
I have a huge heap dump .hprof file (800 MB) in size and I tried to open it with memory analyzer in Eclipse. After parsing the file till 4%, I get internal error occurred. Java heap space. My system has 2GB memory. Below is the command I used to launch eclipse. Can someone help me with this ? Many thanks for your time.
C:\eclipse\eclipse.exe -vmargs -Xms512M -Xmx512M -XX:PermSize=256M -XX:MaxPermSize=256M
I have JRE 1.6.0_05-b13 installed on the system.
Thanks,
Hari

Hello Hari,
I would recommend that you first try to give more memory to eclipse and see if this helps. Try with 1200m for example.
I can't give you a precise estimation how much memory will be needed, as the limiting factor is the number of objects in the heap dump (not the size of the file). This number varies from case to case. In 800mb you may have only a few huge objects, but it may also happen that there are more than 20.000.000 of very small objects.
So, please try with more memory, and let me know if you still encounter the problem.
Regards,
Krum

Unreachable statement error occured while using return statement.

Consider this code
class q25{
     public static void main(String args[]){
          amethod(args);
     public static void amethod(String args[]){
          String str;
          try{
               str = "Hello "+args[0];
               System.out.println(str);
               System.out.println("Returning to caller");
               System.exit(0);
          catch(Exception e){
               System.out.println("Exception ocured");
               System.exit(0);
          finally{
               System.out.println("In finally");
          System.out.println("At the end of method");
}Above code compiles and runs successfully without any errors.
Now consider below code which is same as above one except "System.exit(0)" statements were replace by "return" statements. Below code when compiled gives error as
"q25.java:22: unreachable statement
System.out.println("At the end of method");
^
1 error"
One thing i didn't understood in this context that, the above code when compiled should get same error as stated above. But not. It is obvious that presence of System.exit(0) must generate unreachable statement same as when it is replaced by "return" statement. What is the difference in getting the error for above but not for below code. Pls anyone help.
class q25{
     public static void main(String args[]){
          amethod(args);
     public static void amethod(String args[]){
          String str;
          try{
               str = "Hello "+args[0];
               System.out.println(str);
               System.out.println("Returning to caller");
               return;
          catch(Exception e){
               System.out.println("Exception ocured");
               return;
          finally{
               System.out.println("In finally");
          System.out.println("At the end of method");
}

warnerja wrote:
masijade. wrote:
Since you have a "return" in both the try and the catch portions of the try/catch block *(the second of which you should never do)* , anything thing that comes after the try/catch/finally blocks will be unreachable.That is not true. There are plenty of reasons to return from a catch block. If you handle the exception instead of rethrowing it or another exception, then you'll need a return somehow, either there or after the catch block. What you should never do is "return" in a finally block, because that will mask any exception in flight about to be thrown to the caller.Perhaps masijade's use of never is too strong, but I too prefer/tend to avoid using return anywhere in try/catch/finally to avoid potential gotchas. Consider:
public class TryCatchFinally
public Data process(String s)
    Data returnData = new Data();
    try
      returnData.value = Integer.parseInt(s);
      returnData.message = "Success";
      return returnData;
    catch (Exception ex)
      returnData.value = -1;
      returnData.message = "Fail";
      return returnData;
    finally
      returnData.value = 42;
      returnData.message = "?";
public static void main(String[] args)
    TryCatchFinally demo = new TryCatchFinally();
    Data d = demo.process("2");
    System.out.println(d.message + ": " + d.value);
    d = demo.process("2.1");
    System.out.println(d.message + ": " + d.value);
class Data
    int value = 0;
    String message = "";
}

An error occurred while parsing a contents stream. Unable to analyze the PDF file

I get this error while attempting to use Preflight to analyze a PDF provided by an outside source. How can I validate the streams within the PDF? I'm on a team of developers who can build a tool given the relevant components, but we don't know where to start.

Are you sure that file paths are correct? I say this because under XP they would have originally pointed to Documents & Settings/My Pictures whereas on W7 it will be User/Pictures, albeit you are using an external hd.
Take a look at this knowledge base note on the correct procedure for back-up and restore.
I think writing metadata to files for such a large catalog will be a thankless task.
http://helpx.adobe.com/photoshop-elements/kb/backup-restore-move-catalog-photoshop.html

Error occured while executing WebSQL statement in Windows (Phone) 8.1

I am debugging Apache Cordova application in Visual Studio 2013.4. The application works fine in Ripple and Android emulator, however, when I try to debug on Windows x64 or Windows Phone (device) I get following error:
On this line: https://github.com/MSOpenTech/cordova-plugin-websql/blob/17015eb938d902eeb6018c03e438658103b28c17/www/windows/SqlTransaction.js#L105
Unhandled exception at line 105, column 9 in ms-appx://io.cordova.myapp.../www/plugins/com.msopentech.websql/www/windows/SqlTransaction.js
0x800a139e - JavaScript - runtime error [object Object]
Here is my code inside index.html:
<script type="text/javascript">
document.addEventListener("deviceready", onDeviceReady, false);
var db = null;
function onDeviceReady() {
var dbSize = 5 * 1024 * 1024;
// 5MB
db = window.openDatabase("lilka", "1.0", "Lilka hybrid db", dbSize)
if (db) {
populateDatabase();
function populateDatabase() {
db.transaction(function(tx) {
tx.executeSql("CREATE TABLE IF NOT EXISTS Product (Id INTEGER, Name TEXT)", [], onSuccess, onError);
tx.executeSql("INSERT INTO Product(Id, Name) values (1, 'testvalue')", [], onSuccess, onError);
tx.executeSql('SELECT * FROM Product', [], function(tx, results) {
var len = results.rows.length,
i;
for (i = 0; i < len; i++) {
alert(results.rows.item(i).Name);
</script>
Note: I am using
WebSQL plugin from MS Open Tech.

Please refer to reply posted on
https://github.com/MSOpenTech/cordova-plugin-websql/issues/19.
-Ellen

Error while parsing CLOB

I got following error while parsing clob :
ORA-20100: Error occurred while parsing: ORA-00942: table or view does not exist
ORA-06512: at "SYSTEM.XMLPARSER", line 22
ORA-06512: at "SYSTEM.XMLPARSER", line 98
Any Ideas ? What Table or View it is looking for ?

Code :
DECLARE
doctoparse clob;
p Xmlparser.Parser;
doc Xmldom.DOMDocument;
nl Xmldom.DOMNodeList;
len NUMBER;
len2 NUMBER;
n Xmldom.DOMNode;
m Xmldom.DOMNode;
e Xmldom.DOMElement;
nnm Xmldom.domNamedNodeMap;
attrname VARCHAR2(100);
attrval VARCHAR2(100);
BEGIN
SELECT detaildata
INTO doctoparse
FROM USERDATA
WHERE userid = 50650;
p := Xmlparser.newParser;
Xmlparser.setValidationMode(p, FALSE);
Xmlparser.parseclob(p, doctoparse);
doc := Xmlparser.getDocument(p);
Xmlparser.freeParser (p);
nl := Xmldom.getElementsByTagName(doc, '*');
len := Xmldom.getLength(nl);
dbms_output.put_line('LENGTH OF DOM = ' | | TO_CHAR(len));
FOR i IN 0..len-1 LOOP
n := Xmldom.item(nl, i);
e := Xmldom.makeElement(n);
dbms_output.put_line(Xmldom.getTagName(e) | | ':' );
m := Xmldom.getFirstChild(n);
dbms_output.put(Xmldom.getNodeValue(m));
m := xmldom.getparentnode(n);
e := xmldom.makeelement(m);
dbms_output.put_line('Parent = ' | | Xmldom.getTagName(e) | | CHR(13)) ;
nnm := Xmldom.getAttributes(n);
len2 := Xmldom.getlength(nnm);
FOR j IN 0 ..len2 - 1 LOOP
m := Xmldom.item(nnm, j);
attrname := Xmldom.getNodeName(m);
attrval := Xmldom.getNodeValue(m);
dbms_output.put(' ' | | attrname | | ' = ' | | attrval);
END LOOP;
dbms_output.put_line('');
END LOOP;
xmldom.freedocument(doc);
END;
Data in CLOB :
<Data><Country>nklmdnl</Country><Fax>6788267882</Fax><City>sdfsdf</City><WorkPhone>6788267882</WorkPhone><State>nn</S tate><Zip>12343</Zip></Data>
Thanks,

Error while parsing xml document that file name is Japanese.

who can help me.
when my xml file name is Japanese. Error occurs while parsing.
the error message is "ORA-20100: Error occurred while parsing: No such file or directory"
thanks.

Hi,
When I am trying to parse the XML file, I am getting
the following error. When I run it on Windows having
JDK1.4 it is working fine. But when I am running it
on UNIX having JDK1.2, I am getting this ERROR.
org.xml.sax.SAXParseException: Illegal character at
end of document, <.
Any help is appreiciated.I am just guessing, but I would imagine that some of the classes of your JDK 1.4 API have code that is not backwards compatible with earlier versions. There were a few significant changes to the language when 1.4 was released. You would have to read the release notes of 1.4 and also check the API documentation for the classes you are using to parse the XML.
Also, there are some subtle differences between the OS versions of the Java compiler. You are using two different versions of the Java language and two different versions of operating system code.

IDOC_ERROR_PARSE_FAILURE: An IDocIllegalTypeException occurred while parsing IDocXML:state=READING_SEGMENT_STARTTAG

Similar Messages

Maybe you are looking for