vault client hanging on one machine

Guest · Post by **Guest** » Fri Jun 17, 2005 8:26 am

vault 3.0 client is running fine on two dev laptops, and talking to the server quite happily. however the client app running on the *same server* as the web services has started hanging! i've checked obvious things such as proxy settings, and verified i can browse to the ASMX using IE on the same machine, but no joy. i've turned on client logging, and this is all i get:

Code: Select all

17/06/2005 14:56:27 <generic>: [<No Name>:2924] VaultGUIClient, Version=3.0.6.2856, Culture=neutral, PublicKeyToken=null
17/06/2005 14:56:27 <generic>: [<No Name>:2924] Logging all classes
17/06/2005 14:56:30 <statussearch>: [GUIClientWorkerThread:3692] Refresh called
17/06/2005 14:56:30 <statussearch>: [GUIClientWorkerThread:3692] Returning from refresh early (no GCI, CI, or TC)
17/06/2005 14:56:30 <statussearch>: [GUIClientWorkerThread:3692] Refresh finished
17/06/2005 14:56:32 <connection>: [GUIClientWorkerThread:3692] InitService started.
17/06/2005 14:56:43 <connection>: [GUIClientWorkerThread:3692] InitService finished.
17/06/2005 14:56:49 <connection>: [GUIClientWorkerThread:3692] Login started.
17/06/2005 14:56:49 <statussearch>: [Main:2924] Connection state changed from Unconnected to Connecting
17/06/2005 14:56:49 <emailview>: [Main:2924] Connection state changed from Unconnected to Connecting

..after that there's no activity.

lbauer · Post by **lbauer** » Fri Jun 17, 2005 8:46 am

Is there anything helpful in the sgvault.log file in %windir%\temp?

Guest · Post by **Guest** » Sat Jun 18, 2005 4:34 am

nope. it looks as if the service is never getting called by that instance of the client. all the log entries pertain to clients running on other machines.

Post by **jeremy_sg** » Mon Jun 20, 2005 6:51 am

Try running the Connection Test program. It's a very simple C# app that makes one unauthenticated call to the Vault web service.

Guest · Post by **Guest** » Wed Jun 22, 2005 2:08 am

all is well again - it seems we've got wider problems with the server (unrelated to vault). thanks for the help though...