MSSQLSvc

Hi,
I have recently been getting the following error on a
regular basis:
Event Type: Error
Event Source: KDC
Event Category: None
Event ID: 11
Date: 23/01/2004
Time: 2:08:27:AM
User: N/A
Computer: Server
Description:
There are multiple accounts with name
MSSQLSvc/Server.Domain.com:1433 of type 10.
does anybody have any ideas how to resolve this or what is
causing this to occur.
Regards
AdamMultiply Accounts with the Domain have been configured as a SQL Service account for
the Servername server. This causes both service accounts to have the same SPN
registered.
If the accounts are known then use ADSI edit and remove then SPN on the account
that is no longer used to start the service on servername
This posting is provided "AS IS" with no warranties, and
confers no rights.
http://www.microsoft.com/info/cpyright.ht
-- Adam wrote: --
Hi,
I have recently been getting the following error on a
regular basis
Event Type: Erro
Event Source: KD
Event Category: Non
Event ID: 1
Date: 23/01/200
Time: 2:08:27:A
User: N/
Computer: Serve
Description
There are multiple accounts with name
MSSQLSvc/Server.Domain.com:1433 of type 10.
does anybody have any ideas how to resolve this or what is
causing this to occur.
Regard
Ada

MSSQLServerOLAPService Stops

MSSQLServerOLAPService Service seems to crash rather sporadically during our nightly ETL with the error of:

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Internal error: An unexpected exception occured. Internal error: An unexpected exception occured..

The time of the error in the event viewer seems to correspond with the step in the ETL that processes our AS 2005 database (Analysis Services Command Task). The job step reports success, and the data is refreshed so I don't understand why it is reporting an error in Event Viewer.

The server is x86 with SQL 2005 sp2 installed.

Has anyone else run across this?

I'm getting the same issue when I run a particular MDX query. I'm also on x86 with SQL 2005 sp2 installed. Please post if you find anything out.

Thanks,

Craig

MSSQLServerOLAPServi - Server - 129

I have got SQL Server 2000 and 7.0 on a one computer with Windows NT Server. In the Event Log I received next message:
Source: MSSQLServerOLAPServi
Category: Server
ID: 129
There was an error during loading dimension Promotions in database FoodMart. Dimension file(s) may be corrupted or missing.
But the FoodMart database is sample database and we are't use this database.
Must I anything doing?
Michael S. Androsov
EXPOCENTR> I have got SQL Server 2000 and 7.0 on a one computer with Windows NT
Server.
> In the Event Log I received next message:
> Source: MSSQLServerOLAPServi
> Category: Server
> ID: 129
> There was an error during loading dimension Promotions in database
FoodMart.
> Dimension file(s) may be corrupted or missing.
> But the FoodMart database is sample database and we are't use this
database.
> Must I anything doing?
> Michael S. Androsov
> EXPOCENTR
--
Are you using Analysis Services 2000 at all? If so, you can simply
uninstall it.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

MSSQLServerOLAPServi - Server - 129

I have got SQL Server 2000 and 7.0 on a one computer with Windows NT Server. In the Event Log I received next message:
Source: MSSQLServerOLAPServi
Category: Server
ID: 129
There was an error during loading dimension Promotions in database FoodMart. Dimension file(s) may be corrupted or missing.
But the FoodMart database is sample database and we are't use this database.
Must I anything doing?
Michael S. Androsov
EXPOCENTR

> I have got SQL Server 2000 and 7.0 on a one computer with Windows NT
Server.
> In the Event Log I received next message:
> Source: MSSQLServerOLAPServi
> Category: Server
> ID: 129
> There was an error during loading dimension Promotions in database
FoodMart.
> Dimension file(s) may be corrupted or missing.
> But the FoodMart database is sample database and we are't use this
database.
> Must I anything doing?
> Michael S. Androsov
> EXPOCENTR
Are you using Analysis Services 2000 at all? If so, you can simply
uninstall it.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

MSSQLServerOLAPServi - Server - 129

I have got SQL Server 2000 and 7.0 on a one computer with Windows NT Server.
In the Event Log I received next message:
Source: MSSQLServerOLAPServi
Category: Server
ID: 129
There was an error during loading dimension Promotions in database FoodMart.
Dimension file(s) may be corrupted or missing.
But the FoodMart database is sample database and we are't use this database.
Must I anything doing?
Michael S. Androsov
EXPOCENTR
> I have got SQL Server 2000 and 7.0 on a one computer with Windows NT
Server.
> In the Event Log I received next message:
> Source: MSSQLServerOLAPServi
> Category: Server
> ID: 129
> There was an error during loading dimension Promotions in database
FoodMart.
> Dimension file(s) may be corrupted or missing.
> But the FoodMart database is sample database and we are't use this
database.
> Must I anything doing?
> Michael S. Androsov
> EXPOCENTR
--
Are you using Analysis Services 2000 at all? If so, you can simply
uninstall it.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

MSSQLServerADHelper is problem?

MSSQLServerADHelper isn't running and we can't get it to
start. System Event Log says "The MSSQLServerADHelper
service terminated with service-specific error 3221225572."
Any clues at all how to fix?

>--Original Message--
>That's SQL Server 2000 (sorry!) and Windows (Server)
>2000... it's almost like SQL isn't reading from or
>synchronizing with Active Directory properly, but we can
>find no other indicator that there is a problem.
>Again, any help is greatly appreciated!
>
>login
I
>a
the
>.
>That's normal behavior. You can't start the service
manually. It runs when requested to by SQL Server service or
Analysis Server service and then stops running when it's
completed it's work.
-Sue
On Thu, 25 Mar 2004 12:27:49 -0800, "Sandy Mach"
<anonymous@.discussions.microsoft.com> wrote:
>MSSQLServerADHelper isn't running and we can't get it to
>start. System Event Log says "The MSSQLServerADHelper
>service terminated with service-specific error 3221225572."
>Any clues at all how to fix?
>
>I
>the|||Well I was just trying to find something... is there any
way to see if it's working properly when it's supposed to
be working? My gut tells me this problem has to do with
AD somehow...
Can you think of any other options or ways to fix?

>--Original Message--
>That's normal behavior. You can't start the service
>manually. It runs when requested to by SQL Server service
or
>Analysis Server service and then stops running when it's
>completed it's work.
>-Sue
>On Thu, 25 Mar 2004 12:27:49 -0800, "Sandy Mach"
><anonymous@.discussions.microsoft.com> wrote:
>
3221225572."
can
if
in
adding
and
won't
then
>.
>|||Try revoking the login and then re-add it and see if you can
add the login as a database user.
Is the a problem for all logins or just one or a few? Is it
a problem with trying to add them to any database or just
one specific database?
-Sue
On Thu, 25 Mar 2004 13:31:55 -0800, "Sandy Mach"
<anonymous@.discussions.microsoft.com> wrote:
>Well I was just trying to find something... is there any
>way to see if it's working properly when it's supposed to
>be working? My gut tells me this problem has to do with
>AD somehow...
>Can you think of any other options or ways to fix?
>
>or
>3221225572."
>can
>if
>in
>adding
>and
>won't
>then|||Well, that did the job, but now I have to re-set the
group's permissions on each db, some of which contain over
200 tables... yikes. I guess I could look at the bright
side--I should only have to do this once!
Thanks for your help Sue.
Sandy

>--Original Message--
>Try revoking the login and then re-add it and see if you
can
>add the login as a database user.
>Is the a problem for all logins or just one or a few? Is
it
>a problem with trying to add them to any database or just
>one specific database?
>-Sue
>On Thu, 25 Mar 2004 13:31:55 -0800, "Sandy Mach"
><anonymous@.discussions.microsoft.com> wrote:
>
to
service
to
but
error
looked
use|||Your welcome...glad it's working now and thanks for posting
back.
-Sue
On Thu, 25 Mar 2004 14:22:19 -0800, "Sandy Mach"
<anonymous@.discussions.microsoft.com> wrote:
>Well, that did the job, but now I have to re-set the
>group's permissions on each db, some of which contain over
>200 tables... yikes. I guess I could look at the bright
>side--I should only have to do this once!
>Thanks for your help Sue.
>Sandy
>
>can
>it
>to
>service
>to
>but
>error
>looked
>use

MSSQLServerADHelper

Hi
I am getting the following error (given at the end) in the event log and the
MSSQLServerADHelper service does not start. What can I do?
Thanks
Regards
Event Type: Error
Event Source: MSSQLServerADHelper
Event Category: None
Event ID: 100
Date: 09/07/2004
Time: 18:41:36
User: N/A
Computer: MYSERVER
Description:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.This also comes up.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 09/07/2004
Time: 19:15:36
User: N/A
Computer: MYSERVER
Description:
The MSSQLServerADHelper service terminated with service-specific error
3221225572 (0xC0000064).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"John" <john@.nospam.infovis.co.uk> wrote in message
news:ei8G85dZEHA.3092@.tk2msftngp13.phx.gbl...
> Hi
> I am getting the following error (given at the end) in the event log and
the
> MSSQLServerADHelper service does not start. What can I do?
> Thanks
> Regards
>
> Event Type: Error
> Event Source: MSSQLServerADHelper
> Event Category: None
> Event ID: 100
> Date: 09/07/2004
> Time: 18:41:36
> User: N/A
> Computer: MYSERVER
> Description:
> '0' is an invalid number of start up parameters. This service takes two
> start up parameters.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>

MSSQLServerADHelper

MSSQLServerADHelper failed to start with error code
1073741724 on the initial error message box. When going
into event viewer the error code for the failed service
is 3221225572.
I have tried restarting the service and restarting the
server but it still fails, I have also tried starting the
service with the Admin account.
Any advice would be much appreciated.
ThanksHello,
Theres something it doesn't like about the account. See
http://support.microsoft.com/default.aspx?scid=kb;en-
us;273499.
Try deleing then recreating it.
>--Original Message--
>MSSQLServerADHelper failed to start with error code
>1073741724 on the initial error message box. When going
>into event viewer the error code for the failed service
>is 3221225572.
>I have tried restarting the service and restarting the
>server but it still fails, I have also tried starting the
>service with the Admin account.
>Any advice would be much appreciated.
>Thanks
>.
>

MSSQLServerADHelper

Hi
I am getting the following error (given at the end) in the event log and the
MSSQLServerADHelper service does not start. What can I do?
Thanks
Regards
Event Type: Error
Event Source: MSSQLServerADHelper
Event Category: None
Event ID: 100
Date: 09/07/2004
Time: 18:41:36
User: N/A
Computer: MYSERVER
Description:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
This also comes up.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 09/07/2004
Time: 19:15:36
User: N/A
Computer: MYSERVER
Description:
The MSSQLServerADHelper service terminated with service-specific error
3221225572 (0xC0000064).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"John" <john@.nospam.infovis.co.uk> wrote in message
news:ei8G85dZEHA.3092@.tk2msftngp13.phx.gbl...
> Hi
> I am getting the following error (given at the end) in the event log and
the
> MSSQLServerADHelper service does not start. What can I do?
> Thanks
> Regards
>
> Event Type: Error
> Event Source: MSSQLServerADHelper
> Event Category: None
> Event ID: 100
> Date: 09/07/2004
> Time: 18:41:36
> User: N/A
> Computer: MYSERVER
> Description:
> '0' is an invalid number of start up parameters. This service takes two
> start up parameters.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>

MSSQLServerADHelper

Hi
I am getting the following error (given at the end) in the event log and the
MSSQLServerADHelper service does not start. What can I do?
Thanks
Regards
Event Type: Error
Event Source: MSSQLServerADHelper
Event Category: None
Event ID: 100
Date: 09/07/2004
Time: 18:41:36
User: N/A
Computer: MYSERVER
Description:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.This also comes up.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 09/07/2004
Time: 19:15:36
User: N/A
Computer: MYSERVER
Description:
The MSSQLServerADHelper service terminated with service-specific error
3221225572 (0xC0000064).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"John" <john@.nospam.infovis.co.uk> wrote in message
news:ei8G85dZEHA.3092@.tk2msftngp13.phx.gbl...
> Hi
> I am getting the following error (given at the end) in the event log and
the
> MSSQLServerADHelper service does not start. What can I do?
> Thanks
> Regards
>
> Event Type: Error
> Event Source: MSSQLServerADHelper
> Event Category: None
> Event ID: 100
> Date: 09/07/2004
> Time: 18:41:36
> User: N/A
> Computer: MYSERVER
> Description:
> '0' is an invalid number of start up parameters. This service takes two
> start up parameters.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>

MSSQLSERVER errors on PC running MSDE

