Connection closed on client

dcrick · Post by **dcrick** » Mon Apr 30, 2007 9:43 am

Several our my users are getting connection closed by the client. This is starting to happen more frequently, and not sure how to address the problem. Not sure if the problem is related to server is taxed, but the server never runs at more that 60%. Sometimes starting and stopping the services fixes the problem. We are running on Win2003 Standard SP1. The server is running in a VM with 1GIG of dedicated to the VM, under VMWare ESX server.

Here is a sample of the errors were are getting in our log.txt

4/30/2007 10:16:33 AM - Connection accepted from 10.255.126.84:28371 on local address 10.1.15.136:8080, session id is 1.
4/30/2007 10:16:34 AM - Killing disconnected or idle client - (10.255.126.84)
4/30/2007 10:16:34 AM - Connection accepted from 10.1.1.147:1252 on local address 10.1.15.136:8080, session id is 2.
4/30/2007 10:16:37 AM - 1: Unable to get hostname from address: 10.255.126.84
4/30/2007 10:16:37 AM - 1: Exception processing messages: Object reference not set to an instance of an object.
4/30/2007 10:16:37 AM - Killing disconnected or idle client gmme-l01 - (10.1.1.147)
4/30/2007 10:16:37 AM - 2: Exception processing messages: A blocking operation was interrupted by a call to WSACancelBlockingCall
4/30/2007 10:16:40 AM - Connection accepted from 10.255.126.84:28414 on local address 10.1.15.136:8080, session id is 3.
4/30/2007 10:16:44 AM - 3: Unable to get hostname from address: 10.255.126.84
4/30/2007 10:16:45 AM - Killing disconnected or idle client 10.255.126.84 - (10.255.126.84)
4/30/2007 10:16:45 AM - Connection accepted from 10.1.1.147:1253 on local address 10.1.15.136:8080, session id is 4.
4/30/2007 10:16:47 AM - Killing disconnected or idle client gmme-l01 - (10.1.1.147)
4/30/2007 10:16:49 AM - 4: Exception during Login while checking ProjectRightsEnabled: Object reference not set to an instance of an object.
4/30/2007 10:17:27 AM - Connection accepted from 10.255.126.84:28691 on local address 10.1.15.136:8080, session id is 5.
4/30/2007 10:17:32 AM - 5: Unable to get hostname from address: 10.255.126.84
4/30/2007 10:18:21 AM - Killing disconnected or idle client 10.255.126.84 - (10.255.126.84)
4/30/2007 10:18:21 AM - Connection accepted from 10.1.1.147:1260 on local address 10.1.15.136:8080, session id is 6.
4/30/2007 10:18:21 AM - Killing disconnected or idle client gmme-l01 - (10.1.1.147)
4/30/2007 10:18:21 AM - Connection accepted from 10.1.1.159:1742 on local address 10.1.15.136:8080, session id is 7.
4/30/2007 10:18:21 AM - 6: Exception processing messages: A blocking operation was interrupted by a call to WSACancelBlockingCall
4/30/2007 10:18:21 AM - Killing disconnected or idle client - ()
4/30/2007 10:18:21 AM - 7: Exception processing messages: Object reference not set to an instance of an object.
4/30/2007 10:18:32 AM - Connection accepted from 10.1.1.147:1261 on local address 10.1.15.136:8080, session id is 8.

Just looking for ideas or options to try and resolve this issue.
Thanks,
crick

lbauer · Post by **lbauer** » Mon Apr 30, 2007 12:35 pm

What version of SOS Clients and Server are you using?

What version of the SourceSafe automation component (ssapi.dll) is SOS Server using?

NOTE: There may be more than one version of the ssapi.dll on the machine. To determine which is used by SOS Server, look under this registry key:

Code:
HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32

The value will have the path to the specific ssapi.dll file used by SOS Server.

dcrick · Post by **dcrick** » Mon Apr 30, 2007 3:07 pm

- Version of SOS Clients are all 4.2 and server is 4.2.

- The ssapi.dll version is: 6.0.98.48, and their is only one installed

lbauer · Post by **lbauer** » Wed May 02, 2007 9:27 am

This may help:

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

dcrick · Post by **dcrick** » Wed May 02, 2007 11:24 am

Have already done the steps in that posting. Had to do that to solve a problem early on in the installation.

But thanks.

Still need to find something else that might be causing this, or suggestions on thinks I can look for.

Thanks,
crick

lbauer · Post by **lbauer** » Wed May 02, 2007 4:29 pm

These are hard to troubleshoot, as they are often network related.

Are there any firewalls, proxies, anti-hacking software that could be closing the connection?

Is there any pattern as to when the connections get closed -- when the client sits idle, or during a long recursive operation, for instance?

Are users getting disconnected while using Visual Studio?

Check your setting in the SOS Server Manager under ->General Settings->Timeout Idle connections. Is that checked? If so, try unchecking it.

If a firewall or other device is closing the connection after a certain amount of time when no data is moving between client and server, you could try enabling the Keep Alive signal in the Vault GUI Client under Tools->Options->General.

We haven't tested SOS running a production server on VMWare, so we're not sure how that might factor in.

dcrick · Post by **dcrick** » Thu May 03, 2007 8:22 am

I figured this was not going to be easy.

We don't have any firewalls or proxies between the client and server. Everybody that is connecting is on the LAN.

The problem is always when they attempt to make their initial connections and general happens after the server has been running for a week.

It happens with both Visual Studio and the SOS client directly.

I will try and see if their are any VMWare network settings that might be conflicting.

Are their any other switches on the server or client that can be turned on for more detailed logging?

crick

lbauer · Post by **lbauer** » Sat May 05, 2007 7:31 am

You could enable verbose and method logging:
http://support.sourcegear.com/viewtopic.php?t=463

This will give some information. However if it's network or environment related, the server will report the connection is closed, and not much info on why.