Urgent: FailDBConn error when trying to connect to Vault

samuel_d_jack · Post by **samuel_d_jack** » Mon Apr 25, 2005 8:27 am

Hello,
I have just moved my Vault installation and Database from a Small Business Server 2003 machine to a Windows Server 2003 machine.

I succesfully moved the database (use Backup/Restore) and installed Vault Server on the new machine. I worked for a while (I was able to connect with Admin and Client tools from other machines) but then it stopped working. It seemed to stop when I enable mixed-mode security on SQL Server.

I get the FailDBConn error message and the sgvault.log file says the following:

----25/04/2005 14:50:02 sgvaultsystem--()--
System Started
Version 3.0.6.2856
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://######/VaultService
Identity = NT AUTHORITY\NETWORK SERVICE
----25/04/2005 14:50:18 --()-- Vault Failed to establish a connection to the database.
----25/04/2005 14:50:18 --()-- SQL Server does not exist or access denied.
----25/04/2005 14:50:18 --()-- Vault Failed to establish a connection to the database.
----25/04/2005 14:50:18 --()-- SQL Server does not exist or access denied.
----25/04/2005 14:50:18 --()-- The session information was not removed from the database. Please check sgvault.dbo.tblsessions within SQL Server. There may be orphaned sessions stored within the database. Error: FailDBConn
----25/04/2005 14:50:20 --####(127.0.0.1)--SSL Disabled Vault Failed to establish a connection to the database.
----25/04/2005 14:50:20 --####(127.0.0.1)--SSL Disabled SQL Server does not exist or access denied.
----25/04/2005 14:50:20 Admin--####(127.0.0.1)--SSL Disabled Vault Failed to establish a connection to the database.
----25/04/2005 14:50:20 Admin--#####(127.0.0.1)--SSL Disabled SQL Server does not exist or access denied.
----25/04/2005 14:52:17 --####(192.168.1.1)--SSL Disabled Vault Failed to establish a connection to the database.
----25/04/2005 14:52:17 --#####(192.168.1.1)--SSL Disabled SQL Server does not exist or access denied.
----25/04/2005 14:52:17 --####(192.168.1.1)--SSL Disabled Vault Failed to establish a connection to the database.
----25/04/2005 14:52:17 --####(192.168.1.1)--SSL Disabled SQL Server does not exist or access denied.
----25/04/2005 14:52:26 sam.jack--####(192.168.1.1)--SSL Disabled Vault Failed to establish a connection to the database.
----25/04/2005 14:52:26 sam.jack--#####(192.168.1.1)--SSL Disabled SQL Server does not exist or access denied.
----25/04/2005 14:52:51 sam.jack--####(192.168.1.1)--SSL Disabled Vault Failed to establish a connection to the database.
----25/04/2005 14:52:51 sam.jack--####(192.168.1.1)--SSL Disabled SQL Server does not exist or access denied.
----25/04/2005 14:53:28 sam.jack--####(192.168.1.1)--SSL Disabled Vault Failed to establish a connection to the database.
----25/04/2005 14:53:28 sam.jack--####(192.168.1.1)--SSL Disabled SQL Server does not exist or access denied.
----25/04/2005 14:56:39 Admin--###(127.0.0.1)--SSL Disabled Vault Failed to establish a connection to the database.
----25/04/2005 14:56:39 Admin--####(127.0.0.1)--SSL Disabled SQL Server does not exist or access denied.

I've tried various things like reinstalling Vault, and following the adice in th KB article linked to by the error message but I can't get it to work.

Thanks for your help.

Post by **jclausius** » Mon Apr 25, 2005 8:46 am

Perhaps the "easiest" thing to do would be to uninstall the Vault server (Keeping the database) and re-install the Vault server (Keeping the database).

If you would like, we could also try to manually track down the problem.

samuel_d_jack · Post by **samuel_d_jack** » Mon Apr 25, 2005 8:57 am

I've tried uninstalling and reinstalling and that doesn't work.

I think we need to track this down manually.

Post by **jclausius** » Mon Apr 25, 2005 9:20 am

It turned out the Vault server was not connecting to the named instance when using (local)\instancename for the configuration.

We changed the connect string to use the machinename\instancename, and Vault server was able to connect.