SP2010/Wiki Pages: "Sys.WebForms.PageRequestManagerServerErrorException: An unexpected error occured." when editing a page


Over the last few weeks I came across one problem multiple times. When you tried to edit a Wiki Page in SharePoint 2010 you got the error Sys.WebForms.PageRequestManagerServerErrorException: An unexpected error occured. This was quite wired, as the users had "full contol" of the wiki.

So, first we look at the ULS logs at the time when the error occured:

01/18/2011 08:23:58.78                w3wp.exe (0x130C)                                      0x1F04  Web Content Management                        Publishing                          7fz3       Medium              Setting [Display] as the FormContext.FormMode for the current page      d3bba74c-33f8-4659-908a-f37d2bf70a14

01/18/2011 08:23:58.80                w3wp.exe (0x130C)                                      0x1F04  SharePoint Foundation                General                                       8e2s      Medium              Unknown SPRequest error occurred. More information: 0x80070005   d3bba74c-33f8-4659-908a-f37d2bf70a14

01/18/2011 08:23:58.80                w3wp.exe (0x130C)                                      0x1F04  SharePoint Foundation                Runtime                                       test04 Unexpected      System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))    at Microsoft.SharePoint.Library.SPRequest.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt, Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt32 dwListFilterFlags, Boolean bPrefetchMetaData, Boolean bSecurityTrimmed, Boolean bGetSecurityData, Boolean bPrefetchRelatedFields, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount)     at Microsoft.SharePoint.SPListCollection.EnsureListsData(Guid webId, String strListName)     at Microsoft.SharePoint.SPListCollection.Undirty()     at Microsoft.SharePoint.SPBaseCollection.GetEnumerator()     at Microsoft.SharePoint.SPWeb.GetCatalog(SPListTemplateType typeCata...       d3bba74c-33f8-4659-908a-f37d2bf70a14

01/18/2011 08:23:58.80*              w3wp.exe (0x130C)                                      0x1F04  SharePoint Foundation                Runtime                                       test04 Unexpected      ...log)     at Microsoft.SharePoint.Publishing.WebControls.MediaWebPart.get_WebPartAdderId()     at Microsoft.SharePoint.Publishing.WebControls.InsertMediaRibbonButton.RegisterRequiredScripts()     at Microsoft.SharePoint.Publishing.WebControls.InsertMediaRibbonButton.OnPreRender(EventArgs e)     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)               d3bba74c-33f8-4659-908a-f37d2bf70a14

Note the two lines in bold here.

Unknown SPRequest error occurred. More information: 0x80070005   <- This error message tells us that there is some problem with security.

System.UnauthorizedAccessException: Access is denied.  <- That one is more specific, it tells us quite bluntly that we get an access denied somewhere.

So, the first thing is to take a look at the groups. I noticed that the SharePoint Group Style Ressource Readers might be the culprint. This group is an OOTB SharePoint group that comes with the publishing feature. Out of the box, the AD group DOMAIN\Authenticated Users is a member of that group. In that case it wasn't. So I added all authenticated users and all was fine.

NOTE: In some cases it might be required to add the users that have the Wiki Problem to Style Ressource Readers manually. Haven't had the time to go after that tough, just keep it in your mind if you need it.

ANOTHER NOTE: A customer once accidentially deleted the Style Ressource Readers Group. Deleting SharePoint OOTB groups is never a good idea. He recreated the group (just manually added a new group) but it didn't work as expected. If you have to recreate Style Ressource Readers also check the following settings:

The group has to be given read permissions to the Master Page Gallery and the Style Library. This is done under Site Actions > Manage Content and Structure > (Master Page Gallery) Edit Properties > Permissions for the document library > New

 

I hope this short article helped you solve your problem. Cheers SJ

 

 

Comments (9)
  1. Anonymous says:

    Hi Joe,

    I face the same error on one of my wiki subsite wtihin the site collection. I am using NTLM for the authention. I notice that this error only occurs to those users that are on "guest" OU. I've tried the workaround solutions mentioned above but the error does not go away.

    I did try to export the specific site (using stsadm -o export -url -filename -includeusersecurity) and import  the site to a new site collection. The error is gone.

    Can anyone explain why?

    Thanks!  

  2. Anonymous says:

    Hello Srujan,

    Have you found a fix for this issue? We are having the exact same problem.

    Our SharePoint OOTB groups were deleted and we have since recreated them, however I think the permissions are still broken somewhere. All subsite owners are unable to edit their site page, they recieve the above error. The only way I can give them permissions, is to turn off the Wiki Home Page feature which for some reason is getting activated whenever we create a new site.

    Any help is much appreciated.

    Cheers!

  3. Srujan says:

    Found the problem (Workaround). Here is my situation

    User 'Jim' has 'No' Permissions on Top level site of a site collection and Full control on  a subsite,. and

    1. Jim can't edit any wiki pages, Error -" sys.webforms.pagerequestmanagerservererrorexception. An unexpected error occurred"

    2. Jim can't add any webpart to a webpart page except list/ library webparts. (he can't add a CEWP).

    User "John' has Read permissions on Top level site and He can edit the Wiki page in a subsite without any problem. (even with contribute permissions).

    So problem is with the permissions on top level site, which is weird…

  4. Srujan says:

    Hi Jamvan,

    I have fixed the issue by manually assigning permissions (Read permissions to all users) to the following Lists/ libraries

    Style library

    Webpart gallery

    Masterpages & page layouts

  5. Hi all says:

    We have the same problem.

    In our case the User has contribute permissions as member on all levels and additional owner rights for his wiki page and the problem still occurs…

    Any Ideas?

  6. EJL says:

    Incredibly helpful article.  I had been deleting the OOTB SP groups, thinking they weren't needed.  Recreating the site and leaving them in there fixed my issue.

    Thanks again!

  7. spman says:

    this post helped me!. exactly the same problem i had.

    thanks.

  8. laurie says:

    Thank you! Had the same problem and it fixed it immediately.

  9. ryan says:

    Srujan – thank you, thank you, thank you. A lot of strings indicated coding changes and designer stuff that we don’t have access to. Your suggestion about the manual permissions was a lifesaver

Comments are closed.

Skip to main content