Problem Logging in

switchcall · Post by **switchcall** » Wed Apr 04, 2007 9:21 am

Hi,

I am having trouble logging in to the Vault Admin tool. I have followed the FAQ at http://support.sourcegear.com/viewtopic.php?p=2450 but I still can not log in.

I resatarted the server to try and clear the problem, but the first time i try and log in I get the following error message;

Collection cannot be null.
Parameter name: c
After the first attempt other logins receive this error message;

The Vault Server could not establish a connection to the database. Please check the server's log for detailed information. (FailDBConn)

If I restart IIS, I get the first error message. With subsequent logins I get the second error message.

Having looked at the log file there are only two entries for today at 8:55am this morning. The log file (attached) seems to have not been written to since then, despite several failed attempts to log in and a fair bit of activity checking files in and out.

I have made no changes to the configuration of the server (which houses both sourcegear and my SQL Server DB), so am struggling to understand what has happened?

Can anyone suggest a solution. I'm kinda stuck here!

lbauer · Post by **lbauer** » Wed Apr 04, 2007 9:34 am

Your log didn't get attached. Could you email support at sourcegear.com ATTN Linda, and send a copy of the log?

Also, what version of Vault are you using? Was Vault working with no problems before this?

switchcall · Post by **switchcall** » Thu Apr 05, 2007 1:09 am

I have emailed the log file to support. Thanks.

Everything has been working fine with SourceGear for about 4 months, up until yesterday afternoon, when I began getting the unable to connect messages.

I am using SourceGear Vault v3.5.1 (4786)

lbauer · Post by **lbauer** » Thu Apr 05, 2007 2:02 pm

Only two lines in that log. Could you find the log prior to this one and email it?

By default, the log is archived weekly in the %windir%\temp\sgvault folder.

Another option -- do you have good backup of your database? The error you are getting shows there may be a problem with your database. If you have a recent backup, restoring that might be the quickest option.

switchcall · Post by **switchcall** » Thu Apr 12, 2007 1:08 am

Just as a follow up. I could not resolve the problem. The only solution was to install SG on a different server and migrate the SG database - attempting to connect to the existing db with a new installation of SG gave the same error. New server, new SG installation, new copy of the DB!

lbauer · Post by **lbauer** » Fri Apr 13, 2007 3:31 pm

Another possible solution would be to run the installer over the existing installation with the Repair option.