Binary SQL Upgrade Problem

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
baronej
Posts: 9
Joined: Thu Oct 07, 2004 9:51 am
Location: Alexandria, VA

Binary SQL Upgrade Problem

Post by baronej » Fri Sep 16, 2005 9:50 am

I'm trying to upgrade the Vault Server from 3.1.1 to 3.1.2. The SQL Server instance is set up as Binary Collated.

During the upgrade, I get an error that the SGVAULT database cannot be found. My Vault db is named "sgvault". See attachment to see the error I am getting.

Thanks in advance for your help.

John Barone
Attachments
Vault Upgrade Error.gif
Screenshot of install error
Vault Upgrade Error.gif (24.44 KiB) Viewed 3504 times

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Fri Sep 16, 2005 9:54 am

Email me a copy of the Vault install log. It’s called vault_install.log and is in your user’s temp directory, usually C:\Documents and Settings\<username>\Local Settings\TEMP or type %temp% in an address bar. Send it to Linda at SourceGear.com.
Linda Bauer
SourceGear
Technical Support Manager

mabster
Posts: 12
Joined: Wed Dec 15, 2004 9:53 pm

Post by mabster » Sun Oct 09, 2005 11:01 pm

I just tried upgrading to 3.1.2 and got the same error. We also use binary collation on our server, with a database name of 'sgvault' (lower case).

Anything I can do to resolve this?

Cheers!

mabster
Posts: 12
Joined: Wed Dec 15, 2004 9:53 pm

Post by mabster » Tue Oct 11, 2005 9:39 pm

(bump)

Anyone?

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Wed Oct 12, 2005 2:06 pm

We have discovered a bug in the Vault 3.1.2 upgrade that prevents it from
upgrading if SQL is set up as Binary Collated.

We've fixed this for Vault 3.1.3, which will be released in a few weeks. If you need a solution sooner, email linda at Sourcegear.com.
Linda Bauer
SourceGear
Technical Support Manager

mabster
Posts: 12
Joined: Wed Dec 15, 2004 9:53 pm

Post by mabster » Wed Oct 12, 2005 4:37 pm

Thanks for that. We'll hold off 'til 3.1.3.

Post Reply