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.

Help with Error

2 posts in Windows NT Last posting was on 2000-09-25 09:21:27.0Z
rwsheets Posted on 2000-09-22 19:05:05.0Z
From: "rwsheets" <rwsheets@wellingtoninc.com>
Subject: Help with Error
Date: Fri, 22 Sep 2000 15:05:05 -0400
Lines: 31
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID: <2yJ#zmMJAHA.201@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.nt
NNTP-Posting-Host: inet127.wellingtoninc.com 205.247.111.127
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:1612
Article PK: 1089087

Occassionally in our Errorlog we have the following message:

02:00000:00001:2000/09/18 14:41:02.37 kernel nast_readpost: Invalid
tdslength (6912), socket 5, listener 0
00:00000:00009:2000/09/18 16:39:47.31 kernel nast_readpost: Invalid
tdslength (6912), socket 5, listener 0
00:00000:00009:2000/09/18 16:42:44.84 kernel nast_readpost: Invalid
tdslength (6912), socket 7, listener 0
00:00000:00001:2000/09/18 16:55:40.22 kernel nast_readpost: Invalid
tdslength (6912), socket 3, listener 0

As you can see from this excerpt from our Errorlog - it sometimes happens up
to 4 times in a day and then might go several days without it occurring.

It has been reported to Sybase but their only advice was to try to clear up
some of our deadlocks, upgrade to 11.9.2 (we're now at 11.5.1) and then see
if the error goes away.

It doesn't seem to affect anything that we can tell but it is a little
disconcerting to keep getting these messages and not know what to do about
them.

Has anyone else seen similar message? Have you found a solution.

Thanks for any information.

Rodney
rwsheets@wellingtoninc.com


Tony Imbierski Posted on 2000-09-25 09:21:27.0Z
Message-ID: <39CF1917.5E2E723C@sybase.com>
Date: Mon, 25 Sep 2000 10:21:27 +0100
From: Tony Imbierski <tonyi@sybase.com>
X-Mailer: Mozilla 4.72 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Help with Error
References: <2yJ#zmMJAHA.201@forums.sybase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 53
NNTP-Posting-Host: aja.sybase.com 158.76.102.161
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:1611
Article PK: 1089086

This message occurs because we read a tds packet from the network and the length
field is not what we were expecting. The first course of action is to determine
whether the server really is receiving packets with this length field set, in
which case the problem is not with the server, it is with the client or possibly
the network. Fortunately Microsoft supplies exactly the tool for the job with NT
server, but you have to know how to use it. It's called netmon and it will read
and log raw packets from the ethernet card and allow you to pick through them.

There are trace flags that make ASE log raw data packets to the errorlog as it
receives them, but it's not really possible to run a server in production with
these set, as the amount of data produced is phenomenal.

cheers,
tonyi

rwsheets wrote:

> Occassionally in our Errorlog we have the following message:
>
> 02:00000:00001:2000/09/18 14:41:02.37 kernel nast_readpost: Invalid
> tdslength (6912), socket 5, listener 0
> 00:00000:00009:2000/09/18 16:39:47.31 kernel nast_readpost: Invalid
> tdslength (6912), socket 5, listener 0
> 00:00000:00009:2000/09/18 16:42:44.84 kernel nast_readpost: Invalid
> tdslength (6912), socket 7, listener 0
> 00:00000:00001:2000/09/18 16:55:40.22 kernel nast_readpost: Invalid
> tdslength (6912), socket 3, listener 0
>
> As you can see from this excerpt from our Errorlog - it sometimes happens up
> to 4 times in a day and then might go several days without it occurring.
>
> It has been reported to Sybase but their only advice was to try to clear up
> some of our deadlocks, upgrade to 11.9.2 (we're now at 11.5.1) and then see
> if the error goes away.
>
> It doesn't seem to affect anything that we can tell but it is a little
> disconcerting to keep getting these messages and not know what to do about
> them.
>
> Has anyone else seen similar message? Have you found a solution.
>
> Thanks for any information.
>
> Rodney
> rwsheets@wellingtoninc.com

--
Tony Imbierski
Sybase Engineering

~ everything else is just email ~