Increasing the Time-Out Value for Rebuild/Refresh Data Operations
Centrify Report Services invokes multiple database operations when it refreshes and rebuilds its cache of information stored in Active Directory. These database operations can be time-consuming in a large Active Directory environment. If any such database operation cannot be completed within a certain time period, the Centrify Report Services control panel will show that the Refresh/Rebuild process failed.
When Centrify Report Services perform a snapshot rebuilding or refreshing and the amount of the monitored data is too large to be processed within the time-out period, this error will occur:
A database operation error occurred. Please contact your administrator to make sure the remote database is accessible and working properly. ---> System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
You can change the time-out value (3,600 seconds by default) for that time period by performing the following steps:
- Open the registry editor and then locate the key ‘SQLCmdTimeout’ under HKLM\Software\Centrify\Report Services\Service. If you cannot find it under the path, create one with the same name and as 'DWORD' type.
Set to 'SQLCmdTimeout' to a large enough value (unit in second) so that the rebuild/refresh/computing can be finished within the time period.
Note, set the SQLCmdTimeout to 0 (ZERO) mean no time-out. Customer should contact Centrify Technical Support first before changing SQLCmdTimeout to 0.