MSSQLServer Service terminated unexpectedly MS-SQL 2000 with SP4

MSSQLServer service terminated unexpectedly

We are running SQL Server 2000 with SP4. This server has been running for the past six months with no SQL server problems. A Max of 10 users have access to the application running on this server.

The Event Viewer Log shows the
Source: MSSQLServer
Category: (2)
Type: Error
EventID: 17052
Description: The MSSQLSERVER service terminated unexpectedly.

No other error messages were seen in the SQL server log or windows event viewer.
The time when it terminated was not during peak load/activity.

The server is Windows 2003 with SP1. Any help would be appreciated.Are there any *.mdmp or *.txt files in the \mssql\log directory where the errorlogs reside?|||Sorry for my late response. There are a few mdmp and txt files in the log directory but all the log files have dates prior ( probably couple of months old file) to the day the crash occurred.

MSSQLSERVER service terminated unexpectedly

Hi

For 15 days now my SQL server service is terminating with the following error

MSSQLSERVER service terminated unexpectedly. It has done this 2 Time(s).
This service terminates and restarts automatically and sometimes doesnt restart we have to mannuly start it again.
Event ID: 7034.

Version Details

Version: MSSQL Server 2000
Service Pack: 3a
Build: 8.0.0.760

I have checked many forums most of them suggest to apply the latest service pack. But the same error has been reported by sites having SP4 also.
Kindly help.

Thank you
wasimI'd guess a hardware problem.

Or...
...there is an infamous story at one of my old employers about a server that kept unexpectedly rebooting itself. It would always happen at about the same time each evening, but never the exact same time. The techs tried everything to figure out what was going on, but to no avail.
Finally one of the techs agreed to spend the night in the server room to observe the issue first-hand. All was quiet, until about the time the reboot was expected to occur. The tech watched as one of the late-shift workers entered the room to change the tapes. She was, shall we say, a short and portly woman, and as she bent over to eject the tape on one of the servers her derrier' smushed up against the suspect server, depressing its restart button.

Problem diagnosed and solved.

True story.|||Check the start-up account of the MSSQLServer service to see if its password has expired. Or if the account's profile has changed. Or if the service is running under credentials of an employee who has left the company.

MSSQLSERVER service terminated unexpectedly

HI
I have server MSDE 2000 SP3
frequently server stopped, and print in log file information:
1)
17310 :
SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2)
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.
3)
The MSSQLSERVER service terminated unexpectedly.
If you didn't find anything in KB on this and you are on the current service pack: Open a case with MS
Support. Exceptions etc are most often bugs in SQL Server, so you will probably need a fix or workaround from
MS for this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bies" <ANTYSPAMbies22@.poczta.onet.pl> wrote in message news:ca1ij7$dd6$1@.atlantis.news.tpi.pl...
> HI
> I have server MSDE 2000 SP3
> frequently server stopped, and print in log file information:
> 1)
> 17310 :
> SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> 2)
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
> 3)
> The MSSQLSERVER service terminated unexpectedly.
>

MSSQLSERVER service terminated unexpectedly

HI
I have server MSDE 2000 SP3
frequently server stopped, and print in log file information:

1)
17310 :
SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

2)
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.

3)
The MSSQLSERVER service terminated unexpectedly.Hi

This may be as in:

http://support.microsoft.com/defaul...kb;en-us;814572

other possibilities
http://search.microsoft.com/search/...ql+server&na=54

You may also want to check if a anti-virus software is affecting it.

John

"Bies" <ANTYSPAMbies22@.poczta.onet.pl> wrote in message
news:ca1ie6$6gh$1@.nemesis.news.tpi.pl...
> HI
> I have server MSDE 2000 SP3
> frequently server stopped, and print in log file information:
> 1)
> 17310 :
> SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> 2)
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
> 3)
> The MSSQLSERVER service terminated unexpectedly.|||> This may be as in:
> http://support.microsoft.com/defaul...kb;en-us;814572
> other possibilities
http://search.microsoft.com/search/...ql+server&na=54
> You may also want to check if a anti-virus software is affecting it.

thx

MSSQLSERVER service terminated unexpectedly

This probably does not apply, but we had a similar problem and it had to do
with the following article:
KB article 822360
MS had us put in a couple of hot fixes and it seems to have taken care of
the problem.
"Martin Paterson" wrote:

