Prev: xp_sendmail is hanging(SQL Server 2000/sp4)
Next: Missing SQL 2000 PCSOE registry values
From: samk17 on 20 May 2008 13:49
For the past couple of weeks now, my sql server agent shuts down on its own
without leaving any error messages. Nothing really occurs prior to the shut
down.

2008-05-19 13:57:28.84 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2008-05-19 13:57:28.84 server SQL Server is ready for client connections
2008-05-19 13:57:30.01 spid3 Recovery complete.
2008-05-19 13:57:30.01 spid3 SQL global counter collection task is
created.
2008-05-19 13:57:32.56 spid52 Using 'xpsqlbot.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_qv'.
2008-05-19 14:02:35.23 spid59 Using 'xpstar.dll' version '2000.80.2039' to
execute extended stored procedure 'sp_MSgetversion'.
2008-05-19 14:04:43.14 spid59 Process ID 52 killed by hostname DB1, host
process ID 1864.
2008-05-19 14:04:43.18 spid59 Process ID 63 killed by hostname DB1, host
process ID 1864.
2008-05-19 14:04:53.31 spid59 Process ID 51 killed by hostname DB1, host
process ID 1864.
2008-05-19 14:06:15.76 spid51 Using 'xplog70.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_msver'.
2008-05-19 14:08:46.45 spid51 Starting up database '*****'.
2008-05-19 21:28:26.46 spid58 Server shut down by request.

Has anyone experienced similar issures?

From: Ekrem Önsoy on 20 May 2008 14:06
Hello samk17,

It may be because of expiration of an Evaluation Edition instance of SQL
Server. To better understand the reason, you should check out Windows Event
Logs. Probably there you'll find the reason of this shut down.

--
Ekrem Önsoy



"samk17" <u43718(a)uwe> wrote in message news:8471c1045eaca(a)uwe...
> For the past couple of weeks now, my sql server agent shuts down on its
> own
> without leaving any error messages. Nothing really occurs prior to the
> shut
> down.
>
> 2008-05-19 13:57:28.84 server SQL server listening on TCP, Shared
> Memory,
> Named Pipes.
> 2008-05-19 13:57:28.84 server SQL Server is ready for client
> connections
> 2008-05-19 13:57:30.01 spid3 Recovery complete.
> 2008-05-19 13:57:30.01 spid3 SQL global counter collection task is
> created.
> 2008-05-19 13:57:32.56 spid52 Using 'xpsqlbot.dll' version
> '2000.80.2039'
> to execute extended stored procedure 'xp_qv'.
> 2008-05-19 14:02:35.23 spid59 Using 'xpstar.dll' version '2000.80.2039'
> to
> execute extended stored procedure 'sp_MSgetversion'.
> 2008-05-19 14:04:43.14 spid59 Process ID 52 killed by hostname DB1,
> host
> process ID 1864.
> 2008-05-19 14:04:43.18 spid59 Process ID 63 killed by hostname DB1,
> host
> process ID 1864.
> 2008-05-19 14:04:53.31 spid59 Process ID 51 killed by hostname DB1,
> host
> process ID 1864.
> 2008-05-19 14:06:15.76 spid51 Using 'xplog70.dll' version
> '2000.80.2039'
> to execute extended stored procedure 'xp_msver'.
> 2008-05-19 14:08:46.45 spid51 Starting up database '*****'.
> 2008-05-19 21:28:26.46 spid58 Server shut down by request.
>
> Has anyone experienced similar issures?
>

From: samk17 on 20 May 2008 14:29
If my memory is correct, this server doesnt run on an evaluation copy of
MSSQL.

Here are some entries from the Event Viewer application log:


6006 :
Server shut down by request.

SQLServerAgent service successfully stopped.

8128 :
Using 'xplog70.dll' version '2000.80.2039' to execute extended stored
procedure 'xp_msver'.

18100 :
Process ID 51 killed by hostname DB1, host process ID 1864.

18100 :
Process ID 63 killed by hostname DB1, host process ID 1864.

18100 :
Process ID 52 killed by hostname DB1, host process ID 1864.

From: John Bell on 20 May 2008 14:29

"samk17" <u43718(a)uwe> wrote in message news:8471c1045eaca(a)uwe...
> For the past couple of weeks now, my sql server agent shuts down on its
> own
> without leaving any error messages. Nothing really occurs prior to the
> shut
> down.
>
> 2008-05-19 13:57:28.84 server SQL server listening on TCP, Shared
> Memory,
> Named Pipes.
> 2008-05-19 13:57:28.84 server SQL Server is ready for client
> connections
> 2008-05-19 13:57:30.01 spid3 Recovery complete.
> 2008-05-19 13:57:30.01 spid3 SQL global counter collection task is
> created.
> 2008-05-19 13:57:32.56 spid52 Using 'xpsqlbot.dll' version
> '2000.80.2039'
> to execute extended stored procedure 'xp_qv'.
> 2008-05-19 14:02:35.23 spid59 Using 'xpstar.dll' version '2000.80.2039'
> to
> execute extended stored procedure 'sp_MSgetversion'.
> 2008-05-19 14:04:43.14 spid59 Process ID 52 killed by hostname DB1,
> host
> process ID 1864.
> 2008-05-19 14:04:43.18 spid59 Process ID 63 killed by hostname DB1,
> host
> process ID 1864.
> 2008-05-19 14:04:53.31 spid59 Process ID 51 killed by hostname DB1,
> host
> process ID 1864.
> 2008-05-19 14:06:15.76 spid51 Using 'xplog70.dll' version
> '2000.80.2039'
> to execute extended stored procedure 'xp_msver'.
> 2008-05-19 14:08:46.45 spid51 Starting up database '*****'.
> 2008-05-19 21:28:26.46 spid58 Server shut down by request.
>
> Has anyone experienced similar issures?
>

Hi

Do you know what is process 1864? Is there anything in the windows event
log? Have you tried starting SQLServer from a command prompt with minimum
configuration (sqlservr.exe -f)?

John

From: samk17 on 20 May 2008 14:44
I can't anything that traces to 1864. I will try starting the server that
way, however, there's no real way for me to test it except to wait. The
server seems to shut down randomly.

 |  Next  |  Last
Pages: 1 2
Prev: xp_sendmail is hanging(SQL Server 2000/sp4)
Next: Missing SQL 2000 PCSOE registry values