Prev: xp_sendmail is hanging(SQL Server 2000/sp4)
Next: Missing SQL 2000 PCSOE registry values
From: John Bell on 20 May 2008 14:47

"samk17" <u43718(a)uwe> wrote in message news:84721a72f55b8(a)uwe...
> 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.
>

That seems pretty much the same as the SQL log, was there anything in
between? What about the security log?

Have you tried the minimum configuration startup as this eliminates startup
procedures.

John

From: John Bell on 20 May 2008 15:44

"samk17" <u43718(a)uwe> wrote in message news:84723b2f20892(a)uwe...
>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.
>

This implies that it not only at startup?

You may want to run profiler or a trace to see if you can trap what is
causing this.

Are there any other instances on this server? If so do they have the same
issue.

John

From: Uri Dimant on 21 May 2008 03:03
Hi
Enable blackbox trace on the server and the examine what happend just before
shut dowing






"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?
>


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