A Quick Overview of the Check Permissions Function Error in SharePoint 2013
Permission levels are well-defined & pre-decided in SharePoint 2013; henceforth, depending on the functional requirements, permissions are granted to individual users or groups of users or security groups.
Provisions can also be made to allow users gain access to a specific folder, document library, list without granting access to the complete site.
Allocating permissions to groups in SharePoint has a number of benefits linked with it like site structure alignment, partial or complete access as per work requirements and uniform access to users performing similar tasks.
SharePoint 2013 includes a Check Permissions function that plays a highly crucial part in providing accurate information regarding user permissions level.
However, recently, there have been issues with this function as it failed to render the desired accurate information many times. Here, we will take a deeper look into the error that makes this happen.
So, What is this Error Exactly?
Let’s understand the ideal situation for Check permission function.
For a site collection featuring standard team site template, there are SharePoint groups typically defined in the form of Visitors, Members and Owners.
While checking the permissions levels for a user in a document library, following should be displayed ideally –
However, in the case of error, “None” would be rendered by the permissions function irrespective of the user actually being a member of any of the groups as defined above.
SharePoint specialists have worked hard to find a reason for this error and finally discovered it.
The Reason Behind Check Permissions Function Error…
As explained before, the Check Permissions Function returns incorrect information while checking the permissions level for a user.
Experts have found SidHistory to be the reason for the same. In case, you use SidHistory while migrating your Active Directory users & groups to some new domain but leave the SidHistory attributes uncleared post the migration is completed then this error is bound to occur.
What Our Experts Suggest?
Groups with SidHistory attributes specified also cause SharePoint to misbehave in this manner. If you have been experiencing the same issue for long, ensure that following are fully taken care of –
- Check all groups having the common user for which the error is being displayed
- Check nested group membership
- Clear SidHistory attributes completely
Positively, by following all points as mentioned above, you can avoid the Check Permissions Function error in .
- Microsoft Sharepoint2018.03.30How to Select the Best between SharePoint Server and SharePoint Online
- SharePoint Hosting2018.03.22Avoid SharePoint Compliance Risk by implementing a Robust Information Governance Plan
- Dedicated Hosting2018.03.20Guide to Selecting the Best between Office 365 Hosting and Hosted Exchange
- QuickBooks2018.03.07Boost Up Your Accounting Performance with Managed QuickBooks Support Services