> I have a couple of sites that are running MS SQL 2000 Service pack 4 that
are
> stopping (apperantly randomly) and restarting itself. This is causing gre
at
> havoc on some of my applications that are attached to this database. The
> server is dedicated for this purpose only and is hosting only on database.
> reviewing the error logs have not resulted in any explanation as to why SQ
L
> is dying. Google & MS knowledgebase has also resulted in no
> explanation/solution. Any assistance would be greatly appreciated.I have a couple of sites that are running MS SQL 2000 Service pack 4 that ar
e
stopping (apperantly randomly) and restarting itself. This is causing great
havoc on some of my applications that are attached to this database. The
server is dedicated for this purpose only and is hosting only on database.
reviewing the error logs have not resulted in any explanation as to why SQL
is dying. Google & MS knowledgebase has also resulted in no
explanation/solution. Any assistance would be greatly appreciated.|||This probably does not apply, but we had a similar problem and it had to do
with the following article:
KB article 822360
MS had us put in a couple of hot fixes and it seems to have taken care of
the problem.
"Martin Paterson" wrote:

> I have a couple of sites that are running MS SQL 2000 Service pack 4 that
are
> stopping (apperantly randomly) and restarting itself. This is causing gre
at
> havoc on some of my applications that are attached to this database. The
> server is dedicated for this purpose only and is hosting only on database.
> reviewing the error logs have not resulted in any explanation as to why SQ
L
> is dying. Google & MS knowledgebase has also resulted in no
> explanation/solution. Any assistance would be greatly appreciated.|||I looked at KB822360 and it appears to be for active directory issues. The
SQL server that is having this problem does not sit on a domain. thanks in
advance for your assistance.
"CLM" wrote:
[vbcol=seagreen]
> This probably does not apply, but we had a similar problem and it had to d
o
> with the following article:
> KB article 822360
> MS had us put in a couple of hot fixes and it seems to have taken care of
> the problem.
> "Martin Paterson" wrote:
>|||I looked at KB822360 and it appears to be for active directory issues. The
SQL server that is having this problem does not sit on a domain. thanks in
advance for your assistance.
"CLM" wrote:
[vbcol=seagreen]
> This probably does not apply, but we had a similar problem and it had to d
o
> with the following article:
> KB article 822360
> MS had us put in a couple of hot fixes and it seems to have taken care of
> the problem.
> "Martin Paterson" wrote:
>|||What does the sql errorlog say?
Martin Paterson wrote:[vbcol=seagreen]
> I looked at KB822360 and it appears to be for active directory issues. Th
e
> SQL server that is having this problem does not sit on a domain. thanks i
n
> advance for your assistance.
> "CLM" wrote:
>|||there are no errors that I can see...but here is an example of what is
displayed:
2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-06-19 07:01:01.44 server All rights reserved.
2006-06-19 07:01:01.44 server Server Process ID is 2032.
2006-06-19 07:01:01.44 server Logging SQL Server messages in file
'F:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-06-19 07:01:01.46 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2006-06-19 07:01:01.57 server SQL Server configured for thread mode
processing.
2006-06-19 07:01:01.60 server Using dynamic lock allocation. [2500] L
ock
Blocks, [5000] Lock Owner Blocks.
2006-06-19 07:01:02.08 server Attempting to initialize Distributed
Transaction Coordinator.
2006-06-19 07:01:05.10 spid3 Starting up database 'master'.
2006-06-19 07:01:05.24 spid3 0 transactions rolled back in database
'master' (1).
2006-06-19 07:01:05.24 spid3 Recovery is checkpointing database 'master'
(1)
2006-06-19 07:01:05.36 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-06-19 07:01:05.36 spid5 Starting up database 'model'.
2006-06-19 07:01:05.38 spid3 Server name is 'SECDB'.
2006-06-19 07:01:05.40 spid8 Starting up database 'msdb'.
2006-06-19 07:01:05.40 spid9 Starting up database 'pubs'.
2006-06-19 07:01:05.40 spid10 Starting up database 'Northwind'.
2006-06-19 07:01:05.40 spid11 Starting up database 'SSW'.
2006-06-19 07:01:05.60 server SQL server listening on www.xxx.yyy.zzz:
1433.
2006-06-19 07:01:05.60 server SQL server listening on 127.0.0.1: 1433.
2006-06-19 07:01:05.61 spid5 Clearing tempdb database.
2006-06-19 07:01:05.85 spid8 134 transactions rolled forward in database
'msdb' (4).
2006-06-19 07:01:05.91 spid8 0 transactions rolled back in database
'msdb' (4).
2006-06-19 07:01:05.93 spid8 Recovery is checkpointing database 'msdb' (
4)
2006-06-19 07:01:06.27 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-06-19 07:01:06.27 server SQL Server is ready for client connections
2006-06-19 07:01:07.19 spid5 Starting up database 'tempdb'.
2006-06-19 07:01:08.35 spid11 314 transactions rolled forward in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 0 transactions rolled back in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 Recovery is checkpointing database 'SSW' (7
)
2006-06-19 07:01:09.44 spid53 Using 'odsole70.dll' version '2000.80.2039'
to execute extended stored procedure 'sp_OACreate'.
"SQLPoet" wrote:

