SQL Server Agent can't start

Hi Expert,
I have a problem when using SQL Server 2005.
I also use Windows Server 2008
My SQL Server Agent can't start.
When I try to start, I have message "The SQL Server Agent (MSSQLSERVER) service on Local Computer started and then stopped (object explorer).
Why does this problem happen?
Thanks
Regards,
Vicky Oktavianus

> 2010-08-16 15:28:21 - ! [241] Startup error: Unable to initialize error reporting system (reason: The EventLog service has not been started)
> 2010-08-16 15:28:21 - ? [098] SQLServerAgent terminated (normally)
You seem to have an issue with your machine, I suggest you check further up in the event log for problems concerning the event log.
Uploading files here is not possible, open an OSS call (component BC-DB-MSS) and ask the support for help, there you can upload the file.
Markus

Similar Messages

SQL Server Service can't start.

I was try start SQL Server Service in SQL Server Configuration Manager and it prompt out error 'The request failed or the service did not respond in a timely fashion.Consult the event log or other applicable error logs for details.'
I was try set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control ServicePipeTimeout
value to decimal 180000.
I try also change the service account to local system but it prompt WMI error.
But still failed to start the service.
Could anyone help me? Thanks in advance.

I check from event viewer it showing 30++ error
I post some error here:
Windows cannot copy file \\?\C:\Users\Default\AppData\Local\Microsoft\Windows\Temporary
Internet Files\Sqm\iesqmdata0.sqm to location \\?\C:\Users\MSSQL$SQLEXPRESS.NT Service\AppData\Local\Microsoft\Windows\Temporary Internet Files\Sqm\iesqmdata0.sqm. This error may be caused by network problems or insufficient security rights.
Windows cannot find the local profile and is logging
you on with a temporary profile. Changes you make to this profile will be lost when you log off.
Windows cannot copy file \\?\C:\Users\Default\AppData\Local\Microsoft\Windows\Temporary
Internet Files\Sqm\iesqmdata0.sqm to location \\?\C:\Users\TEMP.NT Service.001\AppData\Local\Microsoft\Windows\Temporary Internet Files\Sqm\iesqmdata0.sqm. This error may be caused by network problems or insufficient security rights.
DETAIL - Access is denied.
Windows cannot log you on because your profile cannot
be loaded. Check that you are connected to the network, and that your network is functioning correctly.
DETAIL - Only part of a ReadProcessMemory or WriteProcessMemory
request was completed.
**I
was using administrator account.

Sql Server Agent not starting automatically in failover in a clustered environment.

Hi,
We are running Sql Server 2008 R2 as a 2 node cluster in Windows 2008 R2
server. In the Sql Server Configuration manager we find that service of
the Sql Server(database engine) as got a start mode as manual being
an instance in the 2 node cluster. When the node in which the service is
running fails the the Sql Server service gets started in the other node. However
we find that the Sql Server Agent service(whose start mode is also in manual)
does not get started automatically in the other node along with the Sql Server
service.Why does the cluster service do not start Sql Server agent service as well.
Should we make the Sql Server agent service start mode to be automatic
instead of being manual as it is now? Thanking you in advance
Binny Mathew

Folks - the startup type of all clustered services should be set to manual - when you virtualize SQL Services, they are put in manual startup mode and this should not be changed. It is the cluster manager which starts the SQL and SQLAgent when a
failover happens (SQL does not start SQLAgent). If your SQLAgent doesn't start after a cluster failover, check the SQLAgent logs to see what the root cause of the problem is and rectify it. You should not change the startup type to "Automatic" -
leave it as manual
Satish Kartan www.sqlfood.com
I suspect that your clustered SQLAgent resource is currently NOT dependent on SQL resource. If not, make SQLAgent dependent on SQL resource, which will coerce SQLAgent to wait for the SQL resource to come online before it brings itselft (SQLAgent) resource
online, when a failover happens.
Satish Kartan www.sqlfood.com

Unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1

I am unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1. Log message is as follows:
Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\xplog70.dll'.
Error: 17750, Severity: 16, State: 0.
Could not load the DLL xplog70.dll, or one of the DLLs it references. Reason: (null).

