locked
"Web Part Error: This page has encountered a critical error. Contact your system administrator if this problem persists." RRS feed

  • Question

  • Hello,

    I've been running wss 3.0 sp3 on a windows server 2003 R2 std w/sp2 server.  It's been running for a couple of months now and my intentions were to harden the server.  So I decided to move the virtual directories from the C:\ to the D:\ and remove the "everyone" security group from both C:\ and D:\.  After making these changes, the wss site would not render.  So i change the virtual directory path in IIS back to C:\ where it was prior.  The site renders but none of the web parts display any content.  All I get is the message:  "Web Part Error: This page has encountered a critical error. Contact your system administrator if this problem persists."  I have three sites under this wss installation and they all do the same thing.

    I am a complete loss and don't know where to start.  Anyone have any suggestions?

    Thanks,
    hrodz
    Wednesday, October 28, 2009 11:37 AM

Answers

All replies

  • Are you sure about this

    > I've been running wss 3.0 sp3

    There isn't a WSS 3.0 SP3.

    FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com
    Complete Book Lists (incl. foreign language) on each site.
    Wednesday, October 28, 2009 12:01 PM
  • Your right.  I meant to say SP2.  I was able to change the web.config file to show more details.  This is what I get now when i browse to the wss site:

    Web Part Error: This page has encountered a critical error. Contact your system administrator if this problem persists.

    [WebPartPageUserException: This page has encountered a critical error. Contact your system administrator if this problem persists.]
      at Microsoft.SharePoint.ApplicationRuntime.SafeControls.RethrowExceptionIfNeeded()
      at Microsoft.SharePoint.ApplicationRuntime.SafeControls.GetTypeFromGuid(Guid guid)
      at Microsoft.SharePoint.WebPartPages.SPWebPartManager.CreateWebPartsFromRowSetData(Boolean onlyInitializeClosedWebParts)

    Also I looked at the LOGS folder of WSS I found this information:

    10/28/2009 07:53:33.20  w3wp.exe (0x0F98)                        0x0F78 Windows SharePoint Services    General                        8e26 Medium   Failed to open the language resource keyfile compproc. 
    10/28/2009 07:53:33.20  w3wp.exe (0x0F98)                        0x0F78 Windows SharePoint Services    General                        8e25 Medium   Failed to look up string with key "XomlUrl", keyfile core. 
    10/28/2009 07:53:33.20  w3wp.exe (0x0F98)                        0x0F78 Windows SharePoint Services    General                        8l3c Medium   Localized resource for token 'XomlUrl' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\Fields\fieldswss.xml". 
    10/28/2009 07:53:33.20  w3wp.exe (0x0F98)                        0x0F78 Windows SharePoint Services    General                        8e25 Medium   Failed to look up string with key "RulesUrl", keyfile core. 
    10/28/2009 07:53:33.20  w3wp.exe (0x0F98)                        0x0F78 Windows SharePoint Services    General                        8l3c Medium   Localized resource for token 'RulesUrl' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\Fields\fieldswss.xml". 
    10/28/2009 07:53:33.54  w3wp.exe (0x0F98)                        0x0F78 Windows SharePoint Services    Runtime                        6610 Critical Safe mode did not start successfully. This page has encountered a critical error. Contact your system administrator if this problem persists. 
    10/28/2009 07:53:33.90  w3wp.exe (0x0F98)                        0x0F78 Windows SharePoint Services    General                        8sl3 High     DelegateControl: Exception thrown while building custom control 'Microsoft.SharePoint.SPControlElement': Microsoft.SharePoint.WebPartPages.WebPartPageUserException: This page has encountered a critical error. Contact your system administrator if this problem persists.     at Microsoft.SharePoint.ApplicationRuntime.SafeControls.RethrowExceptionIfNeeded()     at Microsoft.SharePoint.ApplicationRuntime.SafeControls.IsSafeControl(String virtualPath)     at Microsoft.SharePoint.SPControlElement.ValidControlAttributes(String sControlAssembly, String sControlClass, String sControlSrc)     at Microsoft.SharePoint.SPControlElement.BuildCustomControl(TemplateControl tctlPage, String sControlAssembly, String sControlClass, String sControlSrc, XmlNode xnElementDefinition, SPFeatureDefinition featdefEl... 
    10/28/2009 07:53:33.90* w3wp.exe (0x0F98)                        0x0F78 Windows SharePoint Services    General                        8sl3 High     ...ement, String sElementId)     at Microsoft.SharePoint.SPControlElement.BuildCustomControl(TemplateControl tctlPage)     at Microsoft.SharePoint.WebControls.DelegateControl.BuildCustomControlResilient(SPControlElement ctlelemDefinition) 
    10/28/2009 07:53:33.95  w3wp.exe (0x0F98)                        0x0F78 Windows SharePoint Services    Web Parts                      7935 Information https://wss/default.aspx - An unexpected error has been encountered in this Web Part.  Error: This page has encountered a critical error. Contact your system administrator if this problem persists., Source: [WebPartPageUserException: This page has encountered a critical error. Contact your system administrator if this problem persists.]<br>&nbsp;   at Microsoft.SharePoint.ApplicationRuntime.SafeControls.RethrowExceptionIfNeeded() <br>&nbsp;   at Microsoft.SharePoint.ApplicationRuntime.SafeControls.GetTypeFromGuid(Guid guid) <br>&nbsp;   at Microsoft.SharePoint.WebPartPages.SPWebPartManager.CreateWebPartsFromRowSetData(Boolean onlyInitializeClosedWebParts) 
    10/28/2009 07:53:33.98  w3wp.exe (0x0F98)                        0x0F78 Windows SharePoint Services    Web Parts                      7935 Information https://wss/default.aspx - An unexpected error has been encountered in this Web Part.  Error: This page has encountered a critical error. Contact your system administrator if this problem persists., Source: [WebPartPageUserException: This page has encountered a critical error. Contact your system administrator if this problem persists.]<br>&nbsp;   at Microsoft.SharePoint.ApplicationRuntime.SafeControls.RethrowExceptionIfNeeded() <br>&nbsp;   at Microsoft.SharePoint.ApplicationRuntime.SafeControls.GetTypeFromGuid(Guid guid) <br>&nbsp;   at Microsoft.SharePoint.WebPartPages.SPWebPartManager.CreateWebPartsFromRowSetData(Boolean onlyInitializeClosedWebParts) 
    10/28/2009 07:53:34.00  w3wp.exe (0x0F98)                        0x0F78 Windows SharePoint Services    Web Parts                      7935 Information https://wss/default.aspx - An unexpected error has been encountered in this Web Part.  Error: This page has encountered a critical error. Contact your system administrator if this problem persists., Source: [WebPartPageUserException: This page has encountered a critical error. Contact your system administrator if this problem persists.]<br>&nbsp;   at Microsoft.SharePoint.ApplicationRuntime.SafeControls.RethrowExceptionIfNeeded() <br>&nbsp;   at Microsoft.SharePoint.ApplicationRuntime.SafeControls.GetTypeFromGuid(Guid guid) <br>&nbsp;   at Microsoft.SharePoint.WebPartPages.SPWebPartManager.CreateWebPartsFromRowSetData(Boolean onlyInitializeClosedWebParts) 
    10/28/2009 07:53:34.00  w3wp.exe (0x0F98)                        0x0F78 Windows SharePoint Services    Web Parts                      7935 Information https://wss/default.aspx - An unexpected error has been encountered in this Web Part.  Error: This page has encountered a critical error. Contact your system administrator if this problem persists., Source: [WebPartPageUserException: This page has encountered a critical error. Contact your system administrator if this problem persists.]<br>&nbsp;   at Microsoft.SharePoint.ApplicationRuntime.SafeControls.RethrowExceptionIfNeeded() <br>&nbsp;   at Microsoft.SharePoint.ApplicationRuntime.SafeControls.GetTypeFromGuid(Guid guid) <br>&nbsp;   at Microsoft.SharePoint.WebPartPages.SPWebPartManager.CreateWebPartsFromRowSetData(Boolean onlyInitializeClosedWebParts) 



    Any thoughts?
    Thank you in Advance.
    • Proposed as answer by kartheekyar Wednesday, November 3, 2010 12:23 PM
    Wednesday, October 28, 2009 2:37 PM
  • Hi hrodz

    In order to move virtual directory from one location to another, you need to create a new web application which is stored and has the desired virtual directory location.
    Then, you should migrate the content database of the source web application to the new with all the contents being correctly retained.

    For step by step instructions about moving virtual directory, please refer to Nicholas Bisciotti’s blog:
    http://njbblog.blogspot.com/2008/01/sharepoint-v3-move-web-applications.html

    By the way, a reference for migrating content database will help you to walk through.
    http://technet.microsoft.com/en-us/library/cc263299.aspx

    Best Regards!

    • Marked as answer by Lily Wu Wednesday, November 4, 2009 9:44 AM
    Friday, October 30, 2009 5:28 AM
  • Hi hrodz,

      I had the same issue as you.

      My problem came about because I was tampering with the web.conf.  Unfortunately for me, I was running SP and OWA on the same server.  I should have known that these two MSFT products wouldn't co-exist peacefully.

      Anyway, after getting my OMA/OWA to work, I broke SP. 

      The fix: I undid all the changes on my web.config file and the problem was resolved.  Simply copy over with an archived version if you have one.  Otherwise, find another installation of SP running the same version/service pack and take their web.config.

      That worked for me.  GL.

    goran.
    Wednesday, March 3, 2010 5:20 PM