> What does the sql errorlog say?
>
> Martin Paterson wrote:
>|||Martin Paterson wrote:
> there are no errors that I can see...but here is an example of what is
> displayed:
> 2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
> Corporation.
That's the current log that was generated when SQL restarted. What does
the archived error log contain? Last 15-20 lines should be sufficient.|||there are no errors that I can see...but here is an example of what is
displayed:
2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-06-19 07:01:01.44 server All rights reserved.
2006-06-19 07:01:01.44 server Server Process ID is 2032.
2006-06-19 07:01:01.44 server Logging SQL Server messages in file
'F:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-06-19 07:01:01.46 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2006-06-19 07:01:01.57 server SQL Server configured for thread mode
processing.
2006-06-19 07:01:01.60 server Using dynamic lock allocation. [2500] L
ock
Blocks, [5000] Lock Owner Blocks.
2006-06-19 07:01:02.08 server Attempting to initialize Distributed
Transaction Coordinator.
2006-06-19 07:01:05.10 spid3 Starting up database 'master'.
2006-06-19 07:01:05.24 spid3 0 transactions rolled back in database
'master' (1).
2006-06-19 07:01:05.24 spid3 Recovery is checkpointing database 'master'
(1)
2006-06-19 07:01:05.36 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-06-19 07:01:05.36 spid5 Starting up database 'model'.
2006-06-19 07:01:05.38 spid3 Server name is 'SECDB'.
2006-06-19 07:01:05.40 spid8 Starting up database 'msdb'.
2006-06-19 07:01:05.40 spid9 Starting up database 'pubs'.
2006-06-19 07:01:05.40 spid10 Starting up database 'Northwind'.
2006-06-19 07:01:05.40 spid11 Starting up database 'SSW'.
2006-06-19 07:01:05.60 server SQL server listening on www.xxx.yyy.zzz:
1433.
2006-06-19 07:01:05.60 server SQL server listening on 127.0.0.1: 1433.
2006-06-19 07:01:05.61 spid5 Clearing tempdb database.
2006-06-19 07:01:05.85 spid8 134 transactions rolled forward in database
'msdb' (4).
2006-06-19 07:01:05.91 spid8 0 transactions rolled back in database
'msdb' (4).
2006-06-19 07:01:05.93 spid8 Recovery is checkpointing database 'msdb' (
4)
2006-06-19 07:01:06.27 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-06-19 07:01:06.27 server SQL Server is ready for client connections
2006-06-19 07:01:07.19 spid5 Starting up database 'tempdb'.
2006-06-19 07:01:08.35 spid11 314 transactions rolled forward in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 0 transactions rolled back in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 Recovery is checkpointing database 'SSW' (7
)
2006-06-19 07:01:09.44 spid53 Using 'odsole70.dll' version '2000.80.2039'
to execute extended stored procedure 'sp_OACreate'.
"SQLPoet" wrote:

> What does the sql errorlog say?
>
> Martin Paterson wrote:
>|||Martin Paterson wrote:
> there are no errors that I can see...but here is an example of what is
> displayed:
> 2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
> Corporation.
That's the current log that was generated when SQL restarted. What does
the archived error log contain? Last 15-20 lines should be sufficient.

MSSQLSERVER service terminated unexpectedly

HI
I have server MSDE 2000 SP3
frequently server stopped, and print in log file information:
1)
17310 :
SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2)
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.
3)
The MSSQLSERVER service terminated unexpectedly.If you didn't find anything in KB on this and you are on the current service
pack: Open a case with MS
Support. Exceptions etc are most often bugs in SQL Server, so you will proba
bly need a fix or workaround from
MS for this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bies" <ANTYSPAMbies22@.poczta.onet.pl> wrote in message news:ca1ij7$dd6$1@.atlantis.news.tpi.
pl...
> HI
> I have server MSDE 2000 SP3
> frequently server stopped, and print in log file information:
> 1)
> 17310 :
> SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> 2)
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
> 3)
> The MSSQLSERVER service terminated unexpectedly.
>

MSSQLSERVER service terminated unexpectedly