Hi JFriedley,
According to your error message, there might three reasons for this issue.
xplog70.dll is corrupt, you need to check if you have any SQL Server running on same file version and same production
edition. If xplog70.dll is corrupt, you can copy it from the new server where agent is running fine to your problematic server.
Native client not installed properly. If you try applying any latest Service Pack or Cumulative Update then check if the SQL Server Agent can start, if that also doesn’t solve issue then try to reinstalling SQL Server Native client from SQL Server setup
files.
There is a similar issue about error 17750, you can review the following article.
http://blogs.lostincreativity.com/sqldba/sqlserver-error-17750-could-not-load-the-dll-xpstar90-dll/
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

Logs for sql server agent restart

Hi,
Can I get log on the sql server agent restart history of week. I mean the sql server agent has been restarted several times in last week I want to know the date and time when the sql server agent restarted in that week. Is it possible to get
the info?
Thanks in advance,
Pavan
Pavan

In addition to Uri's post, here is some more information that might help you:
SQLAGENT.OUT, the log file for SQL Agent. SQL Server Agent can maintain up to 10 Error Logs files. The currently used SQL Server Agent Error Log will be named SQLAGENT.OUT
where is the SQLAGENT.OUT file?
C:\Program Files\Microsoft SQL Server\MSSQL11.SQL2012\MSSQL\Log\
What will be when a new file create?
The old file should get a name like SQLAGENT.X and the new file get the name SQLAGENT.OUT (X is numbers 1-9)
This can help you to get more information on sql agent properties (like the location of the log file, the user that start the service and more):
EXEC msdb..sp_get_sqlagent_properties
[Personal Site] [Blog] [Facebook]

How to pass values to SQL server Agent Job which internally calls SSIS

Hi,
I have a requirement where i need to call remotely SSIS package from ASPX. After following MSDN form, I have creaed one SQL server agent job and calling that job from ASPX. I am ablt call SQL server agent job from ASPX. Only issue i am facing is: I need
to pass 2 variables from ASPX to SQL Agent job so that from Job i can map the same to SSIS Package.
I am using system SP (sp_start_job) for calling SQL server agent job as mentioned in MSDN forum.
below is the code , which i am using to call SQL serve agent job.
Code:
SqlConnection
jobConnection;
SqlCommand jobCommand;
SqlParameter jobReturnValue;
SqlParameter jobParameter;
int jobResult;
                jobConnection =
