Root element miss

We work in graphics server2.1 ,using operation system is window xp of china
now,run example of net show err "root element miss"
Does anyone know why?

Hi Rodrigo,
Check if your input schedule has numberics with long decimals .
Ideally the BW cube  can only save the number within 13 digits left of the decimal point, and 7 digits right of the decimal point.
If it crosses beyond that then you get the subjected error.Correct the decimals in the input schedule and try sending data again you will not see the error anymore. Hope this helps. Thanks.
Sanjeev

Similar Messages

  • Namespace prefix in Root element missing during variable assignment in SOA Suite 11g

    I need qualified element Namespaces in one of the target variables. All elements being referred to would have the namespace prefixed. This is working for all child elements, but not the for root element. How can i get the root element prefixed with the namespace?
    We are using SOA Suite 11g and the Jdeveloper version we are using is 11.1.1.6.0
    when i use transform operation to populate the target variable the variable gets populated something like this :
    <inputVariable>
    <part  name="payload">
    <Message>
    <msg:Header>
    <head:field1>xxxxxx</head:field1>
    <head:field2>2013-07-09T08:00:55</head:field1>
    </msg:Header>
    </Message>
    But the actual output we need is
    <inputVariable>
    <part  name="payload">
    <msg:Message>
    <msg:Header>
    <head:field1>xxxxxx</head:field1>
    <head:field2>2013-07-09T08:00:55</head:field1>
    </msg:Header>
    </msg:Message>
    We tried the fix suggested in one of the SOA threads but its not working for us and looks like that will work only for SOA SUITE 10g.
    Please provide us any help/suggestions if anyone know the solution.
    Thank you in advance for the help.

    Any one can help us please.......

  • Namespace prefix in Root element missing during variable assignment

    In bpel 10.1.3.4, I need qualified element Namespaces in one of the target variables. I have an xsd that has elementFormDefault = "qualified" set, therefore all elements being referred to would have the namespace prefixed. This is working for all child elements, but not the root element. How can i get the root element prefixed with the namespace?
    If i use transform or copy/append operation to populate in the target variable the variable gets populated something like this :
    <Invoice xmlns:pidx="http://www.api.org/pidXML/v1.0" pidx:transactionPurposeIndicator="Original" pidx:version="1.0" xmlns="http://www.api.org/pidXML/v1.0">
    <pidx:InvoiceProperties>
    <pidx:InvoiceNumber>test123</pidx:InvoiceNumber>
    </pidx:InvoiceProperties>
    </Invoice>
    Whereas i need :
    <*pidx:*Invoice xmlns:pidx="http://www.api.org/pidXML/v1.0" pidx:transactionPurposeIndicator="Original" pidx:version="1.0" xmlns="http://www.api.org/pidXML/v1.0">
    <pidx:InvoiceProperties>
    <pidx:InvoiceNumber>test123</pidx:InvoiceNumber>
    </pidx:InvoiceProperties>
    </*pidx:*Invoice>
    Is there some way to accomplish this?
    Regards,
    Sandeep

    Hi Sandeep,
    We have exactly the same issue, but, when we implemented the solution, we are getting the following error, when we tried to compile the code, we are using 11.1.1.4.0 version of SOA 11g, appreciate if there is any way you can help us on this:
    Jul 12, 2011 2:40:28 PM com.collaxa.cube.CubeLogger info
    INFO: validating "BPELProcess1.bpel" ...
    oracle.jrf.UnknownPlatformException: JRF is unable to determine the current application server platform.
         at oracle.jrf.ServerPlatformSupportFactory.getInstance(ServerPlatformSupportFactory.java:79)
         at oracle.integration.platform.blocks.WLSPlatformConfigurationProvider.<clinit>(WLSPlatformConfigurationProvider.java:44)
         at oracle.integration.platform.blocks.FabricConfigManager.<clinit>(FabricConfigManager.java:154)
         at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXpathFunctions(FabricXPathFunctionResolver.java:282)
         at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXPathConfigFile(FabricXPathFunctionResolver.java:156)
         at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.init(FabricXPathFunctionResolver.java:49)
         at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.loadFabricXpathFunctions(BPELXPathFunctionNameResolver.java:57)
         at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<init>(BPELXPathFunctionNameResolver.java:48)
         at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<clinit>(BPELXPathFunctionNameResolver.java:44)
         at com.collaxa.cube.lang.compiler.bpel.XPathExprValidatorVisitor.<init>(XPathExprValidatorVisitor.java:122)
         at com.collaxa.cube.lang.compiler.bpel.AssignValidator.<init>(AssignValidator.java:89)
         at com.collaxa.cube.lang.compiler.bpel.BpelParser.<init>(BpelParser.java:452)
         at com.collaxa.cube.lang.compiler.bpel.BPELValidator.validate(BPELValidator.java:60)
         at com.collaxa.cube.lang.compiler.BPEL1Processor.validate(BPEL1Processor.java:329)
         at com.collaxa.cube.lang.compiler.BPEL1Processor.process(BPEL1Processor.java:153)
         at com.collaxa.cube.lang.compiler.CubeParserHelper.compile(CubeParserHelper.java:47)
         at oracle.fabric.bpel.bpelc.BPELComponentValidator.validate(BPELComponentValidator.java:40)
         at oracle.soa.scac.ValidateComposite.validateComponentTypeServicesReferences(ValidateComposite.java:1117)
         at oracle.soa.scac.ValidateComposite.doValidation(ValidateComposite.java:500)
         at oracle.soa.scac.ValidateComposite.run(ValidateComposite.java:150)
         at oracle.soa.scac.ValidateComposite.main(ValidateComposite.java:135)
    Jul 12, 2011 2:40:29 PM CubeProcessGenerator compile
    WARNING: classpath is: C:\oracle\Middleware\jdeveloper\jdev\extensions\oracle.sca.modeler.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\oracle\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.mediator_11.1.1\mediator_client.jar;C:\oracle\Middleware\oracle_common\modules\oracle.mds_11.1.1\mdsrt.jar;C:\oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xml.jar;C:\oracle\Middleware\jdeveloper\jdev\extensions;;C:\JDeveloper\mywork\InvoiceTransferApp\InvoiceTransferProj\SCA-INF\classes;C:\JDeveloper\mywork\InvoiceTransferApp\InvoiceTransferProj\SCA-INF\classes;C:\JDeveloper\mywork\InvoiceTransferApp\InvoiceTransferProj\SCA-INF\gen-classes;C:\oracle\Middleware\oracle_common\modules\commonj.sdo_2.1.0.jar;C:\oracle\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;C:\oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel1-1-xbeans.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-common.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel_coherence_config.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-exts.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\thirdparty.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpm-analytics.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-thirdparty.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\wsif-binding.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-validator.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\monitor-rt-xbean.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\oracle.soa.bpmn.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel1.jar;C:\oracle\Middleware\jdeveloper\soa\modules\user-patch.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.thirdparty.jar;C:\oracle\Middleware\jdeveloper\uddi\lib\oracle.soa.uddi.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\bpm-infra.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\testfwk-xbeans.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-ext.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-scheduler.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\xmlunit-1.1.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-tools.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-xpath-exts.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle-soa-client-api.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.wls.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-client.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-was.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-wls.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle.soa.fabric.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.ext_11.1.1\classes
    Regards,
    Sireesh

  • Namespace Prefix in the Root Element of the variable

    Hi Gurus,
    We need to call a webservice which requires a namespace prefix at the root elemnt of the xml payload. But as we know that the default behaviour of BPEL removes the prefix so the invoke activity is failing and so we are stuck.
    I found this thread Namespace prefix in Root element missing during variable assignment but i feel the solution specified in this link works only in SOA 10g environment Please let us know what needs to be done?
    Appreciate a prompt response.
    NOTE: SOA Suite Version- 11.1.1.4
    Regards
    Ayush

    Hi All,
    we are also facing the same issue, Please provide the solution if anyone knows. We are also using the SOA Suite 11g Version.

  • 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();
    }

  • "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

  • 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

  • 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

  • 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

  • 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.

  • So what's the deal with missing context-root element in domain.xml?

    I see that this issue has come up in the past:
    If one hand modifies an application's web.xml file and tries to deploy using JSC, the application's corresponding web-module element's context-root gets nuked in the app server's domain.xml file. The only way I can get the server AND app to successfully run is to manually add context-root back in and manually restart the server (whether from JSC Deployment Server tree node or from the Start Menu (I'm running on XP Pro.) Trying to start either/both from the Run Project button on JSC recreates the problem. Is this a bug? Am I doing something wrong? If bug, will this be addressed soon?

    Here's what I did:
    1. I created a simple HelloWorld JSF project & tested that it compiled, deployed & ran fine using built-in AppServer.
    2. Switched Project View to FileSystem view & opened src/web/WEB-INF/web.xml for editing
    3. Inserted security-constraint
        <!-- Security -->
        <security-constraint>
              <display-name>SecurityConstraint</display-name>
              <web-resource-collection>
                 <web-resource-name>WRCollection</web-resource-name>
                 <url-pattern>/*</url-pattern>
              </web-resource-collection>
              <auth-constraint>
                 <role-name>admin</role-name>
              </auth-constraint>
              <user-data-constraint>
                 <transport-guarantee>NONE</transport-guarantee>
              </user-data-constraint>
        </security-constraint>  4. Tried to deploy & get deplyment failure messages.
    5. Looking in to the %APPSERVERROOT%/domains/creator/config/domain.xml file shows that the HelloWorld webmodule line looks as follows:
    <web-module enabled="true" location="c:/Documents and Settings/Jake Ochs/My Documents/Creator/Projects/HelloWorld/build" name="_helloworld" object-type="user"/>(notice how "context-root" is missing & now needs to be added manually to getthe app to run again.

  • 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.

  • ECC 6.04 : missing 'swap root element' option

    Hi Experts,
    I've developped a WDA application with a Flex component using Adobe Flash Islands on our HR system (ECC 6.04 - NW 7.01). Everything works just fine on this system but now I'd like to copy this application to another system. The new system is also an ECC 6.04 - NW 7.01 system but I can't find the required 'swap root element' option to use Adobe Flash Islands. The Flash Islands libraries are in the MIME repository.
    Do we have to activate something to use the new WDA functionalities?
    Regards,
    Pierre

    Hi,
    My view was empty but the logon language wasn't english. Thanks!
    Regards,
    Pierre

  • Flah Islands:  missing SWAP ROOT ELEMENT

    Hi All,
    I have tired to recreate the tuotrial (pls see http://blip.tv/file/1417778) .
    When I have rightclicked in the views ROOTELEMENTSCONTAINER in order to create a
    SWAP ROOT ELEMENT i was suprised since this option did not exist in my system.
    What can be the resason for it ? Maybe the system release ?
    SAP_BASIS  700
    Component version SAP ECC 6.0
    Regards
    ertas

    Hi Mr. Jung
    I am having a severe problem with my calculator
    I have created a search help (freely programmed).
    I have used this search help in another component. This search help is used at an input
    field. It has the data type i (integer). But if I calculate with zeros and decimals I dont see
    the complete result. I know this is because of the data type. But i also tried it with f .
    It was not possible. in the search help i am using type numeric
    Which data type can I choose.
    method ONACTIONBUTTONPRESS .
      DATA lo_nd_calculator TYPE REF TO if_wd_context_node.
      DATA lo_el_calculator TYPE REF TO if_wd_context_element.
      data lr_value type ref to data.
      data l_string type c LENGTH 60.
      data: val type string.
      data l_binding_string type string.
      lo_nd_calculator = wd_context->get_child_node( name = wd_this->wdctx_calculator ).
      lo_el_calculator = lo_nd_calculator->get_element( ).
      lr_value = lo_el_calculator->get_attribute_ref( WD_COMP_CONTROLLER->value_help_listener->f4_attribute_info-name ).
      FIELD-SYMBOLS <wa_numeric> type numeric.
      ASSIGN lr_value->* to <wa_numeric>.
      val = wdevent->GET_string( 'ID' ).
      CASE val.
        WHEN 'BTN_1'.
          IF WD_COMP_CONTROLLER->COMP EQ 'X'.
            CLEAR: WD_COMP_CONTROLLER->erg, WD_COMP_CONTROLLER->merker, <wa_numeric>, l_string, WD_COMP_CONTROLLER->COMP.
          ENDIF.
          move <wa_numeric> to l_string.
          CONCATENATE l_string `1` into l_string. CONDENSE l_string NO-GAPS.
          <wa_numeric> = l_string.
    endmethod.

Maybe you are looking for