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.

11.9.2.1 ESD 3

4 posts in Windows NT Last posting was on 2000-01-12 09:44:35.0Z
M Watkins Posted on 2000-01-10 15:46:26.0Z
From: "M Watkins" <MWatkins@Channel4.co.uk>
Subject: 11.9.2.1 ESD 3
Date: Mon, 10 Jan 2000 15:46:26 -0000
Lines: 61
X-Newsreader: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Message-ID: <oOUPaJ4W$GA.223@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.nt
NNTP-Posting-Host: 193.122.208.198
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2723
Article PK: 1090446

On a Dell Poweredge 6300 with 2 Pentium II 450 Xeons, 2GB RAM , 32MB Raid
Controller using Raid 1/0 running Sybase 11.9.2.1 with ESD 2 and NT service
pack 5, I was getting the following stack trace.

01:00000:00000:1999/11/09 17:50:23.01 kernel SQL Server system exception
(0xc0000005) generated by a storage access violation.
01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x0 (suspect virtual
address)(0x2002e040, 0x1e5fcb4, 0x0, 0x0)
01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x0 (suspect virtual
address)(0x1, 0x0, 0x1cbfed4, 0x8955d7)
01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x8a3dc9 syb_io_poll+ 0xb9
(0x1, 0x20011f40, 0x0, 0x0)
01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x8a3e4a os_schedcoma+
0x1a (0x1, 0x20011f40, 0x20019334, 0x93e07c)
01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x8955d7 kpcheckio+ 0xe7
(0x0, 0x0, 0x2, 0x20011f40)
01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x89466d kpsched+ 0xc0d
(0x9c406a, 0x2181ebc0, 0x6, 0x80f8a28c)
01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x893a16 kpstartsched+
0xa6 (0x9c406a, 0x6, 0x2181ebc0, 0x9c406a)
01:00000:00000:1999/11/09 17:50:23.25 kernel pc: 0x86d361 kestartup+ 0x451
(0x0, 0x0, 0x0, 0x0)
01:00000:00000:1999/11/09 17:50:23.25 kernel pc: 0x77f04ee8 KERNEL32.dll
(0x0, 0x0, 0x0, 0x0)
01:00000:00000:1999/11/09 17:50:23.25 kernel end of stack trace, kernel
service process: kpid 3407924

After raising a Tech Support Case with Sybase, they advised I move to ESD 3.
Now I am getting the following stack trace

00:00000:00000:2000/01/07 17:36:29.39 kernel SQL Server system exception
(0xc0000005) generated by a storage access violation.
00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x8aa367
os_get_cur_stk_desc+ 0x57 (0x125dd3c, 0x2a002a, 0x125dd3c, 0x0)
00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x8aa367
os_get_cur_stk_desc+ 0x57 (0x125dd3c, 0x125e290, 0x270f, 0x2)
00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x88ac24 pcstkwalk+ 0x224
(0x2a002a, 0x2, 0x270f, 0x0)
00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x88a7be ucstkgentrace+
0x1ce (0x2a002a, 0x1, 0x125ff98, 0x0)
00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x869ee4 ucbacktrace+ 0x84
(0xc0000005, 0x7800ef4e, 0x125e51c, 0x0)
00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x862ba4 kiexception+
0x1b4 (0x1, 0x53f60, 0xffffffff, 0x77f04ee8)
00:00000:00000:2000/01/07 17:36:30.11 kernel pc: 0x4017fd scm__main+ 0xfd
(0x0, 0x0, 0x0, 0x0)
00:00000:00000:2000/01/07 17:36:30.11 kernel pc: 0x77dd8bec ADVAPI32.dll
(0x0, 0x0, 0x0, 0x0)
00:00000:00000:2000/01/07 17:36:30.11 kernel end of stack trace, kernel
service process: kpid 2752554
00:00000:00000:2000/01/07 17:36:30.11 kernel engine 0, os pid 28 exited
00:00000:00000:2000/01/07 17:36:30.11 kernel Could not replace infected
engine.

All that seems to have changed is the dll mentioned in the stack trace. Does
anyone have any ideas as to what is going wrong. Otherwise l will go back to
ESD 1, at least that version was stable.


Simon Trowbridge Posted on 2000-01-11 10:29:05.0Z
From: "Simon Trowbridge" <simon.trowbridge@screwfix.com>
References: <oOUPaJ4W$GA.223@forums.sybase.com>
Subject: Re: 11.9.2.1 ESD 3
Date: Tue, 11 Jan 2000 10:29:05 -0000
Lines: 96
Organization: Screwfix Direct
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Message-ID: <fwIxS7BX$GA.177@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.nt
NNTP-Posting-Host: 62.6.162.98
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2716
Article PK: 1090180

I have been getting this issue as well, running virtually the same
configuration as you, but on Compaq Proliant's.

I too, after getting these errors, was asked to move to ESD 2. This then
had more exception errors. I was then asked to move to ESD 3, again had
more errors.

I moved to ESD4 on 20/12/99 when it first became available - DON'T MOVE TO
IT! - that still has an issue. Whilst ESD4 fixes the exception error with
syb_io_poll, there is a new exception error generated which causes the
server to "freeze".

I am now awaiting a Sybase "emergency fix" for this problem with the
ESD4(EBF 8741) patch which according to Sybase Tech Support will be 31st
January.

If anyone else is experiencing these issues, I would be interested to hear
from you, or if you know of this problem and when it is going to be FIXED!

Regards,

Simon Trowbridge

M Watkins <MWatkins@Channel4.co.uk> wrote in message
news:oOUPaJ4W$GA.223@forums.sybase.com...
> On a Dell Poweredge 6300 with 2 Pentium II 450 Xeons, 2GB RAM , 32MB Raid
> Controller using Raid 1/0 running Sybase 11.9.2.1 with ESD 2 and NT
service
> pack 5, I was getting the following stack trace.
>
> 01:00000:00000:1999/11/09 17:50:23.01 kernel SQL Server system exception
> (0xc0000005) generated by a storage access violation.
> 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x0 (suspect virtual
> address)(0x2002e040, 0x1e5fcb4, 0x0, 0x0)
> 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x0 (suspect virtual
> address)(0x1, 0x0, 0x1cbfed4, 0x8955d7)
> 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x8a3dc9 syb_io_poll+
0xb9
> (0x1, 0x20011f40, 0x0, 0x0)
> 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x8a3e4a os_schedcoma+
> 0x1a (0x1, 0x20011f40, 0x20019334, 0x93e07c)
> 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x8955d7 kpcheckio+ 0xe7
> (0x0, 0x0, 0x2, 0x20011f40)
> 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x89466d kpsched+ 0xc0d
> (0x9c406a, 0x2181ebc0, 0x6, 0x80f8a28c)
> 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x893a16 kpstartsched+
> 0xa6 (0x9c406a, 0x6, 0x2181ebc0, 0x9c406a)
> 01:00000:00000:1999/11/09 17:50:23.25 kernel pc: 0x86d361 kestartup+
0x451
> (0x0, 0x0, 0x0, 0x0)
> 01:00000:00000:1999/11/09 17:50:23.25 kernel pc: 0x77f04ee8 KERNEL32.dll
> (0x0, 0x0, 0x0, 0x0)
> 01:00000:00000:1999/11/09 17:50:23.25 kernel end of stack trace, kernel
> service process: kpid 3407924
>
> After raising a Tech Support Case with Sybase, they advised I move to ESD
3.
> Now I am getting the following stack trace
>
> 00:00000:00000:2000/01/07 17:36:29.39 kernel SQL Server system exception
> (0xc0000005) generated by a storage access violation.
> 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x8aa367
> os_get_cur_stk_desc+ 0x57 (0x125dd3c, 0x2a002a, 0x125dd3c, 0x0)
> 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x8aa367
> os_get_cur_stk_desc+ 0x57 (0x125dd3c, 0x125e290, 0x270f, 0x2)
> 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x88ac24 pcstkwalk+
0x224
> (0x2a002a, 0x2, 0x270f, 0x0)
> 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x88a7be ucstkgentrace+
> 0x1ce (0x2a002a, 0x1, 0x125ff98, 0x0)
> 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x869ee4 ucbacktrace+
0x84
> (0xc0000005, 0x7800ef4e, 0x125e51c, 0x0)
> 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x862ba4 kiexception+
> 0x1b4 (0x1, 0x53f60, 0xffffffff, 0x77f04ee8)
> 00:00000:00000:2000/01/07 17:36:30.11 kernel pc: 0x4017fd scm__main+ 0xfd
> (0x0, 0x0, 0x0, 0x0)
> 00:00000:00000:2000/01/07 17:36:30.11 kernel pc: 0x77dd8bec ADVAPI32.dll
> (0x0, 0x0, 0x0, 0x0)
> 00:00000:00000:2000/01/07 17:36:30.11 kernel end of stack trace, kernel
> service process: kpid 2752554
> 00:00000:00000:2000/01/07 17:36:30.11 kernel engine 0, os pid 28 exited
> 00:00000:00000:2000/01/07 17:36:30.11 kernel Could not replace infected
> engine.
>
> All that seems to have changed is the dll mentioned in the stack trace.
Does
> anyone have any ideas as to what is going wrong. Otherwise l will go back
to
> ESD 1, at least that version was stable.
>
>
>
>


Kenneth Damgaard Posted on 2000-01-12 09:44:35.0Z
From: "Kenneth Damgaard" <kennethp@aloc.dk>
Subject: Re: 11.9.2.1 ESD 3
References: <oOUPaJ4W$GA.223@forums.sybase.com> <fwIxS7BX$GA.177@forums.sybase.com>
Organization: ALOC Bonnier A/S
Message-ID: <01bf5ce1$16f95820$790ca8c0@nt6127>
X-Newsreader: Microsoft Internet News 4.70.1161
Newsgroups: sybase.public.sqlserver.nt
Date: Wed, 12 Jan 2000 04:44:35 -0500
Lines: 116
NNTP-Posting-Host: 195.41.127.25
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2697
Article PK: 1090152

Hey!!

I had the same stack trace problems, and found out the EBF8671 is the
soulution, now the servers are running stable a as rock

Kenneth

Simon Trowbridge <simon.trowbridge@screwfix.com> skrev i artiklen
<fwIxS7BX$GA.177@forums.sybase.com>...

> I have been getting this issue as well, running virtually the same
> configuration as you, but on Compaq Proliant's.
>
> I too, after getting these errors, was asked to move to ESD 2. This then
> had more exception errors. I was then asked to move to ESD 3, again had
> more errors.
>
> I moved to ESD4 on 20/12/99 when it first became available - DON'T MOVE
TO
> IT! - that still has an issue. Whilst ESD4 fixes the exception error
with
> syb_io_poll, there is a new exception error generated which causes the
> server to "freeze".
>
> I am now awaiting a Sybase "emergency fix" for this problem with the
> ESD4(EBF 8741) patch which according to Sybase Tech Support will be 31st
> January.
>
> If anyone else is experiencing these issues, I would be interested to
hear
> from you, or if you know of this problem and when it is going to be
FIXED!
>
> Regards,
>
> Simon Trowbridge
>
> M Watkins <MWatkins@Channel4.co.uk> wrote in message
> news:oOUPaJ4W$GA.223@forums.sybase.com...
> > On a Dell Poweredge 6300 with 2 Pentium II 450 Xeons, 2GB RAM , 32MB
Raid
> > Controller using Raid 1/0 running Sybase 11.9.2.1 with ESD 2 and NT
> service
> > pack 5, I was getting the following stack trace.
> >
> > 01:00000:00000:1999/11/09 17:50:23.01 kernel SQL Server system
exception
> > (0xc0000005) generated by a storage access violation.
> > 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x0 (suspect virtual
> > address)(0x2002e040, 0x1e5fcb4, 0x0, 0x0)
> > 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x0 (suspect virtual
> > address)(0x1, 0x0, 0x1cbfed4, 0x8955d7)
> > 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x8a3dc9 syb_io_poll+
> 0xb9
> > (0x1, 0x20011f40, 0x0, 0x0)
> > 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x8a3e4a
os_schedcoma+
> > 0x1a (0x1, 0x20011f40, 0x20019334, 0x93e07c)
> > 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x8955d7 kpcheckio+
0xe7
> > (0x0, 0x0, 0x2, 0x20011f40)
> > 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x89466d kpsched+
0xc0d
> > (0x9c406a, 0x2181ebc0, 0x6, 0x80f8a28c)
> > 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x893a16
kpstartsched+
> > 0xa6 (0x9c406a, 0x6, 0x2181ebc0, 0x9c406a)
> > 01:00000:00000:1999/11/09 17:50:23.25 kernel pc: 0x86d361 kestartup+
> 0x451
> > (0x0, 0x0, 0x0, 0x0)
> > 01:00000:00000:1999/11/09 17:50:23.25 kernel pc: 0x77f04ee8
KERNEL32.dll
> > (0x0, 0x0, 0x0, 0x0)
> > 01:00000:00000:1999/11/09 17:50:23.25 kernel end of stack trace,
kernel
> > service process: kpid 3407924
> >
> > After raising a Tech Support Case with Sybase, they advised I move to
ESD
> 3.
> > Now I am getting the following stack trace
> >
> > 00:00000:00000:2000/01/07 17:36:29.39 kernel SQL Server system
exception
> > (0xc0000005) generated by a storage access violation.
> > 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x8aa367
> > os_get_cur_stk_desc+ 0x57 (0x125dd3c, 0x2a002a, 0x125dd3c, 0x0)
> > 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x8aa367
> > os_get_cur_stk_desc+ 0x57 (0x125dd3c, 0x125e290, 0x270f, 0x2)
> > 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x88ac24 pcstkwalk+
> 0x224
> > (0x2a002a, 0x2, 0x270f, 0x0)
> > 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x88a7be
ucstkgentrace+
> > 0x1ce (0x2a002a, 0x1, 0x125ff98, 0x0)
> > 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x869ee4 ucbacktrace+
> 0x84
> > (0xc0000005, 0x7800ef4e, 0x125e51c, 0x0)
> > 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x862ba4 kiexception+
> > 0x1b4 (0x1, 0x53f60, 0xffffffff, 0x77f04ee8)
> > 00:00000:00000:2000/01/07 17:36:30.11 kernel pc: 0x4017fd scm__main+
0xfd
> > (0x0, 0x0, 0x0, 0x0)
> > 00:00000:00000:2000/01/07 17:36:30.11 kernel pc: 0x77dd8bec
ADVAPI32.dll
> > (0x0, 0x0, 0x0, 0x0)
> > 00:00000:00000:2000/01/07 17:36:30.11 kernel end of stack trace,
kernel
> > service process: kpid 2752554
> > 00:00000:00000:2000/01/07 17:36:30.11 kernel engine 0, os pid 28
exited
> > 00:00000:00000:2000/01/07 17:36:30.11 kernel Could not replace
infected
> > engine.
> >
> > All that seems to have changed is the dll mentioned in the stack trace.
> Does
> > anyone have any ideas as to what is going wrong. Otherwise l will go
back
> to
> > ESD 1, at least that version was stable.
> >
> >
> >
> >
>
>
>


