VaultGUIClient.exe hangs on startup on Windows Server 2003

Bart Read · Post by **Bart Read** » Thu Oct 28, 2004 7:35 am

Hi,

A couple of days ago Vault client stopped working when I try to run it on one of our servers which I'm accessing via a remote desktop connection. I've tried restarting the serer, and even deleting the SourceGear folder from C:\Documents and Settings\My.User.Name\Application Data but to no avail.

The exact issue I'm having is as follows. I log in to the machine using Remote Desktop Connection from a Windows XP Pro box. The server itself is running Windows Server 2003 Standard Edition. When I try to start the Vault client the mouse cursor changes to the hourglass cursor for a few moments, and then back to the standard mouse cursor and then NOTHING else happens. The usual Vault window does not appear.

However, VaultGUIClient.exe can be seen in the process list in Task Manager under my username, generally using 14 - 15 MB of RAM and no CPU time. Doesn't matter how long I walk away from the machine, nothing further happens. I've tried (as I said) a number of things: killing all instances of this process, rebooting the machine, deleting the SourceGear folder from Application Data but I'm just at a bit of a loss.

One last point is that the problem only seems to affect my username, and it's only a problem on this machine. Also, and I'm not sure whether or not this is relevant, I do have admin rights on the machine in question.

Any help would be much appreciated.

Many thanks,
Bart Read

Post by **jclausius** » Thu Oct 28, 2004 7:49 am

Bart:

What version of the Vault client are you using? From your description, it sounds like an older bug which has since been fixed.

If you :
1) Close down all VaultGUIClient.exe processes
2) Delete the registry key HKCU\Software\SourceGear\Vault\Client, and restart . Normal registry disclaimer - Modifying the registry incorrectly may render your system inoperable, please be careful.
3) Restart the GUI client

Does that resolve the situation?

Bart Read · Post by **Bart Read** » Thu Oct 28, 2004 8:52 am

Hi Jeff,

Thanks for the quick response. I'm using version 2.0.4.

I'll give your suggestion a try.... I'm sure it will be fine. :-S Will let you know what happens.

Thanks,
Bart

Post by **jclausius** » Thu Oct 28, 2004 9:02 am

Bart:

If that does solve the problem, I'd recommend upgrading to Vault 2.0.6.

Bart Read · Post by **Bart Read** » Thu Oct 28, 2004 10:20 am

Thanks Jeff,
That registry hack worked a treat. However, if it happens again I'll try to persuade my boss to upgrade, but I guess if / when we go down that route he's going to want to upgrade everyone's systems.
Bart

Post by **jclausius** » Thu Oct 28, 2004 10:30 am

Bart:

Did you by chance upgrade to .Net 1.1 SP1? If so, I'd recommend having everyone move to Vault 2.0.6.

Remember, the Vault 2.0.6 upgrade is no-cost to existing Vault 2.0.x customers. Just download and install.

Bart Read · Post by **Bart Read** » Thu Nov 04, 2004 5:54 am

Hi Jeff,
Thanks for this. I've just recommended this to my manager, especially since I've just had to apply the registry hack again on our build server, so at the very least I'll be putting 2.0.6 on that.
Thanks,
Bart

Guest · Post by **Guest** » Tue Feb 15, 2005 10:05 pm

The registry contains many keys for the older version 1.2.2, but deleting them all fixed the problem there for me.

SourceGear Support