Typically, if you don’t have access to a SharePoint 2013 site and access requests are not enabled, You get : “Sorry, this site hasn’t been shared with you” message when you try to access any SharePoint 2013 sites. Its a common issue and simply means that you have not been granted access to the site!
OK, How to solve this error?
Login to the site collection with either site collection administrator or Farm Admin (granted with “Full control” Web Application user policy!), grant appropriate access to the user in question by going to Site Settings >> People and Groups. Once you do this, users prompted for credentials instead of the Sorry, this site hasn’t been shared with you error.
To confirm this issue is specific to a particular user’s access rights, Try Login as a different user who has permission to the site already: http:/sharepoint-site-url/_layouts/closeConnection.aspx?loginasanotheruser=true
Still getting the same “Sorry, this site hasn’t been shared with you.”?
- Might be because of cached credentials from a prior browser session. Try clearing IE cache: Open a new browser window >> Go to Internet options >> In the general tab, click the Delete button >> Make sure that passwords and temporary Internet files are selected. Try a different browser such as Firefox!
- If you didn’t run the product and configuration wizard after installation/patch, you may get this error even if you are a site collection administrator. Run it once and get rid of this issue.
- Stop and Start “Microsoft SharePoint Foundation Web Application” service from Central Admin >>Application Management >>Manage services on server. In case, you face issues, use STSADM command line.
stsadm -o provisionservice -action stop -servicetype spwebservice
stsadm -o provisionservice -action start -servicetype spwebservice
- If are migrated from SharePoint 2010, or backup-restore/import-exported: If your source site collection is in classic windows authentication mode and the target is in claims authentication, You must change classic mode authentication to claims-based authentication (Convert-SPWebApplication or $WebApp.MigrateUsers($true))
- If you have a custom master page verify it’s published! Checked-out master pages could cause this issue. Try Check-in and make sure all resources such as CSS, Images, JS files are having at least read access to all authenticated users.
- If you have this feature enabled: “
- Try clearing the Distribution Cache, Do the IIS reset.
- On publishing sites: Make sure you set the cache accounts: Super User & Reader to a domain account for the SharePoint 2013 Web Application with appropriate rights – Configure SharePoint 2013 Object Cache Super User, Super Reader Accounts , http://technet.microsoft.com/en-us/library/ff758656.aspx