SourceGear Support

I am going to purchase a new version of vault and upgrad from version 3.1.9 ... TODAY! Are there any special steps to take when doing this? This is actually for a client, and they are kinda rushing things, I just want to make sure that things go smooth ... so please provide me with links to upgrade ...

We have a vault server with quite a few repositories on it.

We would like to move a single repository (not the entire database) to another vault server with all of its history in tact ... is this possible ???

We are using version 3.1.9.

Jay Johnson

I upgraded from 3.1.1 to 3.1.9. On the web server I have my IIS web site listed "SourceGearVault". Its home directory is "C:\Inetpub\wwwroot\SourceGearVault". Under that site there is: * "VaultService" * "VaultShadowFolder: These 2 items reside in the following dir...

One thing I noticed was it seems to be using either NT AUTH, or the domain user I setup with IdentitySwitcher. The web.config is not using the SQL auth. I thought it was using 'sgvaultuser' but it apparently is not. I could use some help understanding this. I would like to know if it is secure using...

Well I finally found all the posts I needed to get this done. Everything seems to work. This was the link I needed to fix the Active Directory integration: http://support.sourcegear.com/viewtopic.php?t=6814&highlight=active After running the IndentitySwitcher ... I still had to goto the "Se...

Well this is fun :) . I now seem to have upgraded, and I am able to log in with the admin tool. I manually added the 'sgvaultuser' to MS SQL, and then un-installed and re-installed. Now it seems that my users that are set up for Active Directory authentication cannot log in. I have a CCNET build use...

removed

I noticed my database does not have a 'sgvaultuser' listed under Users.

Any reason why I wouldn't have this user?

I know it did before the upgrade.

Jay Johnson

After reading through the forums I found some things that might help. I was able to upgrade the server, as far as I can tell. The installer went through, said it updated the schema, and said everything was fine. When I tried to connect to Vault using the Vault Admin Tool, I got the following: "...

Ok ... I think I might have found where I went wrong. During setup when I thought I was specifying the a database user for Vault to use for all of its database transactions, I should have entered a user with Admin rights just for installation purposes. The whole create a new user thing I did was wro...

I thought I had everything ready to go, and I would not run into any issues. Here is what I did: 1.) Backed up my database through the Vault Admin Tool, and MS SQL Enterprise manager. 2.) Create a new SQL user with SQL authentication in MS SQL with the same rights as the 'sgvaultuser'. 3.) Installed...

I currently have Vault server version 3.1.1.3506 running. I want to upgrade to 3.1.9. I have the database backed up, but what I do not have is the 3.1.1.3506 install executable. Is there an archive link that would give me access to the 3.1.1.3506 install exe? I would imaging in order to roll back (i...

For the client(s) and admin tool upgrades, do I have to uninstall the previous version, or does the installer take care of all that for me?

Thank you.

I am upgrading from 3.0. I have a few CC.NET build servers setup that are currently pulling code from Vault. Will I have to do anything other than updating the Vault clients on the build machines? Here is the entry from my CCNet.config file: <sourcecontrol type="vault" autoGetSource="...