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

Similar Messages

What would be the reason for sql server agent [MSSQLSERVER] service terminated unexpectedly?

What would be the reason for sql server agent [MSSQLSERVER] service terminated unexpectedly?
only below details found in error log
07:26:44.170 spid60
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
07:26:45.720 spid51
Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
07:26:45.730 spid51
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
07:28:57.840 spid64
Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
07:28:57.840 spid64
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
and below error on agent log
2014-01-01 07:26:28 - ? [131] SQLSERVERAGENT service stopping due to a stop request from a user, process, or the OS...
2014-01-01 07:26:43 - + [188] Scheduler engine timed out (after 15 seconds) waiting for 1 jobs(s) to stop
2014-01-01 07:26:44 - + [098] SQLServerAgent terminated (forcefully)
Rahul

What would be the reason for sql server agent [MSSQLSERVER] service terminated unexpectedly?
only below details found in error log
07:26:44.170 spid60
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
07:26:45.720 spid51
Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
07:26:45.730 spid51
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
07:28:57.840 spid64
Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
07:28:57.840 spid64
FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'MSSQLSERVER'.
and below error on agent log
2014-01-01 07:26:28 - ? [131] SQLSERVERAGENT service stopping due to a stop request from a user, process, or the OS...
2014-01-01 07:26:43 - + [188] Scheduler engine timed out (after 15 seconds) waiting for 1 jobs(s) to stop
2014-01-01 07:26:44 - + [098] SQLServerAgent terminated (forcefully)
Rahul
Can you post the output of below query
select @@version.
If you are using SQl server express edition ,SQL server agent feature is not available.It seems from errorlog that you can start it but actually you cannot.But first confirm what is version and edition of your SQL server
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SQL Server Agent Windows Service

I have created a override for parameter, Alert only if service startup type is automatic in monitor SQL Server Agent Windows Service to false, as my SQL Admin informs that this service startup type is Manual. As SQL servers are clustered, even SQL agent
service runs on even node and odd SQL agent service runs on the odd node. Should this resolve the issue my SQL Admin's are complaining they were not receiving notifications for SQL Agent stopping. Or, should it create noise as I should expect alerts from odd
SQL Agent service that are not running on even node and vice versa.
From SQL Server end,
Thanks, Harry :-)

Hi,
The below article should be helpful:
Monitoring Clusters by Using Operations Manager
http://technet.microsoft.com/en-us/library/hh212773.aspx
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

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

SQL Server Agent running SSIS package fails Unable to determine if the owner of job has server access

I have a web application developed through VS 2012 which has a button on a form that when operated starts a SQL Server agent job on the server that runs an SSIS package. The website and the instance of SQL Server with the agent and SSIS package are
on the same windows 2008 r2 server. When the button is operated no exceptions are raised but the SSIS package did not execute.
When I look in the logfileviewer at the job history of the sql server agent job I see that the job failed with message...
The job failed. Unable to determine if the owner (DOMAINNAME\userid) of job runWebDevSmall has server access (reason: Could not obtain information about Windows NT group/user 'DOMAINNAME\userid'<c/> error code 0x6e. [SQLSTATE 42000] (Error 15404)).,00:00:00,0,0,,,,0
...even though DOMAINNAME\userid is in the logins for the sql server and has admin authorities.
Could someone show me what I need to do to get this to run? Thanks tonnes in advance for any help, Roscoe

This can happen when the network is too slow to allow a timely completion of the verification. Or the account running has no such right.
I suggest you try using the SA account for the job as it does not require to poll the AD.
Arthur My Blog

SQL Server Agent Job/Service Account

Hi All,
I want to schedule a SSIS packages using SQL Server agent, My Agent is running on default local account
(No Service account). But currently there is a scenario that SSIS package should connect to some network path. As per my understnading the account on which SQL Agent is running will not be able to access the path. How can i achieve this? Do i need to start
my agent on a service account where the service account has total access to the netwrk path or can i impersonate using proxy accounts.
PLease help
Thanks,

you need to create a proxy account for that. Give it required access to path
see
http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

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

Getting SQL Server Agent running

