Vault Client 3.5.2 on W2k Pro - No server found at URL

jayeldee · Post by **jayeldee** » Mon Aug 13, 2007 12:11 pm

We currently run 3.5.2 and have had no problems except with a new developer in our organization.

He is running Windows 2000 Professional and receiving the following error each time he tries to connect:

Code: Select all

Unable to connect to http://<our vault server>/VaultService.  No server was found at the specified URL.  Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.  Web Exception: The operation has timed-out.

I verified that he is able to open up a browser and navigate to <our vault server>/VaultService and can log in with his UN/PW no problem. I tested logging in with my domain account and connecting to Vault from his laptop and I am receiving the same error message so it seems to be something machine specific.

The vault logs do not show any activity originating from his machine, and I enabled client-side logging which shows the following:

Code: Select all

8/13/2007 11:40:04 AM <busy>: [GUIClientWorkerThread:732] Setting GUI to busy.
8/13/2007 11:40:17 AM <connection>: [GUIClientWorkerThread:732] Login started.
8/13/2007 11:40:17 AM <statussearch>: [Main:1200] Connection state changed from Unconnected to Connecting
8/13/2007 11:40:17 AM <emailview>: [Main:1200] Connection state changed from Unconnected to Connecting
8/13/2007 11:43:17 AM <statussearch>: [Main:1200] Connection state changed from Connecting to Disconnecting
8/13/2007 11:43:17 AM <emailview>: [Main:1200] Connection state changed from Connecting to Disconnecting
8/13/2007 11:43:17 AM <connection>: [GUIClientWorkerThread:732] Logout started.
8/13/2007 11:43:22 AM <connection>: [GUIClientWorkerThread:732] Logout finished.
8/13/2007 11:43:22 AM <statussearch>: [Main:1200] Active repository changed to 
8/13/2007 11:43:22 AM <emailview>: [Main:1200] Active repository changed to 
8/13/2007 11:43:22 AM <statussearch>: [Main:1200] Connection state changed from Disconnecting to Unconnected
8/13/2007 11:43:22 AM <emailview>: [Main:1200] Connection state changed from Disconnecting to Unconnected
8/13/2007 11:43:22 AM <busy>: [GUIClientWorkerThread:732] Setting GUI to unbusy.
8/13/2007 11:43:28 AM <busy>: [GUIClientWorkerThread:732] Setting GUI to busy.
8/13/2007 11:43:31 AM <busy>: [GUIClientWorkerThread:732] Setting GUI to unbusy.
8/13/2007 11:43:31 AM <statussearch>: [GUIClientWorkerThread:732] StatusSearchScan run with DONTSEARCH. Reporting empty search results.

Just to satisfy my curiosity I had him run the client on my machine and he was able to connect just fine.

I verified our license, which allows 5 users total and the new developer only puts us at 4.

Is there anything special I need to do with a Windows 2000 Professional client besides installing the 1.1 Framework?

Thanks,

John

Beth · Post by **Beth** » Mon Aug 13, 2007 1:02 pm

Can you open up a client from one of your other machines and go to Help - Technical support and copy the information from there for me?

Does the URL http://<your vault server>/vaultservice/vaultservice.asmx work on his machine as well?

What service pack is running on the Windows 2000 machine?

jayeldee · Post by **jayeldee** » Mon Aug 13, 2007 1:15 pm

Beth wrote:Can you open up a client from one of your other machines and go to Help - Technical support and copy the information from there for me?

This is the output from my laptop.

Code: Select all

Client Information
    Vault Client Version: 3.5.2.5087
    .Net Framework Version: 1.1.4322.2407
    Operating System: Microsoft Windows XP Professional
    Service Pack: 2.0
    OS Version: 5.1.2600
    Total Physical Memory: 1023.29 MB
    Time Zone: (GMT-06:00) Central Time (US & Canada)
    
Server Information
    Server version information unavailable
    
License Information
        License information unavailable

This is the output from the problem laptop:

Code: Select all

Client Information
    Vault Client Version: 3.5.2.5087
    .Net Framework Version: 1.1.4322.573
    Operating System: Microsoft Windows 2000 Professional
    Service Pack: 4.0
    OS Version: 5.0.2195
    Total Physical Memory: 511.48 MB
    Time Zone: (GMT-06:00) Central Time (US & Canada)
    
Server Information
    Server version information unavailable
    
License Information
        License information unavailable

Beth wrote: Does the URL http://<your vault server>/vaultservice/vaultservice.asmx work on his machine as well?

Yes, that link brings up the list of functions from the Web Service as expected.

Beth wrote: What service pack is running on the Windows 2000 machine?

He is running Windows 2000 Service Pack 4

Thanks for your quick response Beth,

John

GregM · Post by **GregM** » Mon Aug 13, 2007 1:23 pm

We've had problems like this in the past that turned out to be that the client was being blocked by the windows firewall or a third-party virus scanner that included a port blocker.

jayeldee · Post by **jayeldee** » Mon Aug 13, 2007 2:05 pm

GregM wrote:We've had problems like this in the past that turned out to be that the client was being blocked by the windows firewall or a third-party virus scanner that included a port blocker.

Thanks for the input Greg. I had considered this possibility but I checked the installed software thoroughly and there is no 3rd party software present that would cause this behavior and there isn't a Firewall built into his version of Windows. I checked TCP/IP for any filtering that might be occurring and did not find any.

Beth · Post by **Beth** » Mon Aug 13, 2007 2:09 pm

Can you add in the server information? Again you can go to Help - Technical support in a client that works, but make sure that you let it connect to the server first.

Terence · Post by **Terence** » Mon Aug 13, 2007 2:09 pm

It would help us, if you could have him try to connect to http://<server ip address> and see if that gets you a different error message.

jayeldee · Post by **jayeldee** » Mon Aug 13, 2007 2:35 pm

Beth wrote:Can you add in the server information? Again you can go to Help - Technical support in a client that works, but make sure that you let it connect to the server first.

My apologies - I did it on my client without connecting it first

Code: Select all

Client Information
    Vault Client Version: 3.5.2.5087
    .Net Framework Version: 1.1.4322.2407
    Operating System: Microsoft Windows XP Professional
    Service Pack: 2.0
    OS Version: 5.1.2600
    Total Physical Memory: 1023.29 MB
    Time Zone: (GMT-06:00) Central Time (US & Canada)
    
Server Information
    Vault Server Version: 3.5.2.5087
    .Net Framework Version: 2.0.50727.42
    Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
    Service Pack: 2.0
    OS Version: 5.2.3790
    Timezone: (GMT-06:00) Central Time (US & Canada)
    SQL Version: Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) 
        	Oct 14 2005 00:33:37 
        	Copyright (c) 1988-2005 Microsoft Corporation
        	Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
    
License Information
    1 serial number(s):
        1 of 1: 5 users, permanent

Terence wrote:It would help us, if you could have him try to connect to http://<server ip address> and see if that gets you a different error message.

Terrence, I tried your suggestion and received the same error message. It may also be noteworthy that the timeout itself takes approximately 3 minutes before the error message appears.

Beth · Post by **Beth** » Mon Aug 13, 2007 2:43 pm

I'm going to have you try making the .NET frameworks match. There have been times that I've seen just strange things happen when the frameworks don't match, even though they are supposed to be able to talk to each other.

This document here will give instructions on how to change the .NET framework on your client to 2.0:

Change Client .NET Framework

You will most likely have to download it and install it first for your Windows 2000 machine.

jayeldee · Post by **jayeldee** » Mon Aug 13, 2007 3:23 pm

Beth wrote:I'm going to have you try making the .NET frameworks match. There have been times that I've seen just strange things happen when the frameworks don't match, even though they are supposed to be able to talk to each other.

That fixed it. Thanks for all your help.