April 11, 2011 at 10:08 pm
Hello,
Our server shut down unexpectedly and everything seemed to restart correctly
except for the SQL Server Agent. I have it set to restart automatically, but
it did not restart. I see no error messages in any of the logs. All I see is:
SQLServerAgent terminated (normally)
Message
[LOG] Exception 5 caught at line 228 of file t:\yukon\sql\komodo\src\core\sqlagent\src\autostrt.cpp. SQLServerAgent initiating self-termination
So that looks correct in shutting down, but then I see nothing about it
attempting to restart. I just did a right click on SQL Server Agent in
Management Studio and manually restarted the service...but still not work.
Please help me.......
Sachin:-)
April 11, 2011 at 10:31 pm
kumar.sachu08 (4/11/2011)
. I just did a right click on SQL Server Agent inManagement Studio and manually restarted the service...but still not work.
Did you try restarting it from Configuration Manager or from within Services?
Leo
Leo
Nothing in life is ever so complicated that with a little work it can't be made more complicated.
April 11, 2011 at 11:46 pm
Thanks for your reply......yes i have tried from Configuration Manager or within Services.
when i restart agent service with Configuration Manager or within Services.msc ....then it's started successfully.....but again & again after 1 second it's automatically go for disable mode....
So, I can't understand why this is happening......
Sachin.
April 12, 2011 at 3:24 am
can anyone suggest me on this issue.....?
My sql server agent service is not running.
Sachin
April 12, 2011 at 3:38 am
Sachin
Please will you post the contents of your latest SQLAGENT.OUT file?
Thanks
John
April 12, 2011 at 3:43 am
Hi John, Please find......
2011-04-12 10:19:53.57 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Evaluation Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2011-04-12 10:19:53.57 Server (c) 2005 Microsoft Corporation.
2011-04-12 10:19:53.57 Server All rights reserved.
2011-04-12 10:19:53.57 Server Server process ID is 1388.
2011-04-12 10:19:53.57 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2011-04-12 10:19:53.57 Server This instance of SQL Server last reported using a process ID of 3964 at 4/12/2011 10:12:35 AM (local) 4/12/2011 4:42:35 AM (UTC). This is an informational message only; no user action is required.
2011-04-12 10:19:53.57 Server Registry startup parameters:
2011-04-12 10:19:53.57 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2011-04-12 10:19:53.57 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2011-04-12 10:19:53.57 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2011-04-12 10:19:53.65 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-04-12 10:19:53.65 Server Detected 2 CPUs. This is an informational message; no user action is required.
2011-04-12 10:19:53.85 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2011-04-12 10:19:53.98 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2011-04-12 10:19:55.51 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2011-04-12 10:19:55.51 Server Database Mirroring Transport is disabled in the endpoint configuration.
2011-04-12 10:19:55.57 spid3s Starting up database 'master'.
2011-04-12 10:19:55.84 spid3s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2011-04-12 10:19:56.34 spid3s SQL Trace ID 1 was started by login "sa".
2011-04-12 10:19:56.45 spid3s Starting up database 'mssqlsystemresource'.
2011-04-12 10:19:56.71 spid3s Server name is 'JTG-8CE295D2BF8'. This is an informational message only. No user action is required.
2011-04-12 10:19:56.73 spid8s Starting up database 'model'.
2011-04-12 10:19:57.31 Server A self-generated certificate was successfully loaded for encryption.
2011-04-12 10:19:57.31 Server Server is listening on [ 'any' <ipv4> 1433].
2011-04-12 10:19:57.31 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2011-04-12 10:19:57.31 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2011-04-12 10:19:57.32 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2011-04-12 10:19:57.32 Server Dedicated admin connection support was established for listening locally on port 1434.
2011-04-12 10:19:57.32 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2011-04-12 10:19:57.32 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2011-04-12 10:19:57.39 spid12s Starting up database 'ReportServer'.
2011-04-12 10:19:57.39 spid14s Starting up database 'ReportServerTempDB'.
2011-04-12 10:19:57.39 spid13s Starting up database 'msdb'.
2011-04-12 10:19:57.39 spid16s Starting up database 'DBA'.
2011-04-12 10:19:57.39 spid18s Starting up database 'pubs'.
2011-04-12 10:19:57.39 spid19s Starting up database 'Northwind'.
2011-04-12 10:19:59.36 spid8s Clearing tempdb database.
2011-04-12 10:19:59.70 spid15s Analysis of database 'Operations' (7) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
2011-04-12 10:20:00.46 spid12s Starting up database 'Library'.
2011-04-12 10:20:00.49 spid18s Starting up database 'AdventureWorks'.
2011-04-12 10:20:00.81 spid14s Starting up database 'Partitiontest'.
2011-04-12 10:20:00.87 spid13s Starting up database 'DB'.
2011-04-12 10:20:06.28 spid8s Starting up database 'tempdb'.
2011-04-12 10:20:06.71 spid12s The Service Broker protocol transport is disabled or not configured.
2011-04-12 10:20:06.71 spid12s The Database Mirroring protocol transport is disabled or not configured.
2011-04-12 10:20:06.85 spid12s Service Broker manager has started.
2011-04-12 10:20:08.62 spid17s Analysis of database 'ServerMonitor' (9) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
2011-04-12 10:20:08.87 spid3s Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
2011-04-12 10:20:08.87 spid3s Recovery is complete. This is an informational message only. No user action is required.
2011-04-12 10:20:08.92 spid3s Launched startup procedure 'StartSQLAgent'.
2011-04-12 10:20:09.06 spid54s SQL Server blocked access to procedure 'sys.xp_cmdshell' of component 'xp_cmdshell' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'xp_cmdshell' by using sp_configure. For more information about enabling 'xp_cmdshell', see "Surface Area Configuration" in SQL Server Books Online.
2011-04-12 10:20:09.06 spid54s Error: 15281, Severity: 16, State: 1.
2011-04-12 10:20:09.06 spid54s SQL Server blocked access to procedure 'sys.xp_cmdshell' of component 'xp_cmdshell' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'xp_cmdshell' by using sp_configure. For more information about enabling 'xp_cmdshell', see "Surface Area Configuration" in SQL Server Books Online.
2011-04-12 10:20:09.90 spid54 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-04-12 10:20:10.23 spid54 Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-04-12 10:20:10.24 spid54 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2011-04-12 10:20:11.28 spid54 Using 'xpsqlbot.dll' version '2005.90.1399' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
2011-04-12 10:20:11.74 spid54 Using 'xpstar90.dll' version '2005.90.1399' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2011-04-12 10:20:11.87 spid54 Using 'xplog70.dll' version '2005.90.1399' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2011-04-12 10:20:16.93 spid54 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-04-12 10:20:16.93 spid54 Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
2011-04-12 10:20:16.95 spid54 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2011-04-12 14:49:27.29 spid54 DBCC TRACEON 3604, server process ID (SPID) 54. This is an informational message only; no user action is required.
2011-04-12 14:49:27.40 spid54 DBCC TRACEOFF 3604, server process ID (SPID) 54. This is an informational message only; no user action is required.
2011-04-12 14:49:51.49 Backup Database backed up. Database: Partitiontest, creation date(time): 2011/04/07(16:41:21), pages dumped: 211, first LSN: 20:362:38, last LSN: 20:380:1, number of dump devices: 1, device information: (FILE=3, TYPE=DISK: {'C:\Partitiontest.bak'}). This is an informational message only. No user action is required.
---
Sachin.
April 12, 2011 at 3:46 am
Sachin
That's the errorlog file, isn't it? I need SQLAGENT.OUT.
Thanks
John
April 12, 2011 at 3:47 am
Hi John...Please fond SQLAGENT.OUT details....
2011-04-12 10:20:04 - ? [393] Waiting for SQL Server to recover databases...
2011-04-12 10:20:11 - ? [100] Microsoft SQLServerAgent version 9.00.1399.06 (x86 unicode retail build) : Process ID 2116
2011-04-12 10:20:11 - ? [101] SQL Server JTG-8CE295D2BF8 version 9.00.1399 (0 connection limit)
2011-04-12 10:20:11 - ? [102] SQL Server ODBC driver version 9.00.1399
2011-04-12 10:20:11 - ? [103] NetLib being used by driver is DBNETLIB.DLL; Local host server is
2011-04-12 10:20:11 - ? [310] 2 processor(s) and 960 MB RAM detected
2011-04-12 10:20:11 - ? [339] Local computer is JTG-8CE295D2BF8 running Windows NT 5.2 (3790) Service Pack 2
2011-04-12 10:20:12 - ? [432] There are 11 subsystems in the subsystems cache
2011-04-12 10:20:12 - ! [364] The Messenger service has not been started - NetSend notifications will not be sent
2011-04-12 10:20:12 - ? [129] SQLSERVERAGENT starting under Windows NT service control
2011-04-12 10:20:12 - + [260] Unable to start mail session (reason: No mail profile defined)
2011-04-12 10:20:12 - + [396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
2011-04-12 10:20:15 - ! [LOG] Exception 5 caught at line 228 of file t:\yukon\sql\komodo\src\core\sqlagent\src\autostrt.cpp. SQLServerAgent initiating self-termination
2011-04-12 10:20:17 - ? [098] SQLServerAgent terminated (normally)
----
Sachin.
April 12, 2011 at 3:55 am
Sachin
I would concentrate on that line you mentioned in your original post. Have you searched the internet for it? What have you got installed on your T drive?
John
April 12, 2011 at 4:03 am
Hi John,
I don't know why below message is comming in SQLAGENT.OUT
2011-04-12 10:20:15 - ! [LOG] Exception 5 caught at line 228 of file t:\yukon\sql\komodo\src\core\sqlagent\src\autostrt.cpp. SQLServerAgent initiating self-termination
While I don't have any T drive in my Local PC.
I have only c: and d: drive.
Sachin.:w00t:
April 12, 2011 at 4:06 am
Right. I'm not doing all your work for you. Have you searched for that error message? What else do you have installed on your server?
John
April 13, 2011 at 1:56 am
Hi John,
sorry my reply i dont have any idea about SQL AGENT .out please help me on this ... i need learn it.
What is SQLAGENT.OUT where can we find.
My answer is :
in error log it is availble or can you tel me exact location
Tx
April 13, 2011 at 3:09 am
Sorry, but are you the original poster logging in under a different name? If you're not, please start a new thread. If you are, you've confused me, because you've already provided the contents of the log.
John
April 13, 2011 at 3:16 am
Hi John...
I don't know who is Tx.
I am Sachin.
April 13, 2011 at 3:18 am
but john still i am not able to solve my problem itself.
if u don't mind kindly help me regarding my problem.
sachin.
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply