Vault VS2003 Integration Crashing when Change Source Control

[drofish]

I am running 2.0.5 with VS2003 and when I take my laptop (with client) remotely I do "Change Source Control" and then disconnect from the server.

When I try and reconnect (by going back to Change Source Control) .. I get some HRESULT exception and then VS2003 bombs completely.

My only way back is to use Vault client to check things back in.... blow out local copy and then Open From Source Control into a new directory. Obviously pain-ful, scary, and inefficient.

BTW, running 1.1 on this machine.

HELP???

[dan]

A few questions:

Did this use to work, but now does not? If so, what has changed recently?

By 1.1, do you mean the 1.1 framework? Is it the SP1 version of the framework? 2.0.6 contained some fixes that related to Framework 1.1 SP1, but none were known to be related to the IDE client. Howeer, it might help to upgrade.

[Guest]

This used to work and stopped working when the server was migrated to a different machine. The migration seemed to go ok, but the client failed like this immediately ... only after we did the Open from Source Control into a clean directory could we get the client to come up at all. So, it seems related to that.

The machine is running the following version of the .NET framework ... I don't see any references to SP1. Can you tell from this?

(version 1.1.4322.573)

[dan]

Check the Vault server log at the time of the re-connect. If the problems started with a change to the server, it might be that the server is timing out or something else.

Is the new server on win2003 server and the old one not? Win2K3 by default has more severe timeouts than other versions of windows.