Error in page rendering.

Topics: ASP.NET 2.0
Sep 2, 2014 at 5:13 PM
Has any one seen this before? im hoping its a data issue?

Ooops! An unexpected error has occurred.

This one's down to me! Please accept my apologies for this - I'll see to it that the developer responsible for this happening is given 20 lashes (but only after he or she has fixed this problem).
Error Details:

Url : http://www.mysitehere.com/default.aspx

Raw Url : /

Message : Exception of type 'System.Web.HttpUnhandledException' was thrown.

Source : System.Web

StackTrace : at System.Web.UI.Page.HandleError(Exception e)

at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

at System.Web.UI.Page.ProcessRequest()

at System.Web.UI.Page.ProcessRequest(HttpContext context)

at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

TargetSite : Boolean HandleError(System.Exception)

Message : There is an unclosed literal string. Line 30196, position 105.

Source : System.Xml

StackTrace : at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)

at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)

at System.Xml.XmlTextReaderImpl.ParseAttributes()

at System.Xml.XmlTextReaderImpl.ParseElement()

at System.Xml.XmlTextReaderImpl.ParseElementContent()

at System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r)

at System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r, LoadOptions o)

at System.Xml.Linq.XDocument.Load(XmlReader reader, LoadOptions options)

at System.Xml.Linq.XDocument.Load(String uri, LoadOptions options)

at SexySelect.Net.PostViewBase.ViewCount(Guid PostID, Boolean Unique)

at SexySelect.Net.PostView.Post_Serving(Object sender, ServingEventArgs e)

at System.EventHandler`1.Invoke(Object sender, TEventArgs e)

at BlogEngine.Core.Post.OnServing(Post post, ServingEventArgs arg)

at BlogEngine.Core.Web.Controls.PostViewBase.get_Body()

at BlogEngine.Core.Web.Controls.PostViewBase.OnLoad(EventArgs e)

at System.Web.UI.Control.LoadRecursive()

at System.Web.UI.Control.LoadRecursive()

at System.Web.UI.Control.LoadRecursive()

at System.Web.UI.Control.LoadRecursive()

at System.Web.UI.Control.LoadRecursive()

at System.Web.UI.Control.LoadRecursive()

at System.Web.UI.Control.LoadRecursive()

at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

TargetSite : Void Throw(System.String, System.String)
Coordinator
Sep 2, 2014 at 5:29 PM
Marked as answer by Randalthor on 9/2/2014 at 12:01 PM
Sep 2, 2014 at 7:29 PM
Hi rtur,
Many thanks for your reply.
I followed your advice and turned off custom errors, I also set debug to true in the web.config.
This resulted in me being given more detailed error information, on analyzing this I was able to deduce that an extension called postcount was at fault.
Deleting this extension from the extensions folder and removing the corresponding web.config setting, my site was working again.
Many thanks for your tips.
Regards...