Upgrade from 3.0.5 to 3.1.9

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
gmshanes
Posts: 3
Joined: Tue Nov 21, 2006 11:34 am

Upgrade from 3.0.5 to 3.1.9

Post by gmshanes » Tue Nov 21, 2006 12:00 pm

I made a backup of my sgvault database and restored it on a different SQL server, I am moving from SQL2000 to SQL2005. I am also installing 3.1.9 on a new server, so I should be alright using 3.0.5 until I get this going.


I got a message during the install that I needed an account common to both machines, so I setup a domain account that I am using to install vault, run the IIS process, and is the owner of the sgvault database on the new SQL server. After I choose to connect to SQL, I use Windows Authentication since I am logged in as a dbo_owner on the sgvault database, and I get the following message.


"OK
Configuring your new Vault Installation
Requesting Vault Admin user password...OK
Connecting to the SQL Server...OK
Verifying the SQL Server requirements...OK
Checking for an existing Vault database...Not found.
Creating a new Vault database on SQLdistributor...
Creating the SourceGear Vault database...CREATE DATABASE permission denied in database 'master'.
Vault Setup is exiting due to a failure or cancellation. Error Code = 402"

I am going to get with our DBA and work on the create CREATE DATABASE problem, but right before that it says "Checking for an existing Vault database...Not found." Should it be finding my database so it can convert it to the new format?

I also wanted to make sure I was picking the right Collation. SQL_Latin1_General_CP1_CI_AS is what SQL says the collation is; I have been choosing the default "Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode Data" collation, is that correct?

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Tue Nov 21, 2006 1:29 pm

If you use Windows authentication for the SQL Server Setup portion of the installation, the Vault installer uses the credentials of the logged in user (you) to modify the database. You need to have SA rights or the equivalent, because you're modifying more than the sgvault database -- the installer also adds the SQL Server login for your domain account.
Checking for an existing Vault database...Not found.


During the installation, did you point the installer to the machine with the restored database?

Do you have SQL Server 2005 Express? By default this installs as an instance -- machine\SQLExpress.
Linda Bauer
SourceGear
Technical Support Manager

gmshanes
Posts: 3
Joined: Tue Nov 21, 2006 11:34 am

Post by gmshanes » Tue Nov 21, 2006 1:37 pm

It is SQL2005 Standard Edition. I put the name of that SQL server in for the instance.

"Connecting to the SQL Server...OK
Verifying the SQL Server requirements...OK
Checking for an existing Vault database...Not found.
Creating a new Vault database on SQLdistributor..."

If I am reading this right it can connect to the database, and SQLDistributor on the last line is the right server name. I am still waiting to get with the DBA and add more permissions, so hopefully that is all it's going to take.

Post Reply