2.0.6 -> 3.1.8 upgrade fails: Invalid object name

rbrother · Post by **rbrother** » Mon Apr 10, 2006 6:09 am

Vault 2.0.6 -> 3.1.8 upgrade attempt 10.4.2006:

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...Found.
Asking for database's fate...Keep existing.
Upgrading the existing Vault database...
This may take a long time. Do NOT stop this process!
Checking the installed database version...OK
Ensuring that sgvaultuser has access to the Vault database... Grant database access to sgvaultuser...OK
Upgrading SourceGear Vault database schema...OK
Checking Vault share information...OK
Checking Vault folder entry information...Invalid object name 'tbltransactionfsobjectversions'.
Working on repository: 3
Vault Setup is exiting due to a failure or cancellation. Error Code = 453

I have reverted to 2.0.6 DB backup and installation. Please give info to get the upgrade going on further. I have read similar upgrade problem threads from this forum but none seem to have exactly same problem.

mskrobul · Post by **mskrobul** » Mon Apr 10, 2006 9:14 am

First, we should check the schema version of your 2.0.6 database.
If you run the following SQL script, what do you get as the result?

use sgvault
go
select schemaversion from tblschemaversions

rbrother · Post by **rbrother** » Tue Apr 11, 2006 1:51 am

Schema version = 2.0.4.0

Post by **jclausius** » Tue Apr 11, 2006 8:53 am

Robert:

It could be a problem with the conversion to the new sharing format. I'd like to attempt the upgrade with the following steps:

1) Make a good backup the Vault 2.0.6 database.
2) As an intermediary, upgrade to Vault 3.0.7 Server.
3) If that installation succeeds, upgrade to Vault 3.1.8.

I'm guessing there is a problem in the middle step. By actually running the Vault 3.0.7 install, it will do the upgrade in a two step process.

Please post the results, so we can follow up.

Thanks.

Edit: Added 3.0.7 Server link

rbrother · Post by **rbrother** » Fri Apr 21, 2006 5:14 am

I was able to make the installation with no errors doing it with the two steps (2.0.6 -> 3.0.7 -> 3.1.

as you adviced. Thank you!

Post by **jclausius** » Fri Apr 21, 2006 8:22 am

There is a routine used to scan for inconsistencies in the source tree during upgrade. Unfortunately, the Vault 3.1.x upgrade code has some dependencies on structures set up by the Vault 3.0.x upgrade. However, in some cases, the Vault 3.1.x upgrade script runs before the Vault 3.0.x script.

We've logged the problem, but the current work around is to upgrade to Vault 3.0.x first - ensuring the 3.0.x schema is set in place, and then install Vault 3.1.x. This ensures no "catch-22" situation will come into play.

Thanks for your patience and feedback. It has been most helpful.