Socket Error - ParseStream()

[gotdablues]

Support:

My clients (all two of them) are connecting to a VSS 2005 database using SOS 4.2 client/server (with encryption). The connections are getting dropped while checkin/checkout files via VS.NET 2003. Eventually, we are able to connect and complete the check in/out process.

I have applied the regstry setting for the threading model. I changed from 'Apartment' to 'Both'. The jury is out whether this has made a different.

In addition, I am seeing a number of Socket errors in my log file. I have included a snippet below. Any thoughts are the socket errors and what was be causing this.

12/15/2006 10:29:51 PM - ****************************************************
12/15/2006 10:29:51 PM - SourceOffSite Server 4.2 Professional - With Cryptography

12/15/2006 10:29:51 PM - CurrentCulture is en-US.

12/15/2006 10:29:51 PM - Server Information
12/15/2006 10:29:51 PM - Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
12/15/2006 10:29:51 PM - Service Pack: 1.0
12/15/2006 10:29:51 PM - OS Version: 5.2.3790
12/15/2006 10:29:51 PM - Locale: Ox0409
12/15/2006 10:29:51 PM - OSLanguage: 1033
12/15/2006 10:29:51 PM - Total Physical Memory: 1023.39 MB
12/15/2006 10:29:51 PM - Time Zone: (GMT-05:00) Eastern Time (US & Canada)
12/15/2006 10:29:51 PM -
12/15/2006 10:29:51 PM - SSAPI.dll Information:
12/15/2006 10:29:51 PM - Location: file:///C:/Program Files/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
12/15/2006 10:29:51 PM - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null
12/15/2006 10:29:51 PM -
12/15/2006 10:29:51 PM - Started at 12/15/2006 10:29:51 PM

12/15/2006 10:29:51 PM - General logging level is Error. Method logging is Disabled.

12/15/2006 10:29:51 PM - Number of licenses configured: 2
12/15/2006 10:29:51 PM - SourceSafe Initialization file(s) located at:
12/15/2006 10:29:51 PM - C:\???????\srcsafe.ini

12/15/2006 10:29:52 PM - ????? is attempting to listen for connections on secure port 1600


12/15/2006 10:29:52 PM - Waiting for a connection....secure = True
12/15/2006 10:32:36 PM - Connection accepted from X.X.X.X:33452 on local address 10.20.30.247:1600, session id is 1.
12/15/2006 10:33:26 PM - Connection accepted from X.X.X.X:33699 on local address 10.20.30.247:1600, session id is 2.
12/15/2006 10:33:27 PM - 12/15/2006 10:33:27 PM - Server Exception (-100): [Socket error - ParseStream(). Received : 0] - CONNECTION CLOSED
12/15/2006 10:33:27 PM - 2: Connection Closed: CONNECTION CLOSED
12/15/2006 10:33:27 PM - Connection accepted from X.X.X.X:33611 on local address 10.20.30.247:1600, session id is 3.
12/15/2006 10:34:49 PM - 12/15/2006 10:34:49 PM - Server Exception (-100): [Socket error - ParseStream(). Received : 0] - CONNECTION CLOSED
12/15/2006 10:34:49 PM - 3: Connection Closed: CONNECTION CLOSED
12/15/2006 10:34:51 PM - 1: Exception: An existing connection was forcibly closed by the remote host



Thanks.

Steve

[lbauer]

I have applied the regstry setting for the threading model. I changed from 'Apartment' to 'Both'. The jury is out whether this has made a different.

This fix is specifically for VSS 6.0d, ssapi.dll version 98.48 and probably won't make a difference for VSS 2005.

Disconnects are often caused by network issues. Could anything be interfering with or closing the connection, like a firewall, router, anti-virus scanning?

[gotdablues]

Linda,

What are the typical issues you see with network configurations? Do certain ports need to be open (we use 1600)? Any others? Are there certain keep-alive values that need to be increased?

Any info you have would be helpful so when I talk with my network guys, I ask the right questions

Thanks.

Steve