none
Permission Error - Site collection has turned read only

    질문

  • Hi,

    Site administrator account on my publishing template sharepoint site is unable to edit or update site pages.

    The account is site administrator according to the central admin. It was able to edit the site pages/lists etc till day before yesterday. However, from yesterday all it sees is a site with
    1. View All Site Content
    2. View Reports
    3. Manage Content and Structure
    In Site action menu.

    Even when I go into document libraries, I do not see options like "Check out", "Approve" etc and the same is true for all other accounts in the site. Since yesterday they can't access the editing features at all making the site read only.

    On noticing this I tried to create a new user, make it secondary site administrator and make it member of servers local administrators group and tried to add it using stsadm adduser command 

          stsadm -o adduser -url http://servername -userlogin abcdef\admintemp -useremail someone@abcdef.com -role "Full Control" -siteadmin -username "Admin temp"
    
    
    
    
    
    
    
          Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
    
    
    
    
    
    
    
    
    
    
    
    


    So even though the user is site collection administrator, it can't add a user using stsadm account.

    When I try to browse the website using the original site administrator account , the SharePoint logs show folloing listing (Scroll right to see full listing )

    PermissionMask check failed. asking for 0x00000005, have 0x0C031061  
    
    
    
    05/20/2009 16:58:01.72  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x00000015, have 0x0C03 1061 
    
    
    
    05/20/2009 16:58:01.72  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x00000005, have 0x0C03 1061 
    
    
    
    05/20/2009 16:58:01.72  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x00000015, have 0x0C03 1061 
    
    
    
    05/20/2009 16:58:01.72  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x00000004, have 0x0C03 1061 
    
    
    
    05/20/2009 16:58:01.72  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x20000000, have 0x0C03 1061 
    
    
    
    05/20/2009 16:58:01.72  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x30000000, have 0x0C03 1061 
    
    
    
    05/20/2009 16:58:01.72  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         75g4    Verbose     Usage: Rights and Roles: GetWebPartPage: Shared  
    
    
    
    05/20/2009 16:58:01.75  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x00000005, have 0x0C031061  
    
    
    
    05/20/2009 16:58:01.75  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x00000015, have 0x0C031061  
    
    
    
    05/20/2009 16:58:01.75  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x00000005, have 0x0C031061  
    
    
    
    05/20/2009 16:58:01.75  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x00000015, have 0x0C031061  
    
    
    
    05/20/2009 16:58:01.75  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x00000004, have 0x0C031061  
    
    
    
    05/20/2009 16:58:01.75  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x20000000, have 0x0C031061  
    
    
    
    05/20/2009 16:58:01.75  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x30000000, have 0x0C031061  
    
    
    
    05/20/2009 16:58:01.75  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         75g4    Verbose     Usage: Rights and Roles: GetWebPartPage: Shared  
    
    
    
    05/20/2009 16:58:01.79  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x00000005, have 0x0C031061  
    
    
    
    05/20/2009 16:58:01.79  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x00000015, have 0x0C031061  
    
    
    
    05/20/2009 16:58:01.79  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x00000005, have 0x0C031061  
    
    
    
    05/20/2009 16:58:01.79  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x00000015, have 0x0C031061  
    
    
    
    05/20/2009 16:58:01.79  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x00000004, have 0x0C031061  
    
    
    
    05/20/2009 16:58:01.79  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x20000000, have 0x0C031061  
    
    
    
    05/20/2009 16:58:01.79  w3wp.exe (0x1ED0)                           0x1F78  Windows SharePoint Services     General                         8xfr    Verbose     PermissionMask check failed. asking for 0x30000000, have 0x0C031061
    
    
    
    

    Which seems to suggest that the user which is part of "<Site> Owner" group and is site collection administrator when it tries to access the site is having permission masks which corresponds to read only access. 

    There seems to be inconsistency between the "Settings" which give the user accounts enough permissions, and the actual permission mask when user tries to browse the site. 

    Note that this web application has several site collections and only one of the site collection is showing this problem. Rest of the site collections are fine. 

    What could be the reason ? Is there anyway to make the site collection editable again ? 

    Best Regards,
    Shishir 

    2009년 5월 20일 수요일 오후 1:11

답변

  • I found solution for this problem. The issue had been read only lock on the site collection. This prevented even someone with permissions from modifying the site. It happened because one of the server on which a scheduled job was running was hard reset after it had obtained read only lock on the site collection.

    The solution was to query the site collection lock status using
    stsadm -o getsitelock -url http://<site collection url>

    This detected dirty lock and returned it to no lock status. After this site became operational and started showing edit options in site actions.

    • 답변으로 제안됨 Dan Luciano 2009년 9월 18일 금요일 오후 4:56
    • 답변으로 표시됨 Steven AndrewsEditor 2011년 11월 3일 목요일 오후 5:25
    2009년 5월 27일 수요일 오후 12:56
  • For clarity to unlock the site use:

    stsadm -o setsitelock -url 
    http://server_name -lock none

    reference:

    http://technet.microsoft.com/en-us/library/cc287893.aspx

    • 답변으로 제안됨 Dan Luciano 2009년 9월 18일 금요일 오후 4:56
    • 답변으로 표시됨 Steven AndrewsEditor 2011년 11월 3일 목요일 오후 5:24
    2009년 9월 18일 금요일 오후 4:14

모든 응답

  • Have you tried stsadm -o siteowner ?
    Alpesh Nakar Blog: http://alpesh.nakars.com/blog | Twitter: @alpesh SharePoint Resources: http://www.justsharepoint.com | Twitter @justsharepoint
    2009년 5월 26일 화요일 오전 5:33
  • You should also check the rights on the master pages. Make sure you have at least read access rights to them. If you can't read them, then you can have permission errors.

    Another area to look is to see if your site's permissions hasn't been adjusted:
     Site Settings > Permissions > Permission Levels

    Check and make sure that all the SITE PERMISSIONS are enabled with FULL CONTROL account.

    Tell us how it goes.

    That's SharePoint for you...
    2009년 5월 26일 화요일 오후 3:55
  • I found solution for this problem. The issue had been read only lock on the site collection. This prevented even someone with permissions from modifying the site. It happened because one of the server on which a scheduled job was running was hard reset after it had obtained read only lock on the site collection.

    The solution was to query the site collection lock status using
    stsadm -o getsitelock -url http://<site collection url>

    This detected dirty lock and returned it to no lock status. After this site became operational and started showing edit options in site actions.

    • 답변으로 제안됨 Dan Luciano 2009년 9월 18일 금요일 오후 4:56
    • 답변으로 표시됨 Steven AndrewsEditor 2011년 11월 3일 목요일 오후 5:25
    2009년 5월 27일 수요일 오후 12:56
  • For clarity to unlock the site use:

    stsadm -o setsitelock -url 
    http://server_name -lock none

    reference:

    http://technet.microsoft.com/en-us/library/cc287893.aspx

    • 답변으로 제안됨 Dan Luciano 2009년 9월 18일 금요일 오후 4:56
    • 답변으로 표시됨 Steven AndrewsEditor 2011년 11월 3일 목요일 오후 5:24
    2009년 9월 18일 금요일 오후 4:14
  • You just helped me a ton.  I can't thank you enough.
    Willner001
    2011년 11월 2일 수요일 오후 1:43
  • Thanks for the post Nrog, it helped me fix the issue as well. 
    2012년 6월 26일 화요일 오전 8:58