Document root element is missing: migrating spring app from tomcat

Hi!
can anybody help me with this issue?
I have ported my tomcat spring application to netweaver(6.40, SP 17, Windows 2k SP4) and i get the following error:
Error occured in invoking event "contextInitialized()" on listener clas
s com.webapp.listener.StartupListener. The error is: org.springfram
ework.beans.factory.BeanCreationException: Error creating bean with nam
e 'sessionFactory' defined in ServletContext resource [/WEB-INF/applica
tionContext-hibernate.xml]: Initialization of bean failed; nested excep
tion is org.hibernate.MappingException: Could not parse mapping documen
t in input stream
org.hibernate.MappingException: Could not parse mapp
ing document in input stream
     at org.hibernate.cfg.Configuration.addIn
putStream(Configuration.java:430)
     at org.springframework.orm.hibernat
e3.LocalSessionFactoryBean.afterPropertiesSet(LocalSessionFactoryBean.j
ava:654)
     at org.springframework.beans.factory.support.AbstractAutowir
eCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactor
y.java:1059)
     at org.springframework.beans.factory.support.AbstractAut
owireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.j
ava:363)
     at org.springframework.beans.factory.support.AbstractBeanFac
tory.getBean(AbstractBeanFactory.java:226)
     at org.springframework.bea
ns.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java
:147)
     at org.springframework.beans.factory.support.DefaultListableBea
nFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:269)
     at org.springframework.context.support.AbstractApplicationContext.ref
resh(AbstractApplicationContext.java:320)
     at org.springframework.web.
context.support.AbstractRefreshableWebApplicationContext.refresh(Abstra
ctRefreshableWebApplicationContext.java:134)
     at org.springframework.w
eb.context.ContextLoader.createWebApplicationContext(ContextLoader.java
:246)
     at org.springframework.web.context.ContextLoader.initWebApplica
tionContext(ContextLoader.java:184)
     at org.springframework.web.contex
t.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:4
9)
     at com.ifx.webapp.listener.StartupListener.contextInitialized(Star
tupListener.java:42)
     at com.sap.engine.services.servlets_jsp.server.r
untime.context.WebEvents.contextInitialized(WebEvents.java:45)
     at com
.sap.engine.services.servlets_jsp.server.container.ApplicationThreadIni
tializer.run(ApplicationThreadInitializer.java:112)
     at com.sap.engine
.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.sec
urity.AccessController.doPrivileged(Native Method)
     at com.sap.engine.
core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.
sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
C
aused by: org.dom4j.DocumentException: Error on line 1 of document  : D
ocument root element is missing. Nested exception: Document root elemen
t is missing.
     at org.dom4j.io.SAXReader.read(SAXReader.java:482)
     at
org.hibernate.cfg.Configuration.addInputStream(Configuration.java:421)
     ... 18 more
And yes, the xml files are valid xml files at least in anything i've used to look at them (eclipse, ultraedit, notepad, ie) :).....
Thank you!
ps. the file:
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN"
    "http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
    <!-- Hibernate SessionFactory -->
    <bean id="sessionFactory" class="org.springframework.orm.hibernate3.LocalSessionFactoryBean">
        <property name="dataSource" ref="dataSource"/>
        <property name="mappingResources">
            <list>
                <value>package/ModelObj1.hbm.xml</value>
                <value>package/ModelObj2.hbm.xml</value>
            </list>
        </property>
        <property name="hibernateProperties">
            <props>
                <prop key="hibernate.dialect">org.hibernate.dialect.Oracle9Dialect</prop>
            </props>
        </property>
    </bean>
    <!-- Transaction manager for a single Hibernate SessionFactory (alternative to JTA) -->
    <bean id="transactionManager" class="org.springframework.orm.hibernate3.HibernateTransactionManager">
        <property name="sessionFactory" ref="sessionFactory"/>
    </bean>
    <!-- Generic DAO - can be used when doing standard CRUD -->
    <bean id="dao" class="com.dao.hibernate.BaseDAOHibernate">
        <property name="sessionFactory" ref="sessionFactory"/>
    </bean>
</beans>

hi istvan,
we are also migrating from websphere to netweaver.
But in spring framework we r facing problems.
We hav spring-beans.jar file in lib dir of Web Application. But When we are creating BeanFactory from xml as,
BeanFactory beanFactory = new ClassPathXmlApplicationContext ("client-config.xml");
clent-config.xml file contains :
[code<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
     <bean id="propertyConfigurer" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer" >
          <property name="location">
               <value>conf/service-client/client.properties</value>
          </property>
     </bean></beans>
[/code]
But code is giving exception: ClassNotFoundException -org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.
Wat is the problem ?
Kindly help.
We are also using JAAS for authentication.We are refering above code from our LoginModules login() method.
Regards,
sagar.

Similar Messages

  • Org.xml.sax.SAXParseException: Document root element is missing.

    Hi,
    I am trying to get the portal login id from a weblogic server based application from iplaet portal server.
    I get this follwoing error
    org.xml.sax.SAXParseException: Document root element is missing.
    at com.sun.xml.parser.Parser.fatal(Parser.java:2817)
    at com.sun.xml.parser.Parser.fatal(Parser.java:2805)
    at com.sun.xml.parser.Parser.parseInternal(Parser.java:493)
    at com.sun.xml.parser.Parser.parse(Parser.java:284)
    at com.sun.xml.tree.XmlDocument.createXmlDocument(XmlDocument.java:226)
    at com.iplanet.portalserver.util.XMLParser.<init>(XMLParser.java:70)
    at com.iplanet.portalserver.naming.share.NamingResponseParser.<init>(NamingResponseParser.java:33)
    at com.iplanet.portalserver.naming.share.NamingResponse.parseXML(NamingResponse.java:74)
    at com.iplanet.portalserver.naming.WebtopNaming.updateNamingTable(WebtopNaming.java:174)
    at com.iplanet.portalserver.naming.WebtopNaming.getNamingProfile(WebtopNaming.java:155)
    at com.iplanet.portalserver.naming.WebtopNaming.getServiceURL(WebtopNaming.java:57)
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:534)
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:520)
    at com.iplanet.portalserver.session.Session.getSession(Session.java:414)
    at jsp_servlet.__eatonPortalLogin._jspService(__eatonPortalLogin.java:155)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:462)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    <May 19, 2004 9:01:12 AM EDT> <Error> <HTTP> <101017> <[ServletContext(id=4873279,name=ematrix,context-path=/ematrix)] Root cause of ServletException
    com.iplanet.portalserver.session.SessionException
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:539)
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:520)
    at com.iplanet.portalserver.session.Session.getSession(Session.java:414)
    at jsp_servlet.__eatonPortalLogin._jspService(__eatonPortalLogin.java:155)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:462)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    Any help/pointers will be appreciated.
    Ashish

    Just for anyone else who hits this problem: I encountered the same issue with an XML document that XMLSpy claims is quite well formed. I opened the document in a hex editor, and there at the from was a three-byte byte order marker - the marker that I believe the UTF-8 standard says is optional. I removed these three bytes, and the file was parsed correctly.
    In this case, the XML file was created using a Microsft DOM (save).
    My solution is to make the java parser - as I use it - a tad more robust: Open the file and create an input stream - a pushback input stream. Read the first three bytes; if they are NOT a BOM, then push those bytes back. Now - in any case - give the stream to the parser to read.
    try {
    // Open file for reading.
    f = new File(path);
    FileInputStream fis = new FileInputStream(f);
    PushbackInputStream pis = new PushbackInputStream(fis);
    byte[] buf = new byte[3];
    pis.read(buf, 0, 3);
    if (! (buf[0] == 0x00EF) && (buf[1] == 0x00BB) && (buf[2] == 0x00BF) ) {
         pis.unread(buf, 0, 3);
    builder = DocumentBuilderFactory.newInstance().newDocumentBuilder();
    doc = builder.parse(pis);
    catch (Exception x) {
         x.printStackTrace();
    }

  • XML "Document root element is missing"

    i have made a research in the forums but i have no definite solution about the error.
    my flash client sends XML stream to my ServerSocket. and i want to parse these XML datas.
    Document XMLDoc;
    DocumentBuilderFactory Factory = DocumentBuilderFactory.newInstance();
    DocumentBuilder Builder = Factory.newDocumentBuilder() ;
    InputSource Is = new InputSource(new BufferedReader(new InputStreamReader(Sock.getInputStream(),"UTF-16LE")));
    XMLDoc = Builder.parse(Is);
    But now i have problem called "Document root element is missing". My XML stream comming from flash client :
    // Actionscript code :
         XDoc = new XML("<?XML version=\"1\"?><LOGIN><USERNAME>KHARON</USERNAME><PASSWORD>485009</PASSWORD></LOGIN>");
    ----- The XML data i want to sent to ...
    <?XML version="1"?>
    <LOGIN>
    <USERNAME>KHARON</USERNAME>
    <PASSWORD>485009</PASSWORD>
    </LOGIN>
    What is the problem ?

    now ?
    // Actionscript
    XSock = new XMLSocket();
    XSock.connect("127.0.0.1",6667);
    XDoc = new XML("<?xml version=\"1.0\"?><LOGIN><USERNAME>KHARON</USERNAME><PASSWORD>ew2345dfs</PASSWORD></LOGIN>");
    // Java
    public void run() {
    try {
    Document XMLDoc;
    DocumentBuilderFactory Factory = DocumentBuilderFactory.newInstance();
    DocumentBuilder Builder = Factory.newDocumentBuilder() ;
    InputSource Is = new InputSource(new BufferedReader(new InputStreamReader(Sock.getInputStream(),"UTF-16LE")));
    XMLDoc = Builder.parse(Is);
    org.w3c.dom.Node Node = XMLDoc.getFirstChild();
    System.out.print(Node.getNodeValue());
    /* Incomming data test code
    System.out.print("Listening to incomming messeges");
    char in ;
    while ( (in = (char)Reader.read()) != -1 ) {
    System.out.print( in );
    but the result
    parser exception ( Document root element is missing )
    ihave made a research ( i am newbee in XML) and i have made some declerations like <!DOCTYPE LOGIN <!Element ...
    i have declared root element with DOC type decleration. but the same error. :|
    since 2 days i am working over these, but solution = null

  • Parsing xml file error: Document root element is missing.

    Hi,
    When I try to parse an xml file with SAX parser, the SAXParseException message I got is: "Document root element is missing." Anybody knows what it is? How should I fix it? Thanks a lot in advance!
    J.H.

    An XML document has only a single root element. So after the XML header, your document must look something like this:
    <tag>
    </tag>
    If you have more than one element like this, for example:
    <tag>
    </tag>
    <anothertag>
    </anothertag>
    then you don't have a root element and your parser will give the message you referred to.

  • Migrating WebServices app from Tomcat to Glassfish...

    Hello!
    I've a WebService app. which now runs on Tomcat 5.5.23 and was written using JAX-WS. I've install Sun Java System App. Server 9.0 and I intend to migrate our app. here.
    The application is delivered as a war file which I've already deployed in glassfish using admin GUI of asadmin. I can see our app. at WebApplications section but I can't see it under WebServices section, although it seems at a first view that the application works and respond to client's request.
    I'd like to ask you if I need to use a special tool for migrating our aplication or what I did is enough and there is no need for other changes.
    Thank you very much
    With best regards,
    Sorin

    If I understand correctly, you are trying to load a few properties files on WLS that is specific to an application that you are migrating from tomcat to WLS. If that is the case, then as per my understanding we have the following options:
    a. Add all the properties in a jar file and add the same to the classpath or place the same in the lib directory of the server which can be picked at the server start-up.
    b. Place the properties file in the domain home which should help.
    Refer: loading a new properties file without restarting the managed server
    c. Else place the properties files in the web-inf of the application, that should help.

  • Does anyone know this message: "Document root element is missing"

    I'm getting this message by loading an XML File from my server into an DocumentBuilder. The only strange thing, if I'm doing that from my local machine (linux) it works, but executing by Java WebStart I get the message above !?!
    Does anyone know why?

    That was the first idea i had, but InputStream.available() on the given File means something about 3500 signs.
    Somewhere I read, that a Classpath, or Path may be missing, but I'm not using any special imports!
    package com.msgis.XML;
    import java.io.*;
    import org.xml.sax.*;
    import org.xml.sax.helpers.DefaultHandler;
    //API
    import javax.xml.parsers.DocumentBuilderFactory;
    import javax.xml.parsers.DocumentBuilder;
    import javax.xml.parsers.FactoryConfigurationError;
    import javax.xml.parsers.ParserConfigurationException;
    //Exceptions
    import org.xml.sax.SAXException;
    import org.xml.sax.SAXParseException;
    //Reading XML File
    import java.io.File;
    import java.io.IOException;
    //DOM definition and Exceptions
    import org.w3c.dom.Document;
    import org.w3c.dom.DOMException;
    //URL
    import java.net.URL;
    import java.net.*;
    Ideas?
    That is the only idea left, because, in the IDE (Sun ONE Studio 5 Update 1, Standard Edition) it works, and from other projects I know that the IDE is linking its own classes.
    java pgm does not work. It delivers the same Exception.
    SAXParseException Document blablabla .......

  • "root element is missing" - UTF-8

    I have 2 identical files, except they are stored in ISO-8859-1 and UTF-8.
    "Test ansii.xml":
    <?xml version="1.0" encoding="ISO-8859-1"?><e></e>
    "Test utf8.xml":
    <?xml version="1.0" encoding="UTF-8"?><e></e>
    When I look at them in Internet Explorer they show correctly. But when I parse them with SAX in java I get an error when I parse the file stored in UTF-8.
    import java.io.*;
    import javax.xml.parsers.*;
    import org.xml.sax.*;
    import org.xml.sax.helpers.*;
      public static void testXML(){
        try{
          File ansiiFile=new File("Test ansii.xml");
          File utf8File=new File("Test utf8.xml");
          SAXParserFactory factory = SAXParserFactory.newInstance();
          SAXParser saxParser = factory.newSAXParser();
          //try ISO-8859-1
          InputSource in = new InputSource(new InputStreamReader(new FileInputStream(ansiiFile),"ISO-8859-1"));
          saxParser.parse(in,new DefaultHandler());
          //try UTF-8
          in = new InputSource(new InputStreamReader(new FileInputStream(utf8File),"UTF-8"));
          saxParser.parse(in,new DefaultHandler());
        }catch(Exception e){
          e.printStackTrace();
      }The first file parses well, but when I parse the file encoded in UTF-8 I get this error:
    org.xml.sax.SAXParseException: The Document root element is missing.
         at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3182)
         at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3170)
         at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:501)
         at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
         at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
         at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
         at test.Test.testXML(Test.java:44)
         at test.Test.main(Test.java:25)
    Gil

    Sigh, I found the answer.
    http://www.i18ngurus.com/encyclopedia/byte_order_mark.html
    byte order mark
    Also known as BOM.
    Name given to the Unicode character U+FEFF when used at the beginning of a Unicode byte stream. This invisible character generally know as ZERO WIDTH NO-BREAK SPACE (ZWNBSP) serves to identify unambiguously the Unicode transformation form used (and especially the byte order) for the stream. Indeed U+FFFE is a noncharacter so there is no risk of misinterpretation.
    The following represents the byte signature of the character U+FEFF with the various Unicode Transformation Forms:
    Bytes Encoding
    00 00 FE FF UTF-32, big-endian
    FF FE 00 00 UTF-32, little-endian
    FE FF UTF-16, big-endian
    FF FE UTF-16, little-endian
    EF BB BF UTF-8
    Historically the ZWNBSP was also used to indicate non-breaking but this use is now deprecated and replaced by the character U+2060 for that purpose.
    http://p2p.wrox.com/archive/xslt/2002-11/79.asp
    I suspect you edited the stylesheet using a text editor that inserts the
    BOM at the start of the file. For example, I think Windows Notepad does
    this.
    Some XML parsers accept a BOM at the start of a UTF-8 file, others
    don't. For example, the Crimson parser that comes with JDK 1.4 doesn't.
    You basically need to find a text editor and an XML parser that agree
    with each other about whether or not to use a byte order mark.
    Alternatively, use a different encoding for the stylesheet, e.g.
    iso-8859-1.
    The code above found these strange bytes while expecting '<', and crashed of course.
    Gil

  • CORE3282: stdout: org.xml.sax.SAXParseException: Document root element

    I got an application running on Sun ONE Web Server 6.1SP5, during the application start, I got the following message. The application can run without any problem. I would like to know if there is any solution to avoid the PARSE error? Thanks a lot.
    [01/Aug/2006:11:42:09] info (21921):      CORE1116: Sun ONE Web Server 6.1SP5 B08/18/2005 02:17
    [01/Aug/2006:11:42:09] info (21923):      CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.2_04] from [Sun Microsystems Inc.]
    [01/Aug/2006:11:42:09] info (21923):      WEB0100: Loading web module in virtual server [https-sunfire] at [myapp]
    [01/Aug/2006:11:42:09] info (21923):      WEB0100: Loading web module in virtual server [https-sunfire] at [search]
    [01/Aug/2006:11:42:13] info (21923):      CORE3282: stdout: PARSE error at line 6 column 19
    [01/Aug/2006:11:42:13] info (21923):      CORE3282: stdout: org.xml.sax.SAXParseException: Document root element "taglib", must match DOCTYPE root "null".
    [01/Aug/2006:11:42:13] info (21923):      WEB2798: [myapp] ServletContext.log(): Loading Spring root WebApplicationContext
    [01/Aug/2006:11:42:18] info (21923):      WEB2798: [myapp] ServletContext.log(): Loading WebApplicationContext for Spring FrameworkServlet 'action'
    [01/Aug/2006:11:42:18] info (21923):      HTTP3072: [LS ls1] http://sunfire:9999 ready to accept requests
    [01/Aug/2006:11:42:18] info (21923):      CORE3274: successful server startup

    That doesn't say much. Which is this xml file? and what have you given in the <!DOCTYPE > tag? Probably, that is the mistake...

  • Document root element

    When starting Sun One Application Server 7 I get the following error in the console:
    SEVERE ( 5028): ContextConfig[ROOT] Parse error in application web.xml
    org.xml.sax.SAXParseException: Document root element "web-app", must match DOCTYPE root "null".
    What does this error mean and how do I fix?
    My web.xml file:
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee      http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
      version="2.4">
      <display-name>My appliation</display-name>
      <description>My appliation</description>
      <context-param>
        <param-name>log4j-file</param-name>
        <param-value>WEB-INF/log4j.properties</param-value>
      </context-param>
      <listener>
        <listener-class>
          com.gh.web.listener.Listener
        </listener-class>
      </listener>
      <servlet>
        <servlet-name>action</servlet-name>
        <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
        <init-param>
          <param-name>config</param-name>
          <param-value>/WEB-INF/struts-config.xml</param-value>
        </init-param>
        <init-param>
          <param-name>debug</param-name>
          <param-value>0</param-value>
        </init-param>
        <load-on-startup>2</load-on-startup>
      </servlet>
      <jsp-config>
        <taglib>
          <taglib-uri>/tags/common</taglib-uri>
          <taglib-location>/WEB-INF/tld/common.tld</taglib-location>
        </taglib>
      </jsp-config>
    </web-app>

    If running on Tomcat Server, then is start without errors.
    I made a following change in web.xml and error is disappeared:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN'
      'http://java.sun.com/j2ee/dtds/web-app_2_3.dtd'>
    <web-app>
    </web-app>The reason for the 'break' is because I attempting to deploy a web application following the 2.4 spec that Sun One Application Server 7 does not support or why?

  • DSDP 3.0 - CM 2012 R2 CU3 - Import Driver Packages Fail - Root element is missing

    I realize that the Dell Server Deployment Pack 3.0 plug in is a vendor plugin to CM 2012 R2 but they (dell) are clueless.  So I am hoping that there is some knowledge here.
    I've opened a case with Dell and have used the Dell forums to document my issue here:
    http://en.community.dell.com/techcenter/systems-management/f/4469/t/19613996
    (there are some pics that might help.)
    I have a ConfigMan 2012 R2 environment where I have integrated the Dell Server Deployment Pack 3.0.  The installation succeeded and I have been able to also run the Dell System Integration using the DTK 4.4.  I am doing all of this work directly
    on the CM 2012 primary site server.
    However, when I try to Import Dell Drivers, I get an error in the wizard:
    I have tried multiple OM DVD's each one produces the same results:
    OM_SMTD_801_A00.iso
    OM_SMTD_802_A00.iso
    OM_SMTD_740_A00.iso
    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.
    ************** Exception Text **************
    System.Xml.XmlException: Root element is missing.
       at System.Xml.XmlTextReaderImpl.Throw(Exception e)
       at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
       at System.Xml.XmlTextReaderImpl.Read()
       at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
       at System.Xml.XmlDocument.Load(XmlReader reader)
       at System.Xml.XmlDocument.Load(String filename)
       at Microsoft.ConfigurationManagement.OemDeployment.DellDriverPackageImport.PackageSelection.GetPackageListXml(String dellCatalogXml)
       at Microsoft.ConfigurationManagement.OemDeployment.DellDriverPackageImport.PackageSelection.PackageSelection_Load(Object sender, EventArgs e)
       at System.Windows.Forms.Form.OnLoad(EventArgs e)
       at System.Windows.Forms.Form.OnCreateControl()
       at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
       at System.Windows.Forms.Control.CreateControl()
       at System.Windows.Forms.Control.WmShowWindow(Message& m)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
       at System.Windows.Forms.ContainerControl.WndProc(Message& m)
       at System.Windows.Forms.Form.WmShowWindow(Message& m)
       at System.Windows.Forms.Form.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.34014 built by: FX45W81RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
    Microsoft.ConfigurationManagement
        Assembly Version: 5.0.0.0
        Win32 Version: 5.0.7958.1401
        CodeBase: file:///D:/Program%20Files/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.ConfigurationManagement.exe
    System
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.34239 built by: FX452RTMGDR
        CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    .... (log continues)....
    Any ideas? 
    My CM 2012 R2 is running on Windows 2012 R2.

    Thanks for your comment. I thought that Microsoft might have had some involvement with the writing of this tool:
    http://en.community.dell.com/techcenter/systems-management/w/wiki/4125.dell-server-deployment-pack-dsdp-for-configuration-manager

  • Org.xml.sax.SAXParseException: Document root element "taglib", must match D

    hi
    using tomcat 4
    and jdf1.5
    i am getting bellow error
    org.xml.sax.SAXParseException: Document root element "taglib", must match DOCTYPE root "null".

    Check your web.xml once again.

  • Root element is missing - Response from a WCF service - WCF-Custom adapter

    hi BizTalk experts,
    In the production environment, as soon as the response is getting subscribed by the orchestration, the orchestration instance is getting suspended and the error that shows up in console is 
    "Root element is missing".
    I have checked the actual response message in the console it is a well formed xml. This is happening only for a few responses from the WCF services. A majority of them are getting processed successfully. I have tried getting the parsing the response in a
    pipeline (using custom pipeline component, the production one uses xml receive) and pass it to the orchestration, but it fails giving the same error.
    Thanks in advance.

    Do you have any mapping done on the response message from the WCF service . ?
    If so Better to copy the suspended message coming from the WCF service and validate against the custom response Schema you have created.
    Note : You can try running fiddler tool to check the response from from the web service incase of failure.
    Also try logging the message in the event viewer or any debug tool.
    Thanks
    Abhishek

  • "Root element is missing." - While using Sharepoint List Source in SSIS.

    Hi Team,
    We are trying to import data from sharepoint list using sharepointlist source in SSIS. But the following error pops-up.
    [SP_SRC_SharePointList [67]] Error: System.Xml.XmlException: Root element is missing.
       at System.Xml.XmlTextReaderImpl.Throw(Exception e)
       at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
       at System.Xml.XmlTextReaderImpl.Read()
       at System.Xml.XmlReader.MoveToContent()
       at System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options)
       at System.Xml.Linq.XElement.Parse(String text, LoadOptions options)
       at System.Xml.Linq.XElement.Parse(String text)
       at Microsoft.Samples.SqlServer.SSIS.SharePointListAdapters.SharePointListSource.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers)
       at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper100 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer100[] buffers, IntPtr ppBufferWirePacket)
    We are unable to debug / move any further. Request your help.
    Thank you.
    Best Regards,
    Gayathri

    It appears that the XML you trying to load does indeed not have the root element.
    E.g.
    <?xml version="1.0" encoding="UTF-8"?>
    <iii>
    <kkk>test</kkk>
    <ppp>000</ppp>
    </iii>
    <iii>
    <kkk>test</kkk>
    <ppp>000</ppp>
    </iii>
    <iii>
    <kkk>test</kkk>
    <ppp>000</ppp>
    </iii>has nonemust be<?xml version="1.0" encoding="UTF-8"?>
    <Root><iii>
    <kkk>test</kkk>
    <ppp>000</ppp>
    </iii>
    <iii>
    <kkk>test</kkk>
    <ppp>000</ppp>
    </iii>
    <iii>
    <kkk>test</kkk>
    <ppp>000</ppp>
    </iii></Root>
    Arthur My Blog

  • Migrate essbase app from 6 to 9

    planning to migrate the app from essbase 6 to esbase 9.to a whole new server.
    Any issues with that...any doc on migration from 6 would be useful.
    its urgent

    I started to migrate from 6.6 to 9.3.1 and it went quite smooth. What I have done:
    Installed the server.
    Used the config tool and removed shared services registration.
    Copied essbase.cfg to new installation.
    Had to add the env variables manually on AIX from the hyperionenv.doc.
    Installed the eas server.
    Used config tool for config and deployment of eas on std settings.
    Installed the eas client and used the migration tool to migrate some databases to the new server from a 6.6 (6.6 running on different machine than 9.3)
    Tested our batch processing for data load, security transfers, data staging etc. which uses some api interfaces and ESSCMD and maxl scripts. All without any problems. All settings were kept the same as on the old systems (essbase.cfg, db settings, app settings).

  • Ive migrated my apps from an old mac to my new mac. When i try to open my CS5 programs it get a pop up that says i need to install the legacy java SE 6. Ive done that and it still does not open?

    Ive migrated my apps from an old mac to my new mac. When i try to open my CS5 programs it get a pop up that says i need to install the legacy java SE 6. Ive done that and it still does not open?

    I'm having a similar problem...but mine results from an OS upgrade from 10.6.4 to 10.8.5.
    Where did you access a clean copy of Java SE 6?  The link at adobe for archicval plug-ins is a dead download (and it doesn't appear to contain Java SE 6.).
    Jerry

Maybe you are looking for