Tag Archives: Sharepoint 2013

Office Web Apps via HTTPS are slow and you can’t open documents without an error

March 22, 2014 1:28 AM / Leave a Comment /

You’ve installed an Office Web Apps Server with HTTPS and its slow? We really had slow office web apps and an enormous amount of documents that failed to open with the following error message “Sorry, something went wrong”.  Make sure your SharePoint Web Applications are using https and  “AllowOAuthoverHTTP” is not enabled. You should not use AllowOAuthoverHTTP when using HTTPS.

$config = (Get-SPSecurityTokenServiceConfig)
$config.AllowOAuthOverHttp = $false
$config.Update()

More solutions to resolve your problem on TechNet

 

Posted in: Microsoft, OfficeWebApps, 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: , , ,