VS.Net cannot connect to server, but client can

[rob]

Hi,

I have SourceVault installed and setup on my machine as the default source control provider. I have confirmed all items mentioned in http://support.sourcegear.com/viewtopic.php?t=736.

During the week I work with connected to the vault server in VS.Net so that I can check in and out as need be. On the weekend, however, I work in disconnected mode. However, on returning to the office, VS.Net is no longe able to reconnect to the Vault db. Strangely enought, the Vault client can without any problem. This is the first time I have tried to work in disconnected mode and then re-establish the connection.

I am using version 2.04 of the client. All the files I worked with in disconnected mode were previously checked out.

Any suggestions?

[rob]

I eventually got everything working again buy shutting down all applications, uninstalling the Vault client, rebooting and the reinstalling the Vault client. '

This behaviour is a bit worrisome. Does anybody have any ideas? I did notice that when trying to re-establish the server connection from inside VS.NET the "Can't connect" error came up very quickly, almost as though it wasn't actually trying to connect, but had cached the fact that it couldn't.

Thanks

[dan]

Can you post the exact steps you are using, so we can try to reproduce this here?

Also, can you reproduce it simply by working disconnecting and then attempting to reconnect right away, or does it only happen when you working disconnected and actually modify files, and or wait a long time?

One last thing: Can you post the output of Help->Technical Support from the GUI client, so we can see the full environment you are running on?

[rob]

Dan,

Thanks for the response. Since I'm working quite busily on a project I'm not going to attempt to repeat it, since the whole fix process takes quite some time out of my day .

However these were the steps I followed:

1) Have project in SourceVault
2) Check out entire project
3) Disconnect from network
4) Shut down VS.Net & PC
5) Start PC & VS.Nett
6) Choose to work in disconnected mode
7) Modify files as required
Shut down VS.NET & PC
9) Restart PC & VS.NET while connected to network
10) Attempt to re-connect to SourceVault DB

It was at this point the error occured. The error is the exact same one you get when you try to connect to server that doesn't exist ("Unable to connect to http://<VaultServer>/VaultService. No server was found at the specified URL. Please veryify your network settings using the Options Dialog under the Tools menu in the Vault GUI Client. Web Exception: The underlying connection was closed: The remote name couldn not be resolved"). I know this is not the case since the client can connect with the exact same settings.

Here are the settings from Help -> Technical Support

Client Information
Vault Client Version: 2.0.4.2190
Operating System: Microsoft Windows XP Professional
Service Pack: 1.0
OS Version: 5.1.2600
Total Physical Memory: 1023.35 MB
Time Zone: (GMT+02:00) Harare, Pretoria

Server Information
Vault Server Version: 2.0.4.2190
Operating System: Microsoft(R) Windows(R) Server 2003, Enterprise Edition
Service Pack: 0.0
OS Version: 5.2.3790
Timezone: (GMT-05:00) Eastern Time (US & Canada)
SQL Version: Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )