Server error: This document already has a DocumentElement node.
I'm getting this error related to the creation of cache objects when a page is requested by a user, does this ring any bells? I'm not sure where to look for a solution (there are no other discussions with a solution, only a few other users with the same issue...)
Here are some error details:
Server Error in '/' Application. ________________________________________ This document already has a 'DocumentElement' node. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.InvalidOperationException: This document already has a 'DocumentElement' node.
Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
The umbraco.cms.businesslogic.web.Access.AccessXml property getter loads a static copy of access.xml in memory, if it has not already been loaded. There is a race condition here, which implies that an exception may be thrown when the site starts.
Server error: This document already has a DocumentElement node.
I'm getting this error related to the creation of cache objects when a page is requested by a user, does this ring any bells? I'm not sure where to look for a solution (there are no other discussions with a solution, only a few other users with the same issue...)
Here are some error details:
The umbraco.cms.businesslogic.web.Access.AccessXml property getter loads a static copy of access.xml in memory, if it has not already been loaded. There is a race condition here, which implies that an exception may be thrown when the site starts.
Will try to report the bug + submit a patch.
Reported (with suggested fix) here: http://umbraco.codeplex.com/workitem/29412
Thanks stephen.
I can confirm that this bug still exits in 4.5.2
Looks like it's been fixed but not assigned to a release yet. Hopefully it will make 4.6.2
http://umbraco.codeplex.com/workitem/29412
Was this fixed ?
is working on a reply...