Solving access denied login for site collection administrators

Sometimes we face a problem with the site collection administrators that disable them from login to the site.

I do have a good solution for such problem, the secret is behind the application pools on your server.

first navigate to IIS Manager, and select application pools from left corner.

Then select the web application that contains the site collection which you couldn’t login to.

As you see below select advanced settings…

After that you will see a panel of properties look at the Identity property, you should see your user name (DOMAIN\user name).

make a selection to this name you will see a browsing button click it and you will be prompted to set a new account, write again your domain username and password like below, click ok to close.

Now,only one step remaining just stop the application and restart it again, try to login again, you will be succeeded.

These kind of problems may occur as a result of changing the domain user password, specially if this user is the site collection administrator.



About Hossam Kamal

Hossam Kamal Senior SharePoint Developer with high development skills in C#, ASP.NET, SharePoint Server Technologies, jQuery, CSS, XML, O.O.D, SSRS and MS.SQL Server.
This entry was posted in SharePoint Configurations, SharePoint General. Bookmark the permalink.

5 Responses to Solving access denied login for site collection administrators

  1. mox-moi says:

    Thanks a lot.

  2. This was to the point… Thank you so much

  3. LynPalmos48 says:

    Thank you for any other informative site. The place else may I am getting that type of information written in such a perfect method? I’ve a mission that I am simply now operating on, and I have been at the look out for such information.

  4. I did the same thing but still it is giving me the access denied exception. But I finally solved it.
    Sol: Check whether the content DB is set to read-only mode. if it is in read only change it to “not locked” mode.
    Please read the post for more details:

    Sasi Kumar Reddy

  5. Matawanakee says:

    In our case, there was a webpart on the page pulling data from another site. The users needed permission to that data. Problem solved!

Leave a Reply

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

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

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s