dbaspot
Tags Register FAQ Calendar Search Today's Posts Mark Forums Read

MSSQLSERVER Error 17052 - ms-sqlserver

This is a discussion on MSSQLSERVER Error 17052 - ms-sqlserver ; 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: ...


Home > Database Forum > Microsoft SQL Server > ms-sqlserver > MSSQLSERVER Error 17052

Reply

 

LinkBack Thread Tools Display Modes
  #1  
Old 02-20-2007, 05:59 AM
Database Bot
 
Join Date: Sep 2009
Posts: 1,236,254
Database Administrator is on a distinguished road
Default 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)
Reply With Quote
  #2  
Old 02-20-2007, 06:12 AM
Database Bot
 
Join Date: Sep 2009
Posts: 1,236,254
Database Administrator is on a distinguished road
Default Re: MSSQLSERVER Error 17052

Hi
Can open the SQL Server errorlog file in notepad to see if you have
additional information?





"Eggbert" 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)



Reply With Quote
  #3  
Old 02-20-2007, 06:12 AM
Database Bot
 
Join Date: Sep 2009
Posts: 1,236,254
Database Administrator is on a distinguished road
Default Re: MSSQLSERVER Error 17052

Hi
Can open the SQL Server errorlog file in notepad to see if you have
additional information?





"Eggbert" 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)



Reply With Quote
  #4  
Old 02-20-2007, 09:37 AM
Database Bot
 
Join Date: Sep 2009
Posts: 1,236,254
Database Administrator is on a distinguished road
Default Re: MSSQLSERVER Error 17052

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

>
>
>

Reply With Quote
  #5  
Old 02-20-2007, 09:37 AM
Database Bot
 
Join Date: Sep 2009
Posts: 1,236,254
Database Administrator is on a distinguished road
Default Re: MSSQLSERVER Error 17052

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

>
>
>

Reply With Quote
  #6  
Old 02-20-2007, 09:46 AM
Database Bot
 
Join Date: Sep 2009
Posts: 1,236,254
Database Administrator is on a distinguished road
Default Re: MSSQLSERVER Error 17052

Hi
1) Is it SQL Server 7.0/2000/2005?
2) Is it clustered?
http://www.tutorials-ne.com/clusteri...-create-14238/
3) Have you tried to set LocalSystem account to the service?
4) http://msdn2.microsoft.com/en-us/lib...7(sql.80).aspx

"Eggbert" 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" 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)

>>
>>
>>



Reply With Quote
  #7  
Old 02-20-2007, 09:46 AM
Database Bot
 
Join Date: Sep 2009
Posts: 1,236,254
Database Administrator is on a distinguished road
Default Re: MSSQLSERVER Error 17052

Hi
1) Is it SQL Server 7.0/2000/2005?
2) Is it clustered?
http://www.tutorials-ne.com/clusteri...-create-14238/
3) Have you tried to set LocalSystem account to the service?
4) http://msdn2.microsoft.com/en-us/lib...7(sql.80).aspx

"Eggbert" 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" 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)

>>
>>
>>



Reply With Quote
  #8  
Old 02-20-2007, 01:31 PM
Database Bot
 
Join Date: Sep 2009
Posts: 1,236,254
Database Administrator is on a distinguished road
Default Re: MSSQLSERVER Error 17052

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/clusteri...-create-14238/
> 3) Have you tried to set LocalSystem account to the service?
> 4) http://msdn2.microsoft.com/en-us/lib...7(sql.80).aspx
>
> "Eggbert" 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" 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)
> >>
> >>
> >>

>
>
>

Reply With Quote
  #9  
Old 02-20-2007, 01:31 PM
Database Bot
 
Join Date: Sep 2009
Posts: 1,236,254
Database Administrator is on a distinguished road
Default Re: MSSQLSERVER Error 17052

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/clusteri...-create-14238/
> 3) Have you tried to set LocalSystem account to the service?
> 4) http://msdn2.microsoft.com/en-us/lib...7(sql.80).aspx
>
> "Eggbert" 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" 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)
> >>
> >>
> >>

>
>
>

Reply With Quote
  #10  
Old 02-20-2007, 03:36 PM
Database Bot
 
Join Date: Sep 2009
Posts: 1,236,254
Database Administrator is on a distinguished road
Default Re: MSSQLSERVER Error 17052

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" 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/clusteri...-create-14238/
>> 3) Have you tried to set LocalSystem account to the service?
>> 4) http://msdn2.microsoft.com/en-us/lib...7(sql.80).aspx
>>
>> "Eggbert" 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" 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)
>> >>
>> >>
>> >>

>>
>>
>>


Reply With Quote
Reply

Thread Tools
Display Modes



All times are GMT -4. The time now is 03:32 AM.