Increasing the database timeout period for Protect

• 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: Ensure to close the Protect application before proceeding.

Step 1:

• In Protect 8.0 that was upgraded from an earlier version, navigate to this directory:
  1. 32bit – C:\Program Files\Shavlik Technologies\NetChk
  2. 64bit – C:\Program Files (x86)\Shavlik Technologies\NetChk

• In a fresh installation of Protect 8.0, navigate to:
  1. 32bit – C:\Program Files\VMware\vCenter Protect
  2. 64bit – C:\Program Files (x86)\ VMware\vCenter Protect

• In Shavlik Protect v.9.0, navigate to:
  1. All architecture - C:\Program Files\LANDesk\Shavlik Protect

Step 2:

• Locate the ST.Data.Config file and open it using a text editor.

Step 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.
• Save the changes for the ST.Data.Config file.

Step 4:

• Re-open your Protect console, and test to see if the issue is resolved.

Shavlik Protect 9.x

vCenter Protect 8.x