Moving Vault to new server

[rklaassen]

I have followed the instructions from the posts by jclausius and jeremy_sg on this forum but cannot install Vault on my new server (Databases have been Detached, moved and Attached to new server. I'm using my Windows Authentication and have full admin rights to the server and sysadmin rights to the SQL Server 2012 instance (prior server was SQL Server 2005).

Results of install:
Looking for IIS Version
Configuring your new Vault Standard Installation
Requesting the IIS Process User...
Pre-Website Check...

Entering Website Check...
Looking for websites on this machine...
Looking for websites on this machine...
Prepped IIS Path : IIS://LocalHost/W3SVC. Preparing to do directory entry
Directory Entry succeeded : W3SVC
W3SVC child is FILTERS
W3SVC child is APPPOOLS
W3SVC child is INFO
W3SVC child is 1
1Added to _websites
Found website - 'Default Web Site'

Successfully exited Website Check...
Creating the Virtual Directory, VaultService...Already Exists.
Creating the Virtual Directory, SgDav...Already Exists.
Creating the Virtual Directory, VaultShadowFolder...Already Exists.
Requesting Admin user password...OK
Connecting to the SQL Server...OK
Verifying the SQL Server requirements...OK
Checking for 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!
Found 'Auto Update Statistics' ON for database sgvault -- setting it to OFF...User does not have permission to alter database 'sgvault', the database does not exist, or the database is not in a state that allows access checks.
ALTER DATABASE statement failed.
Vault Standard Setup is exiting due to a failure or cancellation. Error Code = -1280

[Beth]

When you are connecting to SQL Server, are you using Windows authentication or SQL authentication?

Is SQL Server on the same machine or a different machine than where you are installing the Vault server?

[rklaassen]

I'm using Windows Authentication (I'm a Domain and SQLServer Admin).

I'm trying to install Vault on the same server as the database.

Ray

[Beth]

Is your SQL Server configured to allow SQL authentication as well? If so, try installing using SQL authentication and login with the 'sa' account. If it can work with the 'sa' account, then there still is something wrong with your permissions.

If it doesn't work with the 'sa' account, then I'm going to have you try restoring the SQL 2005 database so that it gets upgraded by SQL 2012 rather than using attach.

[rklaassen]

Using the SA password it progressed past the previous point of failure, but now indicates that it can't find the stored procedure sp_dboption.

P.S.
I'm trying to install Vault 5.1.1 (64 bit) which is what I have been running. I have paid my maintenance fees so should I download the latest version of Vault and install that?

Ray

[Beth]

Vault 5.1.x doesn't support SQL 2012. Before upgrading, let's double check your licenses. Once we're sure we have your licenses set, then I'd say yes, go ahead and upgrade to Vault 6.1.0.

Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?

[rklaassen]

Beth:
I sent you an email last night updating you on the status of my issue. Since I haven't heard back, I'm posting what I sent you here.

I logged on to the Customer Service Portal and downloaded the key for Vault 6.1 (2 users).

I then ran the install on the new server and everything ran fine, i.e. install completed without error. However the install finishes by bringing up a browser to log in as “admin” which is where I thought I would have to enter the key. It wouldn’t accept the admin user/password I entered so I wasn’t able to complete it

Would it work better if I ?
-Restored my backup to my old server.
-Upgraded from Vault 5.1 to Vault 6.1 on that old server.
-Then migrated the database to the new server.
-Install Vault 6.1 on the new server.

Ray

[Beth]

I had responded last night, but hadn't heard back. If you find that email, you can ignore it, because I'll have you do something else here.

Try an uninstall, but choose the option to keep your database.

Then run the installer again. It will allow you to set your password. then try logging in.

If that still doesn't work, I'm going to suggest we continue offline with this.

HS: 227585