We've been using Vault for work projects and now I wanted to try and use it for my personal projects using the free single user license.
We have Vault server 3.5.1 installed at work and I had client 3.5.1 working from both client PCs I work on (Windows XP Pro). I was able to connect, check in, check out, etc.
I installed server 4.0.6 on one of these PCs, the one I do most of my personal projects on. During the installation, I also installed client 4.0.6 and it connects fine to the local server. However, when I try to connect to my work server now, I get the error message "the server uses a protocol that is not supported by this client".
I tried to uninstall client 4.0.6 and install client 3.5.1 and the install appears to complete successfully, but still client 4.0.6 always runs and won't allow me to connect to the server at work.
What are my options? Install 3.5.1 at home so it works with home and work?
Installing vault server 4.0.6/client 3.5.1 runs client 4.0.6
Moderator: SourceGear
We have not really tested having both Vault a 3.5.x and Vault 4.x.
While it's possible to have both on the same machine, it's rather tricky. First, you will need to uninstall both Vault 3.5.x and Vault 4.x. You may need to go through the registry and search for "Vault client" and delete registry entries that reference the Vault client.
*be sure to backup your registry first*
Then install Vault client 3.5.x. Copy the contents of the Vault client directory and paste them into a directory somewhere else on your local machine. Then install Vault client 4.0.x.
If you are using IDE integration with the Visual Studio 2003 plug-in in Vault 4.x, you may need to change the value in these registry keys to make sure that they are pointed at the proper location of the Vault version you are using at a particular time.
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider
HKEY_LOCAL_MACHINE\SOFTWARE\SourceGear\Vault Client
While it's possible to have both on the same machine, it's rather tricky. First, you will need to uninstall both Vault 3.5.x and Vault 4.x. You may need to go through the registry and search for "Vault client" and delete registry entries that reference the Vault client.
*be sure to backup your registry first*
Then install Vault client 3.5.x. Copy the contents of the Vault client directory and paste them into a directory somewhere else on your local machine. Then install Vault client 4.0.x.
If you are using IDE integration with the Visual Studio 2003 plug-in in Vault 4.x, you may need to change the value in these registry keys to make sure that they are pointed at the proper location of the Vault version you are using at a particular time.
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider
HKEY_LOCAL_MACHINE\SOFTWARE\SourceGear\Vault Client
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Hi Linda,
thanks for your quick reply!
Yikes, maybe I'll just install and use 3.5 until my company upgrades. I'm probably just using a subset of vault's possible features anyway and don't need the latest and greatest.
Unless...: I'm using Visual Studio .net 2008. Is there anything that doesn't work with that in 3.5 that does in 4.0?
(I'll check the 4.0 updated notes for that in the meantime.)
thanks for your quick reply!
Yikes, maybe I'll just install and use 3.5 until my company upgrades. I'm probably just using a subset of vault's possible features anyway and don't need the latest and greatest.
Unless...: I'm using Visual Studio .net 2008. Is there anything that doesn't work with that in 3.5 that does in 4.0?
(I'll check the 4.0 updated notes for that in the meantime.)
Ok, it looks like the answer to my original question is right in the Vault 4.0 Release Notes (http://support.sourcegear.com/viewtopic.php?t=8047):
Vault 4.0 is not backwards compatible with previous versions of Vault. In essence, Vault 4.0 clients will only interact with Vault 4.0 servers and vice versa. Vault 2.0, 3.0, 3.1, and 3.5 clients and servers are not compatible with Vault 4.0 clients and servers.
However, the way it behaves is very unintuitive. I had installed the version 4 client and then installed the 3.5.1 client. The 3.5.1 client installation completed with no problems, yet when I start the client, it opens version 4.0. I thought something was messed up or not working as intended on my machine.
I understand that you probably don't want to go back and change the 3.x client installations, and I don't expect you to, but I have these suggestions:
- Ideally, I would be able to run both clients side by side on the same PC.
- If not, perhaps the 4.0 client can detect whether I tried to install an older client after installing the new client and tell me why it is opening instead, something like "We've noticed that you've installed the 3.5.1 client after installing the 4.0 client. This won't work". Then I would have known what happened.
Thanks!
Vault 4.0 is not backwards compatible with previous versions of Vault. In essence, Vault 4.0 clients will only interact with Vault 4.0 servers and vice versa. Vault 2.0, 3.0, 3.1, and 3.5 clients and servers are not compatible with Vault 4.0 clients and servers.
However, the way it behaves is very unintuitive. I had installed the version 4 client and then installed the 3.5.1 client. The 3.5.1 client installation completed with no problems, yet when I start the client, it opens version 4.0. I thought something was messed up or not working as intended on my machine.
I understand that you probably don't want to go back and change the 3.x client installations, and I don't expect you to, but I have these suggestions:
- Ideally, I would be able to run both clients side by side on the same PC.
- If not, perhaps the 4.0 client can detect whether I tried to install an older client after installing the new client and tell me why it is opening instead, something like "We've noticed that you've installed the 3.5.1 client after installing the 4.0 client. This won't work". Then I would have known what happened.
Thanks!