I have a retail account with 2 PC's running the latest version of
Microsofts RMS. One of the PC's
acts as the server using MSDE. In the event viewer for this PC there are
hundreds of
errors that show this:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 11/25/2004
Time: 2:55:04 AM
User: N/A
Computer: W_CM1
Description:
Error: 644, Severity: 21, State: 3
Could not find the index entry for RID '160000019f9af100' in index page
(1:28465), index ID 0, database 'conrevhb2'.
Data:
0000: 84 02 00 00 15 00 00 00 ?......
0008: 06 00 00 00 57 00 5f 00 ...W._.
0010: 43 00 4d 00 31 00 00 00 C.M.1...
0018: 0a 00 00 00 63 00 6f 00 ...c.o.
0020: 6e 00 72 00 65 00 76 00 n.r.e.v.
0028: 68 00 62 00 32 00 00 00 h.b.2...
Can someone help me out?
Thanks
John
"John" <jk@.rt.com> wrote in message
news:%23EknDWi1EHA.304@.TK2MSFTNGP11.phx.gbl...
>I have a retail account with 2 PC's running the latest version of
>Microsofts RMS. One of the PC's
> acts as the server using MSDE. In the event viewer for this PC there are
> hundreds of
> errors that show this:
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 11/25/2004
> Time: 2:55:04 AM
> User: N/A
> Computer: W_CM1
> Description:
> Error: 644, Severity: 21, State: 3
> Could not find the index entry for RID '160000019f9af100' in index page
> (1:28465), index ID 0, database 'conrevhb2'.
> Data:
> 0000: 84 02 00 00 15 00 00 00 ?......
> 0008: 06 00 00 00 57 00 5f 00 ...W._.
> 0010: 43 00 4d 00 31 00 00 00 C.M.1...
> 0018: 0a 00 00 00 63 00 6f 00 ...c.o.
> 0020: 6e 00 72 00 65 00 76 00 n.r.e.v.
> 0028: 68 00 62 00 32 00 00 00 h.b.2...
> Can someone help me out?
> Thanks
> John
>
>
Your clustered index on database conrevhb2 has problems with it. Take a
look at the BOL for DBCC CHECKDB command. There are some repair options.
If that doesn't work, you may need to drop and recreate your clustered
index. (Keep in mind that it may be your Primary key constraint as well, as
this automatically creates a clustered index by default.).
HTH
Rick Sawtell
MCT, MCSD, MCDBA
|||Rick,
Thanks for the reply but, I am not a database admin so I know I can do a
google search and see what you are suggesting but is this correct for a
database using the MSDE engineon a Win2K Pro machine?
TIA
John
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:uLLOjpi1EHA.1264@.TK2MSFTNGP12.phx.gbl...
> "John" <jk@.rt.com> wrote in message
> news:%23EknDWi1EHA.304@.TK2MSFTNGP11.phx.gbl...
> Your clustered index on database conrevhb2 has problems with it. Take a
> look at the BOL for DBCC CHECKDB command. There are some repair options.
> If that doesn't work, you may need to drop and recreate your clustered
> index. (Keep in mind that it may be your Primary key constraint as well,
> as this automatically creates a clustered index by default.).
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
|||MSDE uses the same DLLs that SQL Server uses. It has certain built-in
limitations on how it operates, but this is essentially what needs to be
fixed.
If you don't have Query Analzer, you may try to use osql and do this work
from the command line.
Rick
"John" <jk@.rt.com> wrote in message
news:ec$IJyi1EHA.3596@.TK2MSFTNGP12.phx.gbl...
> Rick,
> Thanks for the reply but, I am not a database admin so I know I can do a
> google search and see what you are suggesting but is this correct for a
> database using the MSDE engineon a Win2K Pro machine?
> TIA
>
> John
>
> "Rick Sawtell" <quickening@.msn.com> wrote in message
> news:uLLOjpi1EHA.1264@.TK2MSFTNGP12.phx.gbl...
>
|||Thanks Rick!!
John
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:%23xY1J%23i1EHA.2540@.TK2MSFTNGP09.phx.gbl...
> MSDE uses the same DLLs that SQL Server uses. It has certain built-in
> limitations on how it operates, but this is essentially what needs to be
> fixed.
> If you don't have Query Analzer, you may try to use osql and do this work
> from the command line.
> Rick
>
> "John" <jk@.rt.com> wrote in message
> news:ec$IJyi1EHA.3596@.TK2MSFTNGP12.phx.gbl...
>

MSSQLSERVER errors on PC running MSDE

I have a retail account with 2 PC's running the latest version of
Microsofts RMS. One of the PC's
acts as the server using MSDE. In the event viewer for this PC there are
hundreds of
errors that show this:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 11/25/2004
Time: 2:55:04 AM
User: N/A
Computer: W_CM1
Description:
Error: 644, Severity: 21, State: 3
Could not find the index entry for RID '160000019f9af100' in index page
(1:28465), index ID 0, database 'conrevhb2'.
Data:
0000: 84 02 00 00 15 00 00 00 ?......
0008: 06 00 00 00 57 00 5f 00 ...W._.
0010: 43 00 4d 00 31 00 00 00 C.M.1...
0018: 0a 00 00 00 63 00 6f 00 ...c.o.
0020: 6e 00 72 00 65 00 76 00 n.r.e.v.
0028: 68 00 62 00 32 00 00 00 h.b.2...
Can someone help me out?
Thanks
John"John" <jk@.rt.com> wrote in message
news:%23EknDWi1EHA.304@.TK2MSFTNGP11.phx.gbl...
>I have a retail account with 2 PC's running the latest version of
>Microsofts RMS. One of the PC's
> acts as the server using MSDE. In the event viewer for this PC there are
> hundreds of
> errors that show this:
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 11/25/2004
> Time: 2:55:04 AM
> User: N/A
> Computer: W_CM1
> Description:
> Error: 644, Severity: 21, State: 3
> Could not find the index entry for RID '160000019f9af100' in index page
> (1:28465), index ID 0, database 'conrevhb2'.
> Data:
> 0000: 84 02 00 00 15 00 00 00 ?......
> 0008: 06 00 00 00 57 00 5f 00 ...W._.
> 0010: 43 00 4d 00 31 00 00 00 C.M.1...
> 0018: 0a 00 00 00 63 00 6f 00 ...c.o.
> 0020: 6e 00 72 00 65 00 76 00 n.r.e.v.
> 0028: 68 00 62 00 32 00 00 00 h.b.2...
> Can someone help me out?
> Thanks
> John
>
>
Your clustered index on database conrevhb2 has problems with it. Take a
look at the BOL for DBCC CHECKDB command. There are some repair options.
If that doesn't work, you may need to drop and recreate your clustered
index. (Keep in mind that it may be your Primary key constraint as well, as
this automatically creates a clustered index by default.).
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||Rick,
Thanks for the reply but, I am not a database admin so I know I can do a
google search and see what you are suggesting but is this correct for a
database using the MSDE engineon a Win2K Pro machine?
TIA
John
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:uLLOjpi1EHA.1264@.TK2MSFTNGP12.phx.gbl...
> "John" <jk@.rt.com> wrote in message
> news:%23EknDWi1EHA.304@.TK2MSFTNGP11.phx.gbl...
> Your clustered index on database conrevhb2 has problems with it. Take a
> look at the BOL for DBCC CHECKDB command. There are some repair options.
> If that doesn't work, you may need to drop and recreate your clustered
> index. (Keep in mind that it may be your Primary key constraint as well,
> as this automatically creates a clustered index by default.).
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>|||MSDE uses the same DLLs that SQL Server uses. It has certain built-in
limitations on how it operates, but this is essentially what needs to be
fixed.
If you don't have Query Analzer, you may try to use osql and do this work
from the command line.
Rick
"John" <jk@.rt.com> wrote in message
news:ec$IJyi1EHA.3596@.TK2MSFTNGP12.phx.gbl...
> Rick,
> Thanks for the reply but, I am not a database admin so I know I can do a
> google search and see what you are suggesting but is this correct for a
> database using the MSDE engineon a Win2K Pro machine?
> TIA
>
> John
>
> "Rick Sawtell" <quickening@.msn.com> wrote in message
> news:uLLOjpi1EHA.1264@.TK2MSFTNGP12.phx.gbl...
>|||Thanks Rick!!
John
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:%23xY1J%23i1EHA.2540@.TK2MSFTNGP09.phx.gbl...
> MSDE uses the same DLLs that SQL Server uses. It has certain built-in
> limitations on how it operates, but this is essentially what needs to be
> fixed.
> If you don't have Query Analzer, you may try to use osql and do this work
> from the command line.
> Rick
>
> "John" <jk@.rt.com> wrote in message
> news:ec$IJyi1EHA.3596@.TK2MSFTNGP12.phx.gbl...
>

MSSQLSERVER Error 17052

Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17052
Date:2/20/2007
Time:4:38:39 AM
User:N/A
Computer:LEESQL
Description:
SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: a8 01 00 00 0a 00 00 00 ¨......
0008: 0e 00 00 00 4c 00 45 00 ...L.E.
0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
0018: 00 00 0e 00 00 00 6d 00 .....m.
0020: 61 00 73 00 74 00 65 00 a.s.t.e.
0028: 72 00 00 00 r...
Everytime I try to run a job in sql server agent it shuts down the agent.
None of the files in the log directory have any details about the shutdown.
This is driving me nuts. I have checked and rechecked permissions and even
created a new login for the sql server and the agent to use. Still the same
thing. Since I am getting no error logs I am totally lost as to where to look
for information. I am also not finding anything about this when I google for
it. Any help anyone could give would be appreciated.
Mark A. Lutz (aka Eggbert)
Hi
Can open the SQL Server errorlog file in notepad to see if you have
additional information?
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 2/20/2007
> Time: 4:38:39 AM
> User: N/A
> Computer: LEESQL
> Description:
> SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: a8 01 00 00 0a 00 00 00 ......
> 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
> 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
> 0018: 00 00 0e 00 00 00 6d 00 .....m.
> 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
> 0028: 72 00 00 00 r...
> Everytime I try to run a job in sql server agent it shuts down the agent.
> None of the files in the log directory have any details about the
> shutdown.
> This is driving me nuts. I have checked and rechecked permissions and even
> created a new login for the sql server and the agent to use. Still the
> same
> thing. Since I am getting no error logs I am totally lost as to where to
> look
> for information. I am also not finding anything about this when I google
> for
> it. Any help anyone could give would be appreciated.
> --
> Mark A. Lutz (aka Eggbert)
|||As I mentioned I had done that and not found anything informative but I will
paste them here:
____________
SQLAGENT.OUT
2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
(x86 unicode retail build) : Process ID
2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
(x86 unicode retail build) : Process ID 396
2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
connection limit)
2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version 3.86.1830
2007-02-20 04:38:39 - ? [103] NetLib being used by driver is DBMSSHRN.DLL;
Local host server is
2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM detected
2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running Windows NT
5.2 (3790) Service Pack 1
2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows NT
service control
2007-02-20 04:38:39 - + [260] Unable to start mail session (reason: No mail
profile defined)
2007-02-20 04:38:39 - + [396] An idle CPU condition has not been defined -
OnIdle job schedules will have no effect
____________
SQLAGENT.1
2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-02-20 04:36:59.00 server All rights reserved.
2007-02-20 04:36:59.00 server Server Process ID is 1184.
2007-02-20 04:36:59.00 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-02-20 04:36:59.00 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2007-02-20 04:36:59.09 server SQL Server configured for thread mode
processing.
2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2007-02-20 04:36:59.10 server Attempting to initialize Distributed
Transaction Coordinator.
2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2007-02-20 04:37:00.51 server SQL Server is ready for client connections
2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
2007-02-20 04:37:55.15 spid2 Recovery complete.
2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
created.
2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_qv'.
2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_sqlagent_monitor'.
____________
ERRORLOG
2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-02-20 04:36:59.00 server All rights reserved.
2007-02-20 04:36:59.00 server Server Process ID is 1184.
2007-02-20 04:36:59.00 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-02-20 04:36:59.00 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2007-02-20 04:36:59.09 server SQL Server configured for thread mode
processing.
2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2007-02-20 04:36:59.10 server Attempting to initialize Distributed
Transaction Coordinator.
2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2007-02-20 04:37:00.51 server SQL Server is ready for client connections
2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
2007-02-20 04:37:55.15 spid2 Recovery complete.
2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
created.
2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_qv'.
2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_sqlagent_monitor'.
Mark A. Lutz (aka Eggbert)
"Uri Dimant" wrote:

> Hi
> Can open the SQL Server errorlog file in notepad to see if you have
> additional information?
>
>
> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
>
>
|||Hi
1) Is it SQL Server 7.0/2000/2005?
2) Is it clustered?
http://www.tutorials-ne.com/clustering/Cannot-create-14238/
3) Have you tried to set LocalSystem account to the service?
4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...[vbcol=seagreen]
> As I mentioned I had done that and not found anything informative but I
> will
> paste them here:
>
> ____________
> SQLAGENT.OUT
> 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
> (x86 unicode retail build) : Process ID
> 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
> (x86 unicode retail build) : Process ID 396
> 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
> connection limit)
> 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version 3.86.1830
> 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is DBMSSHRN.DLL;
> Local host server is
> 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM detected
> 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running Windows NT
> 5.2 (3790) Service Pack 1
> 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows NT
> service control
> 2007-02-20 04:38:39 - + [260] Unable to start mail session (reason: No
> mail
> profile defined)
> 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been defined -
> OnIdle job schedules will have no effect
> ____________
> SQLAGENT.1
> 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2007-02-20 04:36:59.00 server All rights reserved.
> 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2007-02-20 04:36:59.00 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> processing.
> 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> Lock
> Blocks, [5000] Lock Owner Blocks.
> 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
> 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> Memory,
> Named Pipes.
> 2007-02-20 04:37:00.51 server SQL Server is ready for client
> connections
> 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> 2007-02-20 04:37:55.15 spid2 Recovery complete.
> 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> created.
> 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> '2000.80.2039'
> to execute extended stored procedure 'xp_qv'.
> 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_sqlagent_monitor'.
> ____________
> ERRORLOG
> 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2007-02-20 04:36:59.00 server All rights reserved.
> 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2007-02-20 04:36:59.00 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> processing.
> 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> Lock
> Blocks, [5000] Lock Owner Blocks.
> 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
> 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> Memory,
> Named Pipes.
> 2007-02-20 04:37:00.51 server SQL Server is ready for client
> connections
> 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> 2007-02-20 04:37:55.15 spid2 Recovery complete.
> 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> created.
> 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> '2000.80.2039'
> to execute extended stored procedure 'xp_qv'.
> 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_sqlagent_monitor'.
> --
> Mark A. Lutz (aka Eggbert)
>
> "Uri Dimant" wrote:
|||1.
Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2.
No it is not clustered.
3.
Yes I have tried to run both the SQL Server and Agent under the local system
account
4.
I have checked all logs and nothing is recorded when Agent goes down with
the exception of what I have already stated.
Mark A. Lutz (aka Eggbert)
"Uri Dimant" wrote:

> Hi
> 1) Is it SQL Server 7.0/2000/2005?
> 2) Is it clustered?
> http://www.tutorials-ne.com/clustering/Cannot-create-14238/
> 3) Have you tried to set LocalSystem account to the service?
> 4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
>
>
|||Check your system and see if you have MS07-009 applied (KB 927779). This is
a windows update security patch released ths month.
Is your system in a resource domain that is called by users in another
domain?
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:B96458B0-B21A-4017-A509-3F9FEF7372D3@.microsoft.com...[vbcol=seagreen]
> 1.
> Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> 2.
> No it is not clustered.
> 3.
> Yes I have tried to run both the SQL Server and Agent under the local
> system
> account
> 4.
> I have checked all logs and nothing is recorded when Agent goes down with
> the exception of what I have already stated.
> --
> Mark A. Lutz (aka Eggbert)
>
> "Uri Dimant" wrote:
|||You may also want to turn on verbose logging for SQL Agent -
from the Properties window for Agent, select Include
Execution Trace Messages from the general section on the
properties for Agent. You don't want to keep this on - just
use it for troubleshooting. Turn it on and restart Agent and
check to see what's going on more with the job executions.
The additional details will be logged to the SQL Agent error
log.
-Sue
On Tue, 20 Feb 2007 09:31:13 -0800, Eggbert
<Eggbert@.discussions.microsoft.com> wrote:

>1.
>Microsoft SQL Server 2000 - 8.00.2039
>(Intel X86)
>May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation
>Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>2.
>No it is not clustered.
>3.
>Yes I have tried to run both the SQL Server and Agent under the local system
>account
>4.
>I have checked all logs and nothing is recorded when Agent goes down with
>the exception of what I have already stated.
|||In my setup we have 4 servers that are colocated with a web hosting service
so I do not have direct contact with them. The servers are not in an Active
Directory Domain Structure and each opperates independantly. The server in
question is my SQL server only. Each of my servers have two network cards.
One card is connected to the internet and the other card is connected to an
internal only router. The SQL server is setup to only respond to the internal
cart and port. The account running the SQL Server and SQL Agent is the a
local account for the SQL Server box.
The last time one of my jobs ran sucsesfully was 2/6/07. It does not appear
that MS07-009 has been applied. The way I checked was to go out to
windowsupdate.microsoft.com and used the View your Update History option.
Again this is the oddest thing I have seen and I cant find a reason for it.
As I mentioned in another post wether I try to run a job manually or let
agent run it at a specific time, as soon as the job starts Agent shuts down
and restarts. There are no the last entry in the log is that the job was
requested to run i.e.
2007-02-21 08:57:58 - ? [177] Job SWFHomes Listings Alert has been requested
to run by User LEESQL\Mark
The System Event viewer records "The SQLSERVERAGENT service terminated
unexpectedly." and that the Agent has restarted. There are no other log
entries anywhere.
Mark A. Lutz (aka Eggbert)
"Geoff N. Hiten" wrote:

> Check your system and see if you have MS07-009 applied (KB 927779). This is
> a windows update security patch released ths month.
> Is your system in a resource domain that is called by users in another
> domain?
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> news:B96458B0-B21A-4017-A509-3F9FEF7372D3@.microsoft.com...
>
|||I turned this on but it did not result in any additional information. As soon
as I manually or the agent triggers a job to run the agent immediatly shuts
down with no log entries and then restarts. Again it happens if I do it by
right clicking on the job and start it or the event fires off on it's own.
Mark A. Lutz (aka Eggbert)
"Sue Hoegemeier" wrote:

> You may also want to turn on verbose logging for SQL Agent -
> from the Properties window for Agent, select Include
> Execution Trace Messages from the general section on the
> properties for Agent. You don't want to keep this on - just
> use it for troubleshooting. Turn it on and restart Agent and
> check to see what's going on more with the job executions.
> The additional details will be logged to the SQL Agent error
> log.
> -Sue
> On Tue, 20 Feb 2007 09:31:13 -0800, Eggbert
> <Eggbert@.discussions.microsoft.com> wrote:
>
>
|||Thanks.
I am seeing the exact same thing at a client after a maintenance window
where updates were applied. I suspect an interaction between an update and
the SQL agent, but am having some difficulty proving it. Thanks for the
details on your configuration. I will let you know if I find anything on my
end.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:E76F1FDD-5BEC-4B98-9A19-5AEBAAEA4214@.microsoft.com...[vbcol=seagreen]
> In my setup we have 4 servers that are colocated with a web hosting
> service
> so I do not have direct contact with them. The servers are not in an
> Active
> Directory Domain Structure and each opperates independantly. The server in
> question is my SQL server only. Each of my servers have two network cards.
> One card is connected to the internet and the other card is connected to
> an
> internal only router. The SQL server is setup to only respond to the
> internal
> cart and port. The account running the SQL Server and SQL Agent is the a
> local account for the SQL Server box.
> The last time one of my jobs ran sucsesfully was 2/6/07. It does not
> appear
> that MS07-009 has been applied. The way I checked was to go out to
> windowsupdate.microsoft.com and used the View your Update History option.
> Again this is the oddest thing I have seen and I cant find a reason for
> it.
> As I mentioned in another post wether I try to run a job manually or let
> agent run it at a specific time, as soon as the job starts Agent shuts
> down
> and restarts. There are no the last entry in the log is that the job was
> requested to run i.e.
> 2007-02-21 08:57:58 - ? [177] Job SWFHomes Listings Alert has been
> requested
> to run by User LEESQL\Mark
> The System Event viewer records "The SQLSERVERAGENT service terminated
> unexpectedly." and that the Agent has restarted. There are no other log
> entries anywhere.
> --
> Mark A. Lutz (aka Eggbert)
>
> "Geoff N. Hiten" wrote:

MSSQLSERVER Error 17052

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 2/20/2007
Time: 4:38:39 AM
User: N/A
Computer: LEESQL
Description:
SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: a8 01 00 00 0a 00 00 00 ¨......
0008: 0e 00 00 00 4c 00 45 00 ...L.E.
0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
0018: 00 00 0e 00 00 00 6d 00 .....m.
0020: 61 00 73 00 74 00 65 00 a.s.t.e.
0028: 72 00 00 00 r...
Everytime I try to run a job in sql server agent it shuts down the agent.
None of the files in the log directory have any details about the shutdown.
This is driving me nuts. I have checked and rechecked permissions and even
created a new login for the sql server and the agent to use. Still the same
thing. Since I am getting no error logs I am totally lost as to where to loo
k
for information. I am also not finding anything about this when I google for
it. Any help anyone could give would be appreciated.
--
Mark A. Lutz (aka Eggbert)Hi
Can open the SQL Server errorlog file in notepad to see if you have
additional information?
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 2/20/2007
> Time: 4:38:39 AM
> User: N/A
> Computer: LEESQL
> Description:
> SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: a8 01 00 00 0a 00 00 00 ......
> 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
> 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
> 0018: 00 00 0e 00 00 00 6d 00 .....m.
> 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
> 0028: 72 00 00 00 r...
> Everytime I try to run a job in sql server agent it shuts down the agent.
> None of the files in the log directory have any details about the
> shutdown.
> This is driving me nuts. I have checked and rechecked permissions and even
> created a new login for the sql server and the agent to use. Still the
> same
> thing. Since I am getting no error logs I am totally lost as to where to
> look
> for information. I am also not finding anything about this when I google
> for
> it. Any help anyone could give would be appreciated.
> --
> Mark A. Lutz (aka Eggbert)|||As I mentioned I had done that and not found anything informative but I will
paste them here:
____________
SQLAGENT.OUT
2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
(x86 unicode retail build) : Process ID
2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
(x86 unicode retail build) : Process ID 396
2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
connection limit)
2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version 3.86.1830
2007-02-20 04:38:39 - ? [103] NetLib being used by driver is DBMSSHRN.DL
L;
Local host server is
2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM detected
2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running Windows N
T
5.2 (3790) Service Pack 1
2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows NT
service control
2007-02-20 04:38:39 - + [260] Unable to start mail session (reason: No m
ail
profile defined)
2007-02-20 04:38:39 - + [396] An idle CPU condition has not been defined
-
OnIdle job schedules will have no effect
____________
SQLAGENT.1
2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-02-20 04:36:59.00 server All rights reserved.
2007-02-20 04:36:59.00 server Server Process ID is 1184.
2007-02-20 04:36:59.00 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-02-20 04:36:59.00 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2007-02-20 04:36:59.09 server SQL Server configured for thread mode
processing.
2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500] L
ock
Blocks, [5000] Lock Owner Blocks.
2007-02-20 04:36:59.10 server Attempting to initialize Distributed
Transaction Coordinator.
2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2007-02-20 04:37:00.51 server SQL Server is ready for client connections
2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
2007-02-20 04:37:55.15 spid2 Recovery complete.
2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
created.
2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_qv'.
2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_sqlagent_monitor'.
____________
ERRORLOG
2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-02-20 04:36:59.00 server All rights reserved.
2007-02-20 04:36:59.00 server Server Process ID is 1184.
2007-02-20 04:36:59.00 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-02-20 04:36:59.00 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2007-02-20 04:36:59.09 server SQL Server configured for thread mode
processing.
2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500] L
ock
Blocks, [5000] Lock Owner Blocks.
2007-02-20 04:36:59.10 server Attempting to initialize Distributed
Transaction Coordinator.
2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2007-02-20 04:37:00.51 server SQL Server is ready for client connections
2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
2007-02-20 04:37:55.15 spid2 Recovery complete.
2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
created.
2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_qv'.
2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_sqlagent_monitor'.
Mark A. Lutz (aka Eggbert)
"Uri Dimant" wrote:

> Hi
> Can open the SQL Server errorlog file in notepad to see if you have
> additional information?
>
>
> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
>
>|||Hi
1) Is it SQL Server 7.0/2000/2005?
2) Is it clustered?
http://www.tutorials-ne.com/cluster...t-create-14238/
3) Have you tried to set LocalSystem account to the service?
4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...[vbcol=seagreen]
> As I mentioned I had done that and not found anything informative but I
> will
> paste them here:
>
> ____________
> SQLAGENT.OUT
> 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.20
39
> (x86 unicode retail build) : Process ID
> 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.20
39
> (x86 unicode retail build) : Process ID 396
> 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
> connection limit)
> 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version 3.86.1830
> 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is DBMSSHRN.
DLL;
> Local host server is
> 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM detected
> 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running Windows
NT
> 5.2 (3790) Service Pack 1
> 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows NT
> service control
> 2007-02-20 04:38:39 - + [260] Unable to start mail session (reason: No
> mail
> profile defined)
> 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been defin
ed -
> OnIdle job schedules will have no effect
> ____________
> SQLAGENT.1
> 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2007-02-20 04:36:59.00 server All rights reserved.
> 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2007-02-20 04:36:59.00 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> processing.
> 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> Lock
> Blocks, [5000] Lock Owner Blocks.
> 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
> 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> Memory,
> Named Pipes.
> 2007-02-20 04:37:00.51 server SQL Server is ready for client
> connections
> 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> 2007-02-20 04:37:55.15 spid2 Recovery complete.
> 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> created.
> 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> '2000.80.2039'
> to execute extended stored procedure 'xp_qv'.
> 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_sqlagent_monitor'.
> ____________
> ERRORLOG
> 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2007-02-20 04:36:59.00 server All rights reserved.
> 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2007-02-20 04:36:59.00 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> processing.
> 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> Lock
> Blocks, [5000] Lock Owner Blocks.
> 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
> 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> Memory,
> Named Pipes.
> 2007-02-20 04:37:00.51 server SQL Server is ready for client
> connections
> 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> 2007-02-20 04:37:55.15 spid2 Recovery complete.
> 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> created.
> 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> '2000.80.2039'
> to execute extended stored procedure 'xp_qv'.
> 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_sqlagent_monitor'.
> --
> Mark A. Lutz (aka Eggbert)
>
> "Uri Dimant" wrote:
>|||1.
Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2.
No it is not clustered.
3.
Yes I have tried to run both the SQL Server and Agent under the local system
account
4.
I have checked all logs and nothing is recorded when Agent goes down with
the exception of what I have already stated.
--
Mark A. Lutz (aka Eggbert)
"Uri Dimant" wrote:

