XML parsing fatal error: Invalid document structure, line: 1, file: ... (in this case "Classic.xml"

dreamweaver not initiating..claiming a parsing fatal cerr because classic.xml is corrupted. I tried re-installing dreamweaver... nothing

See here Dreamweaver CS5 fatal error XML parsing: Invalid document structure, line:1, File: C:\User\Tyler\App

Similar Messages

Adobe Flash Cs4 : xml parsing fatal error invalid document structure line 1 file

Hi there.. Well, this is in the title.. I got a problem with adobe flash cs4 : I can't launch it normaly and its says that a fatal error has occured.. I really don't know what I must do.. Please, help me.... I've just lost like 3 or 4 files of adobe by trying to reinstall it.. Help me please..
** My tools are now invisible **

Say do you have a designer.xml file

Dreamweaver stopped working. XML parsing fatal error: Invalid document structure, line1 Tried reloading DW. Didn't work.

Dreamweaver (CS5) stopped working. The error message says - XML parsing fatal error: Invalid document structure, line: 1, I tried to reload DW. No change. I also tried to reset the computer to an earlier date before I reloaded. Also didn't work. Can anybody shed some light?

The first thing to try is Deleting Corrupted Cache. Be sure to turn on Hidden Files & Folders in your file manager (Win Explorer or Mac Finder).
http://forums.adobe.com/thread/494811
If that doesn't help, try Restore Preferences
http://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver-cs4-cs5.html
If all else fails, use the CC Cleaner Tools below to wipe DW from your system, followed by a software re-install.
http://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html
Keep us posted on your results.
Nancy O.

Dreamweaver CS5 fatal error XML parsing: Invalid document structure, line:1, File: C:\User\Tyler\App

XML parsing fatal error: Invalid document structure, line: 1, file: C:\User\Tyler\AppData\Roaming\Adobe\Dreamweaver CS5\en_US\Configureation\Workspace\Classic.xml
I have gone through older disscussion forums and have followed the steps recommended by deleting the corrupted .xml file itself (in this case "Classic.xml") but imidiatly after when i try to open Dreamweaver again, i am prompted with the same fatal error message including the file that i have just deleted. Next i deleted the entire configure file and this did not help either.
It is also odd that when i follow the path to find the corrupted .xml file from the prompt, the path is different in that i do not find the "Classic.xml" file through th "en_US\Configuration\Weorkspace" navigation, however i do find the corrupt "Classic.xml" file in the "configure" folder of the "Adobe Dreamweaver CS5" file.
Im not sure what to do now and i would really like Dreamweaver back up and running so please help if you can!!!
Thanks
-Tyler

Step 1: Close DW, Navigate to C:\User\Tyler\AppData\Roaming\Adobe\Dreamweaver CS5\en_US\Configureation\Workspace\ and delete that Classic.xml file
Re-open DW. DW should auto-create your Workspace layout XML file again. See if it works fine.
PROCEED TO STEP 2 ONLY IF STEP 1 DOESN'T SOLVE THE ISSUE
Step 2: Navigate to C:\Users\Tyler\AppData\Roaming\Adobe\Dreamweaver CS5\en-US\Configuration and delete the entire 'CONFIGURATION' folder. Re-open DW. DW should auto-create your configuration folder based on predefined layouts and config options. This will definitely fix your issue.
Reason for this issue: This issue would have been caused due to a malformed workspace layout configuration. That may happen due to customizations you may have done to the layout/ improper file permissions/ improper shutdown on Windows.
See if these fixes resolve your issue and post your results here.
Cheers,
ST

XML parsing fatal error [subject edited by moderator]

Hello, when I try to open dreamweaver CS 5 I have this message: XML parsing fatal error: Invalid document structure, line: 1, File:C:\Users\Jean\AppData\Roaming\Adobe\Dreamweaver CS5\fr_FR\configuration\Workspace\Designer.xml Please help me.
Thank you to help me for this question about fatal error.

Deleting a corrupted cache file

Can't open DW CS5.5 Invalid document structure line 1 - anyone know how to fix this?

I get:
XML parsing fatal error: Invalid document structure, line 1, file:

The first thing to try is Deleting Corrupted Cache in DW
http://forums.adobe.com/thread/494811
If that doesn't help, try Restore Preferences
http://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver-cs4-cs5.html
If all else fails, use the CC Cleaner Tools below followed by a software re-install.
http://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html
Nancy O.

Error At Essbase Startup: Fatal Error: Invalid item index in security file

Hi
I'm newbie in ESSbase
A Essbase startup, i got this message: Fatal Error: Invalid item index in security file
I do a copy a the Essabse.bak to Essbase.sec and get the same message.
Need some help : it's a Production Application
Thanks in advance

Please try to restart Essbase once do rename Essbase.bak to Essbase.sec and check now

Dreamweaver cs5 : cant launch it suddenly due to XML parsing fatal error. WHY ?

System asked me to load a correct layout from WINDOWS - WORKSPACE
1/ it was not like that yesterday
2/ from the folder window ,I could not
find any file named WORKSPACE
* MY o/s - Windows 7
==> should I re-install dreamweaver first before doing anything ?
==> how can I load that layout ?
3/ my dreamweaver cs3 is no problem

before I noted your comments,I uninstalled it already.
Last time I failed after uninstalling & reinstalling it probably
becos I forgot to restart the computer.
Now , it resumes normal

I have Dreamweaver CS5.5 and all of a sudden I can't open it says XML parsing fatel error. Invalid Document Structure What do I do? Thanks

I have Dreamweaver CS5.5 and all of a sudden I can't open it says XML parsing fatel error. Invalid Document Structure What do I do? Thanks

You need to rename the Configuration folder to Configuration_BU.
The folder can be found by following this http://www.dmxzone.com/go/16740/clearing-dreamweaver-s-cache/

Org.xml.sax.SAXParseException: Line 1, Column 1 : XML-0108: (Fatal Error)

Hi ,
I am using SAX parser in a java code , which compiles and parses an xml correctly in the local JVM.
But the same code in OC4J(10g) - version 9.0.4.2 throws the following exception when traced the error stack.
08/04/04 17:48:40 Loading file workingday.xml from directory ========================== :::java.io.BufferedInputStream@bd4e3c
08/04/04 17:48:40 Read the xml into instream => STEP II
08/04/04 17:48:40 Read the xml into instream => STEP II
08/04/04 17:48:40 adding to the bankholiday list
org.xml.sax.SAXParseException: <Line 1, Column 1>: XML-0108: (Fatal Error) Start of root element expected.
08/04/04 17:48:40 at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:226)
08/04/04 17:48:40 at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:162)
08/04/04 17:48:40 at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:305)
08/04/04 17:48:40 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:267)
08/04/04 17:48:40 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:149)
08/04/04 17:48:40 at oracle.xml.jaxp.JXSAXParser.parse(JXSAXParser.java:286)
08/04/04 17:48:40 at oracle.xml.jaxp.JXSAXParser.parse(JXSAXParser.java:224)
Though I have imported the following JDK parsers in the code , the Oracle's SAX parser is taking other inside the application server and throwing the above error for an xml , which is absolutely alright.
import javax.xml.parsers.ParserConfigurationException;
import javax.xml.parsers.SAXParser;
import javax.xml.parsers.SAXParserFactory;
Please let me know why this happens? Is it a known bug in the OC4J 9.0.4.2?
Thanks and Regards
Antara

hi Antara
about "... Though I have imported the following JDK parsers in the code , the Oracle's SAX parser is taking other inside the application server ..."
If you have used the SAXParserFactory.newSAXParser() method to get a parser, the documentation for this method says "Creates a new instance of a SAXParser using the currently configured factory parameters.".
So you might get a different parser in a different environment.
regards
Jan Vervecken

Trying to create a pdf with jasper - Parse Fatal Error at line 1 column 1:

29/11/2007 16:52:03 org.apache.commons.digester.Digester fatalError
SEVERE: Parse Fatal Error at line 1 column 1: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
     at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
     at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
     at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(XMLDocumentScannerImpl.java:899)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
     at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
     at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
     at org.apache.commons.digester.Digester.parse(Digester.java:1666)
     at net.sf.jasperreports.engine.xml.JRPrintXmlLoader.loadXML(JRPrintXmlLoader.java:151)
     at net.sf.jasperreports.engine.xml.JRPrintXmlLoader.load(JRPrintXmlLoader.java:103)
     at net.sf.jasperreports.view.JRViewer.loadReport(JRViewer.java:1376)
     at net.sf.jasperreports.view.JRViewer.<init>(JRViewer.java:243)
     at net.sf.jasperreports.view.JRViewer.<init>(JRViewer.java:214)
     at net.sf.jasperreports.view.JasperViewer.<init>(JasperViewer.java:140)
     at net.sf.jasperreports.view.JasperViewer.viewReport(JasperViewer.java:397)
     at net.sf.jasperreports.view.JasperViewer.viewReport(JasperViewer.java:328)
     at br.com.abril.contratos.Gerar.geraRelatorio(Gerar.java:38)
     at br.com.abril.contratos.Gerar.main(Gerar.java:47)

The XML file that you're reading has something before the first line - either a comment, whitespace, or other characters. The first characters of your XML file MUST be the XML declaration:
<?xml ...
If there's anything before that angle bracket it's not valid XML.

Error Error oracle.iam.platform.context.ContextManager BEA-000000 IAM-0030007 org.xml.sax.SAXParseException: Line 1, Column 1 : XML-20108: (Fatal Error) Start of root element expected. error in oim logs

Hi ,
I am getting the below error at times in oim logs not able to find the reason please help.
<Error> <oracle.iam.platform.context.ContextManager> <BEA-000000> <IAM-0030007
org.xml.sax.SAXParseException: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
    at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:422)
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:414)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:355)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
<XELLERATE.DATABASE> <BEA-000000> <Class/Method: tcDataBaseClient/bindToInstance encounter some problems: java.lang.ClassNotFoundException: weblogic/jndi/WLInitialContextFactory
oracle.iam.platform.utils.ServiceInitializationException: java.lang.ClassNotFoundException: weblogic/jndi/WLInitialContextFactory
    at oracle.iam.platform.Platform.getService(Platform.java:265)
    at oracle.iam.platform.OIMInternalClient.getService(OIMInternalClient.java:188)
    at com.thortech.xl.dataaccess.tcDataBaseClient.bindToInstance(tcDataBaseClient.java:151)
    at com.thortech.xl.client.dataobj.tcDataBaseClient.recoverConnection(tcDataBaseClient.java:401)
    at com.thortech.xl.client.dataobj.tcDataBaseClient.getInterface(tcDataBaseClient.java:385)
    at com.thortech.xl.dataaccess.tcDataBaseClient.close(tcDataBaseClient.java:349)
    at com.thortech.xl.server.tcDataBaseClient.close(tcDataBaseClient.java:62)
    at com.thortech.xl.server.tcDataBaseClient.finalize(tcDataBaseClient.java:43
Caused By: java.lang.ClassNotFoundException: weblogic/jndi/WLInitialContextFactory
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    at com.sun.naming.internal.VersionHelper12.loadClass(Ve
<Class/Method: tcDataBaseClient/getInterface encounter some problems: RuntimeException encountered. Reconnecting!
java.lang.NullPointerException
    at oracle.iam.platform.context.ContextManager.getCounter(ContextManager.java:697)
    at oracle.iam.platform.context.ContextManager.incrementCounter(ContextManager.java:684)
<Error> <XELLERATE.DATABASE> <BEA-000000> <Class/Method: tcDataBaseClient/close encounter some problems: Bean has been deleted.
javax.ejb.NoSuchEJBException: Bean has been deleted.
Thanks,
Sahana

hi Antara
about "... Though I have imported the following JDK parsers in the code , the Oracle's SAX parser is taking other inside the application server ..."
If you have used the SAXParserFactory.newSAXParser() method to get a parser, the documentation for this method says "Creates a new instance of a SAXParser using the currently configured factory parameters.".
So you might get a different parser in a different environment.
regards
Jan Vervecken

Error(1,1): Line 1, Column 1 : XML-20108: (Fatal Error) Start of root elem

Hi
Plz tell me the solution of the following error .
D:\JDeveloperOAF\jdevhome\jdev\myhtml\OA_HTML\WEB-INF\web.xml
Error(1,1): <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
D:\JDeveloperOAF\jdevhome\jdev\myhtml\OA_HTML\test_fwktutorial.jsp
Error: java.lang.NullPointerException

Where r u getting the error?
--Shiv

XML-32009: (Fatal Error) Failed to parse the input schema.

I am attempting to generate the Java classes for the attached XLM schema (JMdict_e.xsd) using the following command:
oracle.xml.jaxb.orajaxb -schema JMdict_e.xsd -targetPkg generated
which results in the error "XML-32009: (Fatal Error) Failed to parse the input schema."
I created the schema from a DTD file (http://www.csse.monash.edu.au/~jwb/jmdict_dtd_h.html) following the instructions in the example http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28394/adx_j_sproc.htm#CIHICCJB
I am using version xdk_nt_10_1_0_2_0_production.
Can anyone help me with this please? Thanks.
JMdict_e.xsd
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="dial" type="xs:string"/>
<xs:element name="example" type="xs:string"/>
<xs:element name="upd_date" type="xs:string"/>
<xs:element name="ke_pri" type="xs:string"/>
<xs:element name="re_nokanji" type="xs:string"/>
<xs:element name="xref" type="xs:string"/>
<xs:element name="etym" type="xs:string"/>
<xs:element name="re_inf" type="xs:string"/>
<xs:element name="k_ele">
<xs:complexType>
<xs:sequence>
<xs:element ref="keb"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="ke_inf"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="ke_pri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="links">
<xs:complexType>
<xs:sequence>
<xs:element ref="link_tag"/>
<xs:element ref="link_desc"/>
<xs:element ref="link_uri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="lsource">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="lang" fixed="eng"/>
<xs:attribute name="ls_type" use="optional" type="xs:string"/>
<xs:attribute name="ls_wasei" use="optional" type="xs:string"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="ent_seq" type="xs:string"/>
<xs:element name="info">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="links"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="bibl"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="etym"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="audit"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="s_inf" type="xs:string"/>
<xs:element name="link_uri" type="xs:string"/>
<xs:element name="bib_txt" type="xs:string"/>
<xs:element name="link_tag" type="xs:string"/>
<xs:element name="bibl">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" ref="bib_tag"/>
<xs:element minOccurs="0" ref="bib_txt"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="upd_detl" type="xs:string"/>
<xs:element name="ant" type="xs:string"/>
<xs:element name="ke_inf" type="xs:string"/>
<xs:element name="audit">
<xs:complexType>
<xs:sequence>
<xs:element ref="upd_date"/>
<xs:element ref="upd_detl"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="pos" type="xs:string"/>
<xs:element name="pri" type="xs:string"/>
<xs:element name="r_ele">
<xs:complexType>
<xs:sequence>
<xs:element ref="reb"/>
<xs:element minOccurs="0" ref="re_nokanji"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="re_restr"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="re_inf"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="re_pri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="bib_tag" type="xs:string"/>
<xs:element name="re_restr" type="xs:string"/>
<xs:element name="stagk" type="xs:string"/>
<xs:element name="sense">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="stagk"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="stagr"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="pos"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="xref"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="ant"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="field"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="misc"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="s_inf"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="lsource"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="dial"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="gloss"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="example"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="keb" type="xs:string"/>
<xs:element name="field" type="xs:string"/>
<xs:element name="link_desc" type="xs:string"/>
<xs:element name="reb" type="xs:string"/>
<xs:element name="entry">
<xs:complexType>
<xs:sequence>
<xs:element ref="ent_seq"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="k_ele"/>
<xs:element maxOccurs="unbounded" ref="r_ele"/>
<xs:element minOccurs="0" ref="info"/>
<xs:element maxOccurs="unbounded" ref="sense"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="stagr" type="xs:string"/>
<xs:element name="re_pri" type="xs:string"/>
<xs:element name="gloss">
<xs:complexType mixed="true">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="pri"/>
</xs:choice>
<xs:attribute name="lang" fixed="eng"/>
<xs:attribute name="g_gend" use="optional" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="misc" type="xs:string"/>
<xs:element name="JMdict">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="entry"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>

@Bhaskar (and @user11922800): You have to update the db10g/xdk to a version at least of 10.1.0.4. There were major bug fixes including XML-32009 error (bug number 3375952).
http://www.eygle.com/case/bug10104.htm
I've even tried the op's listing with my more to-date xdk without encountering any problem and it is compiled just fine.
ps: I am sure that was the hasty typo in dvohra16 post. The namespace in the op (/2001/) is correct. Encoding is still capable of resulting in some problems (I've had encounted if I recall), but that is not the problem for the issue raised in this thread.

Encountering XML-20108: (Fatal Error) Start of root element expected

Hi,
We are trying to invoke a XML Publisher report from a custom OAF page using API's. However, it is erroring out with the following error message (in xdo.log)
[021710_121811671][oracle.apps.xdo.common.xml.XSLTWrapper][EXCEPTION] XSL error:
<Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
[021710_121811672][oracle.apps.xdo.template.FOProcessor][STATEMENT] clearInputs(Object) is called.
[021710_121811672][oracle.apps.xdo.template.FOProcessor][STATEMENT] clearInputs(Object) done. All inputs are cleared.
[021710_121811673][][EXCEPTION] java.lang.reflect.InvocationTargetException
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:597)
at oracle.apps.xdo.common.xml.XSLT10gR1.invokeParse(XSLT10gR1.java:517)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:224)
at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:177)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1044)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:997)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:212)
at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1665)
at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:975)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5936)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3459)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3548)
at lxe.oracle.apps.ibu.returnmgmt.server.RmaCreateReturnAMImpl.xxPrintShipLabel(RmaCreateReturnAMImpl.java:1046)
at lxe.oracle.apps.ibu.returnmgmt.webui.OrderConfirmCo.processFormRequest(OrderConfirmCo.java:167)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:815)
at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:382)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:815)
at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:382)
at oracle.apps.fnd.framework.webui.beans.layout.OAStackLayoutBean.processFormRequest(OAStackLayoutBean.java:370)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:1027)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:993)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:848)
at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:382)
at oracle.apps.fnd.framework.webui.beans.form.OAFormBean.processFormRequest(OAFormBean.java:395)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:1027)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequestChildren(OAWebBeanHelper.java:993)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processFormRequest(OAWebBeanHelper.java:848)
at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processFormRequest(OAWebBeanContainerHelper.java:382)
at oracle.apps.fnd.framework.webui.beans.OABodyBean.processFormRequest(OABodyBean.java:363)
at oracle.apps.fnd.framework.webui.OAPageBean.processFormRequest(OAPageBean.java:2863)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1840)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:538)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:426)
at jtfcrmchrome.jspService(_jtfcrmchrome.java:1191)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:379)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:619)
Caused by: oracle.xdo.parser.v2.XMLParseException: Start of root element expected.
at oracle.xdo.parser.v2.XMLError.flushErrors1(XMLError.java:337)
at oracle.xdo.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:343)
at oracle.xdo.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:285)
at oracle.xdo.parser.v2.XMLParser.parse(XMLParser.java:289)
... 56 more
The XML is generated from the code and is as below:
<ShippingLabelVO>
<ShippingLabelVORow>
<RowKey>1</RowKey>
<ShipSentToAddr>XXX Repair Center 125 Technology Parkway Austin, TX</ShipSentToAddr>
<SerialNum>BC104</SerialNum>
<OrderNum>8000324</OrderNum>
<ItemNum>MX7AM-170540</ItemNum>
</ShippingLabelVORow>
</ShippingLabelVO>
I can successfully create the PDF from the desktop using the above XML. When I add the XML file to sample XML (in data definition), I can see the output when I choose Preview.
But, this is not working from the code.
Any pointers?
Thanks,
Ashish

Hi,
We are currently on R12.XDO.B.1 (5.6.3?) Is there a patch we'll need to apply on top of this?
Is there a workaround for this?
Thanks,
Ashish

XML parsing fatal error: Invalid document structure, line: 1, file: ... (in this case "Classic.xml"

Similar Messages

Maybe you are looking for