HI
I have server MSDE 2000 SP3
frequently server stopped, and print in log file information:
1)
17310 :
SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2)
17311 :
SQL Server is aborting. Fatal exception c0000005 caught.
3)
The MSSQLSERVER service terminated unexpectedly.If you didn't find anything in KB on this and you are on the current service pack: Open a case with MS
Support. Exceptions etc are most often bugs in SQL Server, so you will probably need a fix or workaround from
MS for this.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bies" <ANTYSPAMbies22@.poczta.onet.pl> wrote in message news:ca1ij7$dd6$1@.atlantis.news.tpi.pl...
> HI
> I have server MSDE 2000 SP3
> frequently server stopped, and print in log file information:
> 1)
> 17310 :
> SqlDumpExceptionHandler: Process 1984 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> 2)
> 17311 :
> SQL Server is aborting. Fatal exception c0000005 caught.
> 3)
> The MSSQLSERVER service terminated unexpectedly.
>

MSSQLSERVER service terminated unexpectedly

I have a couple of sites that are running MS SQL 2000 Service pack 4 that are
stopping (apperantly randomly) and restarting itself. This is causing great
havoc on some of my applications that are attached to this database. The
server is dedicated for this purpose only and is hosting only on database.
reviewing the error logs have not resulted in any explanation as to why SQL
is dying. Google & MS knowledgebase has also resulted in no
explanation/solution. Any assistance would be greatly appreciated.This probably does not apply, but we had a similar problem and it had to do
with the following article:
KB article 822360
MS had us put in a couple of hot fixes and it seems to have taken care of
the problem.
"Martin Paterson" wrote:
> I have a couple of sites that are running MS SQL 2000 Service pack 4 that are
> stopping (apperantly randomly) and restarting itself. This is causing great
> havoc on some of my applications that are attached to this database. The
> server is dedicated for this purpose only and is hosting only on database.
> reviewing the error logs have not resulted in any explanation as to why SQL
> is dying. Google & MS knowledgebase has also resulted in no
> explanation/solution. Any assistance would be greatly appreciated.|||I looked at KB822360 and it appears to be for active directory issues. The
SQL server that is having this problem does not sit on a domain. thanks in
advance for your assistance.
"CLM" wrote:
> This probably does not apply, but we had a similar problem and it had to do
> with the following article:
> KB article 822360
> MS had us put in a couple of hot fixes and it seems to have taken care of
> the problem.
> "Martin Paterson" wrote:
> > I have a couple of sites that are running MS SQL 2000 Service pack 4 that are
> > stopping (apperantly randomly) and restarting itself. This is causing great
> > havoc on some of my applications that are attached to this database. The
> > server is dedicated for this purpose only and is hosting only on database.
> > reviewing the error logs have not resulted in any explanation as to why SQL
> > is dying. Google & MS knowledgebase has also resulted in no
> > explanation/solution. Any assistance would be greatly appreciated.|||What does the sql errorlog say?
Martin Paterson wrote:
> I looked at KB822360 and it appears to be for active directory issues. The
> SQL server that is having this problem does not sit on a domain. thanks in
> advance for your assistance.
> "CLM" wrote:
> > This probably does not apply, but we had a similar problem and it had to do
> > with the following article:
> > KB article 822360
> > MS had us put in a couple of hot fixes and it seems to have taken care of
> > the problem.
> >
> > "Martin Paterson" wrote:
> >
> > > I have a couple of sites that are running MS SQL 2000 Service pack 4 that are
> > > stopping (apperantly randomly) and restarting itself. This is causing great
> > > havoc on some of my applications that are attached to this database. The
> > > server is dedicated for this purpose only and is hosting only on database.
> > > reviewing the error logs have not resulted in any explanation as to why SQL
> > > is dying. Google & MS knowledgebase has also resulted in no
> > > explanation/solution. Any assistance would be greatly appreciated.|||there are no errors that I can see...but here is an example of what is
displayed:
2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-06-19 07:01:01.44 server All rights reserved.
2006-06-19 07:01:01.44 server Server Process ID is 2032.
2006-06-19 07:01:01.44 server Logging SQL Server messages in file
'F:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-06-19 07:01:01.46 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2006-06-19 07:01:01.57 server SQL Server configured for thread mode
processing.
2006-06-19 07:01:01.60 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2006-06-19 07:01:02.08 server Attempting to initialize Distributed
Transaction Coordinator.
2006-06-19 07:01:05.10 spid3 Starting up database 'master'.
2006-06-19 07:01:05.24 spid3 0 transactions rolled back in database
'master' (1).
2006-06-19 07:01:05.24 spid3 Recovery is checkpointing database 'master'
(1)
2006-06-19 07:01:05.36 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-06-19 07:01:05.36 spid5 Starting up database 'model'.
2006-06-19 07:01:05.38 spid3 Server name is 'SECDB'.
2006-06-19 07:01:05.40 spid8 Starting up database 'msdb'.
2006-06-19 07:01:05.40 spid9 Starting up database 'pubs'.
2006-06-19 07:01:05.40 spid10 Starting up database 'Northwind'.
2006-06-19 07:01:05.40 spid11 Starting up database 'SSW'.
2006-06-19 07:01:05.60 server SQL server listening on www.xxx.yyy.zzz:
1433.
2006-06-19 07:01:05.60 server SQL server listening on 127.0.0.1: 1433.
2006-06-19 07:01:05.61 spid5 Clearing tempdb database.
2006-06-19 07:01:05.85 spid8 134 transactions rolled forward in database
'msdb' (4).
2006-06-19 07:01:05.91 spid8 0 transactions rolled back in database
'msdb' (4).
2006-06-19 07:01:05.93 spid8 Recovery is checkpointing database 'msdb' (4)
2006-06-19 07:01:06.27 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-06-19 07:01:06.27 server SQL Server is ready for client connections
2006-06-19 07:01:07.19 spid5 Starting up database 'tempdb'.
2006-06-19 07:01:08.35 spid11 314 transactions rolled forward in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 0 transactions rolled back in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 Recovery is checkpointing database 'SSW' (7)
2006-06-19 07:01:09.44 spid53 Using 'odsole70.dll' version '2000.80.2039'
to execute extended stored procedure 'sp_OACreate'.
"SQLPoet" wrote:
> What does the sql errorlog say?
>
> Martin Paterson wrote:
> > I looked at KB822360 and it appears to be for active directory issues. The
> > SQL server that is having this problem does not sit on a domain. thanks in
> > advance for your assistance.
> >
> > "CLM" wrote:
> >
> > > This probably does not apply, but we had a similar problem and it had to do
> > > with the following article:
> > > KB article 822360
> > > MS had us put in a couple of hot fixes and it seems to have taken care of
> > > the problem.
> > >
> > > "Martin Paterson" wrote:
> > >
> > > > I have a couple of sites that are running MS SQL 2000 Service pack 4 that are
> > > > stopping (apperantly randomly) and restarting itself. This is causing great
> > > > havoc on some of my applications that are attached to this database. The
> > > > server is dedicated for this purpose only and is hosting only on database.
> > > > reviewing the error logs have not resulted in any explanation as to why SQL
> > > > is dying. Google & MS knowledgebase has also resulted in no
> > > > explanation/solution. Any assistance would be greatly appreciated.
>|||Martin Paterson wrote:
> there are no errors that I can see...but here is an example of what is
> displayed:
> 2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
> Corporation.
That's the current log that was generated when SQL restarted. What does
the archived error log contain? Last 15-20 lines should be sufficient.|||I have looked through all the error logs (errorlogs.1 -> .6) and they are all
the same. The only thing is that the modified date and time are the same as
the eventlog time stating that MSSQLSERVER has died and that it has done this
xx number of times before. I have yet been able to determine what is causing
it. No error messages in the errorlog or eventlog. I have looked to see if
there is additional parameters that need to be set to show more in the
errorlog on failure but I have not been able to find anything
"Tracy McKibben" wrote:
> Martin Paterson wrote:
> > there are no errors that I can see...but here is an example of what is
> > displayed:
> > 2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
> > (Intel X86)
> > May 3 2005 23:18:38
> > Copyright (c) 1988-2003 Microsoft Corporation
> > Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> >
> > 2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
> > Corporation.
> That's the current log that was generated when SQL restarted. What does
> the archived error log contain? Last 15-20 lines should be sufficient.
>|||For the person that first posted their original problem in this threa
regarding ODSOLE70.dll 2000.80.2039 , did you ever come up with
solution? We are experiencing the exact same dynamic link librar
showing up in our logs when our error occurs. I am having little luc
finding any other solutions fto get around it. I wondered if perhap
you might be using the same software? or would like to confirm that yo
aren't so I can rule that as the problem. Please advise?
Our problem occurs the minute we try to generate a schedule usin
software called Schedulesoft and then starts the generation and neve
ends (hangs) requiring us to cancel it. Then in the log I find the sam
reference to ODSOLE70.dll 2000.80 2039 Does anyone have any ideas o
where I might look. We are also on fix pack 4 using SQL Server 200
--
shanleatherma
----
shanleatherman's Profile: http://unixadmintalk.com/59
View this thread: http://unixadmintalk.com/showthread.php?t=18590