Upgrading free version

[jtfml]

Hi,

I'm a one-man shop using the "free" version of vault on an XP laptop (Vault version 3.5.1.4786). I have just obtained a Windows 7 laptop and am in the process of installing the development environment onto it. I have not yet installed Vault because I need to be able to import the database. I have found the following page, [url]http://support.sourcegear.com/viewtopic ... pro#p49231[/url], which has a lot of good information. However, at the top, it mentions the license keys. I'm not sure what those would be for the free version. I am planning to upgrade in stages, like the article says, but I'm not sure where to obtain the incremental versions. I also would like to upgrade to the professional version but I'm not sure if I should do that at the earlier versions or as the last step. Finally, I'll be moving the database from one PC to another, but I don't have a domain set up and so I can't easily do a data export that creates the database in the process because I have to use the NetPipes connection to create a connection to a remote SQL Server engine, so I think I'll have to backup, move, and restore. So, let me get to the questions.

Where can I get the intermediate versions of Vault?
Where can I find the license key for my "free" version (single-user)?
Should I do the upgrade to the Professional version as the last step?
Is there anything I should be wary of when creating a backup of the database and moving it to the new laptop to restore it?

Thanks for your help!

JT

[Beth]

Where can I get the intermediate versions of Vault?

Go to this link for the intermediate versions of Vault Standard: http://www.sourcegear.com/vault/downloa ... uote]Where can I find the license key for my "free" version (single-user)?[/quote]No need to worry about that. The part about license keys only applies to those who buy licenses.

Should I do the upgrade to the Professional version as the last step?

You can upgrade Vault Standard up to Vault 4.1.4 and then jump from there to Vault Professional, but you will need to uninstall Vault Standard before installing Vault Professional.

Is there anything I should be wary of when creating a backup of the database and moving it to the new laptop to restore it?

Make sure you make a full backup of sgvault and sgmaster before starting.

Here's your steps in full:

• 1) Backup sgvault and sgmaster.
  2) Upgrade Vault 3.5.1 to Vault 4.0.6. Don't bother installing the client, just upgrade the server portion.
  3) Upgrade to Vault 4.1.4.
  4) Backup sgvault and sgmaster, but don't overwrite your original ones in case something goes wrong.
  5) Restore the last backups of sgvault and sgmaster to your new machine that has SQL Server on it or SQL Server Express.
  6) Install Vault 5.1.1 Professional.
  7) Install the Vault 5.1.1 client.

[jtfml]

Hi Beth,

Thanks for your help. According to the other page I referenced, there is not an sgmaster database before version 4.x, and I can't find one on my system, so once that appears I'll back it up.

I just double-checked the other link and in item 7 it also mentions that I can jump from 4.1.4 Standard directly to 5.1.1 Professional, so reassures me that I don't need to install version 5.0.4 along the way. Plus, I see where I missed the link for the previous releases (thanks).

Also, what's not clear is whether or not I should be installing and uninstalling each version along the way or if I can just install on top of the previous versions. I get the impression that the reason for incremental upgrades is to modify the databases and not particularly to add libraries or make registry changes. So I guess my final question is:

Should I uninstall after each step?

Thanks again!

...
Began the process and here's what happened. (actual machine names are not "x" and "y")

I ran into an unforeseen problem. A while back I changed my machine name from x to y. The upgrade from 3.5.1 to 3.5.3 went very smoothly even though when I looked at the vault_install.log file it showed "x\ASPNET" instead of "y\ASPNET" as the user name for the vault service. However, trying to upgrade to 4.0.6, it failed saying, "The stored procedure to grant a Windows Login database access failed. Windows NT user or group 'y\ASPNET' not found. Check the name again.
The user, y\ASPNET, could not be added as a SQL Server login. Please verify the windows account exists on this machine.

Note, on some database collations check the case of the user's name."

Because I can't differentiate between x\ASPNET and y\ASPNET when creating a user, I can't create the old version of the user. Is there a way to reconfigure Vault to look at the new user when running the installation?

I went into the database and removed the x\ASPNET user and added the y\ASPNET user and attempted the installation again. No change. I attempted to restore the 3.5.3 backup and with a small snag I was able to restore it, however I cannot reinstall version 3.5.3 of the Vault server, admin, and client because of the same error, so I no longer have access to any source control!

...

I updated SQL Server by removing the old x\ASPNET user from the logins and updated all of the database users to use the new y\ASPNET user. I then reinstalled 3.5.3 successfully, but now I can't log in with my old account. I get the following error:
Your serial number is not a valid serial number. User logins are currently disabled.
If I try to log into the admin client I get the following error:
The username or password supplied is invalid.

I am not typing them wrong. I'm wondering if somehow the web service affects how the passwords are decrypted because it's now using a different username (y\ASPNET). If I have a new "serial number" is that being used to decrypt my passwords?

I'm going to try uninstalling and reinstalling one more time to make sure I didn't mistype the admin password in the installation process.

...

No. I reinstalled and retyped it correctly. I still cannot gain access to Vault even though I've reinstalled successfully. This has now been an all day effort. It's now 7:30 PM from 10:00 AM this morning.


Please help me resolve this soon!

Thanks,

[Beth]

there is not an sgmaster database before version 4.x

Correct.

I just double-checked the other link and in item 7 it also mentions that I can jump from 4.1.4 Standard directly to 5.1.1 Professional, so reassures me that I don't need to install version 5.0.4 along the way.

Sorry, 5.0.4 should be in there too.

You don't need to uninstall after each install. The only place where you would need to uninstall is if you are going from Vault Standard to Professional and the Standard version is currently installed.

On the users, it would be best to not try creating them in SQL Server manually. You could try removing the ASPNET user and letting Vault add it.

For the rest of it, it might be easier if I could take a more direct look. Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?

[jtfml]

Okay, I sent the email.

Thanks.

[jtfml]

Hey Beth,

I just wanted to put this out on the forum. As you know, after getting over the hump of installing version 4.0.6, everything seemed to go very smoothly and the issue seemed to be related to my machine name/ASPNET account.

Thanks for your help, and I'm excited about the Pro version of Vault!

JT

[Beth]

Thank you for the update.

For future users, the aspnet account did not appear to have db_owner permissions to the sgvault database. Once that account was given db_owner permissions, it worked. I'm unsure of how it ended up without the permissions it needed.