Client freezes on login and cannot display options dialog

[thorbenw]

Hi,

the vault GUI client is unable to connect to the vault server, and if I try to open the options dialog box the whole client freezes.

I use vault with VFP9, and within VFP it still works fine. Because the client doesn't even try to connect the server (no entries about a logon request in server log), I think it's not a server or connectivity issue. So I focused on bringing up the options dlgbox first...

I'm working with client version 4.1.2 (now 4.1.4).

So far, I tried the following:
- rename the HKCU\Software\SourceGear\Vault\Client\Settings key
-> it's recreated with default values, but doesn't help
- rename the VaultGUIClient.exe.config file
-> doesn't help
- change proxy settings in VaultGUIClient.exe.config to invalid values, hoping to get at least an error message
-> didn't work
- reinstall the client
-> didn't solve the problem
- update client to 4.1.4
-> didn't solve the problem
- have a look at process monitor
-> the last thing vaultguiclient.exe does before dying is reading regkeys containing winsock settings
- check winsock catalog (netsh winsock show catalog)
-> everything's ok there

I already had this problem in last november, but I can't reproduce the way I solved it then:
- update client 4.1.1 to 4.1.3 and then go back to 4.1.2 (4.1.3 had a bug I was affected of)

Did anyone else ever have this problem?

Best regards
Thorben

[Beth]

Are other users able to connect?

Are you internal to the network where the Vault server is or remote?

Are any errors being reported in your Event Viewer log?

Are you able to go to Help - About in the Vault GUI client? If so, can you post the client information from there?

[thorbenw]

Are other users able to connect?
- Yes. In VFP, even I am able to connect. So the API seems to work, only the GUI client doesn't.

Are you internal to the network where the Vault server is or remote?
- Internal. And btw: The vault server is running on the same machine I try to connect from.

Are any errors being reported in your Event Viewer log?
- No. Do you want me to create a debug file and post it here?

Are you able to go to Help - About in the Vault GUI client? If so, can you post the client information from there?

- Yes: SourceGear Vault Client, Version 4.1.4 (18402)

Best regards
Thorben

[lbauer]

The first thing I would suggest is to delete your client-side cache files and flush out the server cache. There may be info cached that's out of sync with the database.

http://support.sourcegear.com/viewtopic.php?t=6

I'd suggest renaming the Vault_1 file and allow a new to be created.

So the steps would be:

Close any open clients.
Delete the client-side cache
Restart IIS, which restarts the Vault Server
Then open your client and re-connect.
You'll need to reset working directories.

Let me know if this does not resolve the problem.

[thorbenw]

Hi Linda,

I performed all steps you proposed, but it didn't help.

As I mentioned above, I don't think it's a connectivity issue. The cache directory has not even been recreated, so the client didn't use the cache at all when I tried to connect.

Best regards
Thorben

[lbauer]

Turn on client side logging and perhaps we'll get more information:

http://support.sourcegear.com/viewtopic.php?t=1534

Send the log zipped up to support at sourcegear.com, Attn: Linda.

[thorbenw]

Send the log zipped up to support at sourcegear.com, Attn: Linda.

Done

Best regards
Thorben

[Beth]

The users email has been received and this issue is being worked on offline.

HS: 214936