Problem Description:
Error: “Timeout Expired. The timeout period elapsed prior to completion of the operation or the
server is not responding.”
This can be caused due too many rows in the SharePoint_Config DB in table dbo.TimerJobHistory
You can check on SQL with the following code:
SELECT CONVERT(bigint, rows)
FROM sysindexes
WHERE id = OBJECT_ID(‘dbo.TimerJobHistory’)
AND indid < 2
The root problem is a general SP 2013 “beature”.
The job “Delete Job History” is scheduled weekly but has a timeout. That causes, that ususally a lower number of entries is purged after a week than new entries created during the week on a large farm.
Resolution:
Set the job schedule to 1 minute until you reached a lower and stable number of rows.
After that change the job to run daily.
(No Ratings Yet)
Loading...