{"id":1203,"date":"2021-08-05T16:05:50","date_gmt":"2021-08-05T21:05:50","guid":{"rendered":"https:\/\/zewwy.ca\/?p=1203"},"modified":"2021-08-06T14:22:46","modified_gmt":"2021-08-06T19:22:46","slug":"sharepoint-site-has-not-been-shared-with-you","status":"publish","type":"post","link":"https:\/\/zewwy.ca\/index.php\/2021\/08\/05\/sharepoint-site-has-not-been-shared-with-you\/","title":{"rendered":"SharePoint Site Has Not Been Shared With You"},"content":{"rendered":"

<\/span>SharePoint Site Not Accessible<\/strong><\/span><\/h1>\n

<\/span>Overview Story<\/span><\/h2>\n

Created brand new SharePoint Teams site.<\/p>\n

Enabled Publishing Feature.<\/p>\n

Created Access groups, Nest User in Group.<\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

\"\"<\/a><\/p>\n

<\/span>Troubleshooting<\/strong><\/span><\/h2>\n

First Source<\/a> Disable Access request feature. This feature was enabled, disable it, Result….<\/p>\n

\"\"<\/a><\/p>\n

Second Source\u00a0<\/a>far more thing to try.<\/p>\n

    \n
  1. Cache, not the case same issue from any browser and client machine.<\/li>\n
  2. *PROCEED WITH CAUTION* Stop and Start \u201cMicrosoft SharePoint Foundation Web Application\u201d service from Central Admin >>Application Management >>Manage services on server. In case, you face issues, use STSADM command line.cd “c:\\program files\\common files\\microsoft shared\\Web Server Extentions\\16\\BIN”Stop:
    \nstsadm -o provisionservice -action stop -servicetype spwebservice
    \n[Time taken ~30min not sure went for a break since it was taking so long]
    \niisreset \/noforce [!1min]
    \nStart:
    \nstsadm -o provisionservice -action start -servicetype spwebservice
    \n[Roughly 15 min]
    \niisreset \/noforce<\/li>\n<\/ol>\n

    Result, SharePoint completely broken, Central Admin is accessible, but all sites are in a non working state. I cannot recommend to try this fix, but if you have to ensure you are doing so either in a test environment or have a backup plan.<\/p>\n

    I managed to resolve the issue in my test environment, as it turned out the sites were all defined to be HTTPS, however the binding was done manually on IIS to certs created, and then the AAMs updated on CA. Sources one<\/a> and two<\/a><\/p>\n

    Running these commands SharePoint is not aware to recreate the HTTPS bindings so this has to be done manually.<\/p>\n

    Result:<\/p>\n

    \"\"<\/a><\/p>\n

    Ughhhhhhhhhhhh!<\/p>\n

    3.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<\/p>\n

    Not the case, but tried it anayway, and results…<\/p>\n

    \"\"<\/a><\/p>\n

    This is really starting to bug me…<\/p>\n

    4.If you have a custom master page verify it\u2019s published! Checked-out master pages could cause this issue.<\/p>\n

    We did make changes to the master page to resolve some UI issues, but this had to be published to even have those changes show, so YES, no change in result.<\/p>\n

    5.If you have this feature enabled: \u201cLimited-access user permission lockdown mode\u201d at site collection level \u2013 Deactivate it. \u2013 Because, this prevents limited access users from getting Form pages!<\/p>\n

    Found this, deactivated it and….<\/p>\n

    \"\"<\/a><\/p>\n

    Ughhhhh….<\/p>\n

    6.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.<\/p>\n

    I’ve read this from a different source as well<\/a> however none of my other sites that are teams sites with publishing enabled have these extra properties defined and they are working without issue, I decided to try anyway,<\/p>\n

    Result:<\/p>\n

    \"\"<\/a><\/p>\n

    7. If you didn\u2019t 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.<\/p>\n

    Let’s give it a whirl… Now I pushed this down from #2 as it’s pretty rough like the suggestion I put as #2, which I should probably shift down for the same risk reasons, but I did try this before the other ones and it like the stsadm commands it broke my ShaerPoint Sites, it stated errors about features defined in the content database of attached sites that the features were not installed on the front end server.<\/p>\n

    In this case I tried to run my scripts I had written to fix these types of issues (publishing of script pending), but it wouldn’t accept the site URL stating it was not a site collection, it was at this point running get-spsite returned an error…<\/p>\n

    and sure enough…<\/p>\n

    \"\"<\/a><\/p>\n

    AHHHHHHHHHHHH!!!!!!!!!<\/p>\n

    I asked my colleague for help since he seems to be good at solving issue when I feel I’ve tried everything. He noted the master pages and layouts area had unique permissions, setting it to inherit from parent made the pages finally load. But is this normal? I found someone asking about the permissions here,<\/a> apparently it shouldn’t be inherited and they list the default permission sets:<\/p>\n

    Yes, Master Page Gallery use unique permissions by default.\r\nHere is the default permissions for your information:\r\nApprovers SharePoint Group Approvers Read\r\nDesigners SharePoint Group Designers Design\r\nHierarchy Managers SharePoint Group Hierarchy Managers Read\r\nRestricted Readers SharePoint Group Restricted Readers Restricted Read\r\nStyle Resource Readers SharePoint Group Style Resource Readers Read\r\nSystem Account User SHAREPOINT\\system Full Control<\/pre>\n
    Setting there defaults I still got the page was not shared problem, for some reason it works when I set the library to inherit permissions from the parent site.<\/p>\n
    When checking other sites I was intrigued when there was only the Style Resource Readers defined. I found this blog on a similar issue when sub site inheritance is broken<\/a> which interesting enough directly mentions this group.<\/p>\n
    “It occurs when the built-in SharePoint group \u201cStyle Resource Readers\u201d has been messed with in some way.”<\/p>\n
    Will check this out.<\/p>\n
    So I went through his entire validation process for that group, it all checked out, however as soon as I broke inheritance on the master page library, made it the “known defaults” and verified all Style Resources users were correct and all permission for it on all listed libraries and lists all match,\u00a0 I continued to receive Site not shared with you error.<\/p>\n
    I don’t feel the fix I found is correct, but I can’t find any other cause, or solution at this time. I hope this blog post helps someone, but I’m sad to say I wasn’t able to determine the root cause nor the proper solution.<\/p>\n
     <\/p>\n","protected":false},"excerpt":{"rendered":"
    SharePoint Site Not Accessible Overview Story Created brand new SharePoint Teams site. Enabled Publishing Feature. Created Access groups, Nest User in Group.   Troubleshooting First Source Disable Access request feature. This feature was enabled, disable it, Result…. Second Source\u00a0far more thing to try. Cache, not the case same issue from any browser and client machine. … <\/p>\n
    Continue reading “SharePoint Site Has Not Been Shared With You”<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","footnotes":""},"categories":[8,9],"tags":[365],"class_list":["post-1203","post","type-post","status-publish","format-standard","hentry","category-server-administration","category-sharepoint","tag-site-not-shared-with-you"],"_links":{"self":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/1203","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/comments?post=1203"}],"version-history":[{"count":5,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/1203\/revisions"}],"predecessor-version":[{"id":1208,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/1203\/revisions\/1208"}],"wp:attachment":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/media?parent=1203"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/categories?post=1203"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/tags?post=1203"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}