Installing Vault Server on a New Host with the Same SQL DB

[statpro]

Hi,
I've tried to migrate my current Vault Server to a new host following the instructions found in another post:

First, uninstall the existing Vault Server. When prompted, choose to Keep the database. (You might want to back up the database first).

Next, install Vault on the new Vault Server machine, pointing at the current database location. If Vault is on a different machine than SQL Server use a custom account for the IIS Process model for Windows Authentication or use SQL Server authentication.

If you use SQL Server authentication, the installer will prompt you for an account. This account should have SA or equivalent privileges so the installer can create the sgvaultuser account and login. The SA account is only used during the installation.

The installer will detect the database and ask if you want to keep it. Say Yes.

The Install proceeds correctly but hangs on the checking for exsisitng vault Database, reports none found. Tries to create a new "sgvault" Database but reports one already exists. This halts the installation.

Is there a reason/s that this could occur?

[lbauer]

What version of Vault are you installing? What is the version of SQL Server?

Are you installing to a named instance?

Are you installing Vault on the same machine as SQL Server or is the Vault Service going to be on a different machine?

Check the vault_install.log for for any errors regarding the connection to
SQL Server and creation of the database. This installation log is in your user's temp directory, %temp%.

[statpro]

What version of Vault are you installing? What is the version of SQL Server?

Are you installing to a named instance?

Are you installing Vault on the same machine as SQL Server or is the Vault Service going to be on a different machine?

Check the vault_install.log for for any errors regarding the connection to
SQL Server and creation of the database. This installation log is in your user's temp directory, %temp%.

Hi,

Installing Vault 3.5.2. Onto a Named Instance on a SQL2000 server, This is a separate server to the vault service.

There are no errors due to the product not installing far enough to connect to the SQL server.

Thanks

[lbauer]

The Install proceeds correctly but hangs on the checking for exsisitng vault Database, reports none found. Tries to create a new "sgvault" Database but reports one already exists. This halts the installation.

You might get this error if an sgvault database was detached from SQL Server but is still in the SQL Server Data directory.

If you're installing to a named instance, be sure to specify that in the SQL Server setup portion of the Vault Server installation. When you give the name of the SQL Server, use machinename/instancename, instead of "local" or just the machine name."

Also if SQL Server is on a different machine, you must use a custom account (domain account) in the IIS Process Model part of the installation if you are using Windows Authentication for SQL Server. Or, you can use SQL Server authentication.

[statpro]

Can the Install still take place without the uninstall of Vault on the Previous host?

So I can test your solution.

[lbauer]

Is the other Vault server connecting to the database that the new Vault server is being installed to?

If so, the new installation may change the account Vault is running under and may also change the database user, so that the other Vault server wouldn't be able to connect anymore.

If both Vault installations are using SQL Server authentication and the same Vault Admin password, then both may be still able to connect.

Please Note: you should not use two Vault servers to do source control operations on the same Vault repository -- it can cause database corruption.