Move to new machine install errors

ekrauska · Post by **ekrauska** » Sat Dec 01, 2007 11:22 am

We are moving our Vault DB from a SQL 2000 machine to a SQL 2005 machine. the 2000 machine has version 4.0.5.15922 installed and is functioning. We backed up the sgvault and sgmaster DB's and did a restore on the SQL 2005 machine. Both db's restored fine. The SQL 2005 machine is not in the domain the 2000 machine is in.

After the DB's are restored, we run the install for the same exact version of Vault on the 2005 machine. We specify the exact same admin pwd for Vault. I have tried using Windows authentication and SQL authentication with sa with identicle outcomes. We get the following error:

Database 'sgvault' is already open and can only have one user at a time.

I adjust the DB to being MULTI_USER and try again. Sure enough, same error and the DB is left in SINGLE_USER mode again. I continue to set the mode back to MULTI_USER, attempt install again and get the same error. I'm at a loss. Please help. below is the log:

OK
Configuring your new Vault Installation
Checking for IIS Version...Requesting Vault Admin user password...OK
Connecting to the SQL Server...OK
Verifying the SQL Server requirements...OK
Checking for an existing databases...Found.
Asking for database's fate...Keep existing.
Upgrading the existing source control database...
This may take a long time. Do NOT stop this process!
Checking the installed database version...OK
Grant database access to NT AUTHORITY\NETWORK SERVICE...OK
Upgrading SourceGear master database schema...OK
Upgrading SourceGear source control database schema...OK
Upgrading SourceGear master stored procedures...OK
Upgrading SourceGear source control stored procedures...Database 'sgvault' is already open and can only have one user at a time.
Vault Setup is exiting due to a failure or cancellation. Error Code = -1280

lbauer · Post by **lbauer** » Sat Dec 01, 2007 12:35 pm

Since you're going to be using the same version of Vault, you could try installing Vault first, then restoring the database, and then running the scripts in this KB article to update the database user:

http://support.sourcegear.com/viewtopic.php?t=924

There seems to be some problem when the installer is accessing the database, and these steps will bypass that.

Let us know if this does not resolve the problem.

ekrauska · Post by **ekrauska** » Sun Dec 02, 2007 8:46 am

the instructions say I have to drop the user, but when I attempt to drop sgvaultuser from the DB I a SQL Error 15138, The database principal owns a schema in the database, and cannot be dropped.

I attempted to login anyway via the Admin webpage and I get the following error:

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

and in the event log:

Login failed for user 'sgvaultuser'. [CLIENT: <local machine>]

ekrauska · Post by **ekrauska** » Sun Dec 02, 2007 8:50 am

Disregard the previous post.

I was able to go in and delete the appropriate schema and then delete the user from the db. Still no go though. I still get the same error when attempting to connect to the db via web admin page:

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

(edit) A bit more information. I uninstalled, detached the original DB, and reinstalled. I then logged in to the empty vault DB with no issues. I then detached, attached original and attempted to login. I now get:

Login Failed: A database error has occured (FailDBTransaction)

ekrauska · Post by **ekrauska** » Sun Dec 02, 2007 9:20 am

okay, it looks like I got it working. For some reason after that transact failure, I was able to begin logging in and everythign looks like its still in the repository.

I do have an issue in the Admin manager though. Any of the nodes under my "Projects" repository causes the following error:
Error
Object reference not set to an instance of an object.

I can't obliterate, undo checkout, nothing under this repository. What can be causing this?

lbauer · Post by **lbauer** » Mon Dec 03, 2007 11:43 am

Do you have other repositories that are not affected?
Or is this a problem for all repositories?

Send me a copy of the Vault Server log. It's sgvault.log in %windir%\temp\sgvault on the server machine.