locked
Getting "Additions to this Web site have been blocked" error RRS feed

  • Question

  • Hi Everyone

    While updating item in one of our large document library we are facing below mentioned error:

    Additions to this Web site have been blocked.

    Below is details of error. Appreciate to get solution on this. Pl. note this error we are facing on production and not facing on UAT and Development.

    is it related to content database size?

    Error in Project Documents event Receiver.AddChildMetadataToHashTable(), Error Details : Microsoft.SharePoint.SPException:
    Additions to this Web site have been blocked.

    Please contact the administrator to resolve this problem. --->
    System.Runtime.InteropServices.COMException: <nativehr>0x81020066</nativehr><nativestack></nativestack>
    Additions to this Web site have been blocked.

    Please contact the administrator to resolve this problem.
       at Microsoft.SharePoint.Library.SPRequestInternalClass.AddOrUpdateItem(String bstrUrl, String bstrListName, Boolean bAdd, Boolean bSystemUpdate, Boolean bPreserveItemVersion, Boolean bPreserveItemUIVersion, Boolean bUpdateNoVersion, Int32& plID, String& pbstrGuid, Guid pbstrNewDocId, Boolean bHasNewDocId, String bstrVersion, Object& pvarAttachmentNames, Object& pvarAttachmentContents, Object& pvarProperties, Boolean bCheckOut, Boolean bCheckin, Boolean bUnRestrictedUpdateInProgress, Boolean bMigration, Boolean bPublish, String bstrFileName, ISP2DSafeArrayWriter pListDataValidationCallback, ISP2DSafeArrayWriter pRestrictInsertCallback, ISP2DSafeArrayWriter pUniqueFieldCallback)
       at Microsoft.SharePoint.Library.SPRequest.AddOrUpdateItem(String bstrUrl, String bstrListName, Boolean bAdd, Boolean bSystemUpdate, Boolean bPreserveItemVersion, Boolean bPreserveItemUIVersion, Boolean bUpdateNoVersion, Int32& plID, String& pbstrGuid, Guid pbstrNewDocId, Boolean bHasNewDocId, String bstrVersion, Object& pvarAttachmentNames, Object& pvarAttachmentContents, Object& pvarProperties, Boolean bCheckOut, Boolean bCheckin, Boolean bUnRestrictedUpdateInProgress, Boolean bMigration, Boolean bPublish, String bstrFileName, ISP2DSafeArrayWriter pListDataValidationCallback, ISP2DSafeArrayWriter pRestrictInsertCallback, ISP2DSafeArrayWriter pUniqueFieldCallback)
       --- End of inner exception stack trace ---
       at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
       at Microsoft.SharePoint.Library.SPRequest.AddOrUpdateItem(String bstrUrl, String bstrListName, Boolean bAdd, Boolean bSystemUpdate, Boolean bPreserveItemVersion, Boolean bPreserveItemUIVersion, Boolean bUpdateNoVersion, Int32& plID, String& pbstrGuid, Guid pbstrNewDocId, Boolean bHasNewDocId, String bstrVersion, Object& pvarAttachmentNames, Object& pvarAttachmentContents, Object& pvarProperties, Boolean bCheckOut, Boolean bCheckin, Boolean bUnRestrictedUpdateInProgress, Boolean bMigration, Boolean bPublish, String bstrFileName, ISP2DSafeArrayWriter pListDataValidationCallback, ISP2DSafeArrayWriter pRestrictInsertCallback, ISP2DSafeArrayWriter pUniqueFieldCallback)
       at Microsoft.SharePoint.SPListItem.AddOrUpdateItem(Boolean bAdd, Boolean bSystem, Boolean bPreserveItemVersion, Boolean bNoVersion, Boolean bMigration, Boolean bPublish, Boolean bCheckOut, Boolean bCheckin, Guid newGuidOnAdd, Int32& ulID, Object& objAttachmentNames, Object& objAttachmentContents, Boolean suppressAfterEvents, String filename, Boolean bPreserveItemUIVersion)
       at Microsoft.SharePoint.SPListItem.UpdateInternal(Boolean bSystem, Boolean bPreserveItemVersion, Guid newGuidOnAdd, Boolean bMigration, Boolean bPublish, Boolean bNoVersion, Boolean bCheckOut, Boolean bCheckin, Boolean suppressAfterEvents, String filename, Boolean bPreserveItemUIVersion)
       at IOM.DMSPortal.EventReceivers.ProjectDocEvents.ProjectEventAction.UpdateProjectFiles(Hashtable UpdatedValues, SPFileCollection spFolderColl)
       at IOM.DMSPortal.EventReceivers.ProjectDocEvents.ProjectEventAction.UpdateChildItems(SPItemEventProperties properties, Hashtable UpdatedValues, String strContentType)
       at IOM.DMSPortal.EventReceivers.ProjectDocEvents.ProjectEventAction.AddChildMetadataToHashTable(SPItemEventProperties properties, SPContentType spcont, Hashtable hashUpdatedPropTable, String strContentType)

    Thanks

    Best Regards

    Safder

    Friday, November 29, 2013 11:46 AM

Answers

  • Try:

    Set-SPSite http://SiteCollectionUrl -LockState Unlock


    Trevor Seward, MCC

    Follow or contact me at...
      

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Thursday, December 5, 2013 4:51 AM

