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.

Problem starting Sybase 11.0.2.1 on Windows NT 4.0 (Build 1381-has SP 2 applied)

3 posts in Windows NT Last posting was on 1997-09-13 01:34:40.0Z
George Patrick Sand Posted on 1997-07-11 17:12:06.0Z
Message-ID: <33C66966.4800@mci.com>
Date: Fri, 11 Jul 1997 13:12:06 -0400
From: George Patrick Sand <Pat.Sand@mci.com>
Reply-To: Pat.Sand@mci.com
Organization: MCI FIS (3392/082)
X-Mailer: Mozilla 3.0Gold (Win95; I)
MIME-Version: 1.0
Subject: Problem starting Sybase 11.0.2.1 on Windows NT 4.0 (Build 1381-has SP 2 applied)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 36
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5589
Article PK: 1081666

Whenever I reboot my NT system, I get the following sequence of events
and messages:

in the system log (Event Viewer) in increasing time order:

1.The Sybase BckServer ... service hung on starting.

2.The Sybase SQLServer ... service hung on starting.

3. The Sybase MonServer....depends on the Sybase SQLServer...service
which failed to start because of the following error:
After Starting, the service hung in a start-pending state.

I am also getting warnings that a default network selection was made for
my browser (IE 3.0) to \Device\NwlnkIpx, then to \Device\NetBT_El90x1,
then to Device\NwlnkNb, and finally to \Device\Nbf_El90x1.
(Don't know if this is relevant, but...)

and I get that an application error has occurred in NLNWADVT.exe
Exception: access violation (0xc0000005), Address: 0x0040102d

I am using TCP/IP and NetBEUI (Windows 3.11/95/NT out-of-the-box
protocol). I try to avoid using NetWare like the plague...(NetWare and
I are incompatible--I can find strange errors nobody else can).

The only thing I have determined that has changed is that my database
engine now has data to deal with (about 200 megabytes).

Any help would be appreciated...Thanks in advance...

(If you need more info, let me know and I can e-mail it.)
--
"Travelin' light but right..."
G. Patrick Sand (Pat.Sand@MCI.COM)
Pager: 1-800-MCI-WORD Pin: 212-2610
Also: PatSand@msn.com


Dan Much Posted on 1997-08-05 14:08:58.0Z
From: "Dan Much" <DMuch@csd.ca.gov>
Subject: Re: Problem starting Sybase 11.0.2.1 on Windows NT 4.0 (Build 1381-has SP 2 applied)
References: <33C66966.4800@mci.com>
Message-ID: <01bca1b1$c3826fc0$32cde1cd@dmuch>
X-Newsreader: Microsoft Internet News 4.70.1161
Newsgroups: sybase.public.sqlserver.nt
Date: Tue, 05 Aug 1997 10:08:58 -0400
Lines: 50
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5579
Article PK: 1081655

George,

I have read elsewhere that System 11.0.2.x is terrible and that Sybase is
recommending staying with or rolling back to 11.0.1.x until 11.0.3 is
released.

Under NT, the browser election has nothing to do with IE, it is part of the
browser service (like browsing Network Neighborhood)

Not sure what NLNWADVT.exe is.

Your protocols shouldn't matter to starting Sybase on the server.

George Patrick Sand <Pat.Sand@mci.com> wrote in article
<33C66966.4800@mci.com>...
> Whenever I reboot my NT system, I get the following sequence of events
> and messages:
>
> in the system log (Event Viewer) in increasing time order:
>
> 1.The Sybase BckServer ... service hung on starting.
>
> 2.The Sybase SQLServer ... service hung on starting.
>
> 3. The Sybase MonServer....depends on the Sybase SQLServer...service
> which failed to start because of the following error:
> After Starting, the service hung in a start-pending state.
>
> I am also getting warnings that a default network selection was made for
> my browser (IE 3.0) to \Device\NwlnkIpx, then to \Device\NetBT_El90x1,
> then to Device\NwlnkNb, and finally to \Device\Nbf_El90x1.
> (Don't know if this is relevant, but...)
>
> and I get that an application error has occurred in NLNWADVT.exe
> Exception: access violation (0xc0000005), Address: 0x0040102d
>
> I am using TCP/IP and NetBEUI (Windows 3.11/95/NT out-of-the-box
> protocol). I try to avoid using NetWare like the plague...(NetWare and
> I are incompatible--I can find strange errors nobody else can).
>
> The only thing I have determined that has changed is that my database
> engine now has data to deal with (about 200 megabytes).
>
> Any help would be appreciated...Thanks in advance...
>
> (If you need more info, let me know and I can e-mail it.)
> --
> "Travelin' light but right..."
> G. Patrick Sand (Pat.Sand@MCI.COM)
> Pager: 1-800-MCI-WORD Pin: 212-2610
> Also: PatSand@msn.com
>


Mike Meek Posted on 1997-09-13 01:34:40.0Z
Message-ID: <3419EDB0.52E4@sybase.com>
Date: Fri, 12 Sep 1997 18:34:40 -0700
From: Mike Meek <mmeek@sybase.com>
Reply-To: mmeek@sybase.com
Organization: Sybase Inc.
X-Mailer: Mozilla 3.01Gold (WinNT; U)
MIME-Version: 1.0
Subject: Re: Problem starting Sybase 11.0.2.1 on Windows NT 4.0 (Build 1381-has SP 2 applied)
References: <33C66966.4800@mci.com> <01bca1b1$c3826fc0$32cde1cd@dmuch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 85
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5531
Article PK: 1081609


Dan Much wrote:
>
> George,
>
> I have read elsewhere that System 11.0.2.x is terrible and that Sybase is
> recommending staying with or rolling back to 11.0.1.x until 11.0.3 is
> released.
>
> Under NT, the browser election has nothing to do with IE, it is part of the
> browser service (like browsing Network Neighborhood)
>
> Not sure what NLNWADVT.exe is.
>
> Your protocols shouldn't matter to starting Sybase on the server.
>
> George Patrick Sand <Pat.Sand@mci.com> wrote in article
> <33C66966.4800@mci.com>...
> > Whenever I reboot my NT system, I get the following sequence of events
> > and messages:
> >
> > in the system log (Event Viewer) in increasing time order:
> >
> > 1.The Sybase BckServer ... service hung on starting.
> >
> > 2.The Sybase SQLServer ... service hung on starting.
> >
> > 3. The Sybase MonServer....depends on the Sybase SQLServer...service
> > which failed to start because of the following error:
> > After Starting, the service hung in a start-pending state.
> >
> > I am also getting warnings that a default network selection was made for
> > my browser (IE 3.0) to \Device\NwlnkIpx, then to \Device\NetBT_El90x1,
> > then to Device\NwlnkNb, and finally to \Device\Nbf_El90x1.
> > (Don't know if this is relevant, but...)
> >
> > and I get that an application error has occurred in NLNWADVT.exe
> > Exception: access violation (0xc0000005), Address: 0x0040102d
> >
> > I am using TCP/IP and NetBEUI (Windows 3.11/95/NT out-of-the-box
> > protocol). I try to avoid using NetWare like the plague...(NetWare and
> > I are incompatible--I can find strange errors nobody else can).
> >
> > The only thing I have determined that has changed is that my database
> > engine now has data to deal with (about 200 megabytes).
> >
> > Any help would be appreciated...Thanks in advance...
> >
> > (If you need more info, let me know and I can e-mail it.)
> > --
> > "Travelin' light but right..."
> > G. Patrick Sand (Pat.Sand@MCI.COM)
> > Pager: 1-800-MCI-WORD Pin: 212-2610
> > Also: PatSand@msn.com
> >

Dan and George,

Sybase is DEFINATELY NOT recommending rolling back to 11.0.1.x for
NT. I run customer tests every day with the base 11.0.2 MR release on
NT 3.51. The base MR release of Sybase SQL Server works fine with NT
3.51. If you are running a later version like 11.0.2.2 on NT you should
have installed SP3 (Service Pack 3) or better. SP5 Ideally.
The reason you need the Service Packs installed is because Sybase SQL
Server 11.0.2.2 uses native threads and fibers. The use of the fibers
in NT is a new functionality specific to the later versions of SQL
Server. That is possibly why the service is hanging at startup.
You should check the SQL Server errorlog to see where if there is any
more information that can be used to pinpoint the problem. Using Server
Config you can specify that all errorlog messages go into the NT event
log.
It appears that you have set it up for SQL Server, Backup Server, and
Monitor Server to boot at system boot. Disable this and use the
Services Manager to start the SQL Server after you have seen NT come up
clean.
I would do a search on NLNWADVT.exe and see what application it is
associated with. That may be the major culprit on your system.
Good Luck,

Mike Meek
Sybase Alliance