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.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment