Symptoms
- Shavlik Protect or vCenter Protect report database timeout errors
- In the ST.Protect.managed.log file, you see may see an error such as the following:
System.Transactions.TransactionAbortedException: The transaction has aborted. ---> System.TimeoutException: Transaction Timeout
OR
2012-07-17T21:10:46.8328850Z 0001 W ScanSummaryPresenter.IsRecoverable|A SQL Server query operation timed out. Consider increasing the command timeout in the configuration file
Purpose
This article provides steps to increase the database timeout value in Shavlik Protect and vCenter Protect.
Resolution
To increase the database timeout period:
Note: Close the Protect application before proceeding.
1.Navigate to C:\Program Files\LANDesk\Shavlik Protect
2.Locate the ST.Data.Config file and open it using a text editor.
3.Change this entry:
st.data commandTimeout="30"
To:
st.data commandTimeout="3600"
This increases the timeout period allotted for transactions with the database. This number is in seconds and you can set the number to a higher value as required. 3600+ is the recommendation value for most timeout issues.
4. Save the changes for the ST.Data.Config file.
5.Re-open your Protect console, and test to see if the issue is resolved.
This setting is not maintained during a re-install or upgrade. Also, running the Database Setup Tool will revert this setting to 30 seconds.
Affected Products
Shavlik Protect 9.x