Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Rasmus Lund 2 posts 23 karma points
    Nov 13, 2009 @ 10:36
    Rasmus Lund
    1

    Is this a core error? This document already has a 'DocumentElement' node

    We have multiple websites hosted on a Windows 2003 dedicated server, using Umbraco v 3.0.5 (Assembly version: 1.0.3050.25839), SQL Server on sam emachine also - we encounter that the websites a different times stop responding with the following error registret in the event log on the server:

    Event code: 3005
    Event message: An unhandled exception has occurred.
    Event time: 12-11-2009 16:39:43
    Event time (UTC): 12-11-2009 15:39:43
    Event ID: 9eb5cd6869c84f478f2d8bdff74d82cc Event sequence: 7 Event occurrence: 1 Event detail code: 0

    Application information:
        Application domain: /LM/W3SVC/808231372/Root-1-129025139822470000
        Trust level: Full
        Application Virtual Path: /
        Application Path: D:\Umbraco\Websites\rwiumbracoes\
        Machine name: RWIUMBRACO1

    Process information:
        Process ID: 8732
        Process name: w3wp.exe
        Account name: NT AUTHORITY\NETWORK SERVICE

    Exception information:
        Exception type: InvalidOperationException
        Exception message: This document already has a 'DocumentElement' node.

    Thread information:
        Thread ID: 8
        Thread account name: NT AUTHORITY\NETWORK SERVICE
        Is impersonating: False
        Stack trace:    at System.Xml.XmlDocument.IsValidChildType(XmlNodeType
    type)
       at System.Xml.XmlDocument.AppendChildForLoad(XmlNode newChild, XmlDocument doc)
       at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
       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 umbraco.cms.businesslogic.web.Access.get_AccessXml()
       at umbraco.cms.businesslogic.web.Access.getPage(Int32 documentId)
       at umbraco.cms.businesslogic.web.Access.IsProtected(Int32 DocumentId, String Path)
       at umbraco.requestHandler..ctor(XmlDocument _umbracoContent, String url)
       at umbraco.WebForm1.OnInit(EventArgs e)
       at System.Web.UI.Control.InitRecursive(Control namingContainer)
       at System.Web.UI.Page.ProcessRequestMain(Boolean
    includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    It is not as it is today possible for to upgrade to version 4.

    Do any of you have any experience with this?

  • Rasmus Lund 2 posts 23 karma points
    Nov 13, 2009 @ 10:36
    Rasmus Lund
    0

    And one more thing - can see that this subject has been asked in the "old" forum also - but without a answer http://forum.umbraco.org/yaf_postst5181_This-document-already-has-a-DocumentElement-node.aspx

  • Nalle Jacobsson 32 posts 55 karma points
    May 26, 2010 @ 18:02
    Nalle Jacobsson
    0

    I get the same error sometimes, so far I have no idea why. This is with Umbraco 4.0.3.

    /N

  • Rik Helsen 670 posts 873 karma points
    Aug 16, 2010 @ 14:10
    Rik Helsen
    0

    Did you find a solution? I'm having similar issues with Umbraco 4.0.3 on a live site:

     

  • Malte Baden Hansen 61 posts 158 karma points
    Aug 16, 2010 @ 17:29
    Malte Baden Hansen
    0

    I too has come across that error, only saw it once. The next refresh the error was gone.

  • Rik Helsen 670 posts 873 karma points
    Aug 23, 2010 @ 13:41
    Rik Helsen
    0

    Everytime i run into this error it goes away after refreshing, but it comes up frequently though...

    dont like the idea of my visitors seeing this often...

  • Laurence Gillian 600 posts 1219 karma points
    Oct 21, 2010 @ 10:08
    Laurence Gillian
    0

    We are seeing this error, on the latest build of Umbraco.

    On a variety of hardware & software;

    Windows 2008 Enterprise and Windows 2003.

    SQL2008 Enterprise and SQL2005 Express.

    Ideas?

  • Neil Tootell 73 posts 118 karma points
    Oct 27, 2010 @ 15:23
    Neil Tootell
    1

    Hi all,

    I'm getting exactly the same on one of our production sites on build "4.5.2".

    Server 2008 with SQL Express 2005 and IIS 7.

    I can't get it to go away, and it seems the only way of getting rid of it is to restore an earlier working version of the database. Restarting IIS or the site/app pool doesn't work.

    It is quite a large site with a tricky XSLT build for data driving some flash, but once it kicks in, it runs the same error message for all Umbraco driven pages.

    Any progress on this yet?

     

    Thanks

    Neil

  • Laurence Gillian 600 posts 1219 karma points
    Oct 28, 2010 @ 19:36
    Laurence Gillian
    0

    I've seen this on fresh Umbraco builds, with basic doctype structure and only a maximum of 10 nodes.

    I'm going to setup a watch on the IIS logs to see how often this is occurring.

    /Lau

  • RuneO 36 posts 116 karma points
    Nov 01, 2010 @ 16:21
    RuneO
    0

    I am experiencing the same thing on a fresh site running Umbraco 4.5.2. As far as I've noticed it looks like it always happens right after a worker process recycle.

    The setup includes several IIS websites pointing to the same Umbraco database (don't ask). Without having used any time to dig into it, I am thinking it may be a realtime synchronization error because I don't think Umbraco was build for this type of setup.

    Does any of you has the same kind of setup?

    /Rune

  • Rik Helsen 670 posts 873 karma points
    Nov 02, 2010 @ 09:08
    Rik Helsen
    0

    Rune: sounds like any loadbalancing setup, where multiple frontend IIS servers are querying the same db.

  • RuneO 36 posts 116 karma points
    Nov 02, 2010 @ 10:28
    RuneO
    0

    Maybe I wasn't clear enough - it is several IIS websites on the same server that points to the same code directory and therefore the same database.

    This means that all sites share the same /Data and /App_Data directories, which means that the sites share disk cache but not memory cache. That's what I meant when I said I don't think Umbraco normally support this.

    But maybe this type of setup has nothing to do with the error we're discussing here - I was just curious to hear if any of you who gets this error once in a while, use a similar setup than ours?

    The problem at hand is a standard coding problem, and could occur in a realtime environment as described (because of shared disk cache and not shared memory cache). But if I'm the only one with this problem who uses the described setup, I don't wan't to spend any time looking into changing it.

    Hope this answers your question :-)

    /Rune

  • Laurence Gillian 600 posts 1219 karma points
    Nov 04, 2010 @ 13:17
    Laurence Gillian
    0

    I can confirm our IIS setups are not as above. They are just standard IIS setups. Nothing fancy, nothing special. No additional binaries. 

    Is there a related workitem in Codeplex for this issue? At present, this is fairly high on our very small list of worries.

    /Laurie x

  • wolulcmit 357 posts 693 karma points
    Nov 05, 2010 @ 14:15
    wolulcmit
    0

    +1 for this error, just got the same.... on a similar setup to Laurence, fresh build, small amount of nodes (fewer than 20) Umbraco 4.5.2. Refreshing the page makes the error disappear. Did you figure out how often it's happening for you Laurence?

  • Stephen 767 posts 2273 karma points c-trib
    Nov 12, 2010 @ 12:15
Please Sign in or register to post replies

Write your reply to:

Draft