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.

TCP Listener shutting down

4 posts in General Discussion Last posting was on 2009-07-14 17:40:51.0Z
Thomas Bodell Posted on 2009-07-09 13:36:56.0Z
From: "Thomas Bodell" <thomas@monitor.se>
Newsgroups: ianywhere.public.general
Subject: TCP Listener shutting down
Lines: 13
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6002.18005
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18005
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a55f278$3@forums-3-dub.sybase.com>
Date: 9 Jul 2009 06:36:56 -0700
X-Trace: forums-3-dub.sybase.com 1247146616 10.22.241.152 (9 Jul 2009 06:36:56 -0700)
X-Original-Trace: 9 Jul 2009 06:36:56 -0700, vip152.sybase.com
Path: forums-1-dub!forums-master!forums-3-dub.sybase.com!not-for-mail
Xref: forums-1-dub ianywhere.public.general:7639
Article PK: 6032

Hi all

We are using SQL Anywhere Network server 10.0.1.3873 running on Windows XP
Build 2600 Service Pack 3 on X86. The server randomly indicates "TCP
Listener shutting down (10014)". Service restart is then necessary. Does
anyone have any ideas what might cause this problem. The server was original
running on Windows 2003 Server with the same problem.

TIA

Regards
Thomas Bodell


"Kory Hodgson (Sybase iAnywhere)" <khodgson Posted on 2009-07-09 15:05:46.0Z
From: "Kory Hodgson (Sybase iAnywhere)" <khodgson@A_SPAM_FREE_sybase.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: TCP Listener shutting down
References: <4a55f278$3@forums-3-dub.sybase.com>
In-Reply-To: <4a55f278$3@forums-3-dub.sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a56074a$1@forums-3-dub.sybase.com>
Date: 9 Jul 2009 08:05:46 -0700
X-Trace: forums-3-dub.sybase.com 1247151946 10.22.241.152 (9 Jul 2009 08:05:46 -0700)
X-Original-Trace: 9 Jul 2009 08:05:46 -0700, vip152.sybase.com
Lines: 24
X-Authenticated-User: techsupp
Path: forums-1-dub!forums-master!forums-3-dub.sybase.com!not-for-mail
Xref: forums-1-dub ianywhere.public.general:7640
Article PK: 6031

Thomas,

The 10014 error code is a Winsock error code indicating that a bad
address was passed as a parameter.

Is it possible you are losing your network connection? Maybe it comes
back on a new IP if you are using dynamic IPs and thus a restart picks
up this new address.

Thomas Bodell wrote:
> Hi all
>
> We are using SQL Anywhere Network server 10.0.1.3873 running on Windows
> XP Build 2600 Service Pack 3 on X86. The server randomly indicates "TCP
> Listener shutting down (10014)". Service restart is then necessary. Does
> anyone have any ideas what might cause this problem. The server was
> original running on Windows 2003 Server with the same problem.
>
> TIA
>
> Regards
> Thomas Bodell


"Ian McHardy [Sybase iAnywhere]" <mchardy_no Posted on 2009-07-14 17:30:50.0Z
From: "Ian McHardy [Sybase iAnywhere]" <mchardy_no@spam_ianywhere.com>
Newsgroups: ianywhere.public.general
References: <4a55f278$3@forums-3-dub.sybase.com> <4a56074a$1@forums-3-dub.sybase.com>
Subject: Re: TCP Listener shutting down
Lines: 45
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a5cc0ca$2@forums-3-dub.sybase.com>
Date: 14 Jul 2009 10:30:50 -0700
X-Trace: forums-3-dub.sybase.com 1247592650 10.22.241.152 (14 Jul 2009 10:30:50 -0700)
X-Original-Trace: 14 Jul 2009 10:30:50 -0700, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!forums-master!forums-3-dub.sybase.com!not-for-mail
Xref: forums-1-dub ianywhere.public.general:7645
Article PK: 6039

I don't recall hearing of this problem before, although there have been a
number of problems with unexpected Winsock errors causing the listener to
shut down.

You should be able to ignore the error using the -x tcpip(IgnoreCodes=10014)
parameter on the server command line.

--

Ian McHardy (Sybase iAnywhere)

Please reply only to the newsgroup.

SQL Anywhere Developer Community -
http://www.sybase.com/developer/library/sql-anywhere-techcorner
SQL Anywhere Blog Center - http://www.sybase.com/sqlanyblogs

"Kory Hodgson (Sybase iAnywhere)" <khodgson@A_SPAM_FREE_sybase.com> wrote in
message news:4a56074a$1@forums-3-dub.sybase.com...
> Thomas,
>
> The 10014 error code is a Winsock error code indicating that a bad address
> was passed as a parameter.
>
> Is it possible you are losing your network connection? Maybe it comes back
> on a new IP if you are using dynamic IPs and thus a restart picks up this
> new address.
>
>
>
> Thomas Bodell wrote:
>> Hi all
>>
>> We are using SQL Anywhere Network server 10.0.1.3873 running on Windows
>> XP Build 2600 Service Pack 3 on X86. The server randomly indicates "TCP
>> Listener shutting down (10014)". Service restart is then necessary. Does
>> anyone have any ideas what might cause this problem. The server was
>> original running on Windows 2003 Server with the same problem.
>>
>> TIA
>>
>> Regards
>> Thomas Bodell


Josh Savill [Sybase] Posted on 2009-07-14 17:40:51.0Z
From: "Josh Savill [Sybase]" <no_spam_jsavill_no_spam@sybase.com>
Organization: Sybase iAnywhere
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: TCP Listener shutting down
References: <4a55f278$3@forums-3-dub.sybase.com> <4a56074a$1@forums-3-dub.sybase.com> <4a5cc0ca$2@forums-3-dub.sybase.com>
In-Reply-To: <4a5cc0ca$2@forums-3-dub.sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a5cc323$2@forums-3-dub.sybase.com>
Date: 14 Jul 2009 10:40:51 -0700
X-Trace: forums-3-dub.sybase.com 1247593251 10.22.241.152 (14 Jul 2009 10:40:51 -0700)
X-Original-Trace: 14 Jul 2009 10:40:51 -0700, vip152.sybase.com
Lines: 16
X-Authenticated-User: techsupp
Path: forums-1-dub!forums-master!forums-3-dub.sybase.com!not-for-mail
Xref: forums-1-dub ianywhere.public.general:7646
Article PK: 6035

By default the database server listens on 0.0.0.0:port#. What is your database server command line?
Can you provide a database server output with "-z -o filename.txt" to show the communication links?

--
Joshua Savill
Sybase Inc. - Product Manager

Ian McHardy [Sybase iAnywhere] wrote:
> I don't recall hearing of this problem before, although there have been a
> number of problems with unexpected Winsock errors causing the listener to
> shut down.
>
> You should be able to ignore the error using the -x tcpip(IgnoreCodes=10014)
> parameter on the server command line.
>