Category Archives: Sharepoint

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.

Posted in: Microsoft, SharePoint / Tagged: , ,

Error during install of Microsoft Workflow Manager 1.0 Refresh

June 30, 2014 1:34 PM / Leave a Comment /

Installing the Workflow Manger 1.0 Refresh can be tricky.

During Installation process with the web platform installer 5.0 (only way to install it) the setup of Microsoft Windows Fabric V1 CU1 fails. When you open the log it says 1603.

So lets see what 1603 means. Open cmd prompt and type net helpmsg 1603.

C:\>net helpmsg 1603

Fatal error during Installation.

Not very expressive. But there is a simple solution, install Visual C++ Redistributable for Visual Studio 2012 Update 4.

 

Source: Social MSDN

Posted in: Microsoft, SharePoint / Tagged: , ,

SharePoint 2013 – Zero Byte ULS Logs

February 26, 2014 1:42 PM / Leave a Comment /

Recently I stumbled over out ULS Logs on the Web Frontends. Suprisingly they were empty, 0 bytes. I checked the permissions for the account the tracing service is running with (Web Application Pool Account). Everything was fine, same permissions as on the other servers where it was working.

So I checked the local groups and found out the tracing account must be a member of the “Performance Log Users”. Add the account, restart the “SharePoint Tracing” Service and you will see the uls logs growing.

Posted in: Microsoft, SharePoint / Tagged: , , , ,

SharePoint 2013 – Unknown SQL Exception 64

January 7, 2014 12:46 PM / Leave a Comment /

After a major network outage one of our server doesn’t want to connect to the database server anymore. The event log was spammed with the following message:

Error    07.01.2014 10:09:09    Microsoft-SharePoint Products-SharePoint Foundation    5586    Database    “Unknown SQL Exception 64 occurred. Additional error information from SQL Server is included below.

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 – The specified network name is no longer available.)”

This message only appeared on one out of five servers. No reboot, no iisreset resolved the problem.

We resolved the issue by moving the database to another sql node (FailOver / Always On). When you move the database all connections will be forcibly closed. Seems that the sql server doesn’t allow the server to connect to the database as some connection was still established. If you can’t move the database to another node, simply restart the instance or put the affected database in single user mode to close the connections.

Posted in: Microsoft, SharePoint / Tagged: , , ,

SharePoint 2013 on Windows Server 2012 R2

November 7, 2013 12:53 PM / Leave a Comment /

Not long ago Microsoft released Server 2012 R2 to the public. So what most administrators do? Lookup the support of their software.

Is SharePoint 2013 supported on Windows Server 2012 R2?

Sadly Microsoft announced that its not supported yet. Microsoft will add support with SP1 which is not announced as of today. – http://support.microsoft.com/kb/2891274

Anyways you may can get the prerequisite installer with installing the packages manually and go on with the setup but its not a supported system state. Same workaround applies to SharePoint 2010.

 

Posted in: 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)

 

 

Posted in: SharePoint / Tagged: , , , ,

Secure OfficeWebApps Farm with “FarmOU” Setting

August 23, 2013 3:19 PM / 4 Comments /

As Microsoft describes on TechNet you can prevent other OfficeWebAppsHosts from joining your Farm when the computer account isn’t located in the correct active directory OU.

http://technet.microsoft.com/library/jj219442.aspx

FarmOU Optional System.String Specifies the name of the Active Directory organizational unit (OU) that servers must be a member of to join the Office Web Apps Server farm. Use this parameter to prevent unauthorized servers (that is, servers that are not in the OU) from joining an Office Web Apps Server farm.

But how to apply this setting? As using the DN of the OU does not work you need to use the Canonical Name of the OU. If your machines are located in CONTOSO.COM/Computers/OfficeServer/SERVERNAME1 you need to use the following command:

Set-OfficeWebAppsFarm -FarmOU “Computers/OfficeServer”

To check the setting:

Get-OfficeWebAppsFarm

FarmOU should display the ldap path of the OU.

FarmOU                            : ldap://OU=OfficeServer,OU=Computers

 

Posted in: OfficeWebApps, SharePoint / Tagged: ,