Home > PowerShell, SharePoint 2010 > Fixing SharePoint 2010: Access To This Website Has Been Blocked

Fixing SharePoint 2010: Access To This Website Has Been Blocked

I ran into an issue recently that prevented me from activating a Web Application Feature to a specific web application in my enviornment. When trying to activate the feature I was getting this error:

“Access to this Website has been blocked. Please contact the administrator to resolve the problem.”

Intially thinking it might be a permissions issue I switched users to the Farm Account, but was presented with the same error message when trying to activate.

Usually when this happens you have to make sure there are no locks set on your Site Collections. You can check if there are any locks set by browing to:

http://CENTRAL ADMINISTRATION/_admin/sitequota.aspx

When I checked the Site Collection Quotas and Locks I did not notice my Site Collection as having any locks, so I was a little confused on why I was recieving this error.

What I failed to remember was, even though the main Site Collection did not have a lock, there could possibly be other site Collection within the same Web Application that might have a lock. In my enviornment I have over 20+ databases with over 50 Site Collections.

The Web Application feature I was trying to to activate was trying to iterate through all my Site Collections associated with the Web Application, and unfortunately there was a Site Collection baried within my Web Application that had locks set. Once I found which Site Collection had the lock, I disabled that lock, and then I was able to activate the feature.

If you ever run into this issue, make sure you check ALL site collections within your Web Application and make sure there are no locks.

I will blog about how to automatically check which Site Collections have locks via PowerShell so you don’t have to manually search each Site Collection through Central Administration, especially if you have many Site Collections.

  1. April 22, 2014 at 7:29 pm

    thanks – have old environment with an issue and this solved it.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: