Tag Archives: Permissions

Error while trying to Access “Details” of a SharePoint App

November 6, 2015 1:22 PM / Leave a Comment /

Recently we added Access Services to our SharePoint 2013 environment. After the initial setup we started testing the new implementation and stumbled over an error while accessing the details page of an app. This has nothing to do with access itself, more with apps in general.

2015-11-06_13-03-54

After clicking on details you get an error message with the correlation id. So nothing easier to get the log regarding that error.

SqlError: ‘The EXECUTE permission was denied on the object ‘prc_CountAppInstanceData’, database ‘SharePoint_Logging’, schema ‘dbo’.’    Source: ‘.Net SqlClient Data Provider’ Number: 229 State: 5 Class: 14 Procedure: ‘prc_CountAppInstanceData’ LineNumber: 1 Server: ‘Database.fqdn.com’ f2ec3e9d-ac28-80f1-8d80-1d89f5d672a9
11/06/2015 12:50:34.93  w3wp.exe (Servername.fqdn.com:0x5DE4)            0x5D34 SharePoint Foundation          Database                       5214 Critical Insufficient SQL database permissions for user ‘Name: NT AUTHORITY\IUSR SID: S-1-5-17 ImpersonationLevel: Impersonation’ in database ‘SharePoint_Logging’ on SQL Server instance ‘Database.fqdn.com’. Additional error information from SQL Server is included below.  The EXECUTE permission was denied on the object ‘prc_CountAppInstanceData’, database ‘SharePoint_Logging’, schema ‘dbo’. f2ec3e9d-ac28-80f1-8d80-1d89f5d672a9

This leads us to a permission issue. We tried granting the App Management Service Account “SPDataAccess” permission on our logging database, which did not help.

As you can see in the log there is an user specified IUSR SID: S-1-5-17. This leads to a permission issue from IIS WebServer. Makes sense as all SharePoint Applications are running within the IIS and their Application Pools. As our App Management Service Account wasn’t the issue we granted our Application Pool Account under which the Web Applications are running, the “SPDataAccess” permission on our logging database.

2015-11-06_13-04-42

Et voila, this fixed the issue.

Problem: App Details do not work.

Solution: Grant SPDataAccess Permisson to your Web Application Pool Account on your SharePoint Logging Database.

Was this post helpful? Not HelpfulHelpful
Loading...
Posted in: Microsoft, SharePoint / Tagged: , ,

SharePoint 2013 – Active Directory Security Groups do not work

September 2, 2013 8:29 AM / Leave a Comment /

Last week we created a new Site Collection and published it to our company. We added an active directory universal security group to our visitor group in Sharepoint.

After some time the first users complaint that they have no access to the site collection. Really strange was that all users without sid history had no problem.

Finally we found this article: KB2722087

“Each SharePoint service application must run the C2WTS locally. The C2WTS does not open any ports and cannot be accessed by a remote caller. Further, the C2WTS service configuration file must be configured to specifically trust the local calling client identity.”

Its mandatory that the Claims2WinowsTokenService runs on ALL WebFrontends and Backend Servers! (don’t think its necessary on real Backend Server without user interfaces like search server)

 

 

Was this post helpful? Not HelpfulHelpful
Loading...
Posted in: SharePoint / Tagged: , , , ,