Cannot show history without setting a date range

[Virgil Smith]

Version Check: This Vault Professional client is version 5.1.1.19216
Version Check: Your server is version 5.1.1.19216

We now have numerous folders in a repository upon which an unfiltered "Show History" command results in a 3+ minute lockup of the client followed by a notice that "A database error has occured (FailDBFault)" and then a notice that "The history session could not be found." and a History Explorer window filled with "Retrieving item...".

Requesting the same, but specifying a start date, ANY start date -- including one from before the repository was created (let alone the folder or any branch source folder in question), results in "normal" behavior.

So far the merge branches wizard (which does not let you specify a scope for the history searches) has continued to function, but if this stops then we will have to chunk Vault in the trash bin, select another SCM solution and

[Beth]

In your Vault Tools - Options - History/Labels, what is your "Limit Queries" set to and your "Fetch row in chunks of" set to? is the option to "Act on queries recursively" checked?

How much free disk space do you have available on your Vault server and your SQL Server? If you are short on space anywhere, it can affect large queries.

[Virgil Smith]

Well I had a HUGE amount of additional info, but your BB app threw it all away.

There is 1.9GB of free space on the Vault server. I don't know about the SQL server as I will have to request info/access from IT.

1. I had a query succeed while 2 others were hung. So if this is a global space issue it must cause this stupid long hang rather than being detected/reported to the client.

2. The hangs are close to 10 minutes long (still not an accurate measure, but they are reeeaaallllyyyy long).

3. Queries "by version" actually work. I didn't think this was the case, but my previous "remembered" failures may not have actually gotten that check box checked. (Since this SHOULD be the default, it is rather annoying that I cannot configure it to be so.)

--- Maybe this is why the merge branches wizard still works, dunno ---

4. "by item" queries starting back to 1/1/2009 work, but queries back to 1/1/2008 fail. There should actually be history entries for the SOURCE files of these BRANCHES, but the "top level" folders themselves don't go back that far.

HOWEVER, unconstrained "by item" queries on the SOURCE FOLDERS from which these branches started ACTUALLY WORK. OK, they get truncated at the 1000 rows setting, but they do not hang/fail.

[Beth]

We don't have a BlackBerry app for Vault, so I'm not sure what you mean that it threw changes away. Can you explain further?

I'd like to see your Vault server log as well. Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread? If you can get the Vault server log from the Vault server at %windir%\temp\sgvault\sgvault.log, can you send that at the same time?

[GregM]

BB, as in phpBB, the forum software

[Beth]

Thanks Greg.

[Virgil Smith]

The relevant server log snippet follows (the only other contents werethe header line and Login/Logout statements from our Build/CI Server).

----8/8/2012 9:46:54 AM VSmith--205.162.232.254(205.162.232.254)--SSL Enabled System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
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.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at VaultServiceSQL.VaultSqlSCC.QueryHistory(VaultSqlConn conn, Int32 nUserID, Int32 nRowLimit, Int64 nTxID, VaultHistoryQueryRequest hqr, SqlDataReader& dr) 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.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at VaultServiceSQL.VaultSqlSCC.QueryHistory(VaultSqlConn conn, Int32 nUserID, Int32 nRowLimit, Int64 nTxID, VaultHistoryQueryRequest hqr, SqlDataReader& dr)
----8/8/2012 9:46:54 AM VSmith--205.162.232.254(205.162.232.254)--SSL Enabled BeginHistoryQuery returned: FailDBFault
----8/8/2012 10:06:12 AM VSmith--205.162.232.254(205.162.232.254)--SSL Enabled GetHistoryQueryItems returned: FailHistoryQueryNotFound
----8/8/2012 10:07:26 AM VSmith--205.162.232.254(205.162.232.254)--SSL Enabled EndHistoryQuery returned: FailHistoryQueryNotFound

[Beth]

On your Vault server where the Vault web files were installed, you will find the vault.config file. In there is an entry for <SqlCommandTimeout>360</SqlCommandTimeout>. Add an additional '0' to the 360, then save the file.

Recycle the VaultAppPool and then try the history again.


Recycling the VaultAppPool can be done one of two ways.
1) Go to Start - Run and type iisreset. This will recycle all of IIS.
2) (IIS6) Open your IIS Manager, expand Application Pools, right-click VaultAppPool and select Recycle.
(IIS7) Open your IIS Manager, click on Application Pools, click VaultAppPool and then look to the far right pane to click the Recycle link.

All of these methods will cause users to be disconnected from Vault. It is best to not disconnect users during uploading and downloading files, so you may need to perform the recycle at a convenient time or forewarn your users.

[Beth]

In addition to trying a longer timeout, rebuilding indices can often help with SQL timeouts.

Check out our KB article on Vault database maintenance: http://support.sourcegear.com/viewtopic.php?t=2924.

(Still need to check free space as well, which you are already looking into, or any kind of space limitations in the SQL Server for the databases.)