Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

ERROR 6624 A winsock virtual circuit was reset Remotely

2 posts in Networking Last posting was on 2012-07-02 21:47:33.0Z
AJB Posted on 2012-06-29 18:52:48.0Z
From: "AJB" <abobby@leaderservices.com>
Newsgroups: Advantage.Networking
Subject: ERROR 6624 A winsock virtual circuit was reset Remotely
Date: Fri, 29 Jun 2012 14:52:48 -0400
Lines: 10
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: 12.44.224.2
Message-ID: <4fedf924$1@solutions.advantagedatabase.com>
X-Trace: 29 Jun 2012 11:51:16 -0700, 12.44.224.2
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Networking:1006
Article PK: 1132416

Hi
One of our clients was getting a large number of 6610 & 5035 errors. I
had them add to the ads.ini USE TCP/IP = 1. Now the errors have gone, but
no getting 6624 errors-winsock error.

Wahat could be cause of 6624 error? How to stop the error?

thanks


Edgar Sherman Posted on 2012-07-02 21:47:33.0Z
Date: Mon, 02 Jul 2012 15:47:33 -0600
From: Edgar Sherman <no@email.com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
Newsgroups: Advantage.Networking
Subject: Re: ERROR 6624 A winsock virtual circuit was reset Remotely
References: <4fedf924$1@solutions.advantagedatabase.com>
In-Reply-To: <4fedf924$1@solutions.advantagedatabase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 10.6.193.121
Message-ID: <4ff21690$1@solutions.advantagedatabase.com>
X-Trace: 2 Jul 2012 14:45:52 -0700, 10.6.193.121
Lines: 28
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Networking:1007
Article PK: 1132417

Both the 6610 and 6624 are typically indicators that the ADS service was
shutdown while the client was connected or, in other words, the client
has not issued a "disconnect", but is not able to communicate with the
server any longer. (The 6610 though it a little more broader and can be
returned for packet fragmentation as well)

Judging by the 5035, I am assuming the ADS service is staying up and
continues to run.

Given my assumption is correct, I suspect there may be a firewall/router
that may be "closing" the connection after X amount of time. This would
be difficult to track down, but you might speak with the client and see
if they have any rules setup for timeouts etc.

Edgar

On 6/29/2012 12:52 PM, AJB wrote:
> Hi
> One of our clients was getting a large number of 6610 & 5035 errors. I
> had them add to the ads.ini USE TCP/IP = 1. Now the errors have gone, but
> no getting 6624 errors-winsock error.
>
> Wahat could be cause of 6624 error? How to stop the error?
>
> thanks
>
>