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

Similar Messages

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

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

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

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 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.

Unable to start SQL server agent service

hi,
We have 2 Node SQL Cluster that was working fine. Then We migrated the Linux DNS to Windows DNS successfully.Now restarted the SQL Server after it when we try to start the SQL Server Agent service its says the below msg while machine name and cluster
entries are in windows dns and resolving the IP to name and name to IP
Error msg: The MSSQLSERVER service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service." error message.
But whenever we set the Linux DNS Server ip in SQL Servers then it successfully starts the service. Now i want to know why its happening and what are the requirements or DNS entries/SPN which we missing when we migrated the linux DNS to windows
dns
Sagar

I was experiencing this issue or one just like it on one of our SQL clusters (SQL Server 2008 R2, two node).
The fix for us was the database Security Login for: NT SERVICE\SQLAgent$<instancename> was missing. The actual service account assigned to the SQL Agent service was a valid domain account and we had the credentials correct in the service
configuration, so no changes were needed there.
Using SQL Server Management Studio we manually added this BUILT IN account ( NT SERVICE\SQLAgent$<instancename> ) to the instance, and then assigned it user role = sysadmin (to go along with the default role = public).
Once this was done, we tried to restart the clustered SQL Agent service and it started and remained started.
Hope this helps someone, we spent over a day pouring over the installation trying to find the cause.
This worked for me, thanks:-)

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!!

SSIS fails to load files from network when executed via SQL server Agent (SQL server 2008 R2 SP 2)

Hi All,
I have a simple SSIS package that reads a flat file and copies it into a SQL Server table.
When the flat fiel is on the C drive I have no problem runnign this package from SQL Server Agent, but as soon as I update the path to a network location the package only works when I run it manually, but fails when is executed via the SQL Server agent job.
The error says "cannot open the datafile", while the datafile location is valid.
Is this a kind of limitation of a SQL Server Agent that only local files are allowed to be processed?
Thanks,
Andrei
SSIS question

Hi All,
Thanks for your responses.
I configured the SQL agent service to use my domain account with which I have no porblems accessing the folder. However the issue persisted.
Thanks,
Andrei
SSIS question

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

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

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

SSIS package fails in sql server agent wirh 'Process exit code "-532459699" runs fine when run independantly

I have a SSIS package that fails when running via sql server agent. I can successfully run it from BIDS.    I have created a proxy account that is in the local server administrators group and is sysadmin. SQL Server Agent and SQL
Server Integration Services are running under the same account,
following the the error message:
Error: 2014-02-07 10:29:12.59
   Code: 0xC0029151
   Source: Execute De-linking Execute Process Task
   Description: In Executing "d:\cie\files\working\9426\PowerpointConsole.exe" " 60.ppt" at "d:\cie\files\working\9426", The process exit code was "-532459699" while the expected was "0".
End Error
This package ran successfully on a different server running windows 2003 and sql server 2008 r2. The new environment is windows 7 with sql server 2008 r2.

Hi Gaileg,
As Abhinav said, to check whether it is a 32-bit/64-bit issue, please check whether the package runs in 32-bit runtime mode or 64-bit runtime mode in BIDS by checking the Run64bitRuntime property of the project. Then, make sure the package runs in the same
runtime mode in the SQL Server Agent job by checking or unchecking the “Use 32 bit runtime” option for the Execution options of the job step.
If it is not the issue, please create another job that uses a CmdExec type job step to call the executable “D:\cie\files\working\9426\PowerpointConsole.exe”. If this job also fails, the issue is actually occurs because of the issue between executable and
SQL Server Agent rather than the SSIS package itself.
Regards,
Mike Yin
TechNet Community Support

SQL Procedure working when run manually, not running from sql server agent

I have a procedure that runs fine using the execute command in SSMS, however putting the same command in a job gives the following error.
line 9, character 9, unexpected end of input
The code takes a very long XML string in UTF-8 encoding and puts it into a single nvarchar(max) cell. Then puts this string into a XML cell in a different table, allowing me to query the individual parts of the XML code using the nodes function. I cannot put
the data directly into a nvarchar cell due to encoding differences.
I can't reproduce the string here as it is very very long.
I'm just looking for ideas really as to where it might be going wrong.
Here is what I know so far:
The procedure runs without issue when executed manually
I have checked permission issues, and that doesn't seem to be the problem. The agent runs under my own account and I am a sysadmin on the database
I split the procedure into seperate parts to locate exactly where the problem is occuring. Once again the seperate procedures run fine when executed manually but an error occurs when run through SQL Server agent.
When the query is run seperately through SQL Server Agent it gives a slightly different error. This leads me to believe it is an encoding issue. However I am getting the XML from a webpage and I can't change the encoding on the webpage.
line 1, character 38, unable to switch the encoding
I know this is a long shot since you can't replicate the issue but if anyone could give an idea as to where to start looking for an answer, it would be greatly appreciated.

Here's how I'm taking the XML data and putting it into an nvarchar(max) column (Column Name TEXT):
Select @url = 'http://....'
EXEC @hr=sp_OACreate 'WinHttp.WinHttpRequest.5.1',@win OUT
IF @hr <> 0 EXEC sp_OAGetErrorInfo @win
EXEC @hr=sp_OAMethod @win, 'Open',NULL,'GET',@url,'false'
IF @hr <> 0 EXEC sp_OAGetErrorInfo @win
EXEC @hr=sp_OAMethod @win,'Send'
IF @hr <> 0 EXEC sp_OAGetErrorInfo @win
INSERT #TextData(TEXT)
EXEC @hr=sp_OAGetProperty @win,'ResponseText'
IF @hr <> 0 EXEC sp_OAGetErrorInfo @win
EXEC @hr=sp_OADestroy @win
IF @hr <> 0 EXEC sp_OAGetErrorInfo @win

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

Similar Messages

Maybe you are looking for