new
SqlConnection("Server=ServerName;Initial
Catalog=msdb;Integrated Security=SSPI;user id=username;Password=password");
                jobCommand =
new
SqlCommand("sp_start_job",
jobConnection);
                jobCommand.CommandType =
CommandType.StoredProcedure;
                jobReturnValue =
new
SqlParameter("@RETURN_VALUE",
SqlDbType.Int);
                jobReturnValue.Direction =
ParameterDirection.ReturnValue;
                jobCommand.Parameters.Add(jobReturnValue);
                jobParameter =
new
SqlParameter("@job_name",
SqlDbType.VarChar);
                jobParameter.Direction =
ParameterDirection.Input;
                jobCommand.Parameters.Add(jobParameter);
                jobParameter.Value =
"ImportCMTData";
                jobConnection.Open();
                jobCommand.ExecuteNonQuery();
                jobResult = (
Int32)jobCommand.Parameters["@RETURN_VALUE"].Value;
                jobConnection.Close();
switch (jobResult)
case 0:
Console.WriteLine("SQL
Server Agent job, RunSISSPackage, started successfully.");
break;
default:
Console.WriteLine("SQL
Server Agent job, RunSISSPackage, failed to start.");
break;
Console.Read();
Thanks
Pankaj

"3-4 concurrent users are calling the SSIS package from ASPX page" this is not a proper design
If the data is being ingested than it is likely that this concurrency will lead to one of the packages die
What you shell do is to just queue the data ingress/processing.
In general, again, packages should not be called from ASP web pages, SSIS is ETL-server side technology there is nothing signalling back to the user whether it was successful. The proper way is to write a REST service or alike.
Arthur
MyBlog
Twitter

HOw to avoid DeadLocks when you schedule a Sql Server Agent Job and calling SSIS packages

Hi All,
I have scheduled 2 packages in in Sql Server Agent jobs .
First job which is having Package 1 executing at 11 AM and where I am inserting the data in the table.
Second job which is having Package 2 executing at 12 AM and where I am updating the data in the table based on the first job inserted records.
When I am executing my first job it taking more time and executing till 12 AM and from 12 AM my job 2 also starting ,so getting deadlocks conflicts because inserting happening from job1 and updating happening from Job 2.
How to avoid deadlocks and fix the issue.
Please Suggest .
Thanks & Regards,
Anand

Hi Anand,
Here is another solution, you can set the Job 2 not to run based on a schedule, and create another SQL Server Agent Job which starts at 12 AM and run with a specified time interval to execute a SQL statement in which you do the following steps:
1. Get the status information of Job 1 using the statement:
DECLARE @i int;
EXEC @i = msdb.dbo.sp_help_job @job_name = ‘Job Name'
2. If the value of @i is 1 which means the status of job 1 is success and current time is, then start the job 2. So, the statement is as follows:
IF @I = 1
EXEC msdb.dbo.sp_start_job @job_name= ‘Job Name’
Regards,
Mike Yin
TechNet Community Support

Automatically start SQL Agent service after SQL Server service fails and starts.

Hi!
I have SQL Server 2008 R2 with two main services - SQL Server and SQL Agent.
I'll try to describe my situation. It happens very occasionally, but sometimes SQL Server service terminates unexpectedly. It's my log:
09/13/2013 10:46:21,Service Control Manager,Error,The SQL Server (MSSQLSERVER) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.
09/13/2013 10:46:21,,Error,[359] The local host server is not running,,,,
09/13/2013 10:46:22,MSSQLSERVER,Error,The MSSQLSERVER service terminated unexpectedly.,Server,1073760843,,
09/13/2013 10:46:22,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #1)...,,,,
09/13/2013 10:46:27,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #2)...,,,,
09/13/2013 10:46:32,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #3)...,,,,
09/13/2013 10:46:32,,Error,[140] AutoRestart: The MSSQLSERVER service could not be restarted after 3 attempts,,,,
09/13/2013 10:46:32,,Warning,[360] SQLServerAgent initiating shutdown following MSSQLSERVER shutdown,,,,
As you can see, SQL Server service terminates unexpectedly. Then SQL Agent service tries to start SQL Server service. After unsuccessfully attempts to start SQL Server service, SQL Agent service stops itself. I have the option setting in SQL Server
service to start itself after unexpectedly stop within 2 minutes and it is works well. But I have to start my SQL Agent service after this manually. Unfortunately, I can't investigate the reason of my SQL Server stops unexpectedly and in this case I just want
to make the settings to start both of my services SQL Server and SQL Agent automatically after this. How can I set up this? How can I make my SQL Agent service starts after SQL Server service?

Hello,
SQL server agent service depends on SQL server service so unless SQL server service comes online agent will not come online so agent is depended on SQL server not the other wise.
Now is your server 2008 R2 patched to latest service pack (SP2).If not please upgrade it to latest SP.Some fixes are there in Sp which will subside this issue.Can you paste output of
select @@version
>>Then SQL Agent service tries to start SQL Server service.No this is not the case
>>Unfortunately, I can't investigate the reason of my SQL Server stops unexpectedly
Did you checked sql server errorlog and windows event log completely.Please do so and paste if you find some more info
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Cannot start SQL Server Agent (Version 2014 enterprise core)?

The SQL Server Agent log file has the following information. I already set the firewall for inbound 1433.
2014-11-04 11:59:43 - ? [100] Microsoft SQLServerAgent version 12.0.2000.8 (X64 unicode retail build) : Process ID 6108
2014-11-04 11:59:43 - ? [495] The SQL Server Agent startup service account is ......
2014-11-04 11:59:43 - ! [150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2014-11-04 11:59:43 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2014-11-04 11:59:43 - ! [298] SQLServer Error: 27, Registry information is corrupt or missing. Make sure the provider is installed and registered correctly. [SQLSTATE 08001]
2014-11-04 11:59:43 - ! [298] SQLServer Error: 27, Client unable to establish connection [SQLSTATE 08001]
2014-11-04 11:59:43 - ! [165] ODBC Error: 0, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to
allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001]
2014-11-04 11:59:43 - ! [382] Logon to server '(local)' failed (DisableAgentXPs)
2014-11-04 11:59:43 - ? [098] SQLServerAgent terminated (normally

Is this new SQL Server installation or originally it was working fine ?
Below message makes me think you might as well need to repair your installation
>SQLServer Error: 27, Registry information is corrupt or missing. Make sure the provider is installed and registered correctly. [SQLSTATE 08001]
Please see below link
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/d2a97cf4-54b2-40b7-836a-b9f146442855/unable-to-open-sql-server-logs?forum=sqlsetupandupgrade
Without errorlog it would be difficult to say why this happened but as errorlog says it has found registry inconsistent so repairing installation would help
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Starting SQL Server Agent service

I have a brand new 64-bit laptop and have installed both SQL Server 2014 and SQL Server 2012sp1, but neither instance is able to start its SQL Sever Agent Service. The error is 1053: 'The service did not respond to the start or control request
in a timely fashion'. Googling that message does not seem to give helpful step by step solutions. Please help.
Dave Juergens
[email protected]
Dave Juergens

could you tell us your sql server edition - if it is EXPRESS edition - it does not comes with SQL Server agent. you will sql server agent service in configuration manager but it does not start because the feature is not available.
you can find the sql edition using. select @@version
and post the output here
if it is not Express edition, could you please check the error log or event viewer and if there is more detailed information on the error.
Hope it Helps!!

SQL Server Agent (MSSQLSERVER) service is failing to start

Hi All,
I am using SQL Server 2008 R2 Express edition. When i start SQL Server Agent (MSSQLSERVER) service it is failing to start and gives the below error.
On analyzing the Event logs i found the below event.
The SQL Server Agent (MSSQLSERVER) service terminated unexpectedly. It has done this 14 time(s).
Event id 7034
Event source: Service Control Manager.
I opened the SQL server configuration manager to change the service account and start the service, But that is also failing and it is giving the below error.
Can any one help in this issue ?
Gautam.75801

Like Olaf said SQL Server Agent is available in express but cannot be enabled. This is restriction from MS. The reason is that(why its available and disabled) when you upgrade express to enterprise/standard it just uses this disabled SQL Server agent and
enables it. If this feature was not present SQL Server upgrade process would have to write whole code for SQL agent Which I am sure it does not do while upgrading to standard/enterprise.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Sql server agent is not highlighting start and stop options

I configured snapshot replication , after that sql server agent is not highlighting start and stop options in instance.
But I can start & stop it in services.msc
how I can solve this?

Hi,
Can you post exact error message.
Also refer below article, may be similar issue like yours.
How to start SQL Server Agent when Agent XPs show disabled
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
Praveen Dsa | MCITP - Database Administrator 2008 |
My Blog | My Page

Sql server agent not starting

I installed sql server 2008 r2 sp2
sql server agent is not allowing me to start it.
I run SSCM right click agent but start,stop menus are disabled

i have only one sql instance named SQLEXPRESS
The SQL Server Agent is installed with the Express Edition of SQL Server, but it's not a Feature of the Express Edition, therefore you can't start the Agent.
See
Features Supported by the Editions of SQL Server 2014
Olaf Helper
[ Blog] [ Xing] [ MVP]

When I start SQL server agent (sharepoint) service it stops everytime.

hi,
I have a windows server 2012 and SQL server 2008 R2 and SQL server agent (sharepoint) service goes to stop status everytime i start it ,please help me?

There is no error log ,only 3 information log was there after starting the service that one of them is related to it after stopping (event ID=7036 all of them).but also there is a warning information that source of it is DNS client Events and it's event
ID= 1014 and in the general section of explanation i see the user of last event i mentioned is NETWORK SERVICE ,but the account that the service logs on with it,is administrator.
Without error log message or any kind of message its not possible to help you.Is your SQL Server up and running.Did you checked SQL server errorlog.Run this query after trying to start Agent and post the output.
sp_readerrorlog
Also can you locate SQLAGENT.OUT file and open it in notepad.Location can be at
"Drive :\Program
Files\Microsoft SQL Server\MSSQL\LOG--
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Cannot start SQL-SERVER-AGENT

Hellow friends. I have made a software that uses SQL-SERVER database at back end.. I want to use
express version of SQL-SERVER so i downloaded SQL-SERVER-2008 R2.. But i could not start
SQL-SERVER agent.
Can i still share database over the NEWTWORK
without starting SQL-SERVER-AGENT???

IS it possible to share database over a LAN using SQL server Express 2008.??
Or do EXPRESS-VERSION of sql server does not allow us to do so. ?
I find both 'yes' and 'no' answers when i google this question. Please i am in need of specific answer.
Just because you can get answer from forum dont start flooding it with same question.Below thread has same question see my reply, and reply to below forum only
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/eae75c95-6e98-413e-9e1d-206d95d893bf/cannot-start-sqlserveragent?forum=sqltools
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SQL Server Agent can't start

Similar Messages

Maybe you are looking for