Error on upgrade from 2.0.6 to 3.5, SQL Server 2005

mbrit · Post by **mbrit** » Wed Aug 30, 2006 4:50 pm

Hi,

I'm attempting to upgrade from Vault 2.0.6 to 3.5 with a SQL Server 2005 server (different physical machine to the Vault Server) and am getting the followign output.

This was immediately done after doing a SQL Server backup of the database. No users are logged on to Vault.

OK
Upgrading your Vault configuration.
Checking for IIS Version...Connecting to the SQL Server...OK
Verifying the SQL Server requirements...OK
Requesting Vault Admin user password...OK
Upgrading the existing Vault database...
This may take a long time. Do NOT stop this process!
Checking the installed database version...OK
Upgrading SourceGear Vault database schema...Database 'sgvault' is already open and can only have one user at a time.
Cannot find either column "dbo" or the user-defined function or aggregate "dbo.ufnmd5_3100", or the name is ambiguous.
Cannot find either column "dbo" or the user-defined function or aggregate "dbo.ufnmd5_3100", or the name is ambiguous.
Cannot find either column "dbo" or the user-defined function or aggregate "dbo.ufnmd5_3100", or the name is ambiguous.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Vault Upgrade Setup is exiting due to a failure or cancellation. Error Code = -1001
Please press OK to continue installing the Client and Admin Tools (if selected).

Can anyone help?

Matthew

lbauer · Post by **lbauer** » Thu Aug 31, 2006 8:20 am

It's not clear from the errors just what the problem is. We suggest starting over:

1) Uninstall Vault Server
2) Restore the backup you made before the upgrade.
3) Re-cycle the SQL Server service
3) Try the upgrade to Vault 3.1.9 first
4) Backup the database
5) Upgrade to Vault 3.5

mbrit · Post by **mbrit** » Thu Aug 31, 2006 12:38 pm

Nope - results of the 3.1.9 install are as follows:

OK
Configuring your new Vault Installation
Checking for IIS Version...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...Database 'sgvault' is already open and can only have one user at a time.
Cannot find either column "dbo" or the user-defined function or aggregate "dbo.ufnmd5_3100", or the name is ambiguous.
Cannot find either column "dbo" or the user-defined function or aggregate "dbo.ufnmd5_3100", or the name is ambiguous.
Cannot find either column "dbo" or the user-defined function or aggregate "dbo.ufnmd5_3100", or the name is ambiguous.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Vault Setup is exiting due to a failure or cancellation. Error Code = -1280

lbauer · Post by **lbauer** » Thu Aug 31, 2006 1:49 pm

It looks like you are using SQL Server authentication for Vault's connection to the database. Is that correct?

If so, in the SQL Server set-up portion of the installation:

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

for the login name, are you entering the SQL Server sa user and password, or a user with equivalent rights to modify the database? The user would need to have db_owner and public privileges for the sgvault database.

mbrit · Post by **mbrit** » Thu Aug 31, 2006 2:09 pm

I'm logging on as sa.

I'm a bit confused - as you saying I should be logging on as sa, or as something else?

I will double-check that sa has db_owner and public rights over the database before I try the upgrade again.

lbauer · Post by **lbauer** » Thu Aug 31, 2006 2:34 pm

mbrit wrote:
I'm a bit confused - as you saying I should be logging on as sa, or as something else?

SA is fine.

mbrit · Post by **mbrit** » Thu Aug 31, 2006 2:53 pm

OK, so this time.

- Had 2.0.6 originally.
- Freshly restored 2.0.6 database.
- Uninstalled 2.0.6 server; kept database.
- Installed 3.0.7. This worked OK.
- Checked the repository - all looked OK.
- Uninstalled 3.0.7 server; kept database.

Tried to install 3.5.0, got this:

OK
Configuring your new Vault Installation
Checking for IIS Version...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...Database 'sgvault' is already open and can only have one user at a time.
Cannot find either column "dbo" or the user-defined function or aggregate "dbo.ufnmd5_3100", or the name is ambiguous.
Cannot find either column "dbo" or the user-defined function or aggregate "dbo.ufnmd5_3100", or the name is ambiguous.
Database 'sgvault' is already open and can only have one user at a time.
Database 'sgvault' is already open and can only have one user at a time.
Cannot find either column "dbo" or the user-defined function or aggregate "dbo.ufnmd5_3100", or the name is ambiguous.
Cannot drop the function 'dbo.ufngetunpinnedundeletedfolderskeleton_3100', because it does not exist or you do not have permission.
Cannot drop the function 'dbo.ufngetunpinnedfolderskeleton_3100', because it does not exist or you do not have permission.
Caution: Changing any part of an object name could break scripts and stored procedures.
Vault Setup is exiting due to a failure or cancellation. Error Code = -1280

Help!

lbauer · Post by **lbauer** » Fri Sep 01, 2006 10:16 am

We haven't seen these errors before, so we've asked mbrit to send us a copy of his Vault database so we can determine what the problem is.

drichardson · Post by **drichardson** » Sat Oct 14, 2006 11:14 pm

Has there been any progress with this? I am having the same problem with my upgrade to 3.5.

lbauer · Post by **lbauer** » Mon Oct 16, 2006 8:29 am

Yes, this was resolved by having mbrit upgrade in increments, and upgrading the schema with a SQL script we provided. We can try this for you, too.

Email support@sourcegear.com, attn: linda and I'll send you instructions.

Please provide a link to this forum post in your email

grandavenuesoftware · Post by **grandavenuesoftware** » Wed Feb 14, 2007 3:33 pm

lbauer wrote:Yes, this was resolved by having mbrit upgrade in increments, and upgrading the schema with a SQL script we provided. We can try this for you, too.

Email support@sourcegear.com, attn: linda and I'll send you instructions.

Please provide a link to this forum post in your email

We sent an email earlier today, asking about this procedure and script, but haven't heard anything back yet. Would it be possible for someone to post the solution here?

Sorry for the impatience, and thanks ahead of time,

Jim Ivey
Grand Avenue Software

lbauer · Post by **lbauer** » Thu Feb 15, 2007 7:25 am

I'm pulling together the information and will send something soon.

lbauer · Post by **lbauer** » Thu Feb 15, 2007 7:47 am

I sent you an email with the suggestion to first try upgrading to 3.0.7. If that's successfull, we continue with the next steps that helped the previous poster.

grandavenuesoftware · Post by **grandavenuesoftware** » Thu Feb 15, 2007 10:50 am

lbauer wrote:I sent you an email with the suggestion to first try upgrading to 3.0.7. If that's successfull, we continue with the next steps that helped the previous poster.

Thanks for the response. As you predicted, the 3.0.7 upgrade seemed to apply successfully. However, when we moved on to the next step, with upgrading to 3.1.9, we experienced the same errors as before.

What's the correct next step?

Thanks ahead of time,

Jim Ivey
Grand Avenue Software

lbauer · Post by **lbauer** » Thu Feb 15, 2007 12:50 pm

There were some steps before upgrading to 3.1.9. I've sent you an email regarding starting over, then running an upgrade script.