I came across a SharePoint issue this week which really did have me on the verge of putting my fist through my laptop screen!
I was witnessing intermittent http time-outs when trying to access various SharePoint pages, including Central Administration. The SQL Server they were connecting too had just been converted to virtual from physical infrastructure and therefore, I was convinced this was the bottleneck – that couldn’t have been further from the truth!
When a page was timing-out, I noticed the following exception in the ULS logs:
Exception occurred while connecting to WCF endpoint: System.TimeoutException: The request channel timed out while waiting for a reply after 00:00:20. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. —> System.TimeoutException: The HTTP request to ‘http://sharepoint01.mydomain:32843/10e591de95e54c84aed18dfc3477ddb0/ProfilePropertyService.svc’ has exceeded the allotted timeout of 00:00:20. The time allotted to this operation may have been a portion of a longer timeout. —> System.Net.WebException: The operation has timed out System.Net.HttpWebRequest.GetResponse()
UserProfileApplicationProxy.InitializePropertyCache: Microsoft.Office.Server.UserProfiles.UserProfileException: System.TimeoutException at Microsoft.Office.Server.UserProfiles.MossClientBase`1.ExecuteOnChannel(String operationName, CodeBlock
The problem, believe it or not, was down to us having too many service accounts within the Administrators group of the UPS service (brilliant). Every item in this access-control list increases the time taken for security look-up resolution and subsequently, results in a WCF endpoint timeout if the ACL resolution takes more than 10-15 seconds.
So, headache over thanks a million to the following MS Blog: