Named Instance stack dump upon startup

Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
I have a SQL server for a document imaging application. SQL is installed
along with a named instance that is necessary for the application. I was not
involved in the installation or setup of this machine, but now the
responsibility has fallen to me to maintain it.
The named instance occasionally (once every other month) generates a stack
dump upon startup. Generally all I have to do to "clean" this up is to stop
and restart SQL and it's services, or a reboot. Yesterday I found myself in
this situation again, but the normal "fixes" did not resolve it. This mornin
g
I was searching the net for clues, and still attempting to shutdown and
restart SQL, when SQL finally cooperated and started clean - the app works
fine now.
I have never found anything in the event viewer to give me a hint. The
information in the logs has not provided me with any answers, though I am
pretty inexperiened in that area. I have not been able to find any of the lo
g
contents in MSKB or elsewhere.
I am confident enough to reinstall SQL, to see if any of this is fixed, but
the application's consultant is afraid that the app will break if I do that.
I need to take the time to FIX this rather than band-aiding it when it
breaks. I inherited this last summer, but the issue has been occurring for 2
years, and the server's previous caretaker did not deal with it. The other
hindrance is that our company will be closing this time next year, so the
attitude here is to just keep things running, without any new investment.
Any help with this is much appreciated! Thank-you!!!
Part of the log is listed below:
--
2005-03-22 08:37:42.80 server Microsoft SQL Server 2000 - 8.00.194 (Intel
X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
2005-03-22 08:37:42.80 server Copyright (C) 1988-2000 Microsoft Corporation.
2005-03-22 08:37:42.80 server All rights reserved.
2005-03-22 08:37:42.80 server Server Process ID is 696.
2005-03-22 08:37:42.80 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$LASERFICHE\LOG\ERRORLOG'.
2005-03-22 08:37:42.82 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2005-03-22 08:37:42.92 server SQL Server configured for thread mode
processing.
2005-03-22 08:37:42.92 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-03-22 08:37:43.08 spid2 Starting up database 'master'.
2005-03-22 08:37:43.17 spid2 0 transactions rolled back in database 'master'
(1).
2005-03-22 08:37:43.17 spid2 Recovery is checkpointing database 'master' (1)
2005-03-22 08:37:43.21 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-03-22 08:37:43.21 spid5 Starting up database 'model'.
2005-03-22 08:37:43.22 spid2 Server name is 'HGINT10\LASERFICHE'.
2005-03-22 08:37:43.28 spid8 Starting up database 'msdb'.
2005-03-22 08:37:43.30 spid9 Starting up database 'Reports'.
2005-03-22 08:37:43.39 spid5 Clearing tempdb database.
2005-03-22 08:37:44.88 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2005-03-22 08:37:44.88 server SQL server listening on 157.154.121.239:3977,
127.0.0.1:3977.
2005-03-22 08:37:44.88 server SQL Server is ready for client connections
2005-03-22 08:37:45.47 spid5 Starting up database 'tempdb'.
2005-03-22 08:37:45.50 spid2 Recovery complete.
2005-03-22 08:37:58.50 server Using 'sqlimage.dll' version '4.0.5'
Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL$LASERFICHE\log\SQL00640.dmp
2005-03-22 08:37:58.50 server process_loginread: Process 2072 generated
fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
.
.
.
2005-03-22 09:00:52.91 server SQL Server is aborting. Fatal exception
c0000005 caught.
Karen
"There are two documents in your in-box: tragedy and comedy. Your Pick."
--Dale DautenHi
Install sp3a for SQL Server 2000. You have no Service Pack on that instance.
Server Version: http://www.aspfaq.com/show.asp?id=2160
Regards
Mike
"Karen" wrote:

> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
> I have a SQL server for a document imaging application. SQL is installed
> along with a named instance that is necessary for the application. I was n
ot
> involved in the installation or setup of this machine, but now the
> responsibility has fallen to me to maintain it.
> The named instance occasionally (once every other month) generates a stack
> dump upon startup. Generally all I have to do to "clean" this up is to sto
p
> and restart SQL and it's services, or a reboot. Yesterday I found myself i
n
> this situation again, but the normal "fixes" did not resolve it. This morn
ing
> I was searching the net for clues, and still attempting to shutdown and
> restart SQL, when SQL finally cooperated and started clean - the app works
> fine now.
> I have never found anything in the event viewer to give me a hint. The
> information in the logs has not provided me with any answers, though I am
> pretty inexperiened in that area. I have not been able to find any of the
log
> contents in MSKB or elsewhere.
> I am confident enough to reinstall SQL, to see if any of this is fixed, bu
t
> the application's consultant is afraid that the app will break if I do tha
t.
> I need to take the time to FIX this rather than band-aiding it when it
> breaks. I inherited this last summer, but the issue has been occurring for
2
> years, and the server's previous caretaker did not deal with it. The other
> hindrance is that our company will be closing this time next year, so the
> attitude here is to just keep things running, without any new investment.
> Any help with this is much appreciated! Thank-you!!!
> Part of the log is listed below:
> --
> 2005-03-22 08:37:42.80 server Microsoft SQL Server 2000 - 8.00.194 (Intel
> X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2005-03-22 08:37:42.80 server Copyright (C) 1988-2000 Microsoft Corporatio
n.
> 2005-03-22 08:37:42.80 server All rights reserved.
> 2005-03-22 08:37:42.80 server Server Process ID is 696.
> 2005-03-22 08:37:42.80 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$LASERFICHE\LOG\ERRORLOG'.
> 2005-03-22 08:37:42.82 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2005-03-22 08:37:42.92 server SQL Server configured for thread mode
> processing.
> 2005-03-22 08:37:42.92 server Using dynamic lock allocation. [500] Loc
k
> Blocks, [1000] Lock Owner Blocks.
> 2005-03-22 08:37:43.08 spid2 Starting up database 'master'.
> 2005-03-22 08:37:43.17 spid2 0 transactions rolled back in database 'maste
r'
> (1).
> 2005-03-22 08:37:43.17 spid2 Recovery is checkpointing database 'master' (
1)
> 2005-03-22 08:37:43.21 server Using 'SSNETLIB.DLL' version '8.0.194'.
> 2005-03-22 08:37:43.21 spid5 Starting up database 'model'.
> 2005-03-22 08:37:43.22 spid2 Server name is 'HGINT10\LASERFICHE'.
> 2005-03-22 08:37:43.28 spid8 Starting up database 'msdb'.
> 2005-03-22 08:37:43.30 spid9 Starting up database 'Reports'.
> 2005-03-22 08:37:43.39 spid5 Clearing tempdb database.
> 2005-03-22 08:37:44.88 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
> 2005-03-22 08:37:44.88 server SQL server listening on 157.154.121.239:3977
,
> 127.0.0.1:3977.
> 2005-03-22 08:37:44.88 server SQL Server is ready for client connections
> 2005-03-22 08:37:45.47 spid5 Starting up database 'tempdb'.
> 2005-03-22 08:37:45.50 spid2 Recovery complete.
> 2005-03-22 08:37:58.50 server Using 'sqlimage.dll' version '4.0.5'
> Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL$LASERFICHE\log\SQL00640.dmp
> 2005-03-22 08:37:58.50 server process_loginread: Process 2072 generated
> fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
> terminating this process.
> .
> .
> .
> 2005-03-22 09:00:52.91 server SQL Server is aborting. Fatal exception
> c0000005 caught.
> Karen
> "There are two documents in your in-box: tragedy and comedy. Your Pick."
> --Dale Dauten|||Thanks, Mike, but I have never been able to get sp3a applied to the instance
.
It has been a few months since the last time I tried, so I do not have the
error available, and it will be a few days until I can try again.
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> Install sp3a for SQL Server 2000. You have no Service Pack on that instanc
e.
> Server Version: http://www.aspfaq.com/show.asp?id=2160
> Regards
> Mike|||Hi
The fact that sp3a will not install indicates that there is something wrong
with the machine or installation. So getting stack dumps is not unexpected.
Regards
Mike
"Karen" wrote:

> Thanks, Mike, but I have never been able to get sp3a applied to the instan
ce.
> It has been a few months since the last time I tried, so I do not have the
> error available, and it will be a few days until I can try again.
> "Mike Epprecht (SQL MVP)" wrote:
>
>|||Hi Mike,
It certainly does.
I have discovered that the named instance really isn't a named instance, it
is MSDE, so it is understandable that the sp's did not install. It would hav
e
been nice if the SP install would have given a message to the fact that it
was the wrong version, but that would have been too easy!
I will install the correct sp this week & perhaps there will no longer be
any problems.
Thanks,
Karen
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> The fact that sp3a will not install indicates that there is something wron
g
> with the machine or installation. So getting stack dumps is not unexpected
.
> Regards
> Mike
> "Karen" wrote:
>sql