I was getting “Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator” error randomly when I clicked on New item of customized SharePoint designer page. I have migrated this site/page from 2007 to 2010 version. After digging more into logs I have found out below detailed error message from correlation token id.
Detailed error messages:
Error while executing web part: System.StackOverflowException: Operation caused a stack overflow.
at Microsoft.Xslt.NativeMethod.CheckForSufficientStack()
at <xsl:template name="dvt_1.rowedit">(XmlQueryRuntime , XPathNavigator , String )
at <xsl:template name="dvt_1.body">(XmlQueryRuntime , XPathNavigator , Double , IList`1 )
at <xsl:template name="dvt_1">(XmlQueryRuntime , XPathNavigator , Double )
at Root(XmlQueryRuntime )
at System.Xml.Xsl.XmlILCommand.Execute(Object defaultDocument, XmlResolver dataSources, XsltArgumentList argumentList, XmlWriter writer, Boolean closeWriter)
at System.Xml.Xsl.XmlILCommand.Execute(IXPathNavigable contextDocument, XmlResolver dataSources, XsltArgumentList argumentList, XmlWriter results)
at System.Xml.Xsl.XslCompiledTransform.Transform(IXPathNavigable input, XsltArgumentList arguments, XmlWriter results)
at Microsoft.SharePoint.WebPartPages.DataFormWebPart.ExecuteTransform(XslCompiledTransform xslCompiledTransform, XsltArgumentList xmlArguments, Boolean bDeferExecuteTransform)
at Microsoft.SharePoint.WebPartPages.DataFormWebPart.PrepareAndPerformTransform(Boolean bDeferExecuteTransform)
As per some links what I have found out that when we created page in designer and added some heavy XSLT in a page, in this particular case if page is taking more than second to open and load all the controls then it will failed and displayed above error message in browser. It is known issue and Microsoft also release hotfix for this issue: http://support.microsoft.com/kb/2639184
Here are some links which talks about same issue and how to resolve this issue.
No comments:
Post a Comment