SharePoint 2013: Access Denied to Root Site of Web Application

SharePoint 2013: Access Denied to Root Site of Web Application

Recently, I encountered a very frustrating issue with SharePoint 2013. I had a working web application and everything was running fine. After configuring a few sites in my web application, I started getting emails from other users of the site saying that they were getting Access Denied errors whenever they tried to access the root site collection (ex. https://sharepoint2013/).

I went to that path and was very surprised to find that I, a site collection administrator with Full Control permissions given through the web application user policy, was getting sent to the Access Denied screen as well. After looking around some more, I figured out that only that root site path was throwing the Access Denied error, and that any other path (ex. https://sharepoint2013/default.aspx or https://sharepoint2013/main/default.aspx) was working as expected. I also was able to access Central Administration just fine.

It turns out this problem is a result of the Web Application Authentication settings getting corrupted and can be remedied by enabling and then disabling Anonymous Authentication. This recycles Web Application Authentication settings and clears out the corruption.

To do so, follow these steps:

  • Log into the SharePoint 2013 Central Administration site.
  • Open Application Management.
  • Open Manage web applications.
  • Select the web application that has the problem and open Authentication Providers from the ribbon bar.
  • Open the authentication provider zone that you are using (it is probably just Default).
  • Check the Enable anonymous access option and then Save the Authentication settings. It can take a minute or two to save the settings, so after you click Save just wait for the Authentication Setting window to close.
  • After the Authentication settings window closes and you can see the Authentication Providers window again then try to access your root site again and now you should be able to get to the home page without any Access Denied errors.
  • Now we don't want to leave anonymous access enabled so once again open the authentication provider zone that you are using and now uncheck Enable anonymous access and then Save the Authentication settings.
  • You should now still be able to access the root site of your web application and the issue has been fixed.

Contact us today to learn more about our digital workplace solutions.  


# Bharat
Thanks, we had same issue and struggling to resolved it over week time. This post help us solved it at the moment. Hope this is permanent and no need to re-do the same again and again.
I had this issue while switching from classic to claim based authentication for customized (webpart) sharepoint site.

Thank you!
did you ever find out why authentication got corrupted and how to avoid this from happening again?

# Reza
# Steve
Well done sir!
shyju sasimohanan
# shyju sasimohanan
The permanent fix will be going through the USER POLICY setting of the specified web application and give permission to all the authenticated users
Mauricio Pacheco
# Mauricio Pacheco
Men, I love you, you save me
# Svenni
Thank you, saved me a lot of time :)
# Rafik
Thank you, Great help
nordine Hamza
# nordine Hamza
Thank you this saved my day !!!!!!
# Markus
Thx, worked fine!
Vishnu More
# Vishnu More
Thanks ...!!!

Helpful Information.
Ionut (another)
# Ionut (another)
You sir made my day! Thanks a bunch!
# MSFan
Thanks it helped me too. But in our system I need to set anonymous settings on site also.
$web = get-spweb -Identity site
$Web.AnonymousState = 2;
$Web.AnonymousPermMask64 = "ViewListItems, ViewVersions, ViewFormPages, Open, ViewPages, UseClientIntegration, AddListItems"

and back
$web = get-spweb -Identity site
$Web.AnonymousState = 0;
$Web.AnonymousPermMask64 = "EmptyMask"
# Ionut
# Amar
You saved my two weeks of frustration.

Much Thanks
# Matt
Temporarily solved my issue, however authentication keeps corrupting.
# Anon
Saved my life!

Post a comment

Name (required)

Email (required)

Enter the code shown above:

Related Blog Posts