Error while installing Vault 3.5.2 on Vista

Glebby · Post by **Glebby** » Mon Apr 23, 2007 1:10 am

Trying to upgrade existing Vault 3.5.0 installation and get:

Upgrading SourceGear Vault database schema...ALTER TABLE statement conflicted with COLUMN FOREIGN KEY constraint 'fk_tblrepositories_tblcheckoutlists'. The conflict occurred in database 'sgvault', table 'tblcheckoutlists', column 'colistid'.
Vault Setup is exiting due to a failure or cancellation. Error Code = -1280

Please advise.

Beth · Post by **Beth** » Mon Apr 23, 2007 7:58 am

What version of SQL server are you using?
Is your SQL server on a different machine?
Was Vault 3.5.0 already installed on that Vista machine?

Basically, can you tell me your previous set-up details?

Beth · Post by **Beth** » Mon Apr 23, 2007 9:13 am

Two more things:

Can you provide a Vault install log? The vault_install.log file should be located in the windows temp directory (%temp%).

And can you check schema version this database is currently at? Run the following query on your database in the Query Analyzer and let me know the results:

Code: Select all

SELECT schemaversion from sgvault.dbo.tblschemaversions where productkey = 'SG Vault'

Glebby · Post by **Glebby** » Tue Apr 24, 2007 1:19 am

1) I use SQL 2000 Desktop Engine
2) It runs on the same machine
3) Vault 3.5.0 was previously installed on this machine. After the installation of 3.5.2 has failed, I installed 3.5.0 back again without a problem.
4) I use all default setup settings
5) there is no vault_install.log file in %temp% (C:\Windows\Temp\sgvault) directory. I see other vault log files here but vault_install.log
6) The schema version is 3.5.0.10

May the error be related to that I have some files checked out during install?

Beth · Post by **Beth** » Tue Apr 24, 2007 9:24 am

When you reverted back to 3.5.0, did you use a database backup and restore that first? Vault 3.5.2 will make some changes to the database that may not work well with 3.5.0. If not, before beginning work, I would suggest you detach the database and rename it, uninstall Vault, perform a restore on the previous database before the restore, and then reinstall the 3.5.0.

I think we need to dig further into your database to see what's going on. Can you send an email to support at sourcegear.com (attn: Beth) and include a link to this post so I have the history so far on this?

Glebby · Post by **Glebby** » Tue Apr 24, 2007 12:47 pm

No, I didn't restore DB when reverted back to 3.5.0, but Vault seems to work well - because I got the error at very first steps so no DB changes were performed to break the compatibility.

I will send an email, thank you.