Fred Seen Posted on 2000-01-11 02:58:15.0Z
Reply-To: "Fred Seen" <seenf@kmb.com.hk>
From: "Fred Seen" <seenf@kmb.com.hk>
References: <oOUPaJ4W$GA.223@forums.sybase.com>
Subject: Re: 11.9.2.1 ESD 3
Date: Tue, 11 Jan 2000 10:58:15 +0800
Lines: 79
Organization: KMB
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: <eOOR7$9W$GA.300@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.nt
NNTP-Posting-Host: 202.76.33.62
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2717
Article PK: 1090183

Try ESD4 or EBF8741 it should fix the stack trace problems you are having.
^_^

Cheers,
Fred

"M Watkins" <MWatkins@Channel4.co.uk> wrote in message
news:oOUPaJ4W$GA.223@forums.sybase.com...
> On a Dell Poweredge 6300 with 2 Pentium II 450 Xeons, 2GB RAM , 32MB Raid
> Controller using Raid 1/0 running Sybase 11.9.2.1 with ESD 2 and NT
service
> pack 5, I was getting the following stack trace.
>
> 01:00000:00000:1999/11/09 17:50:23.01 kernel SQL Server system exception
> (0xc0000005) generated by a storage access violation.
> 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x0 (suspect virtual
> address)(0x2002e040, 0x1e5fcb4, 0x0, 0x0)
> 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x0 (suspect virtual
> address)(0x1, 0x0, 0x1cbfed4, 0x8955d7)
> 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x8a3dc9 syb_io_poll+
0xb9
> (0x1, 0x20011f40, 0x0, 0x0)
> 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x8a3e4a os_schedcoma+
> 0x1a (0x1, 0x20011f40, 0x20019334, 0x93e07c)
> 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x8955d7 kpcheckio+ 0xe7
> (0x0, 0x0, 0x2, 0x20011f40)
> 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x89466d kpsched+ 0xc0d
> (0x9c406a, 0x2181ebc0, 0x6, 0x80f8a28c)
> 01:00000:00000:1999/11/09 17:50:23.23 kernel pc: 0x893a16 kpstartsched+
> 0xa6 (0x9c406a, 0x6, 0x2181ebc0, 0x9c406a)
> 01:00000:00000:1999/11/09 17:50:23.25 kernel pc: 0x86d361 kestartup+
0x451
> (0x0, 0x0, 0x0, 0x0)
> 01:00000:00000:1999/11/09 17:50:23.25 kernel pc: 0x77f04ee8 KERNEL32.dll
> (0x0, 0x0, 0x0, 0x0)
> 01:00000:00000:1999/11/09 17:50:23.25 kernel end of stack trace, kernel
> service process: kpid 3407924
>
> After raising a Tech Support Case with Sybase, they advised I move to ESD
3.
> Now I am getting the following stack trace
>
> 00:00000:00000:2000/01/07 17:36:29.39 kernel SQL Server system exception
> (0xc0000005) generated by a storage access violation.
> 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x8aa367
> os_get_cur_stk_desc+ 0x57 (0x125dd3c, 0x2a002a, 0x125dd3c, 0x0)
> 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x8aa367
> os_get_cur_stk_desc+ 0x57 (0x125dd3c, 0x125e290, 0x270f, 0x2)
> 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x88ac24 pcstkwalk+
0x224
> (0x2a002a, 0x2, 0x270f, 0x0)
> 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x88a7be ucstkgentrace+
> 0x1ce (0x2a002a, 0x1, 0x125ff98, 0x0)
> 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x869ee4 ucbacktrace+
0x84
> (0xc0000005, 0x7800ef4e, 0x125e51c, 0x0)
> 00:00000:00000:2000/01/07 17:36:30.06 kernel pc: 0x862ba4 kiexception+
> 0x1b4 (0x1, 0x53f60, 0xffffffff, 0x77f04ee8)
> 00:00000:00000:2000/01/07 17:36:30.11 kernel pc: 0x4017fd scm__main+ 0xfd
> (0x0, 0x0, 0x0, 0x0)
> 00:00000:00000:2000/01/07 17:36:30.11 kernel pc: 0x77dd8bec ADVAPI32.dll
> (0x0, 0x0, 0x0, 0x0)
> 00:00000:00000:2000/01/07 17:36:30.11 kernel end of stack trace, kernel
> service process: kpid 2752554
> 00:00000:00000:2000/01/07 17:36:30.11 kernel engine 0, os pid 28 exited
> 00:00000:00000:2000/01/07 17:36:30.11 kernel Could not replace infected
> engine.
>
> All that seems to have changed is the dll mentioned in the stack trace.
Does
> anyone have any ideas as to what is going wrong. Otherwise l will go back
to
> ESD 1, at least that version was stable.
>
>
>
>