none
Error while executing web part: System.InvalidProgramException: Common Language Runtime detected an invalid program. RRS feed

  • Question

  • hello,

    we have 3 server sharepoint 2010 farm as a live system and a 1 server for development and test system. I've got a problem with one of our portals that gives correlation ID (in 2 or 3 times a week) on all my dataview web parts (total 8 Dataview WP) until i make IIS reset for that portal. (but same portal works like magic on test system over 3 weeks now). there is no custom code in the page other than the customized masterpage and css. and just reseting the IIS solves the problem for a couple of days but i need to fix that permanantly. if anyone can help me about that i will be happy. thank you all in advance.

    here is the log for the correlation ID;

    11/08/2011 09:40:11.72  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Logging Correlation Data       xmnv Medium   Name=Request (GET:http://www.efesithelpdesk.com:80/defaulttr.aspx) 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:11.79  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (GetFileAndMetaInfo). Execution Time=63,946744628158 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:11.79  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (GetWebPartPageContent). Execution Time=64,2515319684485 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:11.79  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Logging Correlation Data       xmnv Medium   Site=/ 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:11.79  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (PostResolveRequestCacheHandler). Execution Time=65.3603321092485 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.22  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (EnsureListItemsData). Execution Time=361.680395134018 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.25  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     Error while executing web part: System.InvalidProgramException: Common Language Runtime detected an invalid program.     at Execute(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.WebPar... 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.25* w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     ...tPages.DataFormWebPart.PrepareAndPerformTransform(Boolean bDeferExecuteTransform) 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.25  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (DataBinding DataFormWebPart (HelpDesk)). Execution Time=391.723110060077 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.25  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (Activate web part connections). Execution Time=416.389513192319 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.28  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     Error while executing web part: System.InvalidProgramException: Common Language Runtime detected an invalid program.     at Execute(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.WebPar... 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.28* w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     ...tPages.DataFormWebPart.PrepareAndPerformTransform(Boolean bDeferExecuteTransform) 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.30  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (EnsureListItemsData). Execution Time=18.8157992147047 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.34  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     Error while executing web part: System.InvalidProgramException: Common Language Runtime detected an invalid program.     at Execute(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.WebPar... 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.34* w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     ...tPages.DataFormWebPart.PrepareAndPerformTransform(Boolean bDeferExecuteTransform) 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.34  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (DataBinding DataFormWebPart (Related Items in Approves)). Execution Time=56.5768833748423 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.36  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (EnsureListItemsData). Execution Time=16.99475771362 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.41  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     Error while executing web part: System.InvalidProgramException: Common Language Runtime detected an invalid program.     at Execute(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.WebPar... 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.41* w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     ...tPages.DataFormWebPart.PrepareAndPerformTransform(Boolean bDeferExecuteTransform) 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.41  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (DataBinding DataFormWebPart (Related Items in Tasks)). Execution Time=59.0992011554541 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.43  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (EnsureListItemsData). Execution Time=20.8265994700444 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.44  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     Error while executing web part: System.InvalidProgramException: Common Language Runtime detected an invalid program.     at Execute(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.WebPar... 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.44* w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     ...tPages.DataFormWebPart.PrepareAndPerformTransform(Boolean bDeferExecuteTransform) 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.46  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (EnsureListItemsData). Execution Time=18.1539832576487 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.47  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     Error while executing web part: System.InvalidProgramException: Common Language Runtime detected an invalid program.     at Execute(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.WebPar... 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.47* w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     ...tPages.DataFormWebPart.PrepareAndPerformTransform(Boolean bDeferExecuteTransform) 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.49  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (EnsureListItemsData). Execution Time=13.4458429772499 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.49  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     Error while executing web part: System.InvalidProgramException: Common Language Runtime detected an invalid program.     at Execute(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.WebPar... 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.49* w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     ...tPages.DataFormWebPart.PrepareAndPerformTransform(Boolean bDeferExecuteTransform) 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.52  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (EnsureListItemsData). Execution Time=23.1282886512113 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.53  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     Error while executing web part: System.InvalidProgramException: Common Language Runtime detected an invalid program.     at Execute(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.WebPar... 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.53* w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Web Parts                      89a1 High     ...tPages.DataFormWebPart.PrepareAndPerformTransform(Boolean bDeferExecuteTransform) 841eadfa-2a71-4cd3-85a4-7b1e3d75355f
    11/08/2011 09:40:12.57  w3wp.exe (0x1AF4)                        0x0BB4 SharePoint Foundation          Monitoring                     b4ly Medium   Leaving Monitored Scope (Request (GET:http://www.efesithelpdesk.com:80/defaulttr.aspx)). Execution Time=845.499567682485 841eadfa-2a71-4cd3-85a4-7b1e3d75355f

    Thursday, November 10, 2011 8:02 AM

All replies

  • Hi,

     

    From your error message, we have similar cases which was resolved by apply this hotfix.

     

    So firstly, please check if you have install SP1 and June CU, if not, install them, then see what’s going on.

     

    And before you proceed with SP1+June’11 CU, please check and confirm the following:

     

    1. Whether publishing Infrastructure is activated or deactivated. If it is deactivated then Activate the publishing Infrastructure feature? You can verify the same while the issue is reproduced.

    2. Whether you use any custom application to copy to SharePoint?

     

    Thanks,

    Rock Wang


    Regards, Rock Wang Microsoft Online Community Support
    Friday, November 11, 2011 7:00 AM
  • thank you for your reply. our publishing infrastructure is active and we are missing SP1, thats why i will try the SP1 next weekend after the farm backup. I will write the results in here again. thanks again.
    Monday, November 14, 2011 7:11 AM
  • Hi,

     

    From your error message, we have similar cases which was resolved by apply this hotfix.

     

    So firstly, please check if you have install SP1 and June CU, if not, install them, then see what’s going on.

     

    And before you proceed with SP1+June’11 CU, please check and confirm the following:

     

    1. Whether publishing Infrastructure is activated or deactivated. If it is deactivated then Activate the publishing Infrastructure feature? You can verify the same while the issue is reproduced.

    2. Whether you use any custom application to copy to SharePoint?

     

    Thanks,

    Rock Wang


    Regards, Rock Wang Microsoft Online Community Support

    nope still giving error after the installation of SP1. now i am testing the hotfix you mentioned and will give feedback in a week of testing again.
    Monday, November 28, 2011 7:01 AM
  • We have same issue with a Blog Post web part (on Posts.aspx page). I was wondering if someone got a solution for this. We have publishing infrastructure activated but no SP1.
    Tuesday, December 13, 2011 6:25 PM
  • any news on that?
    My SharePoint Blog
    Monday, January 16, 2012 8:47 AM
  • nope nothing. but i created a .bat file to restart my IIS site and attached it to server timer jobs to run every night. it is not pretty but works for now.
    Monday, January 16, 2012 9:43 AM
  • so the ms fix does not fix the issue ?

     

     


    My SharePoint Blog
    Monday, January 16, 2012 10:01 AM
  • I am experiencing the same issue and would like to know if anyone finds a solution. this issue crops up once every 2-4 weeks...
    Monday, January 30, 2012 11:43 PM
  • I'm hitting similar issues with xsllistviewwebparts (customised .xsl property)

    During possibly related issues (xsllistviewwp error which is resolved by iisreset), also noticed;

    System.Xml.Xsl.XslTransformException: An item of type 'Root' cannot be constructed within a node of type 'Element'

    Error while executing web part: System.ArgumentException: The signature Type array contains some invalid type (i.e. null, void)

    Interested if anyone makes any progress...

    Wednesday, February 22, 2012 11:44 AM
  • how have you customized the xsl ?

    using SharePoint designer ? or you set an xsl by code ?


    My SharePoint Blog

    Friday, February 24, 2012 8:17 PM
  • We set it by via powershell.   There is nothing wrong with the xsl itself - this is an issue that pops up on a single WFE in the farm (at a time - we have several WFEs that have experiences the issue) and is resolved by an iisreset. 

    As yet we do not know the cause, but it seems somehow memory related i.e. multi-wfes, only one has an issue,  iisreset resolves issue on dodgy wfe.   Waiting for it to happen again so we can capture some more info...

    The xsl itself varies between weparts, but is often an import of main.xsl, along with some additional overides.


    Saturday, February 25, 2012 2:02 AM
  • we have experienced the issue in several different libraries, all customisation has been done through SharePoint Designer 2010 and all work, then stop working randomly, then are fine again after an IIS reset.

    I've got copies of the aspx file before and after the iis reset, and there is an issue with one of the xml strings defining the data source (don't have it in front of me now). the xml is automatically corrected by sharepoint designer (or sharepoint?) as soon as the file is re-saved (without any mods).

    Saturday, February 25, 2012 7:09 AM
  • our farm has only one WFE and we have the same issue.

    We had the issue when the customizations where done directly in SharePoint designer in the xsltviewerwebpart.

    but since I set by code the simplest xsl which use import to load my real xsl, I do not have the issue anymore.

    I do not know if it is related though or just circumstantial.


    My SharePoint Blog

    Saturday, February 25, 2012 10:50 AM
  • Maxine:  Could you please elaborate as to what xml is different?   I can't see how the page could have changed without manual intervention - did someone edit the page with designer after doing the iisreset?

    Gilloux:   We are using simple stylesheets with xsl:includes in some places,  and in others, rather large xsl sheets embedded in the property.  Either way, to me it seems like the same amount of xsl will get compiled - the compiler will just go out and grab the file that is being included - but an interesting observation.

    I hope to have more information in ULS next time the issue occurs, so we can determine exactly what pages (and therefore stylesheets) it occurred on.

    Saturday, February 25, 2012 2:53 PM
  • We are experiencing the same issue with the announcements list on our home page. I would be interested in knowing as well if Maxine is proposing a solution or just describing a characteristic of the issue?

    This is a major annoyance on the production site. I hope there is a fix for it soon.

    Maxine please elaborate on your answer.

    Thanks


    I want to believe

    Friday, March 9, 2012 3:31 PM
  • I am having exactly the same issue. My Front End web server has been updated with SP1 and June CU, but all the Announcements and Links dataview web parts on the site collcetion stopped working -  same logs as quoted above. I opened the pages in SP Designer and the dvwps looked fine. I republished the pages and the web parts worked. But still dont really know what caused it inthe first place. At the moment, I stuck with the thought that every time this occurs, I have to republish every page in the site collection that has an announcement and link dataview!!
    Wednesday, July 18, 2012 12:14 PM
  • Hi ChrisRW

    your not alone, I feel your page.

    BUT there is a quicker solution (if you can take the site offline for a few mins), just do an iisreset and your right to go.

    we had the problem come up once a month or so. Now, I've added an iisreset command to run as scheduled task nightly and the issue hasn't arisen since then.


    Nicholas and Khan (sorry for my delay). if i open the file in SPD, copy the source then save the file, the saved file is refreshed and the xml has been changed. there is some extra information in the WebPartPages:XsltListViewWebPart. for the life of me i cant find the examples, but the post-SPD save had some additional attributes in the tag...

    Wednesday, July 18, 2012 1:12 PM
  • Hi!

    I had same issue on 1 of 3 WFE, when i using https. The difference between these WFE was installed .Net 4 on 2 and 3 WFE. Once installed .Net 4 on 1st WFE issue resolved.


    MCTS

    Wednesday, February 6, 2013 12:11 PM
  • This has been happening every few days for us. All of a sudden any web part with customizations made in SPD break and display the "unable to display webpart..." message. Along with the xml error message in the ULS. I have to do a IISREST from command line to bring everything back up.

    Has anyone found the root cause with a fix that has worked for them? I'm about to schedule an IISRESET every night but it seems like a band-aid solution. We have LCD screens arount the company that display pages with these webparts. Not nice when they break every few days.

    Thursday, February 14, 2013 2:17 PM
  • To summarise where we are so far;

    • All customised xslt webparts on a server display error messages
    • Other servers in the farm are not affected
    • The issue seems to be related to customisations using the xsl property on the webpart
    • (For us) the issue manifests itself when application pools are recycled (over night).  Some times when the recycle happens, one of the servers doesn't come up properly and xsl is broken.  An app pool recycle of the affected content app pool will resolve the issue.  Obviously, an iisreset will also resolve the issue

    Does everyone agree that the issue only happens when app pools recycle?  If it happens during the day, check that it didn't recycle due to errors or something else.

    Saturday, February 16, 2013 1:22 AM
  • Hi Wang,

    The publishing infrastructure feature is activated at the site collection level.

    Do we need to have the "SharePoint Server Publishing" feature also activated at the subsite level, as we still have this issue?

    Thanks & Regards,

    Kusuma

    Tuesday, February 19, 2013 5:27 AM
  • Nicholas Mulder's summary is exactly the issue our server is facing. App pool recycle kicks-off at 2:04am and by 2:06am all our data view web parts are displaying "Unable to display web part ..." I get the same error messages in ULS logs every time it recycles, however it is able to correct itself some of the time. The other times which is every few days, the web parts never come back up.

    Here are a few lines from the log leading up to the recycle and a few after.

    -The application domain /LM/W3SVC/1304874868/ROOT-1-130058022909222844 is unloading and going to be recycled.
    -Shutdown Reason: HostingEnvironment initiated shutdown  HostingEnvironment caused shutdown
    -AppDomain shutdown initiated
    -Flushing connection pool 'Data Source=SPSQL;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Connect Timeout=15'
    -An application domain named /LM/W3SVC/1304874868/ROOT-1-130058174460198926 has just been loaded.
    -Failed to look up string with key "FSAdmin_SiteSettings_UserContextManagement_ToolTip", keyfile Microsoft.Office.Server.Search.
    -Error initializing Safe control - Assembly:Microsoft.Office.SharePoint.ClientExtensions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c TypeName: Microsoft.Office.SharePoint.ClientExtensions.Publishing.TakeListOfflineRibbonControl Error:

    -No webtemp*.xml files found for language 1033 and product version 3.
    -No webtemp*.xml files found for language 1033 and product version 2.
    -Failed to find generic XML file at "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Template\SiteTemplates\STS\xml\stdview.xml"

    -Failed to find generic XML file at "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Template\SiteTemplates\STS\xml\stdview.xml"

    -Error while executing web part: System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.

    -Error while executing web part: System.ArgumentException: An item with the same key has already been added.   
    -Error while executing web part: System.NullReferenceException: Object reference not set to an instance of an object.  
    -AddWithFile:DfwpXslFilesHashCache=Microsoft.SharePoint.WebPartPages.CloneableHashTable
    -Error while executing web part: System.InvalidProgramException: Common Language Runtime detected an invalid program. 


    • Edited by SP3084 Wednesday, February 20, 2013 4:42 PM
    Wednesday, February 20, 2013 4:40 PM
  • Anyone figure out this issue? We are having the problem as well. We added a new dedicated search crawler and ever since we have had this issue. If we remove the server from the topo, the problem goes away. SharePoint is modifying certain ASPX pages and injecting attrivutes onto certain XSLT web parts (i.e. ListUrl = "" or ListDisplayName = ""). There is no consistency to which XSLT views are bombing. Additionally, opening/closing the ASPX pages in Designer solves the problem as Designer strips out unnecessary attributes.

    IISRESETS every night is not a possibility for us, although this would likely temporarily fix the problem until it happens again - not an option.

    We have tried declaring the pages as records so that SharePoint cannot modify them - didn't work.

    We are in the process of seeing if checking out the ASPX pages will temporarily solve the problem.

    We are in the process of seeing if the search crawler happens to be doing this, so we are disabling search from indexing the libraries where the ASPX pages are - I don't anticipate this will fix anything.

    Haven't tried activating/deactivating any features (i.e. Publishing Infrastructure) but I don't think this will fix anything. Again, the views worked fine before adding the new search server.

    3 of the 5 servers in our topo have .NET 4.0 installed (in add/remove programs). 2 of the 5 servers do not have .NET 4.0 installed, including the new server. Someone recommended that in this forum, but I thought .NET 4.0 would cause issues with SharePoint 2010.

    Any input would be much appreciated.

    Thursday, February 28, 2013 6:10 PM
  • Experienced this issue as well. My setup: 1 WFE, 1 APP (Search, CA) running Search Server Express 2010 with SP1. We have around 15-20 web applications in this farm. The problem only happens on one site. I have used host entries to direct the APP server when crawling to crawl itself rather than the WFE. I noticed one unique thing about the site having the problem was that it was the only one being crawled on the WFE (I had forgot to add an entry to hosts for it). I have now changed that and will wait to see if it resolves the problem.
    Friday, March 15, 2013 3:34 PM
  • Hello All,
    Just jumping in here to say we are experiencing the same thing here. It started occassionally and seems to be happening more often. We do recycle our app pools every night but I haven't checked to see if there are any errors after the recycle. Like others, we find that just editing the web part through sharepoint stops the error (no changes, just edit web part, click OK). It seems to only happen to web parts we have modified in Designer to remove the column headings.

    We have 2 WFEs load balanced and I have seen where the error only occurs on 1 of them. I've seen others mention the time out period of XSL transform possibly being related. If anyone has found any other solutions, let us know. Thanks!  :)
    Monday, March 25, 2013 2:59 PM
  • Seems this is effecting more and more environments. Anybody find a solution yet?

    Wednesday, April 10, 2013 12:20 PM
  • With two custom views reporting this issue, we partially resolved it by iisreset and remaining issues were dealt with by editing/saving the page and the web part. Tried even stopping each wfe and trying, no success.

    We experienced similar behavior (cannot display web part) but earlier it was gone just after hitting refresh.

    Wednesday, July 3, 2013 10:31 PM
  • Not really resolved, one user reported still to have the same problem. Since this is per-user now, I wonder if there were any similar experience?
    Monday, July 8, 2013 11:37 AM
  • Has anyone found a resolution that doesn't involve nightly IIS restarts? I've recently started experiencing the same problems Nicholas Mulder summarized. There aren't a lot of other threads discussing this problem, either.
    Friday, April 25, 2014 3:56 PM
  • Hello, got this error recently and applied iisreset solution on SharePoint 2010 SP1. Do you have any info on whether SP2 + latest CU - June 2014 fix the issue or not? Thanks.

    Also, in our case we discovered that Automatic updates were enabled on the FrontEnd OS. It is recommended to disable it and do updates manually with iisreset (server reboot in fact) after the update. Check if the night before the error you did not have any updates coming in.

    Wednesday, July 9, 2014 2:51 PM