> Hi
> 1) Is it SQL Server 7.0/2000/2005?
> 2) Is it clustered?
> http://www.tutorials-ne.com/cluster...t-create-14238/
> 3) Have you tried to set LocalSystem account to the service?
> 4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
>
>|||Check your system and see if you have MS07-009 applied (KB 927779). This is
a windows update security patch released ths month.
Is your system in a resource domain that is called by users in another
domain?
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:B96458B0-B21A-4017-A509-3F9FEF7372D3@.microsoft.com...[vbcol=seagreen]
> 1.
> Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> 2.
> No it is not clustered.
> 3.
> Yes I have tried to run both the SQL Server and Agent under the local
> system
> account
> 4.
> I have checked all logs and nothing is recorded when Agent goes down with
> the exception of what I have already stated.
> --
> Mark A. Lutz (aka Eggbert)
>
> "Uri Dimant" wrote:
>|||You may also want to turn on verbose logging for SQL Agent -
from the Properties window for Agent, select Include
Execution Trace Messages from the general section on the
properties for Agent. You don't want to keep this on - just
use it for troubleshooting. Turn it on and restart Agent and
check to see what's going on more with the job executions.
The additional details will be logged to the SQL Agent error
log.
-Sue
On Tue, 20 Feb 2007 09:31:13 -0800, Eggbert
<Eggbert@.discussions.microsoft.com> wrote:

>1.
>Microsoft SQL Server 2000 - 8.00.2039
>(Intel X86)
>May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation
>Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>2.
>No it is not clustered.
>3.
>Yes I have tried to run both the SQL Server and Agent under the local syste
m
>account
>4.
>I have checked all logs and nothing is recorded when Agent goes down with
>the exception of what I have already stated.|||In my setup we have 4 servers that are colocated with a web hosting service
so I do not have direct contact with them. The servers are not in an Active
Directory Domain Structure and each opperates independantly. The server in
question is my SQL server only. Each of my servers have two network cards.
One card is connected to the internet and the other card is connected to an
internal only router. The SQL server is setup to only respond to the interna
l
cart and port. The account running the SQL Server and SQL Agent is the a
local account for the SQL Server box.
The last time one of my jobs ran sucsesfully was 2/6/07. It does not appear
that MS07-009 has been applied. The way I checked was to go out to
windowsupdate.microsoft.com and used the View your Update History option.
Again this is the oddest thing I have seen and I cant find a reason for it.
As I mentioned in another post wether I try to run a job manually or let
agent run it at a specific time, as soon as the job starts Agent shuts down
and restarts. There are no the last entry in the log is that the job was
requested to run i.e.
2007-02-21 08:57:58 - ? [177] Job SWFHomes Listings Alert has been reque
sted
to run by User LEESQL\Mark
The System Event viewer records "The SQLSERVERAGENT service terminated
unexpectedly." and that the Agent has restarted. There are no other log
entries anywhere.
Mark A. Lutz (aka Eggbert)
"Geoff N. Hiten" wrote:

> Check your system and see if you have MS07-009 applied (KB 927779). This
is
> a windows update security patch released ths month.
> Is your system in a resource domain that is called by users in another
> domain?
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> news:B96458B0-B21A-4017-A509-3F9FEF7372D3@.microsoft.com...
>|||I turned this on but it did not result in any additional information. As soo
n
as I manually or the agent triggers a job to run the agent immediatly shuts
down with no log entries and then restarts. Again it happens if I do it by
right clicking on the job and start it or the event fires off on it's own.
Mark A. Lutz (aka Eggbert)
"Sue Hoegemeier" wrote:

> You may also want to turn on verbose logging for SQL Agent -
> from the Properties window for Agent, select Include
> Execution Trace Messages from the general section on the
> properties for Agent. You don't want to keep this on - just
> use it for troubleshooting. Turn it on and restart Agent and
> check to see what's going on more with the job executions.
> The additional details will be logged to the SQL Agent error
> log.
> -Sue
> On Tue, 20 Feb 2007 09:31:13 -0800, Eggbert
> <Eggbert@.discussions.microsoft.com> wrote:
>
>|||Thanks.
I am seeing the exact same thing at a client after a maintenance window
where updates were applied. I suspect an interaction between an update and
the SQL agent, but am having some difficulty proving it. Thanks for the
details on your configuration. I will let you know if I find anything on my
end.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:E76F1FDD-5BEC-4B98-9A19-5AEBAAEA4214@.microsoft.com...[vbcol=seagreen]
> In my setup we have 4 servers that are colocated with a web hosting
> service
> so I do not have direct contact with them. The servers are not in an
> Active
> Directory Domain Structure and each opperates independantly. The server in
> question is my SQL server only. Each of my servers have two network cards.
> One card is connected to the internet and the other card is connected to
> an
> internal only router. The SQL server is setup to only respond to the
> internal
> cart and port. The account running the SQL Server and SQL Agent is the a
> local account for the SQL Server box.
> The last time one of my jobs ran sucsesfully was 2/6/07. It does not
> appear
> that MS07-009 has been applied. The way I checked was to go out to
> windowsupdate.microsoft.com and used the View your Update History option.
> Again this is the oddest thing I have seen and I cant find a reason for
> it.
> As I mentioned in another post wether I try to run a job manually or let
> agent run it at a specific time, as soon as the job starts Agent shuts
> down
> and restarts. There are no the last entry in the log is that the job was
> requested to run i.e.
> 2007-02-21 08:57:58 - ? [177] Job SWFHomes Listings Alert has been
> requested
> to run by User LEESQL\Mark
> The System Event viewer records "The SQLSERVERAGENT service terminated
> unexpectedly." and that the Agent has restarted. There are no other log
> entries anywhere.
> --
> Mark A. Lutz (aka Eggbert)
>
> "Geoff N. Hiten" wrote:
>

MSSQLSERVER Error 17052

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 2/20/2007
Time: 4:38:39 AM
User: N/A
Computer: LEESQL
Description:
SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: a8 01 00 00 0a 00 00 00 ¨......
0008: 0e 00 00 00 4c 00 45 00 ...L.E.
0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
0018: 00 00 0e 00 00 00 6d 00 .....m.
0020: 61 00 73 00 74 00 65 00 a.s.t.e.
0028: 72 00 00 00 r...
Everytime I try to run a job in sql server agent it shuts down the agent.
None of the files in the log directory have any details about the shutdown.
This is driving me nuts. I have checked and rechecked permissions and even
created a new login for the sql server and the agent to use. Still the same
thing. Since I am getting no error logs I am totally lost as to where to look
for information. I am also not finding anything about this when I google for
it. Any help anyone could give would be appreciated.
--
Mark A. Lutz (aka Eggbert)Hi
Can open the SQL Server errorlog file in notepad to see if you have
additional information?
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 2/20/2007
> Time: 4:38:39 AM
> User: N/A
> Computer: LEESQL
> Description:
> SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: a8 01 00 00 0a 00 00 00 ¨......
> 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
> 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
> 0018: 00 00 0e 00 00 00 6d 00 .....m.
> 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
> 0028: 72 00 00 00 r...
> Everytime I try to run a job in sql server agent it shuts down the agent.
> None of the files in the log directory have any details about the
> shutdown.
> This is driving me nuts. I have checked and rechecked permissions and even
> created a new login for the sql server and the agent to use. Still the
> same
> thing. Since I am getting no error logs I am totally lost as to where to
> look
> for information. I am also not finding anything about this when I google
> for
> it. Any help anyone could give would be appreciated.
> --
> Mark A. Lutz (aka Eggbert)|||As I mentioned I had done that and not found anything informative but I will
paste them here:
____________
SQLAGENT.OUT
2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
(x86 unicode retail build) : Process ID
2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
(x86 unicode retail build) : Process ID 396
2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
connection limit)
2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version 3.86.1830
2007-02-20 04:38:39 - ? [103] NetLib being used by driver is DBMSSHRN.DLL;
Local host server is
2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM detected
2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running Windows NT
5.2 (3790) Service Pack 1
2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows NT
service control
2007-02-20 04:38:39 - + [260] Unable to start mail session (reason: No mail
profile defined)
2007-02-20 04:38:39 - + [396] An idle CPU condition has not been defined -
OnIdle job schedules will have no effect
____________
SQLAGENT.1
2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-02-20 04:36:59.00 server All rights reserved.
2007-02-20 04:36:59.00 server Server Process ID is 1184.
2007-02-20 04:36:59.00 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-02-20 04:36:59.00 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2007-02-20 04:36:59.09 server SQL Server configured for thread mode
processing.
2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2007-02-20 04:36:59.10 server Attempting to initialize Distributed
Transaction Coordinator.
2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2007-02-20 04:37:00.51 server SQL Server is ready for client connections
2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
2007-02-20 04:37:55.15 spid2 Recovery complete.
2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
created.
2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_qv'.
2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_sqlagent_monitor'.
____________
ERRORLOG
2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-02-20 04:36:59.00 server All rights reserved.
2007-02-20 04:36:59.00 server Server Process ID is 1184.
2007-02-20 04:36:59.00 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-02-20 04:36:59.00 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2007-02-20 04:36:59.09 server SQL Server configured for thread mode
processing.
2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2007-02-20 04:36:59.10 server Attempting to initialize Distributed
Transaction Coordinator.
2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2007-02-20 04:37:00.51 server SQL Server is ready for client connections
2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
2007-02-20 04:37:55.15 spid2 Recovery complete.
2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
created.
2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_qv'.
2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_sqlagent_monitor'.
--
Mark A. Lutz (aka Eggbert)
"Uri Dimant" wrote:
> Hi
> Can open the SQL Server errorlog file in notepad to see if you have
> additional information?
>
>
> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
> > Event Type: Error
> > Event Source: MSSQLSERVER
> > Event Category: (2)
> > Event ID: 17052
> > Date: 2/20/2007
> > Time: 4:38:39 AM
> > User: N/A
> > Computer: LEESQL
> > Description:
> > SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: a8 01 00 00 0a 00 00 00 ¨......
> > 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
> > 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
> > 0018: 00 00 0e 00 00 00 6d 00 .....m.
> > 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
> > 0028: 72 00 00 00 r...
> >
> > Everytime I try to run a job in sql server agent it shuts down the agent.
> > None of the files in the log directory have any details about the
> > shutdown.
> > This is driving me nuts. I have checked and rechecked permissions and even
> > created a new login for the sql server and the agent to use. Still the
> > same
> > thing. Since I am getting no error logs I am totally lost as to where to
> > look
> > for information. I am also not finding anything about this when I google
> > for
> > it. Any help anyone could give would be appreciated.
> > --
> > Mark A. Lutz (aka Eggbert)
>
>|||Hi
1) Is it SQL Server 7.0/2000/2005?
2) Is it clustered?
http://www.tutorials-ne.com/clustering/Cannot-create-14238/
3) Have you tried to set LocalSystem account to the service?
4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
> As I mentioned I had done that and not found anything informative but I
> will
> paste them here:
>
> ____________
> SQLAGENT.OUT
> 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
> (x86 unicode retail build) : Process ID
> 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
> (x86 unicode retail build) : Process ID 396
> 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
> connection limit)
> 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version 3.86.1830
> 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is DBMSSHRN.DLL;
> Local host server is
> 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM detected
> 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running Windows NT
> 5.2 (3790) Service Pack 1
> 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows NT
> service control
> 2007-02-20 04:38:39 - + [260] Unable to start mail session (reason: No
> mail
> profile defined)
> 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been defined -
> OnIdle job schedules will have no effect
> ____________
> SQLAGENT.1
> 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2007-02-20 04:36:59.00 server All rights reserved.
> 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2007-02-20 04:36:59.00 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> processing.
> 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> Lock
> Blocks, [5000] Lock Owner Blocks.
> 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
> 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> Memory,
> Named Pipes.
> 2007-02-20 04:37:00.51 server SQL Server is ready for client
> connections
> 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> 2007-02-20 04:37:55.15 spid2 Recovery complete.
> 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> created.
> 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> '2000.80.2039'
> to execute extended stored procedure 'xp_qv'.
> 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_sqlagent_monitor'.
> ____________
> ERRORLOG
> 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2007-02-20 04:36:59.00 server All rights reserved.
> 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2007-02-20 04:36:59.00 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> processing.
> 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> Lock
> Blocks, [5000] Lock Owner Blocks.
> 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
> 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> Memory,
> Named Pipes.
> 2007-02-20 04:37:00.51 server SQL Server is ready for client
> connections
> 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> 2007-02-20 04:37:55.15 spid2 Recovery complete.
> 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> created.
> 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> '2000.80.2039'
> to execute extended stored procedure 'xp_qv'.
> 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_sqlagent_monitor'.
> --
> Mark A. Lutz (aka Eggbert)
>
> "Uri Dimant" wrote:
>> Hi
>> Can open the SQL Server errorlog file in notepad to see if you have
>> additional information?
>>
>>
>> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
>> > Event Type: Error
>> > Event Source: MSSQLSERVER
>> > Event Category: (2)
>> > Event ID: 17052
>> > Date: 2/20/2007
>> > Time: 4:38:39 AM
>> > User: N/A
>> > Computer: LEESQL
>> > Description:
>> > SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
>> >
>> > For more information, see Help and Support Center at
>> > http://go.microsoft.com/fwlink/events.asp.
>> > Data:
>> > 0000: a8 01 00 00 0a 00 00 00 ¨......
>> > 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
>> > 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
>> > 0018: 00 00 0e 00 00 00 6d 00 .....m.
>> > 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
>> > 0028: 72 00 00 00 r...
>> >
>> > Everytime I try to run a job in sql server agent it shuts down the
>> > agent.
>> > None of the files in the log directory have any details about the
>> > shutdown.
>> > This is driving me nuts. I have checked and rechecked permissions and
>> > even
>> > created a new login for the sql server and the agent to use. Still the
>> > same
>> > thing. Since I am getting no error logs I am totally lost as to where
>> > to
>> > look
>> > for information. I am also not finding anything about this when I
>> > google
>> > for
>> > it. Any help anyone could give would be appreciated.
>> > --
>> > Mark A. Lutz (aka Eggbert)
>>|||1.
Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2.
No it is not clustered.
3.
Yes I have tried to run both the SQL Server and Agent under the local system
account
4.
I have checked all logs and nothing is recorded when Agent goes down with
the exception of what I have already stated.
--
Mark A. Lutz (aka Eggbert)
"Uri Dimant" wrote:
> Hi
> 1) Is it SQL Server 7.0/2000/2005?
> 2) Is it clustered?
> http://www.tutorials-ne.com/clustering/Cannot-create-14238/
> 3) Have you tried to set LocalSystem account to the service?
> 4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
> > As I mentioned I had done that and not found anything informative but I
> > will
> > paste them here:
> >
> >
> > ____________
> > SQLAGENT.OUT
> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
> > (x86 unicode retail build) : Process ID
> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
> > (x86 unicode retail build) : Process ID 396
> > 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
> > connection limit)
> > 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version 3.86.1830
> > 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is DBMSSHRN.DLL;
> > Local host server is
> > 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM detected
> > 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running Windows NT
> > 5.2 (3790) Service Pack 1
> > 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows NT
> > service control
> > 2007-02-20 04:38:39 - + [260] Unable to start mail session (reason: No
> > mail
> > profile defined)
> > 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been defined -
> > OnIdle job schedules will have no effect
> >
> > ____________
> > SQLAGENT.1
> > 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
> > (Intel X86)
> > May 3 2005 23:18:38
> > Copyright (c) 1988-2003 Microsoft Corporation
> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> >
> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> > Corporation.
> > 2007-02-20 04:36:59.00 server All rights reserved.
> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority class
> > 'normal'(2 CPUs detected).
> > 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> > processing.
> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> > Lock
> > Blocks, [5000] Lock Owner Blocks.
> > 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> > Transaction Coordinator.
> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> > 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> > 1433.
> > 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> > 1433.
> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> > Memory,
> > Named Pipes.
> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
> > connections
> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> > 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> > created.
> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> > '2000.80.2039'
> > to execute extended stored procedure 'xp_qv'.
> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
> > to execute extended stored procedure 'xp_sqlagent_monitor'.
> >
> > ____________
> > ERRORLOG
> >
> > 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
> > (Intel X86)
> > May 3 2005 23:18:38
> > Copyright (c) 1988-2003 Microsoft Corporation
> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> >
> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> > Corporation.
> > 2007-02-20 04:36:59.00 server All rights reserved.
> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority class
> > 'normal'(2 CPUs detected).
> > 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> > processing.
> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> > Lock
> > Blocks, [5000] Lock Owner Blocks.
> > 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> > Transaction Coordinator.
> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> > 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> > 1433.
> > 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> > 1433.
> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> > Memory,
> > Named Pipes.
> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
> > connections
> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> > 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> > created.
> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> > '2000.80.2039'
> > to execute extended stored procedure 'xp_qv'.
> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
> > to execute extended stored procedure 'xp_sqlagent_monitor'.
> >
> > --
> > Mark A. Lutz (aka Eggbert)
> >
> >
> > "Uri Dimant" wrote:
> >
> >> Hi
> >> Can open the SQL Server errorlog file in notepad to see if you have
> >> additional information?
> >>
> >>
> >>
> >>
> >>
> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> >> news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
> >> > Event Type: Error
> >> > Event Source: MSSQLSERVER
> >> > Event Category: (2)
> >> > Event ID: 17052
> >> > Date: 2/20/2007
> >> > Time: 4:38:39 AM
> >> > User: N/A
> >> > Computer: LEESQL
> >> > Description:
> >> > SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
> >> >
> >> > For more information, see Help and Support Center at
> >> > http://go.microsoft.com/fwlink/events.asp.
> >> > Data:
> >> > 0000: a8 01 00 00 0a 00 00 00 ¨......
> >> > 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
> >> > 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
> >> > 0018: 00 00 0e 00 00 00 6d 00 .....m.
> >> > 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
> >> > 0028: 72 00 00 00 r...
> >> >
> >> > Everytime I try to run a job in sql server agent it shuts down the
> >> > agent.
> >> > None of the files in the log directory have any details about the
> >> > shutdown.
> >> > This is driving me nuts. I have checked and rechecked permissions and
> >> > even
> >> > created a new login for the sql server and the agent to use. Still the
> >> > same
> >> > thing. Since I am getting no error logs I am totally lost as to where
> >> > to
> >> > look
> >> > for information. I am also not finding anything about this when I
> >> > google
> >> > for
> >> > it. Any help anyone could give would be appreciated.
> >> > --
> >> > Mark A. Lutz (aka Eggbert)
> >>
> >>
> >>
>
>|||Check your system and see if you have MS07-009 applied (KB 927779). This is
a windows update security patch released ths month.
Is your system in a resource domain that is called by users in another
domain?
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:B96458B0-B21A-4017-A509-3F9FEF7372D3@.microsoft.com...
> 1.
> Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> 2.
> No it is not clustered.
> 3.
> Yes I have tried to run both the SQL Server and Agent under the local
> system
> account
> 4.
> I have checked all logs and nothing is recorded when Agent goes down with
> the exception of what I have already stated.
> --
> Mark A. Lutz (aka Eggbert)
>
> "Uri Dimant" wrote:
>> Hi
>> 1) Is it SQL Server 7.0/2000/2005?
>> 2) Is it clustered?
>> http://www.tutorials-ne.com/clustering/Cannot-create-14238/
>> 3) Have you tried to set LocalSystem account to the service?
>> 4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
>> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
>> > As I mentioned I had done that and not found anything informative but I
>> > will
>> > paste them here:
>> >
>> >
>> > ____________
>> > SQLAGENT.OUT
>> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
>> > 8.00.2039
>> > (x86 unicode retail build) : Process ID
>> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
>> > 8.00.2039
>> > (x86 unicode retail build) : Process ID 396
>> > 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
>> > connection limit)
>> > 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version 3.86.1830
>> > 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is
>> > DBMSSHRN.DLL;
>> > Local host server is
>> > 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM detected
>> > 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running Windows
>> > NT
>> > 5.2 (3790) Service Pack 1
>> > 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows NT
>> > service control
>> > 2007-02-20 04:38:39 - + [260] Unable to start mail session (reason: No
>> > mail
>> > profile defined)
>> > 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been
>> > defined -
>> > OnIdle job schedules will have no effect
>> >
>> > ____________
>> > SQLAGENT.1
>> > 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
>> > (Intel X86)
>> > May 3 2005 23:18:38
>> > Copyright (c) 1988-2003 Microsoft Corporation
>> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>> >
>> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
>> > Corporation.
>> > 2007-02-20 04:36:59.00 server All rights reserved.
>> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
>> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
>> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
>> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
>> > class
>> > 'normal'(2 CPUs detected).
>> > 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
>> > processing.
>> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
>> > Lock
>> > Blocks, [5000] Lock Owner Blocks.
>> > 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
>> > Transaction Coordinator.
>> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
>> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
>> > '8.0.2039'.
>> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
>> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
>> > 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
>> > 1433.
>> > 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
>> > 1433.
>> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
>> > 1433.
>> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
>> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
>> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
>> > Memory,
>> > Named Pipes.
>> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
>> > connections
>> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
>> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
>> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
>> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
>> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
>> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
>> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
>> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
>> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
>> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
>> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
>> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
>> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
>> > 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
>> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
>> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
>> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
>> > created.
>> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
>> > '2000.80.2039'
>> > to execute extended stored procedure 'xp_qv'.
>> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
>> > '2000.80.2039'
>> > to execute extended stored procedure 'xp_sqlagent_monitor'.
>> >
>> > ____________
>> > ERRORLOG
>> >
>> > 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
>> > (Intel X86)
>> > May 3 2005 23:18:38
>> > Copyright (c) 1988-2003 Microsoft Corporation
>> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>> >
>> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
>> > Corporation.
>> > 2007-02-20 04:36:59.00 server All rights reserved.
>> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
>> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
>> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
>> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
>> > class
>> > 'normal'(2 CPUs detected).
>> > 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
>> > processing.
>> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
>> > Lock
>> > Blocks, [5000] Lock Owner Blocks.
>> > 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
>> > Transaction Coordinator.
>> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
>> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
>> > '8.0.2039'.
>> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
>> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
>> > 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
>> > 1433.
>> > 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
>> > 1433.
>> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
>> > 1433.
>> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
>> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
>> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
>> > Memory,
>> > Named Pipes.
>> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
>> > connections
>> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
>> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
>> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
>> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
>> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
>> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
>> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
>> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
>> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
>> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
>> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
>> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
>> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
>> > 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
>> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
>> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
>> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
>> > created.
>> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
>> > '2000.80.2039'
>> > to execute extended stored procedure 'xp_qv'.
>> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
>> > '2000.80.2039'
>> > to execute extended stored procedure 'xp_sqlagent_monitor'.
>> >
>> > --
>> > Mark A. Lutz (aka Eggbert)
>> >
>> >
>> > "Uri Dimant" wrote:
>> >
>> >> Hi
>> >> Can open the SQL Server errorlog file in notepad to see if you have
>> >> additional information?
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> >> news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
>> >> > Event Type: Error
>> >> > Event Source: MSSQLSERVER
>> >> > Event Category: (2)
>> >> > Event ID: 17052
>> >> > Date: 2/20/2007
>> >> > Time: 4:38:39 AM
>> >> > User: N/A
>> >> > Computer: LEESQL
>> >> > Description:
>> >> > SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: a8 01 00 00 0a 00 00 00 ¨......
>> >> > 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
>> >> > 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
>> >> > 0018: 00 00 0e 00 00 00 6d 00 .....m.
>> >> > 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
>> >> > 0028: 72 00 00 00 r...
>> >> >
>> >> > Everytime I try to run a job in sql server agent it shuts down the
>> >> > agent.
>> >> > None of the files in the log directory have any details about the
>> >> > shutdown.
>> >> > This is driving me nuts. I have checked and rechecked permissions
>> >> > and
>> >> > even
>> >> > created a new login for the sql server and the agent to use. Still
>> >> > the
>> >> > same
>> >> > thing. Since I am getting no error logs I am totally lost as to
>> >> > where
>> >> > to
>> >> > look
>> >> > for information. I am also not finding anything about this when I
>> >> > google
>> >> > for
>> >> > it. Any help anyone could give would be appreciated.
>> >> > --
>> >> > Mark A. Lutz (aka Eggbert)
>> >>
>> >>
>> >>
>>|||You may also want to turn on verbose logging for SQL Agent -
from the Properties window for Agent, select Include
Execution Trace Messages from the general section on the
properties for Agent. You don't want to keep this on - just
use it for troubleshooting. Turn it on and restart Agent and
check to see what's going on more with the job executions.
The additional details will be logged to the SQL Agent error
log.
-Sue
On Tue, 20 Feb 2007 09:31:13 -0800, Eggbert
<Eggbert@.discussions.microsoft.com> wrote:
>1.
>Microsoft SQL Server 2000 - 8.00.2039
>(Intel X86)
>May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation
>Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>2.
>No it is not clustered.
>3.
>Yes I have tried to run both the SQL Server and Agent under the local system
>account
>4.
>I have checked all logs and nothing is recorded when Agent goes down with
>the exception of what I have already stated.|||In my setup we have 4 servers that are colocated with a web hosting service
so I do not have direct contact with them. The servers are not in an Active
Directory Domain Structure and each opperates independantly. The server in
question is my SQL server only. Each of my servers have two network cards.
One card is connected to the internet and the other card is connected to an
internal only router. The SQL server is setup to only respond to the internal
cart and port. The account running the SQL Server and SQL Agent is the a
local account for the SQL Server box.
The last time one of my jobs ran sucsesfully was 2/6/07. It does not appear
that MS07-009 has been applied. The way I checked was to go out to
windowsupdate.microsoft.com and used the View your Update History option.
Again this is the oddest thing I have seen and I cant find a reason for it.
As I mentioned in another post wether I try to run a job manually or let
agent run it at a specific time, as soon as the job starts Agent shuts down
and restarts. There are no the last entry in the log is that the job was
requested to run i.e.
2007-02-21 08:57:58 - ? [177] Job SWFHomes Listings Alert has been requested
to run by User LEESQL\Mark
The System Event viewer records "The SQLSERVERAGENT service terminated
unexpectedly." and that the Agent has restarted. There are no other log
entries anywhere.
--
Mark A. Lutz (aka Eggbert)
"Geoff N. Hiten" wrote:
> Check your system and see if you have MS07-009 applied (KB 927779). This is
> a windows update security patch released ths month.
> Is your system in a resource domain that is called by users in another
> domain?
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> news:B96458B0-B21A-4017-A509-3F9FEF7372D3@.microsoft.com...
> > 1.
> > Microsoft SQL Server 2000 - 8.00.2039
> > (Intel X86)
> > May 3 2005 23:18:38
> > Copyright (c) 1988-2003 Microsoft Corporation
> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> >
> > 2.
> > No it is not clustered.
> >
> > 3.
> > Yes I have tried to run both the SQL Server and Agent under the local
> > system
> > account
> >
> > 4.
> > I have checked all logs and nothing is recorded when Agent goes down with
> > the exception of what I have already stated.
> > --
> > Mark A. Lutz (aka Eggbert)
> >
> >
> > "Uri Dimant" wrote:
> >
> >> Hi
> >> 1) Is it SQL Server 7.0/2000/2005?
> >> 2) Is it clustered?
> >> http://www.tutorials-ne.com/clustering/Cannot-create-14238/
> >> 3) Have you tried to set LocalSystem account to the service?
> >> 4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
> >>
> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> >> news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
> >> > As I mentioned I had done that and not found anything informative but I
> >> > will
> >> > paste them here:
> >> >
> >> >
> >> > ____________
> >> > SQLAGENT.OUT
> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
> >> > 8.00.2039
> >> > (x86 unicode retail build) : Process ID
> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
> >> > 8.00.2039
> >> > (x86 unicode retail build) : Process ID 396
> >> > 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
> >> > connection limit)
> >> > 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version 3.86.1830
> >> > 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is
> >> > DBMSSHRN.DLL;
> >> > Local host server is
> >> > 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM detected
> >> > 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running Windows
> >> > NT
> >> > 5.2 (3790) Service Pack 1
> >> > 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows NT
> >> > service control
> >> > 2007-02-20 04:38:39 - + [260] Unable to start mail session (reason: No
> >> > mail
> >> > profile defined)
> >> > 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been
> >> > defined -
> >> > OnIdle job schedules will have no effect
> >> >
> >> > ____________
> >> > SQLAGENT.1
> >> > 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
> >> > (Intel X86)
> >> > May 3 2005 23:18:38
> >> > Copyright (c) 1988-2003 Microsoft Corporation
> >> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> >> >
> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> >> > Corporation.
> >> > 2007-02-20 04:36:59.00 server All rights reserved.
> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
> >> > class
> >> > 'normal'(2 CPUs detected).
> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> >> > processing.
> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> >> > Lock
> >> > Blocks, [5000] Lock Owner Blocks.
> >> > 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> >> > Transaction Coordinator.
> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
> >> > '8.0.2039'.
> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> >> > 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> >> > 1433.
> >> > 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> >> > 1433.
> >> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
> >> > 1433.
> >> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> >> > Memory,
> >> > Named Pipes.
> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
> >> > connections
> >> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> >> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> >> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> >> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> >> > 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> >> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> >> > created.
> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> >> > '2000.80.2039'
> >> > to execute extended stored procedure 'xp_qv'.
> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
> >> > '2000.80.2039'
> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
> >> >
> >> > ____________
> >> > ERRORLOG
> >> >
> >> > 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 - 8.00.2039
> >> > (Intel X86)
> >> > May 3 2005 23:18:38
> >> > Copyright (c) 1988-2003 Microsoft Corporation
> >> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> >> >
> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> >> > Corporation.
> >> > 2007-02-20 04:36:59.00 server All rights reserved.
> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
> >> > class
> >> > 'normal'(2 CPUs detected).
> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> >> > processing.
> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> >> > Lock
> >> > Blocks, [5000] Lock Owner Blocks.
> >> > 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> >> > Transaction Coordinator.
> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
> >> > '8.0.2039'.
> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> >> > 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> >> > 1433.
> >> > 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> >> > 1433.
> >> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
> >> > 1433.
> >> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> >> > Memory,
> >> > Named Pipes.
> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
> >> > connections
> >> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> >> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> >> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> >> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> >> > 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> >> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> >> > created.
> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> >> > '2000.80.2039'
> >> > to execute extended stored procedure 'xp_qv'.
> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
> >> > '2000.80.2039'
> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
> >> >
> >> > --
> >> > Mark A. Lutz (aka Eggbert)
> >> >
> >> >
> >> > "Uri Dimant" wrote:
> >> >
> >> >> Hi
> >> >> Can open the SQL Server errorlog file in notepad to see if you have
> >> >> additional information?
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> >> >> news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
> >> >> > Event Type: Error
> >> >> > Event Source: MSSQLSERVER
> >> >> > Event Category: (2)
> >> >> > Event ID: 17052
> >> >> > Date: 2/20/2007
> >> >> > Time: 4:38:39 AM
> >> >> > User: N/A
> >> >> > Computer: LEESQL
> >> >> > Description:
> >> >> > SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
> >> >> >
> >> >> > For more information, see Help and Support Center at
> >> >> > http://go.microsoft.com/fwlink/events.asp.
> >> >> > Data:
> >> >> > 0000: a8 01 00 00 0a 00 00 00 ¨......
> >> >> > 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
> >> >> > 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
> >> >> > 0018: 00 00 0e 00 00 00 6d 00 .....m.
> >> >> > 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
> >> >> > 0028: 72 00 00 00 r...
> >> >> >
> >> >> > Everytime I try to run a job in sql server agent it shuts down the
> >> >> > agent.
> >> >> > None of the files in the log directory have any details about the
> >> >> > shutdown.
> >> >> > This is driving me nuts. I have checked and rechecked permissions
> >> >> > and
> >> >> > even
> >> >> > created a new login for the sql server and the agent to use. Still
> >> >> > the
> >> >> > same
> >> >> > thing. Since I am getting no error logs I am totally lost as to
> >> >> > where
> >> >> > to
> >> >> > look
> >> >> > for information. I am also not finding anything about this when I
> >> >> > google
> >> >> > for
> >> >> > it. Any help anyone could give would be appreciated.
> >> >> > --
> >> >> > Mark A. Lutz (aka Eggbert)
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>|||I turned this on but it did not result in any additional information. As soon
as I manually or the agent triggers a job to run the agent immediatly shuts
down with no log entries and then restarts. Again it happens if I do it by
right clicking on the job and start it or the event fires off on it's own.
--
Mark A. Lutz (aka Eggbert)
"Sue Hoegemeier" wrote:
> You may also want to turn on verbose logging for SQL Agent -
> from the Properties window for Agent, select Include
> Execution Trace Messages from the general section on the
> properties for Agent. You don't want to keep this on - just
> use it for troubleshooting. Turn it on and restart Agent and
> check to see what's going on more with the job executions.
> The additional details will be logged to the SQL Agent error
> log.
> -Sue
> On Tue, 20 Feb 2007 09:31:13 -0800, Eggbert
> <Eggbert@.discussions.microsoft.com> wrote:
> >1.
> >Microsoft SQL Server 2000 - 8.00.2039
> >(Intel X86)
> >May 3 2005 23:18:38
> >Copyright (c) 1988-2003 Microsoft Corporation
> >Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> >
> >2.
> >No it is not clustered.
> >
> >3.
> >Yes I have tried to run both the SQL Server and Agent under the local system
> >account
> >
> >4.
> >I have checked all logs and nothing is recorded when Agent goes down with
> >the exception of what I have already stated.
>|||Thanks.
I am seeing the exact same thing at a client after a maintenance window
where updates were applied. I suspect an interaction between an update and
the SQL agent, but am having some difficulty proving it. Thanks for the
details on your configuration. I will let you know if I find anything on my
end.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:E76F1FDD-5BEC-4B98-9A19-5AEBAAEA4214@.microsoft.com...
> In my setup we have 4 servers that are colocated with a web hosting
> service
> so I do not have direct contact with them. The servers are not in an
> Active
> Directory Domain Structure and each opperates independantly. The server in
> question is my SQL server only. Each of my servers have two network cards.
> One card is connected to the internet and the other card is connected to
> an
> internal only router. The SQL server is setup to only respond to the
> internal
> cart and port. The account running the SQL Server and SQL Agent is the a
> local account for the SQL Server box.
> The last time one of my jobs ran sucsesfully was 2/6/07. It does not
> appear
> that MS07-009 has been applied. The way I checked was to go out to
> windowsupdate.microsoft.com and used the View your Update History option.
> Again this is the oddest thing I have seen and I cant find a reason for
> it.
> As I mentioned in another post wether I try to run a job manually or let
> agent run it at a specific time, as soon as the job starts Agent shuts
> down
> and restarts. There are no the last entry in the log is that the job was
> requested to run i.e.
> 2007-02-21 08:57:58 - ? [177] Job SWFHomes Listings Alert has been
> requested
> to run by User LEESQL\Mark
> The System Event viewer records "The SQLSERVERAGENT service terminated
> unexpectedly." and that the Agent has restarted. There are no other log
> entries anywhere.
> --
> Mark A. Lutz (aka Eggbert)
>
> "Geoff N. Hiten" wrote:
>> Check your system and see if you have MS07-009 applied (KB 927779). This
>> is
>> a windows update security patch released ths month.
>> Is your system in a resource domain that is called by users in another
>> domain?
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> news:B96458B0-B21A-4017-A509-3F9FEF7372D3@.microsoft.com...
>> > 1.
>> > Microsoft SQL Server 2000 - 8.00.2039
>> > (Intel X86)
>> > May 3 2005 23:18:38
>> > Copyright (c) 1988-2003 Microsoft Corporation
>> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>> >
>> > 2.
>> > No it is not clustered.
>> >
>> > 3.
>> > Yes I have tried to run both the SQL Server and Agent under the local
>> > system
>> > account
>> >
>> > 4.
>> > I have checked all logs and nothing is recorded when Agent goes down
>> > with
>> > the exception of what I have already stated.
>> > --
>> > Mark A. Lutz (aka Eggbert)
>> >
>> >
>> > "Uri Dimant" wrote:
>> >
>> >> Hi
>> >> 1) Is it SQL Server 7.0/2000/2005?
>> >> 2) Is it clustered?
>> >> http://www.tutorials-ne.com/clustering/Cannot-create-14238/
>> >> 3) Have you tried to set LocalSystem account to the service?
>> >> 4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
>> >>
>> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> >> news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
>> >> > As I mentioned I had done that and not found anything informative
>> >> > but I
>> >> > will
>> >> > paste them here:
>> >> >
>> >> >
>> >> > ____________
>> >> > SQLAGENT.OUT
>> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
>> >> > 8.00.2039
>> >> > (x86 unicode retail build) : Process ID
>> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
>> >> > 8.00.2039
>> >> > (x86 unicode retail build) : Process ID 396
>> >> > 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
>> >> > connection limit)
>> >> > 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version
>> >> > 3.86.1830
>> >> > 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is
>> >> > DBMSSHRN.DLL;
>> >> > Local host server is
>> >> > 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM
>> >> > detected
>> >> > 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running
>> >> > Windows
>> >> > NT
>> >> > 5.2 (3790) Service Pack 1
>> >> > 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows
>> >> > NT
>> >> > service control
>> >> > 2007-02-20 04:38:39 - + [260] Unable to start mail session (reason:
>> >> > No
>> >> > mail
>> >> > profile defined)
>> >> > 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been
>> >> > defined -
>> >> > OnIdle job schedules will have no effect
>> >> >
>> >> > ____________
>> >> > SQLAGENT.1
>> >> > 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 -
>> >> > 8.00.2039
>> >> > (Intel X86)
>> >> > May 3 2005 23:18:38
>> >> > Copyright (c) 1988-2003 Microsoft Corporation
>> >> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>> >> >
>> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
>> >> > Corporation.
>> >> > 2007-02-20 04:36:59.00 server All rights reserved.
>> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
>> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
>> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
>> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
>> >> > class
>> >> > 'normal'(2 CPUs detected).
>> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread
>> >> > mode
>> >> > processing.
>> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation.
>> >> > [2500]
>> >> > Lock
>> >> > Blocks, [5000] Lock Owner Blocks.
>> >> > 2007-02-20 04:36:59.10 server Attempting to initialize
>> >> > Distributed
>> >> > Transaction Coordinator.
>> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
>> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
>> >> > '8.0.2039'.
>> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
>> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
>> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> > 192.168.1.50:
>> >> > 1433.
>> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> > 64.27.15.116:
>> >> > 1433.
>> >> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
>> >> > 1433.
>> >> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
>> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
>> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
>> >> > Memory,
>> >> > Named Pipes.
>> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
>> >> > connections
>> >> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
>> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
>> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
>> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
>> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
>> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
>> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
>> >> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
>> >> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
>> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
>> >> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
>> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
>> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
>> >> > 2007-02-20 04:37:01.29 spid14 Starting up database
>> >> > 'SWFPortalDev'.
>> >> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
>> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
>> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task
>> >> > is
>> >> > created.
>> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
>> >> > '2000.80.2039'
>> >> > to execute extended stored procedure 'xp_qv'.
>> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
>> >> > '2000.80.2039'
>> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
>> >> >
>> >> > ____________
>> >> > ERRORLOG
>> >> >
>> >> > 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 -
>> >> > 8.00.2039
>> >> > (Intel X86)
>> >> > May 3 2005 23:18:38
>> >> > Copyright (c) 1988-2003 Microsoft Corporation
>> >> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>> >> >
>> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
>> >> > Corporation.
>> >> > 2007-02-20 04:36:59.00 server All rights reserved.
>> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
>> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
>> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
>> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
>> >> > class
>> >> > 'normal'(2 CPUs detected).
>> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread
>> >> > mode
>> >> > processing.
>> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation.
>> >> > [2500]
>> >> > Lock
>> >> > Blocks, [5000] Lock Owner Blocks.
>> >> > 2007-02-20 04:36:59.10 server Attempting to initialize
>> >> > Distributed
>> >> > Transaction Coordinator.
>> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
>> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
>> >> > '8.0.2039'.
>> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
>> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
>> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> > 192.168.1.50:
>> >> > 1433.
>> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> > 64.27.15.116:
>> >> > 1433.
>> >> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
>> >> > 1433.
>> >> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
>> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
>> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
>> >> > Memory,
>> >> > Named Pipes.
>> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
>> >> > connections
>> >> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
>> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
>> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
>> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
>> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
>> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
>> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
>> >> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
>> >> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
>> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
>> >> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
>> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
>> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
>> >> > 2007-02-20 04:37:01.29 spid14 Starting up database
>> >> > 'SWFPortalDev'.
>> >> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
>> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
>> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task
>> >> > is
>> >> > created.
>> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
>> >> > '2000.80.2039'
>> >> > to execute extended stored procedure 'xp_qv'.
>> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
>> >> > '2000.80.2039'
>> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
>> >> >
>> >> > --
>> >> > Mark A. Lutz (aka Eggbert)
>> >> >
>> >> >
>> >> > "Uri Dimant" wrote:
>> >> >
>> >> >> Hi
>> >> >> Can open the SQL Server errorlog file in notepad to see if you have
>> >> >> additional information?
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> >> >> news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
>> >> >> > Event Type: Error
>> >> >> > Event Source: MSSQLSERVER
>> >> >> > Event Category: (2)
>> >> >> > Event ID: 17052
>> >> >> > Date: 2/20/2007
>> >> >> > Time: 4:38:39 AM
>> >> >> > User: N/A
>> >> >> > Computer: LEESQL
>> >> >> > Description:
>> >> >> > SQLServerAgent Monitor: SQLServerAgent has terminated
>> >> >> > unexpectedly.
>> >> >> >
>> >> >> > For more information, see Help and Support Center at
>> >> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >> > Data:
>> >> >> > 0000: a8 01 00 00 0a 00 00 00 ¨......
>> >> >> > 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
>> >> >> > 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
>> >> >> > 0018: 00 00 0e 00 00 00 6d 00 .....m.
>> >> >> > 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
>> >> >> > 0028: 72 00 00 00 r...
>> >> >> >
>> >> >> > Everytime I try to run a job in sql server agent it shuts down
>> >> >> > the
>> >> >> > agent.
>> >> >> > None of the files in the log directory have any details about the
>> >> >> > shutdown.
>> >> >> > This is driving me nuts. I have checked and rechecked permissions
>> >> >> > and
>> >> >> > even
>> >> >> > created a new login for the sql server and the agent to use.
>> >> >> > Still
>> >> >> > the
>> >> >> > same
>> >> >> > thing. Since I am getting no error logs I am totally lost as to
>> >> >> > where
>> >> >> > to
>> >> >> > look
>> >> >> > for information. I am also not finding anything about this when I
>> >> >> > google
>> >> >> > for
>> >> >> > it. Any help anyone could give would be appreciated.
>> >> >> > --
>> >> >> > Mark A. Lutz (aka Eggbert)
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||Did you happen on an answer in your situation yet?
--
Mark A. Lutz (aka Eggbert)
"Geoff N. Hiten" wrote:
> Thanks.
> I am seeing the exact same thing at a client after a maintenance window
> where updates were applied. I suspect an interaction between an update and
> the SQL agent, but am having some difficulty proving it. Thanks for the
> details on your configuration. I will let you know if I find anything on my
> end.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> news:E76F1FDD-5BEC-4B98-9A19-5AEBAAEA4214@.microsoft.com...
> > In my setup we have 4 servers that are colocated with a web hosting
> > service
> > so I do not have direct contact with them. The servers are not in an
> > Active
> > Directory Domain Structure and each opperates independantly. The server in
> > question is my SQL server only. Each of my servers have two network cards.
> > One card is connected to the internet and the other card is connected to
> > an
> > internal only router. The SQL server is setup to only respond to the
> > internal
> > cart and port. The account running the SQL Server and SQL Agent is the a
> > local account for the SQL Server box.
> > The last time one of my jobs ran sucsesfully was 2/6/07. It does not
> > appear
> > that MS07-009 has been applied. The way I checked was to go out to
> > windowsupdate.microsoft.com and used the View your Update History option.
> >
> > Again this is the oddest thing I have seen and I cant find a reason for
> > it.
> > As I mentioned in another post wether I try to run a job manually or let
> > agent run it at a specific time, as soon as the job starts Agent shuts
> > down
> > and restarts. There are no the last entry in the log is that the job was
> > requested to run i.e.
> > 2007-02-21 08:57:58 - ? [177] Job SWFHomes Listings Alert has been
> > requested
> > to run by User LEESQL\Mark
> >
> > The System Event viewer records "The SQLSERVERAGENT service terminated
> > unexpectedly." and that the Agent has restarted. There are no other log
> > entries anywhere.
> >
> > --
> > Mark A. Lutz (aka Eggbert)
> >
> >
> > "Geoff N. Hiten" wrote:
> >
> >> Check your system and see if you have MS07-009 applied (KB 927779). This
> >> is
> >> a windows update security patch released ths month.
> >>
> >> Is your system in a resource domain that is called by users in another
> >> domain?
> >>
> >> --
> >> Geoff N. Hiten
> >> Senior Database Administrator
> >> Microsoft SQL Server MVP
> >>
> >>
> >>
> >>
> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> >> news:B96458B0-B21A-4017-A509-3F9FEF7372D3@.microsoft.com...
> >> > 1.
> >> > Microsoft SQL Server 2000 - 8.00.2039
> >> > (Intel X86)
> >> > May 3 2005 23:18:38
> >> > Copyright (c) 1988-2003 Microsoft Corporation
> >> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> >> >
> >> > 2.
> >> > No it is not clustered.
> >> >
> >> > 3.
> >> > Yes I have tried to run both the SQL Server and Agent under the local
> >> > system
> >> > account
> >> >
> >> > 4.
> >> > I have checked all logs and nothing is recorded when Agent goes down
> >> > with
> >> > the exception of what I have already stated.
> >> > --
> >> > Mark A. Lutz (aka Eggbert)
> >> >
> >> >
> >> > "Uri Dimant" wrote:
> >> >
> >> >> Hi
> >> >> 1) Is it SQL Server 7.0/2000/2005?
> >> >> 2) Is it clustered?
> >> >> http://www.tutorials-ne.com/clustering/Cannot-create-14238/
> >> >> 3) Have you tried to set LocalSystem account to the service?
> >> >> 4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
> >> >>
> >> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> >> >> news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
> >> >> > As I mentioned I had done that and not found anything informative
> >> >> > but I
> >> >> > will
> >> >> > paste them here:
> >> >> >
> >> >> >
> >> >> > ____________
> >> >> > SQLAGENT.OUT
> >> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
> >> >> > 8.00.2039
> >> >> > (x86 unicode retail build) : Process ID
> >> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
> >> >> > 8.00.2039
> >> >> > (x86 unicode retail build) : Process ID 396
> >> >> > 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
> >> >> > connection limit)
> >> >> > 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version
> >> >> > 3.86.1830
> >> >> > 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is
> >> >> > DBMSSHRN.DLL;
> >> >> > Local host server is
> >> >> > 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM
> >> >> > detected
> >> >> > 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running
> >> >> > Windows
> >> >> > NT
> >> >> > 5.2 (3790) Service Pack 1
> >> >> > 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows
> >> >> > NT
> >> >> > service control
> >> >> > 2007-02-20 04:38:39 - + [260] Unable to start mail session (reason:
> >> >> > No
> >> >> > mail
> >> >> > profile defined)
> >> >> > 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been
> >> >> > defined -
> >> >> > OnIdle job schedules will have no effect
> >> >> >
> >> >> > ____________
> >> >> > SQLAGENT.1
> >> >> > 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 -
> >> >> > 8.00.2039
> >> >> > (Intel X86)
> >> >> > May 3 2005 23:18:38
> >> >> > Copyright (c) 1988-2003 Microsoft Corporation
> >> >> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> >> >> >
> >> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> >> >> > Corporation.
> >> >> > 2007-02-20 04:36:59.00 server All rights reserved.
> >> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> >> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> >> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> >> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
> >> >> > class
> >> >> > 'normal'(2 CPUs detected).
> >> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread
> >> >> > mode
> >> >> > processing.
> >> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation.
> >> >> > [2500]
> >> >> > Lock
> >> >> > Blocks, [5000] Lock Owner Blocks.
> >> >> > 2007-02-20 04:36:59.10 server Attempting to initialize
> >> >> > Distributed
> >> >> > Transaction Coordinator.
> >> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> >> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
> >> >> > '8.0.2039'.
> >> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> >> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
> >> >> > 192.168.1.50:
> >> >> > 1433.
> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
> >> >> > 64.27.15.116:
> >> >> > 1433.
> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
> >> >> > 1433.
> >> >> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> >> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> >> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> >> >> > Memory,
> >> >> > Named Pipes.
> >> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
> >> >> > connections
> >> >> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> >> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> >> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> >> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> >> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> >> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> >> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> >> >> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> >> >> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> >> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> >> >> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> >> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> >> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> >> >> > 2007-02-20 04:37:01.29 spid14 Starting up database
> >> >> > 'SWFPortalDev'.
> >> >> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> >> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
> >> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task
> >> >> > is
> >> >> > created.
> >> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> >> >> > '2000.80.2039'
> >> >> > to execute extended stored procedure 'xp_qv'.
> >> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
> >> >> > '2000.80.2039'
> >> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
> >> >> >
> >> >> > ____________
> >> >> > ERRORLOG
> >> >> >
> >> >> > 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 -
> >> >> > 8.00.2039
> >> >> > (Intel X86)
> >> >> > May 3 2005 23:18:38
> >> >> > Copyright (c) 1988-2003 Microsoft Corporation
> >> >> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> >> >> >
> >> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> >> >> > Corporation.
> >> >> > 2007-02-20 04:36:59.00 server All rights reserved.
> >> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> >> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> >> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> >> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
> >> >> > class
> >> >> > 'normal'(2 CPUs detected).
> >> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread
> >> >> > mode
> >> >> > processing.
> >> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation.
> >> >> > [2500]
> >> >> > Lock
> >> >> > Blocks, [5000] Lock Owner Blocks.
> >> >> > 2007-02-20 04:36:59.10 server Attempting to initialize
> >> >> > Distributed
> >> >> > Transaction Coordinator.
> >> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> >> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
> >> >> > '8.0.2039'.
> >> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> >> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
> >> >> > 192.168.1.50:
> >> >> > 1433.
> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
> >> >> > 64.27.15.116:
> >> >> > 1433.
> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
> >> >> > 1433.
> >> >> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> >> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> >> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> >> >> > Memory,
> >> >> > Named Pipes.
> >> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
> >> >> > connections
> >> >> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> >> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> >> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> >> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> >> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> >> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> >> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> >> >> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> >> >> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> >> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> >> >> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> >> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> >> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> >> >> > 2007-02-20 04:37:01.29 spid14 Starting up database
> >> >> > 'SWFPortalDev'.
> >> >> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> >> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
> >> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task
> >> >> > is
> >> >> > created.
> >> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> >> >> > '2000.80.2039'
> >> >> > to execute extended stored procedure 'xp_qv'.
> >> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
> >> >> > '2000.80.2039'
> >> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
> >> >> >
> >> >> > --
> >> >> > Mark A. Lutz (aka Eggbert)
> >> >> >
> >> >> >|||Not yet. The client rebuilt the system before I could get into it and do a
good in-depth analysis.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:DC3A1A40-43D3-4BD5-937D-80FCCF379BFA@.microsoft.com...
> Did you happen on an answer in your situation yet?
> --
> Mark A. Lutz (aka Eggbert)
>
> "Geoff N. Hiten" wrote:
>> Thanks.
>> I am seeing the exact same thing at a client after a maintenance window
>> where updates were applied. I suspect an interaction between an update
>> and
>> the SQL agent, but am having some difficulty proving it. Thanks for the
>> details on your configuration. I will let you know if I find anything on
>> my
>> end.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> news:E76F1FDD-5BEC-4B98-9A19-5AEBAAEA4214@.microsoft.com...
>> > In my setup we have 4 servers that are colocated with a web hosting
>> > service
>> > so I do not have direct contact with them. The servers are not in an
>> > Active
>> > Directory Domain Structure and each opperates independantly. The server
>> > in
>> > question is my SQL server only. Each of my servers have two network
>> > cards.
>> > One card is connected to the internet and the other card is connected
>> > to
>> > an
>> > internal only router. The SQL server is setup to only respond to the
>> > internal
>> > cart and port. The account running the SQL Server and SQL Agent is the
>> > a
>> > local account for the SQL Server box.
>> > The last time one of my jobs ran sucsesfully was 2/6/07. It does not
>> > appear
>> > that MS07-009 has been applied. The way I checked was to go out to
>> > windowsupdate.microsoft.com and used the View your Update History
>> > option.
>> >
>> > Again this is the oddest thing I have seen and I cant find a reason for
>> > it.
>> > As I mentioned in another post wether I try to run a job manually or
>> > let
>> > agent run it at a specific time, as soon as the job starts Agent shuts
>> > down
>> > and restarts. There are no the last entry in the log is that the job
>> > was
>> > requested to run i.e.
>> > 2007-02-21 08:57:58 - ? [177] Job SWFHomes Listings Alert has been
>> > requested
>> > to run by User LEESQL\Mark
>> >
>> > The System Event viewer records "The SQLSERVERAGENT service terminated
>> > unexpectedly." and that the Agent has restarted. There are no other log
>> > entries anywhere.
>> >
>> > --
>> > Mark A. Lutz (aka Eggbert)
>> >
>> >
>> > "Geoff N. Hiten" wrote:
>> >
>> >> Check your system and see if you have MS07-009 applied (KB 927779).
>> >> This
>> >> is
>> >> a windows update security patch released ths month.
>> >>
>> >> Is your system in a resource domain that is called by users in another
>> >> domain?
>> >>
>> >> --
>> >> Geoff N. Hiten
>> >> Senior Database Administrator
>> >> Microsoft SQL Server MVP
>> >>
>> >>
>> >>
>> >>
>> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> >> news:B96458B0-B21A-4017-A509-3F9FEF7372D3@.microsoft.com...
>> >> > 1.
>> >> > Microsoft SQL Server 2000 - 8.00.2039
>> >> > (Intel X86)
>> >> > May 3 2005 23:18:38
>> >> > Copyright (c) 1988-2003 Microsoft Corporation
>> >> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>> >> >
>> >> > 2.
>> >> > No it is not clustered.
>> >> >
>> >> > 3.
>> >> > Yes I have tried to run both the SQL Server and Agent under the
>> >> > local
>> >> > system
>> >> > account
>> >> >
>> >> > 4.
>> >> > I have checked all logs and nothing is recorded when Agent goes down
>> >> > with
>> >> > the exception of what I have already stated.
>> >> > --
>> >> > Mark A. Lutz (aka Eggbert)
>> >> >
>> >> >
>> >> > "Uri Dimant" wrote:
>> >> >
>> >> >> Hi
>> >> >> 1) Is it SQL Server 7.0/2000/2005?
>> >> >> 2) Is it clustered?
>> >> >> http://www.tutorials-ne.com/clustering/Cannot-create-14238/
>> >> >> 3) Have you tried to set LocalSystem account to the service?
>> >> >> 4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
>> >> >>
>> >> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> >> >> news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
>> >> >> > As I mentioned I had done that and not found anything informative
>> >> >> > but I
>> >> >> > will
>> >> >> > paste them here:
>> >> >> >
>> >> >> >
>> >> >> > ____________
>> >> >> > SQLAGENT.OUT
>> >> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
>> >> >> > 8.00.2039
>> >> >> > (x86 unicode retail build) : Process ID
>> >> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
>> >> >> > 8.00.2039
>> >> >> > (x86 unicode retail build) : Process ID 396
>> >> >> > 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039
>> >> >> > (0
>> >> >> > connection limit)
>> >> >> > 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version
>> >> >> > 3.86.1830
>> >> >> > 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is
>> >> >> > DBMSSHRN.DLL;
>> >> >> > Local host server is
>> >> >> > 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM
>> >> >> > detected
>> >> >> > 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running
>> >> >> > Windows
>> >> >> > NT
>> >> >> > 5.2 (3790) Service Pack 1
>> >> >> > 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under
>> >> >> > Windows
>> >> >> > NT
>> >> >> > service control
>> >> >> > 2007-02-20 04:38:39 - + [260] Unable to start mail session
>> >> >> > (reason:
>> >> >> > No
>> >> >> > mail
>> >> >> > profile defined)
>> >> >> > 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been
>> >> >> > defined -
>> >> >> > OnIdle job schedules will have no effect
>> >> >> >
>> >> >> > ____________
>> >> >> > SQLAGENT.1
>> >> >> > 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 -
>> >> >> > 8.00.2039
>> >> >> > (Intel X86)
>> >> >> > May 3 2005 23:18:38
>> >> >> > Copyright (c) 1988-2003 Microsoft Corporation
>> >> >> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>> >> >> >
>> >> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002
>> >> >> > Microsoft
>> >> >> > Corporation.
>> >> >> > 2007-02-20 04:36:59.00 server All rights reserved.
>> >> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
>> >> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in
>> >> >> > file
>> >> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
>> >> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at
>> >> >> > priority
>> >> >> > class
>> >> >> > 'normal'(2 CPUs detected).
>> >> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread
>> >> >> > mode
>> >> >> > processing.
>> >> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation.
>> >> >> > [2500]
>> >> >> > Lock
>> >> >> > Blocks, [5000] Lock Owner Blocks.
>> >> >> > 2007-02-20 04:36:59.10 server Attempting to initialize
>> >> >> > Distributed
>> >> >> > Transaction Coordinator.
>> >> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
>> >> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
>> >> >> > '8.0.2039'.
>> >> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
>> >> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
>> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> >> > 192.168.1.50:
>> >> >> > 1433.
>> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> >> > 64.27.15.116:
>> >> >> > 1433.
>> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> >> > 127.0.0.1:
>> >> >> > 1433.
>> >> >> > 2007-02-20 04:37:00.50 spid10 Starting up database
>> >> >> > 'Northwind'.
>> >> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
>> >> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP,
>> >> >> > Shared
>> >> >> > Memory,
>> >> >> > Named Pipes.
>> >> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
>> >> >> > connections
>> >> >> > 2007-02-20 04:37:00.51 spid13 Starting up database
>> >> >> > 'SWFLinker'.
>> >> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
>> >> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
>> >> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
>> >> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
>> >> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
>> >> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
>> >> >> > 2007-02-20 04:37:00.78 spid9 Starting up database
>> >> >> > 'DNNTransfer'.
>> >> >> > 2007-02-20 04:37:00.78 spid10 Starting up database
>> >> >> > 'OpenRealty'.
>> >> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
>> >> >> > 2007-02-20 04:37:00.95 spid15 Starting up database
>> >> >> > 'SWFPortal'.
>> >> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
>> >> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
>> >> >> > 2007-02-20 04:37:01.29 spid14 Starting up database
>> >> >> > 'SWFPortalDev'.
>> >> >> > 2007-02-20 04:37:01.42 spid13 Starting up database
>> >> >> > 'TimeTracker'.
>> >> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
>> >> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection
>> >> >> > task
>> >> >> > is
>> >> >> > created.
>> >> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
>> >> >> > '2000.80.2039'
>> >> >> > to execute extended stored procedure 'xp_qv'.
>> >> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
>> >> >> > '2000.80.2039'
>> >> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
>> >> >> >
>> >> >> > ____________
>> >> >> > ERRORLOG
>> >> >> >
>> >> >> > 2007-02-20 04:36:59.00 server Microsoft SQL Server 2000 -
>> >> >> > 8.00.2039
>> >> >> > (Intel X86)
>> >> >> > May 3 2005 23:18:38
>> >> >> > Copyright (c) 1988-2003 Microsoft Corporation
>> >> >> > Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>> >> >> >
>> >> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002
>> >> >> > Microsoft
>> >> >> > Corporation.
>> >> >> > 2007-02-20 04:36:59.00 server All rights reserved.
>> >> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
>> >> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in
>> >> >> > file
>> >> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
>> >> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at
>> >> >> > priority
>> >> >> > class
>> >> >> > 'normal'(2 CPUs detected).
>> >> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread
>> >> >> > mode
>> >> >> > processing.
>> >> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation.
>> >> >> > [2500]
>> >> >> > Lock
>> >> >> > Blocks, [5000] Lock Owner Blocks.
>> >> >> > 2007-02-20 04:36:59.10 server Attempting to initialize
>> >> >> > Distributed
>> >> >> > Transaction Coordinator.
>> >> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
>> >> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
>> >> >> > '8.0.2039'.
>> >> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
>> >> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
>> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> >> > 192.168.1.50:
>> >> >> > 1433.
>> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> >> > 64.27.15.116:
>> >> >> > 1433.
>> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> >> > 127.0.0.1:
>> >> >> > 1433.
>> >> >> > 2007-02-20 04:37:00.50 spid10 Starting up database
>> >> >> > 'Northwind'.
>> >> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
>> >> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP,
>> >> >> > Shared
>> >> >> > Memory,
>> >> >> > Named Pipes.
>> >> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
>> >> >> > connections
>> >> >> > 2007-02-20 04:37:00.51 spid13 Starting up database
>> >> >> > 'SWFLinker'.
>> >> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
>> >> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
>> >> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
>> >> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
>> >> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
>> >> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
>> >> >> > 2007-02-20 04:37:00.78 spid9 Starting up database
>> >> >> > 'DNNTransfer'.
>> >> >> > 2007-02-20 04:37:00.78 spid10 Starting up database
>> >> >> > 'OpenRealty'.
>> >> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
>> >> >> > 2007-02-20 04:37:00.95 spid15 Starting up database
>> >> >> > 'SWFPortal'.
>> >> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
>> >> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
>> >> >> > 2007-02-20 04:37:01.29 spid14 Starting up database
>> >> >> > 'SWFPortalDev'.
>> >> >> > 2007-02-20 04:37:01.42 spid13 Starting up database
>> >> >> > 'TimeTracker'.
>> >> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
>> >> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection
>> >> >> > task
>> >> >> > is
>> >> >> > created.
>> >> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
>> >> >> > '2000.80.2039'
>> >> >> > to execute extended stored procedure 'xp_qv'.
>> >> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
>> >> >> > '2000.80.2039'
>> >> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
>> >> >> >
>> >> >> > --
>> >> >> > Mark A. Lutz (aka Eggbert)
>> >> >> >
>> >> >> >