I am trying to get my SQL Server Agent running, and no conventional means thus far have worked.
I set it to run automatically in the Services window of the Control Panel. Attempting to run it from there yields the error "The SQL Server Agent (BENTLEYECAD) service on Local Computer started then stopped. Some services stop automatically if they
are not in use by services or programs"
Attempting to start the Server agent in the Server configuration manager yields the 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"
The resulting error log in SQLAGENT.OUT is
2015-02-19 15:58:44 - ? [100] Microsoft SQLServerAgent version 10.50.1600.1 (x86 unicode retail build) : Process ID 6064
2015-02-19 15:58:44 - ? [101] SQL Server HFC-RND-104-D\BENTLEYECAD version 10.50.1600 (0 connection limit)
2015-02-19 15:58:44 - ? [102] SQL Server ODBC driver version 10.50.1600
2015-02-19 15:58:44 - ? [103] NetLib being used by driver is DBNETLIB.DLL; Local host server is HFC-RND-104-D\BENTLEYECAD
2015-02-19 15:58:44 - ? [310] 4 processor(s) and 4096 MB RAM detected
2015-02-19 15:58:44 - ? [339] Local computer is HFC-RND-104-D running Windows NT 6.1 (7601) Service Pack 1
2015-02-19 15:58:44 - ! [000] This installation of SQL Server Agent is disabled. The edition of SQL Server that installed this service does not support SQL Server Agent.
2015-02-19 15:58:44 - ? [098] SQLServerAgent terminated (normally)
I have installed this version of SQL alongside Promise V8i (M). Any advice on how to get this server agent running is welcome
-Eugene

I see.
I'm not sure if it's Express or not, how can I tell? The start-up for the server management studio just says "Microsoft SQL Server 2008 R2"
If this is the case, will any other version of SQL besides Express work? or is it only specific ones?
Thanks,
Eugene O'Donnell

SQL Server Agent and OpenDataSource failing

I have a stored procedure that is using an OpenDataSource query to export data from SQL Server into a excel file for download. I’ve installed the “Microsoft Access database engine 2010”, and can see it listed in SQL Server Management Studio under Server
Objects > Linked Servers > Providers > Microsoft.ACE.OLEDB.12.0.
If I manually run the stored procedure (when logged in as the OS’s administrator), the stored procedure runs fine, and the export is completed successfully.
The stored procedure is set up to be run periodically by a SQL Server Agent job.
However, if I start the SQL Server Agent job (when logged in as the OS’s administrator), the job fails with the following error message:
Executed as user: NT SERVICE\SQLSERVERAGENT. Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "(null)". [SQLSTATE 42000] (Error 7303) OLE DB provider "Microsoft.ACE.OLEDB.12.0"
for linked server "(null)" returned message "Unspecified error". [SQLSTATE 01000] (Error 7412). The step failed.
I have given the “NT SERVICE\SQLSERVERAGENT” user full control permissions on the destination directory where the export file resides (note that it starts out as an empty file just with the column headers defined).
I’ve applied the following configuration settings to SQL Server:
sp_configure 'show advanced options', 1;
RECONFIGURE;
GO
sp_configure 'Ad Hoc Distributed Queries', 1;
RECONFIGURE;
GO
EXEC master.dbo.sp_MSset_oledb_prop N'Microsoft.ACE.OLEDB.12.0', N'AllowInProcess', 1
GO
EXEC master.dbo.sp_MSset_oledb_prop N'Microsoft.ACE.OLEDB.12.0', N'DynamicParameters', 1
GO
What am I missing? Can anyone shed any light on what might be causing the failure?
This is running on SQL Server Web Edition 2012 on Windows Server 2012 Standard.
Thanks!

Hi JonathanT1,
First, I want to inform that, if SQL Server Agent log on account is “NT SERVICE\SQLSERVERAGENT”, we need to grant read and write permission to the destination folder to this account (you have done). From the following message:
Executed as user: NT SERVICE\SQLSERVERAGENT
It seems that you filled “NT SERVICE\SQLSERVERAGENT” in job step properties, “Run as user” option. I suggest changing it to another account who is in SQLAgentUserRole, SQLAgentReaderRole or SQLAgentOperatorRole. For more detail information, you can refer
to the following link:
Create a Transact-SQL Job Step
http://technet.microsoft.com/en-us/library/ms187910.aspx
SQL Server Agent Fixed Database Roles
http://technet.microsoft.com/en-us/library/ms188283.aspx
Allen Li
TechNet Community Support

Data Warehouse errors, SQL Server Agent Stopped

I just installed SCE 2010 on a 2k8 server and went through the config wizard. Now it is showing Data Warehouse alerts, including:
Data Warehouse failed to discover object health state standard data set. Failed to enumerate (discover) Data Warehouse objects and relationships among them. The operation will be retried.
Exception 'SqlException': Management Group with id '6FDBE66E-E35D-BCB8-0FA1-5947E45FE643' is not allowed to access Data Warehouse under login 'domain\user'
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataWarehouse.Discovery.StandardDataSet
Instance name: State data set
Instance ID: {217CFE24-F6F6-0DFF-9EA9-64C62895EE29}
Management group: SCESERVER_MG
I let the SCE install SQL 2008 Express. When I checked on the SQL Services, SQL Server Agent Service is stopped and will not start. Not sure if this is the cause of the above issue. I also can't log in to the SQL Server Management Studio.
How can I fix this? What other information do you need from me.

Danny01 - tried the domain admin rights on the service with no difference - put it back
Radhey Shah - I checked the admin account and it is the same account that I set the SQL up with. How do I verify this account has admin rights on the SQL DB?
The error that comes up when I try to run the SQL Server Agent Service is...
"The Sql Server Agent (Essentials) service on SCESERVER
started and then stopped. Some services stop automatically if
they are not in use by other serives or programs."
Also, when I look at the alerts within SCE, here is the current alert..
OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error
: Cannot open database "OperationsManagerDW" requested by the login. The login failed.
Workflow name: Microsoft.Windows.Client.Vista.ComputerGroup.DiskTrendsComputer
Instance name: Microsoft System Center Data Warehouse
Instance ID: {16781F33-F72D-033C-1DF4-65A2AFF32CA3}
Management group: SCESERVER_MG

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

Agent statistics and SQL server agent

We have CUCCX 5.02 and CUCM 6.1
When agents try to look their "Agent statistics report" in CAD there is no data. And status of this report is "Inactive". All other reports are active.
In CCX "control center" I see that "CRS SQL server Agent - this service is invalid" and "Cisco Desktop LDAP Monitor Service - this service is invalid".
We have problem only with Agent statistics report. Historical reporting - work fine.
What could be the reason?

Hi
Please see this tech note in order to restore the services that have failed:
http://www.ciscosystems.com/en/US/products/sw/custcosw/ps1846/products_tech_note09186a00808278d8.shtml
Regards
Aaron
Please rate helpful posts...

How to add sql server (SQLEXPRESS) AND sql server Agent(SQLEXPRESS) in sql server Configuration Manager

When I had uninstall Sql Server 2008 R2, that time I had uninstalled instances (SQLEXPRESS and MSSQLSERVER) and again installed sql server 2008 r2 setup .
Before uninstalling from control panel >Uninstall program showed two setups
1) Microsoft sql server 2) Microsoft sql server R2 , I uninstalled both.
As i installed SQL R2 again, it is showing only 1 instance ie "Microsoft sql server R2" but the other instance is some how missing -"Microsoft sql server" and
also sql server (SQLEXPRESS) AND sql server Agent(SQLEXPRESS) services from sql server configuration manager are missing
How to retain the missing instance and the above services?
Plz give replay

Hi Tushar,
I need to ask you a question here.
Why you require SQL Express edition on your machine, if there is no need you can safely ignore it and continue using SQL Server 2008 R2 edition.
Express edition can also get installed if you happen to have installed Visual Studio 2010 for instance.
If you need it then you must install SQL Server Express edition, It is a freeware and can be download from Microsoft website.
BR, Shashikant

Schedule SSIS packages as job in SQL Server Agent errors

Hi, I am using SQL Server 2008 R2 and created few SSIS packages and schedule them using SQL Server Agent and every time I try to schedule packages via SQL Server Agent my jobs keep failing. I am using domain/ione as the owner and when I invoke the job on
ServerA let's say and the job gets executed by domain/ServerA$ and fails as it does not have enough privileges. How do I fix this issue firstly without the proxy and why is the job being executed by domain/ServerA$ when the owner & user who invokes
it is domain/ione?
Thanks in advance............
Ione

Hi Ione,
The owner of any SQL jobs should be SA or any other non-expiring account
If you do not want the proxy used, then add the needed priveleges.
The owner of the job is one, the SSIS step gets executed by the account the Agent is running under.
Arthur
MyBlog
Twitter

"Disable Check for SQL Express" against SQL Server Agent

Good afternoon,
Seeing as it has been a know issue for many years now[1],
is there a reason why Microsoft has yet to include a “Disable Check for SQL Express” override (similar to the
Automatic Configuration (& other) monitors) for each of the following objects included in the
Microsoft SQL Server Management Pack?
SQL Server Agent Windows Service (Monitor)
Discover SQL Server Agent for a DB Engine (Discovery)
This would prevent me from have to continually create overrides
disabling the monitor|discovery each time a new instance of SQL Express is installed in our Management Group.
Thanks,
Larry
[1]
http://jmkehayias.blogspot.ca/2009/01/sql-server-2008-express-sql-agent-won.html
http://sqlblogcasts.com/blogs/sqldbatips/archive/2008/06/28/sql-server-2008-express-installs-sql-agent-but-don-t-bother-trying-to-start-it.aspx

Hello,
This is much easier
http://blogs.technet.com/b/emreguclu/archive/2013/01/21/undiscovering-stop-monitoring-sql-2008-express-editions.aspx
just exclude sqlexpress
Regards
Mohammad, IT NOC Team

SQL Server Agent (MSSQLSERVER) service is failing to start

Similar Messages

Maybe you are looking for