I am having issues in accessing a SP 2013 site that I created on port 80.  This site should actually be visible by everyone but I can't even see it, and I created it.  I keep getting 'Sorry, this site hasn't been shared with you.' even though I did share it with myself.

I have tried removing then adding myself as the site collection admin, clearing the Distributed Cache, clearing the bindings.... You name it, I've done it.

Are you trying on your VM? also, Can you add urself from the central admin and try...

It is running on a VM.

I've already added myself through Application Mangement > Manage Applications > User Policy

Also, logged int the site as sharepointadmin and shared with myself

Hello

Are you running your application pools as domain accounts?

They're running as sharepoint admin

can you try accessing the settings page via _layouts/settings.aspx and see thats is accessible or not. is so some components on the home page is creating issues for your access

Regards  Roy Joyson
Please remember to mark your question as "answered"/"Vote helpful" if this solves/helps your problem

That's actually where it tries to go and throws the error.

I had similar problems that had to do with the permissions on the site were in Classic Windows Auth but the security for the site was Claims, so it didn't recognize my account (this was after a migration).

You could look into

Convert-SPWebApplication

or

$wa.MigrateUsers($true)

Thanks Christopher but this didn't solve it.  This is a new installation of 2013

Hello

Have you configured cache accounts?  I just responded to a post that made me think of this thread, if you have not messed with the cache accounts then please disregard.

configure cache accounts

i haven't messed with the cache accounts

Did you ever solve this problem?  I am having the same issue.  We have two new 2013 farms in the same domain (prod &test) configured identically but running under different service accounts (ex: SPSAdmin and tSPSAdmin).  I detached 2 content databases in test that corresponded to two different web apps and deleted them from SQL.  I then restored the production version of these content databases to test SQL, fixed the database security, and re-attached them to test farm.  At first, I could not access either but over the weekend something changed - I can access one web app but not the other.

I am a farm administrator and secondary site collection administrator in both site collections.  I also tried adding myself with full control to the web application policy.

This seems to be an authentication issue where user is not being identified in Claims based authentication. Try removing and adding user through powershell.

1) first remove user,if user exists using Remove-SPUser command

http://technet.microsoft.com/EN-US/library/ff607894.aspx

2) Then add user, using New-SPUser command

http://technet.microsoft.com/EN-US/library/ff607868.aspx

• Proposed as answer by Ahamed Shaamil Wednesday, September 25, 2013 5:13 AM

If you face the problem for specfic user its seems to be authentication problem as Ahamed said.

But if you face this problem for all users you should look to the storage if it is full, you should empty some of storage and it will work fine.

Error Sorry, this site hasnt been shared with you. is the new Access denied in sharepoint 2013.

Sorry, this site hasnt been shared with you. Its a basically uncommon  error for sharepoint users.

What it actually means that your windows account has not been granted access to the site.

This error is cause by permissions/credentials access problem.

If you have credential for account who has rights on site then, by simply hitting below URL, you can have prompt to login prompt.

<href: <a href=http:/serverurl/_layouts/closeConnection.aspx?loginasanotheruser=true />

If you want to add your account as Site collection Administrator or to determine the site collection administrator is:

Lets Log in to SharePoint 2013 Central Administration.

Make sure Select Application Management -> Change Site Collection Administrators.

Select the correct site collection and look at the primary site collection administ

I had this issue for some pages. For me it turned out to be issue with the master page. We have a customized master page. So I checked-out and checked-in again html file for the master page and that solved the problem. I have also allowed all authenticated users to have read permission on Device Channels list.

• Edited by Trupti G Thursday, March 13, 2014 2:52 AM
• Proposed as answer by Trupti G Monday, March 17, 2014 10:27 PM

In my case when i changed from Classic to claims i got this issue

Solution in my case:

$wa = Get-SPWebApplication -Identity "MY URL"
$wa.MigrateUsers($true)

• Proposed as answer by CunningSteve Monday, July 21, 2014 2:19 PM

Solution in my case:

$wa = Get-SPWebApplication -Identity "MY URL"
$wa.MigrateUsers($true)

• Thank you for your help @surapanenikiran. It works fine for me.
  

• Edited by Y.Hoang Tuesday, July 22, 2014 1:05 AM

I am getting 'Access Denied' when I run this command. Any Idea? And also MigrateUsers(Boolean) is not Obsolete?

Hi,

Are you able to create the site collections from the CA with the same account you are using. Also the check the app pool account is not changed.

Regards

Sandeep

Hi,

If above does not work that try giving access to that account on Content DB to that Web app manually and then try to access.

Hopefully this should work.

Regards

Sandeep

If you have set the Object cache Super User and Super Reader accounts for a web app, it also causes this behaviour.
Then you need to assign the correct user policy for those two.
But i guess you've would have known if these ones has been set, since it's a manual operation.

But hey, who know, try to set them and assign the policy and see if it helps.

Configure object cache user accounts in SharePoint Server 2013

BR / Philip

Have you tried checking your Proxy Settings(located in Internet Options -> Connection -> LAN Settings -> Advance)

you might have to configure proxy server settings(add an exception) so that Sharepoint site addresses bypass the proxy server. 

Hope that might work out for you.