locked
"Sorry, you don't have access to this page" Happening on site collections on 2 different 2016, on prem, farms RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
                                              

    Hi,  we are getting an error when browsing to our site collections (team sites).  "Sorry, you don't have access to this page".  When I first built the farms, OOB, I would get this error after enabling some sight collection features in particular SharePoint Server Publishing Infrastructure.   The site would be fine for a minute or so, sometimes over night and then  "Sorry, you don't have access to this page".  I ran some powershell commands to disable Publishing and that fixed the problem a couple of different times; however, on these sites we need Publishing enabled.

    Oddly enough the site collection started working ok on our Dev farm and we had been cruising along doing development and migrating from 2010.  On our QA farm, I had to tear down the site collection and rebuild it from scratch as the powershell script to disable Publishing didn't work.  Just recently, Monday, I enabled HTTPS redirect using the URL rewrite module and everything was fine.  Last night while trying to identify an issue with a custom app, we disabled the redirect rule on both farm.  Immediately our Dev farm blocked access with  "Sorry, you don't have access to this page" and this morning the QA site once again greets us with  "Sorry, you don't have access to this page".

    It doesn't matter what account I use user, owner or farm we can't access the site.  I have searched event logs and trace logs (verbose) with no indication of the error.  I also used fiddler to see if something would surface there and saw nothing unusual.  I have scoured the internet and sought assistance from our developer and an outside vendor, and both were not familiar with this issue.  Any suggestions on how to remedy this would be most appreciated as right now, we are not comfortable going to production with 2016.

    Thursday, June 21, 2018 12:58 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    I opened an MSDN ticket with Microsoft and the support person did notice a cache error.  He had me remove the accounts for superreader and superuser from web applications. Evidently if you have those set, and don't have object caching enabled it can cause problems.
    • Marked as answer by ScottPayne Tuesday, July 3, 2018 12:16 PM
    Tuesday, July 3, 2018 12:16 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi ScottPayne,

    To troubleshoot the issue, check things below:

    1. Run SharePoint 2016 configuration wizard.

    2. RESET IIS.

    3. Re-install SharePoint 2016.

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, June 22, 2018 7:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi ScottPayne,

    How is everything going?

    Is there anything update about this issue?

    If the reply is helpful to you, you could mark the reply as answer. Thanks for your understanding.

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, June 25, 2018 1:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    1. Hi, I have run Config Wizard several times on both farms.

    2. Reset IIS multiple time

    3. Since this is happening on 2 different farms and I am not getting any errors in the logs or config wizard, I don't believe this is related to the install.  Also, I have seen, via internet search. that others have had the same issue.  Unfortunately the solutions they found, so far have not resolved ours

    Thanks

    Scott

    Monday, June 25, 2018 11:49 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi ScottPayne,

    To troubleshoot the issue, you could check if the users have the proper permission in the content database on the SQL server.

    And you could configure and assign the user accounts for Super Reader and Super User and set the full read and full control permissions in the User Policies in the manage web applications in central administration.

    For more detailed information, refer to the articles below.

    Configure SharePoint 2013 Object Cache Super User, Super Reader Accounts.

    http://www.sharepointdiary.com/2014/12/configure-sharepoint-2013-object-cache-superuser-superreader-accounts.html

    Fix "Sorry, this site hasn't been shared with you." Error in SharePoint 2013

    http://www.sharepointdiary.com/2014/01/sorry-this-site-hasnt-been-shared-with-you-sharepoint-2013.html

    There is a similar post:

    https://social.technet.microsoft.com/Forums/azure/en-US/6dc952f9-0279-4a01-ad3b-e34950172f15/sharepoint-server-publishing-infrastructure-sorry-you-dont-have-access-to-this-page?forum=sharepointadmin

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, June 26, 2018 9:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi ScottPayne,

    How is everything going?

    Is there anything update about this issue?

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, June 27, 2018 12:59 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi ScottPayne,

    I am checking to see how things are going there on this issue. Please let us know if you would like further assistance.

    If the issue was resolved, you can mark the helpful post as answer to help other community members find the helpful information quickly. 

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Thursday, June 28, 2018 4:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you Sara, I am sysadmin on the sql server and I set super reader/user when I build the farm and I have a script that I run whenever I add a new web app.

    Scott

    Thursday, June 28, 2018 11:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi ScottPayne,

    You could clear SharePoint configuration cache according to the article below.

    Clearing the SharePoint Configuration Cache.

    https://www.zubairalexander.com/blog/clearing-the-sharepoint-configuration-cache/

    I suggest you could consider re-installing SharePoint 2016.

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, June 29, 2018 10:02 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi ScottPayne,

    If the reply is helpful to you, you could mark the reply as answer. Thanks for your understanding.

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, July 2, 2018 9:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have previously cleared the cache.  Reinstalling SharePoint 2016 should not be an option as this is happening with 2 farms using OOB installation. This would indicate an underlying issue either with SharePoint configuration (and I used the wizard) or the authentication process itself.  Identifying the root cause would be more beneficial since reinstalling isn't always an option or a resolution.  Thanks 
    Monday, July 2, 2018 1:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I opened an MSDN ticket with Microsoft and the support person did notice a cache error.  He had me remove the accounts for superreader and superuser from web applications. Evidently if you have those set, and don't have object caching enabled it can cause problems.
    • Marked as answer by ScottPayne Tuesday, July 3, 2018 12:16 PM
    Tuesday, July 3, 2018 12:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi ScottPayne,

    It is very happy that the issue is resolved.

    Thank you for your sharing and it will help others have the same issue.


    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, July 4, 2018 1:15 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I thought this approach (re-install a Microsoft application) was typical for Windows 95 and Windows 98. Or for calling ISVs, whose first advice was to "powercycle the cable modem". Or the subject of now almost forgotten joke about about Microsoft support. "Glad" to see the "reinstall"/"reboot" advice still alive and kicking and at the same time wondering if Microsoft does the same when troubleshooting identical problems on the Azure cloud.
    Tuesday, December 18, 2018 12:05 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I get the error after installing most recent SP2016 on-prem updates as of Dec 17 2018, after running SP Configuration Wizard (single server dev VM with all roles, 4 logical CPUs, 24GB RAM, 200GB disk space, SQL 2014 Developer) and rebooting the VM.

    If the Microsoft updates modified any SQL 2014 Developer with most recent updates, then Microsoft is doing something wrong (what exactly in the bug fixes warrants modifying SQL DB permissions other than sloppy programming?).

    I got a lot of content (months of work on content alone) on that SP VM and I am not exactly in the mood to risk losing it because the MS Support recommends reinstalling SP2016 (having worked with SP since version 2003 I learned this and that about "resolving" update problems, often painfully). Now I cannot get to my content. Any other suggestions that do not potentially wreck the content?
    Tuesday, December 18, 2018 12:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Resolved, by adding IUSR with read permissions to C:\Inetpub\Wwwroot\wss and all its subfolders recursively. Why MS Updates mess up NTFS permissions I cannot fathom - if there is an actual need to change them in order to apply the updates, the final phase of the update should restore those NTFS permissions. Somehow it's not happening and this results in a 20-year old deja vu. Bad programming practices just can't die.
    Tuesday, December 18, 2018 12:25 AM