Vault Client won't connect

[thad.miller]

I was having a problem in that the Vault Client would not connect to my server. We have 5 other clients, and they worked just fine. I tried uninstall, reinstall, uninstall, reinstall... no luck. Searched the forums and all I found was messages pointing to a router/firewall/network issue, but there was no connection error... the client would just hang when I tried to connect to the server! Finally I tried running the command prompt vault.exe which actually gave me the following error (though, it just hung then too):

Unhandled Exception: System.TypeInitializationException: The type initializer for "System.Net.Sockets.Socket" threw an exception. ---> System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full
at System.Net.Sockets.Socket.InitializeSockets()
at System.Net.Sockets.Socket..cctor()
--- End of inner exception stack trace ---
at System.Net.Connection.StartConnectionCallback(Object state, Boolean wasSignalled)

The error led me too an MS KB article about a known bug: http://support.microsoft.com/default.as ... -us;815209

The last thing I installed was the google desktop search, which added 3 protocol bindings, which just happened to take me over 50, and cause vault to hang. I'd like to suggest to the Vault authors to trap for this, since it is a known, documented bug.

Thanks
-Thad

[dan]

Thanks for tracking this down Thad. I'll log it as an issue - should be easy enough to put in.