3.1.0 Upgrade Issue

davidgottlieb · Post by **davidgottlieb** » Wed Dec 07, 2005 11:39 am

We are currently attempting to upgrade our vault installation from 3.1.0 to 3.1.5 and are unable to because of database issues. Originally, our issue seemed to be that it could not connect to the database but when we had our DBA look into it, every time we run this install it is deleting the SQL user used to talk to the vault database. At this point our development efforts have been brought to a halt because our source control is down.

Any ideas here?

Thanks,

David Gottlieb

davidgottlieb · Post by **davidgottlieb** » Wed Dec 07, 2005 12:04 pm

Just a note. We are able to log into the database with query analyzer until we run the install.

When it is running the install on the database, it obviously can connect to the database because it says that we already have an existing vault database but when it attempts to log in and run the scripts to upgrade it, we get the error that it can't log in. After that happens and we go to query analyzer to log in, the user has been deleted and our DBA has to go re-create it in which case we are back at square 1. Can we get some feedback on this please?

davidgottlieb · Post by **davidgottlieb** » Wed Dec 07, 2005 12:11 pm

Another note. We originally tried just upgrading the instance of vault without uninstalling the existing version on the server. However, when we tried to do that, when asking us for a database instance, the database server field was grayed out with (local) in it which is not where our vault database resides therefore we attempted to uninstall vault from the server all together and do a fresh reinstall which is when we began to encounter these issues.

davidgottlieb · Post by **davidgottlieb** » Wed Dec 07, 2005 1:57 pm

Here is the screen shot of the error we are receiving on install.

lbauer · Post by **lbauer** » Wed Dec 07, 2005 2:55 pm

Did you move the database after your original installation? That could by why the upgrade can't find it.

The installer will create (or recreate) the database user, so your DBA shouldn't have to do that.

Are you using SQL Server authentication or Windows Authentication? If SQL Server authentication, be sure to enter the name and password of the SA account (or equivalent) in the SQL Server Setup portion of installtion, so that the installer has adequate permission to modify the database.

If you're using Windows Authentication and SQL Server is on a different machine, you need to use a custom account for the IIS Process Model portion of the installation. The installer will then create a login and database roles for this custom account in SQL Server. In this case, the installer will use your credentials (as the user logged into the machine) to install Vault and modify the SQL Server database.

See screenshots here:

http://www.sourcegear.com/vault/support ... orial.html
http://www.sourcegear.com/vault/support ... orial.html

If you continue to experience difficulty, email me a copy of the vault_install.log file from your user's temp directory. Email to linda at sourcegear.com