All replies

  • Run the following powershell command and make sure that your site collection is not locked or in read-only mode. Also verify that your database server drives are not running out of space.

    Get-SPSite <Site-collection-url> | select ReadOnly,Readlocked,WriteLocked,LockIssue | ft –autosize


    Reference: http://blogs.c5insight.com/Home/tabid/40/entryid/289/Check-SharePoint-2010-Site-Collection-Locks-with-PowerShell.aspx


    Amit

    Friday, November 29, 2013 2:09 PM
  • First check site collection is not locked in central admin:

    http://neelb.wordpress.com/2012/01/18/additions-to-this-web-site-have-been-blocked-sp2010/

    If still getting, use STSADM with switch SETSITELOCK and GETSITELOCK.

    http://www.techtalkz.com/microsoft-sharepoint-server/392388-additions-web-site-have-been-blocked.html


    • Proposed as answer by R'tun Wednesday, October 7, 2015 2:43 PM
    Friday, November 29, 2013 3:49 PM
  • You'll want to check your database server as well and make sure the content database is not set to read only (Or that some well meaning DBA hasn't changed security rights).  Generally with SP2010 if the database is read only it will remove the add document links in the UI, but code will not take that into account.  An easy way to verify is to check your prod environemt UI to see if the links are there with the appropriate account logged in.

    ieDaddy
    Blog: http://iedaddy.com
    Twit: @iedaddy

    Friday, November 29, 2013 4:41 PM
  • Hi safder husain ,

    For troubleshooting, please take steps as below:

    1. Take a quick look in Central Administration.If the Content Database has been taken "offline" then it will halt any database editing (typically used for maintenance such as backing up / restoring or major farm config).
    2. Check SQL .This can also happen if the Transaction Logs are full .. or you've run out of disk space.
    3. Check if you have set a Site Collection Quota ... if the site collection exceeds the "quota" size then adding new content will be restricted.Go to Central Administration -> Application Management -> Configure Quotas and Locks. Set the Site Lock Information to "Not Lock" (it had been set to " Read-only (blocks additions, updates, and deletions)”).

    Please inform me freely if you have any questions.

    Thanks


    Eric Tao
    TechNet Community Support

    Monday, December 2, 2013 8:48 AM
  • Hi Eric

    Thanks.we have checked Transaction Logs and it seems normal. also lock status of site is "Not locked". Content database is also not 'readonly".

    actually it user is upload doc and this is happening randomly while we update metadata property of documents costume code.

    we have checked code and it looks nothing wrong there. 

    Best Regards,

    Safder 

        

    Thursday, December 5, 2013 4:38 AM
  • Hi 

    Thanks.we have checked Transaction Logs and it seems normal. also lock status of site is "Not locked". Content database is also not 'readonly".

    actually it user is upload doc and this is happening randomly while we update metadata property of documents costume code.

    we have checked code and it looks nothing wrong there. 

    Best Regards,

    Safder 

    Thursday, December 5, 2013 4:41 AM
  • Hi Eric

    Thanks.we have checked Transaction Logs and it seems normal. also lock status of site is "Not locked". Content database is also not 'readonly".

    actually it user is upload doc and this is happening randomly while we update metadata property of documents costume code.

    we have checked code and it looks nothing wrong there. 

    Best Regards,

    Safder 

    Thursday, December 5, 2013 4:41 AM
  • Hi 

    Thanks.we have checked Transaction Logs and it seems normal. also lock status of site is "Not locked". Content database is also not 'readonly".

    actually it user is upload doc and this is happening randomly while we update metadata property of documents costume code.

    we have checked code and it looks nothing wrong there. 

    Best Regards,

    Safder 


    Thursday, December 5, 2013 4:42 AM
  • Hi Amit

    Thanks.we have checked Transaction Logs and it seems normal. also lock status of site is "Not locked". Content database is also not 'readonly".

    actually it user is upload doc and this is happening randomly while we update metadata property of documents costume code.

    we have checked code and it looks nothing wrong there. 

    Best Regards,

    Safder 

    Thursday, December 5, 2013 4:42 AM
  • Try:

    Set-SPSite http://SiteCollectionUrl -LockState Unlock


    Trevor Seward, MCC

    Follow or contact me at...
      

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Thursday, December 5, 2013 4:51 AM
  • Hi Safder,

    I have also faced the same issue.

    Have you Enabled the Versioning settings on the Document Library.

    if there is file which is published and you are trying to update metadata by using Item.UpdateOverrideVersion() method then this will gives you an same error.

    so instead of using System.UpdateOverrideVersion() method you can try for Item.SystemUpdate() method to update the Published file Metadata()


    PD

    Monday, December 16, 2013 4:15 AM
  • Thank you so much.

    its working now.

    Saturday, August 29, 2015 12:50 PM
  • Pravin - we are getting the same error on our SharePoint 2010 farm. This only happens with my clients who have access. the metadata won't update, yet the error goes away and the document uploads without it's properties. any of my team who uploads does not experience the issue, yet only clients seem to have the problem. could this be the existence of XML code in the document or password protection of the file in excel causing the issue?


    Troy Cantrell

    Monday, August 31, 2015 8:02 PM
  • This fixed it! THANK YOU SO MUCH! 
    Wednesday, October 7, 2015 2:42 PM