Increasing the database timeout period in Shavlik Protect and VMware vCenter Protect

Symptoms

• Shavlik Protect or vCenter Protect report database timeout errors 
• In the ST.Protect.managed log file, you see the error:
  
  System.Transactions.TransactionAbortedException: The transaction has aborted. ---> System.TimeoutException: Transaction Timeout

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.

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
2. 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
3. In Shavlik Protect v.9.0, navigate to:
   1. All architecture - C:\Program Files\LANDesk\Shavlik Protect
4. Locate the ST.Data.Config file and open it using a text editor. 
5. 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.
6. To re-establish the connection, go to Start> All Programs> Protect> Database Setup Tool. 
7. Select to your existing database and proceed through the tool to reconnect and automatically restart the Protect services.

Products

Shavlik Protect 9.x

vCenter Protect 8.x