I have been using Vault client and Vault integrated with VS.Net. Now, all of a sudden, I can no longer connect with Vault client. However, I can still connect successfully with Vault through VS.Net IDE. I uninstalled Vault client and reinstalled and have same problem. I cleared cache files and have the same problem. Nothing seems to work. I never get an error, but after I enter my connection information, the bottom left corner of Vault client says "Connection to server...." and bottom right corner says "Connecting", but nothing ever happens. I know it isn't my login information because I went to a different machine and it works with the Vault client as well as working from VS.Net IDE.
Any ideas? I want to be able to use the Vault client outside of VS.Net IDE. As far as I know, nothing else changed for my setup, and I had used this client for months.
Thanks,
LaDonna
Can no longer connect with Vault Client, but can with VS.Net
Moderator: SourceGear
We've never really seen anything like this, so I'm going to ask lots of questions.
What version of Vault are you running?
Can you have one of your coworkers use their Vault username and password to connect from your computer?
Just to clarify -- You can connect with the IDE and can't connect with the GUI client?
Did you make any changes to your machine or network?
What version of Vault are you running?
Can you have one of your coworkers use their Vault username and password to connect from your computer?
Just to clarify -- You can connect with the IDE and can't connect with the GUI client?
Did you make any changes to your machine or network?
Eventually, after more than an hour of trying to connect, it will popup an error that says:
Unable to connect to http://10.0.0.30/VaultService. No server was found at the specified URL. Web Exception: The operation has timed-out.
However, if I open a browser on my machine, I can see the Vault Home page.
I am connecting across a VPN, but I always have been.
When I click on About in the client, it shows Vault 2.0.0 (0). The install file I used was for version 2.0.3. Then I applied the patch to make it work with VS.Net 2002 (by copying over the appropriate DLLs from patch zip file).
No other user Ids work from this computer either.
Yes, I can connect with VS.Net 2002 IDE using SourceGear Vault as source control. I just can't connect with Vault Client directly.
As far as I know, no changes were made to my machine or the network.
This is really baffling me!
Unable to connect to http://10.0.0.30/VaultService. No server was found at the specified URL. Web Exception: The operation has timed-out.
However, if I open a browser on my machine, I can see the Vault Home page.
I am connecting across a VPN, but I always have been.
When I click on About in the client, it shows Vault 2.0.0 (0). The install file I used was for version 2.0.3. Then I applied the patch to make it work with VS.Net 2002 (by copying over the appropriate DLLs from patch zip file).
No other user Ids work from this computer either.
Yes, I can connect with VS.Net 2002 IDE using SourceGear Vault as source control. I just can't connect with Vault Client directly.
As far as I know, no changes were made to my machine or the network.
This is really baffling me!
It's probably unwise to mix the VS2002 patch and the installed 2.0.3 files. If it was working fine before, I'm not going to worry too much about it. As an experiment, try installing the Vault Client to a different directory, and run it from there.
Have you run through the Troubleshooting guide at
http://support.sourcegear.com/viewtopic.php?p=2450
Have you run through the Troubleshooting guide at
http://support.sourcegear.com/viewtopic.php?p=2450
I deleted the whole SourceGear vault directory where cache files are stored. I uninstalled Vault client.
I reinstalled clean new version 2.0.3 of client in new directory. I still can't connect.
Yes, I went through the troubleshooter. Everything there is fine. I just can't connect through Vault client.
Why is it unwise to mix VS2002 patch and installed files? What do you recommend to get VS2002 working with Vault client. When I mix them as I described before, then I can use Vault through VS2002 IDE. My problem is just with Vault client.
What else can I try?
I reinstalled clean new version 2.0.3 of client in new directory. I still can't connect.
Yes, I went through the troubleshooter. Everything there is fine. I just can't connect through Vault client.
Why is it unwise to mix VS2002 patch and installed files? What do you recommend to get VS2002 working with Vault client. When I mix them as I described before, then I can use Vault through VS2002 IDE. My problem is just with Vault client.
What else can I try?
Give me an email with your phone number and we'll figure this out offline.
To answer your questions, I wouldn't recommend pasting the 2002 patch files into the installation directory.They're built with two different versions of the .Net framework. Also, in this case they're probably even two different builds of Vault. It seems like a likely place for oddities to creep in.
To answer your questions, I wouldn't recommend pasting the 2002 patch files into the installation directory.They're built with two different versions of the .Net framework. Also, in this case they're probably even two different builds of Vault. It seems like a likely place for oddities to creep in.
Same Problem
I just tried opening the client and it didn't come up. Its in the task list, but not shown.
I reinstalled from the vault site, but no change. VS.Net 2003 works as expected, but no external client. The "auto-profile" feature was turned on the last time it worked.
Its very strange. I cannot think of anything that changed between it working and not working. Even stranger is how VS.Net works.
Vault Version: 2.0.5.2210
I reinstalled from the vault site, but no change. VS.Net 2003 works as expected, but no external client. The "auto-profile" feature was turned on the last time it worked.
Its very strange. I cannot think of anything that changed between it working and not working. Even stranger is how VS.Net works.
Vault Version: 2.0.5.2210
Just a guess here - Have you (or Auto-Update) installed the 1.1 .Net SP1? There was a change in the framework which busted the GUI client if it is shutdown while the "Search" tab was in the foreground.
There is a quick test to verify this is the problem -
1) Delete the string value FormMain in the key HKEY_CURRENT_USER\Software\SourceGear\Vault\ClientSettings from your registry. The following command might help
Note - Please excersie due care when modifying the registry. Any mistake may render your Operating System inoperable.
2) Start the Vault GUI client.
Does it start now?
If so, you should take a look at grabbing Vault 2.0.6, as the 1.1 .Net SP1 fix is in that build.
There is a quick test to verify this is the problem -
1) Delete the string value FormMain in the key HKEY_CURRENT_USER\Software\SourceGear\Vault\ClientSettings from your registry. The following command might help
Code: Select all
reg.exe DELETE HKCU\Software\SourceGear\Vault\Client\Settings /v FormMain2) Start the Vault GUI client.
Does it start now?
If so, you should take a look at grabbing Vault 2.0.6, as the 1.1 .Net SP1 fix is in that build.
Jeff Clausius
SourceGear
SourceGear
Thank You!
That worked, thank you!!
I will be upgrading right away.
I will be upgrading right away.