Vault Client Crashes on attempt to checkin and login

[sergemerz]

I am running Vault 3.5 on SQL 2005, Windows XP SP2 and was wokring fine until I tried to commit a new folder change (3000+) files and client crashed on attempt to commit with the following brief diagnostic:

AppName: vaultguiclient.exe AppVer: 3.5.2.5087 ModName: hlcap.dll
ModVer: 1.2.5.0 Offset: 0000224e

After that first failure i noticed that it now crashes on login as well.

I checked the size of the sgvaault database and noticed that it was pretty full. I altered the database growth mode to go up by 20% at a time, in the hope that that may (unlikely!) have been the issue. This did not help.
My next step was to restart my PC which made no difference.

Finally I modified VaultGUIClient.exe.config with the following:

<add key="enableLogging" value="true" />
<add key="logFilePath" value="D:\sourcegear\clientlog.txt" />

This did not log very much, although I admit I do not know much about .NET logging.

SO far all of my admittedly uninformed efforts have met with no success, so as an open source user I thought I would repay the favour and let you know.

BTW I have never had any problems like this before.

[sergemerz]

Here is the sgvault.log entries for today which is the only time the issue has been noticed (ip addresses removed):

----17/05/2007 9:05:29 serge--MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled Logout
----17/05/2007 12:06:48 serge--MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled Login
----17/05/2007 12:09:55 serge--MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled Login
----17/05/2007 12:11:19 serge--MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled Login
----17/05/2007 12:12:29 serge--MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled Login
----17/05/2007 12:12:46 serge--MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled Login
----17/05/2007 12:14:03 admin--MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled Login
----17/05/2007 12:14:21 admin--MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled Logout
----17/05/2007 12:14:37 serge--MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled Login
----17/05/2007 12:26:06 --MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled System.Data.SqlClient.SqlException: SHUTDOWN is in progress.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.TdsExecuteTransactionManagerRequest(Byte[] buffer, TransactionManagerRequestType request, String transactionName, TransactionManagerIsolationLevel isoLevel, Int32 timeout, SqlInternalTransaction transaction, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.ExecuteTransactionYukon(TransactionRequest transactionRequest, String transactionName, IsolationLevel iso, SqlInternalTransaction internalTransaction)
at System.Data.SqlClient.SqlInternalConnectionTds.ExecuteTransaction(TransactionRequest transactionRequest, String name, IsolationLevel iso, SqlInternalTransaction internalTransaction)
at System.Data.SqlClient.SqlInternalConnection.BeginSqlTransaction(IsolationLevel iso, String transactionName)
at System.Data.SqlClient.SqlConnection.BeginTransaction(IsolationLevel iso, String transactionName)
at System.Data.SqlClient.SqlConnection.BeginTransaction(IsolationLevel iso)
at VaultServiceSQL.VaultSqlConn.BeginTransaction(IsolationLevel isolationlevel) at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.TdsExecuteTransactionManagerRequest(Byte[] buffer, TransactionManagerRequestType request, String transactionName, TransactionManagerIsolationLevel isoLevel, Int32 timeout, SqlInternalTransaction transaction, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.ExecuteTransactionYukon(TransactionRequest transactionRequest, String transactionName, IsolationLevel iso, SqlInternalTransaction internalTransaction)
at System.Data.SqlClient.SqlInternalConnectionTds.ExecuteTransaction(TransactionRequest transactionRequest, String name, IsolationLevel iso, SqlInternalTransaction internalTransaction)
at System.Data.SqlClient.SqlInternalConnection.BeginSqlTransaction(IsolationLevel iso, String transactionName)
at System.Data.SqlClient.SqlConnection.BeginTransaction(IsolationLevel iso, String transactionName)
at System.Data.SqlClient.SqlConnection.BeginTransaction(IsolationLevel iso)
at VaultServiceSQL.VaultSqlConn.BeginTransaction(IsolationLevel isolationlevel)
----17/05/2007 12:33:04 sgvaultsystem--()--
System Started
Version 3.5.2.5087
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL = http://MRP6WTB5.XX.XX.XX.XX/VaultService
Identity = MRP6WTB5\ASPNET
----17/05/2007 12:33:11 serge--MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled Login
----17/05/2007 12:37:52 serge--MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled Login
----17/05/2007 12:41:37 serge--MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled Login
----17/05/2007 12:42:15 serge--MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled Login
----17/05/2007 12:47:29 serge--MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled Login
----17/05/2007 12:56:45 serge--MRP6WTB5.xxxx.(NN.NN.NN.NN)--SSL Disabled Login

[sergemerz]

I have increased the database buffer size and other size parameters in admin tool which appear to have resolved the problem - must have been the large set that exceeded the limit.

Sorry to have generated an unnecessary post (again!).