Fatal error 625 occurred

James Jeffers · Post by **James Jeffers** » Mon Sep 11, 2006 1:59 pm

Upon rebooting a server hosting our Vault instance, we see this:

----9/11/2006 3:44:45 PM     Jjeffers--172.31.70.186(172.31.70.186)--SSL Disabled	System.Data.SqlClient.SqlException: Warning: Fatal error 625 occurred at Sep 11 2006  3:44PM                   . Note the error and time, and contact your system administrator.
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
   at VaultServiceSQL.VaultSqlSCC.GetFSLockChanges(VaultSqlConn conn, Boolean bGetCheckoutListWithSecurity, Int32 nRepID, Int64 nBaseCheckoutListRevision, Int64 nTargetCheckoutListRevision, Int64 nTxID, Int32 nUserID, Boolean& bRefreshList, VaultCheckOutItemColl& coAddList, VaultCheckOutReleaseColl& coRelList)    at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
   at VaultServiceSQL.VaultSqlSCC.GetFSLockChanges(VaultSqlConn conn, Boolean bGetCheckoutListWithSecurity, Int32 nRepID, Int64 nBaseCheckoutListRevision, Int64 nTargetCheckoutListRevision, Int64 nTxID, Int32 nUserID, Boolean& bRefreshList, VaultCheckOutItemColl& coAddList, VaultCheckOutReleaseColl& coRelList)
----9/11/2006 3:44:45 PM     Jjeffers--172.31.70.186(172.31.70.186)--SSL Disabled	GetCheckOutListChanges returned: FailDBReader

We're using v3.1.9.

Beth · Post by **Beth** » Mon Sep 11, 2006 2:32 pm

Besides the error, what symptoms are you having?

Can you provide me more information with you set up as well, such as server OS, SQL version, .NET version, client OS, other programs or services you are running from that server, etc.?

James Jeffers · Post by **James Jeffers** » Mon Sep 11, 2006 2:37 pm

Other symptoms include: no transactions can be complete with the GUI client.

We're using Windows Server 2003 and SQL Server 2000, MS .NET 1.1. We run a cruisecontrol(.net) service from this box.

This began to happen right after a reboot of the server.

Beth · Post by **Beth** » Mon Sep 11, 2006 2:42 pm

Are you able to connect to the server from a client?

Could you provide me with a Vault Server Log? You can either send it in a private messege through here, or send me an email at beth at sourcegear.com and just reference back to this post.

James Jeffers · Post by **James Jeffers** » Mon Sep 11, 2006 2:49 pm

I've sent you a copy of today's server log.

Beth · Post by **Beth** » Mon Sep 11, 2006 3:14 pm

Can you set the server to debug mode and send me a fresh log? To place the Vault Server into Debug mode, open the Vault Admin Tool and go to the Server Options tab. The second half of the window covers logging. Set the Log Level to Debug.

Are your other users not able to use Vault as well? It was looking like the errors where only occurring under your name.

In a web browser, load the page http://VAULTSERVER/VaultService/serverInstall.html, where VAULTSERVER is the hostname that you entered into the Vault client's login dialog, and let me know what happens.

James Jeffers · Post by **James Jeffers** » Tue Sep 12, 2006 6:38 am

After turning on debug:

Here is the page
<server name>.accipiter.com Server Installation
Version 3.1.9.3798 Installed 09 June 2006

Beth · Post by **Beth** » Tue Sep 12, 2006 2:47 pm

Just posting a quick update for other readers. Received log via email. Seeing what looks to be SQL errors. User suggested corrupted index. Having user run a dbcc checkdb against his database. For more information on that, please see the following KB article: http://support.sourcegear.com/viewtopic.php?t=2924

James Jeffers · Post by **James Jeffers** » Tue Sep 12, 2006 2:48 pm

As it turns out, the dbcc route didn't resolve the issue.
We restored the database from a daily back (from BEFORE the corruption), and things are working again.