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

Similar Messages

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

Change SQL Server Agent service account

How can I change the SQL Server Agent service account from NT SERVICE\SQLSERVERAGENT to a domain user? and most importantly is what permissions I have to give that domain user?
I know that when SQL Server setup, the installer gives the domain user (that we choose to run a SQL Server service) the least privileges required, but my case is that I chose NT SERVICE\SQLSERVERAGENT and
now I want to change it to domain user so I can run successfully jobs that execute something on another SQL Servers.
If I JUST change the service account in the SQL Server Agent Properties window to a normal domain user, this is not enough and non of the jobs (even that execute local jobs) will work ...
So what privileges I should give that domain user to be able to run ALL jobs successfully?

Thanks Andreas ... yes it seems that my problem is not what I was thinking.
Stan210, thank you also :) .... my connection is trusted and the following is the error I'm getting:
The job failed. Unable to determine if the owner (MYDOMAIN\JobOwnerUser) of job
MyJOB has server access (reason: Could not obtain information about Windows NT group/user 'MYDOMAIN\JobOwnerUser', error code 0x6e. [SQLSTATE 42000] (Error
15404)).
if I change the owner of the job to sa I get the follwoing error:
Executed as user: CCCAE\RASO_SSAgent. Login failed for user 'MYDOMAIN\AgentDomainUser'. [SQLSTATE 28000] (Error 18456) Cannot open database "DB_on_other_Server" requested by the login. The login
failed. [SQLSTATE 42000] (Error 4060). The step failed.
if I keep the owner of the job "sa" and add the 'MYDOMAIN\JobOwnerUser'
in 'Run as user' of the step, I get the following error:
'EXECUTE AS USER' failed for the requested user
'MYDOMAIN\JobOwnerUser' in the database 'master'. The step failed.
please note that 'MYDOMAIN\JobOwnerUser'
is a sysadmin on both SQL Servers

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

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

Unable to start SQL Server Browser service in Sql server 2005

we are unable to start the SQL browser service on one of our machine with below error.
I believe this to be the reason, why we could not connect to the instance with below error
I tried troubleshooting as mentioned here, by changing
value in registry from 1 to 0, but still no luck.
SQLservices are also running.
Please help on how to resolve this!

Hello,
You say that SQL Server Browser Service belongs to a SQL Server 2005, but based on the name of the instance is a SQL Server
2012 instance.
Do you have any issues installing/uninstalling SQL Server 2005 or 2012? One of them 32-bit and the other 64-bit?
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Error Starting SQL Server Analysis Services (SharePoint - Central Administration)

I am not able to start the SQL Server Analysis Services via SharePoint Central Administration but SQL Server PowerPivot System Services yes.
I then tried to start the SQL Server Analysis Services(PowerPivot) via the sql server(powerpivot), it was started but will stopped after a while. I am not sure why it happened. Can anyone helps me? I have debugged this issue for almost 2 weeks time but still
failed to solve it.
Microsoft SharePoint Server 2010 - 14.0.6029.1000 (x64)
Microsoft SQL Server 2008 R2 (SP2) (PowerPivot) - 10.50.4000.0 (X64)

Hello,
Have you got any error message or log information in your scenario? Please help to check Windows Event log and SharePoint log for further investigation:
Configure and View SharePoint Log Files and Diagnostic Logging (PowerPivot for SharePoint):
http://technet.microsoft.com/en-us/library/ee210652.aspx
Or this issue might be caused by expired password. Please try to update an expired password for SQL Server Analysis Services (PowerPivot) instance:
http://technet.microsoft.com/en-us/library/ee210642.aspx
Regards,
Elvis Long
TechNet Community Support

DBACOCKPIT uses MS SQL Server Agent service?

Hello
I am trying to make backup from DBACOCKPIT to a netowrk location.
If i go to MS SQL SERVER AGENT and define log on by a domain user i get the error
"Executed as user: GOLDENFOODS\kkoulis. Must declare the scalar variable "@location1". [SQLSTATE 42000] (Error 137) "
anybody can help with the solution?
thx

Hello
Yes i have created it to the location which you mention and it works fine.
After if i go to SAP at the transaction DBACOCKPIT and try to run a FULL or LOG backup there, i have the following error:
SQL Job information   ******************************
Jobname:    SAP CCMS Log Backup of GDW [20110802094537-2-094537]
Type:       TSQL
DB-Name:    GDW
For Run:    20110802 09:45:37
Job history information *****************************
Stepname:   CCMS-step 1
Command:    declare @exeStmt nvarchar(2000) exec gdw.sap_backup_databases @dbList=
            "GDW",@r3Db="GDW",@bDev="@FisticLOG2",@expDays= 27,@jobName= "SAP CCMS
             Log Backup of GDW [20110802094537-2-094537]",@bkupChecksum="N",@bkupC
            ompress="N",@bkupType="L",@nativeBkup="N",@exeDate = "20110802094537",
            @bkupSim = "N",@format = 0,@init = 0,@bkupDb = "GDW",@unload = 0,@exeS
            tmt = @exeStmt OUTPUT
Status:     (failure)
Message:    2528
Severity:                                                                                15
Duration:   0 hours(s) 0 min(s) 0 sec(s)
Last msg:   Executed as user: GOLDENFOODS\kkoulis. Must declare the scalar variabl
            e "@FisticLOG2". [SQLSTATE 42000] (Error 137) Incorrect syntax near t
            he keyword 'with'. If this statement is a common table expression, an
            xmlnamespaces clause or a change tracking context clause, the previous
             statement must be terminated with a semicolon. [SQLSTATE 42000] (Erro
            r 319) DBCC execution completed. If DBCC printed error messages, cont
            act your system administrator. [SQLSTATE 01000] (Error 2528). The ste
            p failed.
                    <----
End of Job Step History -
>
thx in advance

Can't Start the SQL Server & SQL Server Agent Services

Hello i had to make Help Please.
2014-10-31 12:18:55.66 Server Feb 10 2012 19:39:15
Copyright (c) Microsoft Standard Edition (64-bit) 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server -d C:\Program Files\Microsoft -e C:\Program Files\Microsoft -l C:\Program Files\Microsoft 2014-10-31 12:18:55.69 Server -s "MSSQLSERVER"
2014-10-31 12:18:56.21 Server 2014-10-31 12:18:56.21 Server 2014-10-31 12:18:56.21 Server 2014-10-31 12:18:56.21 Server 2014-10-31 12:18:58.04 Server 2014-10-31 12:18:58.05 Server 2014-10-31 12:18:58.07 Server 2014-10-31 12:18:58.08 Server 2014-10-31 12:18:58.15 spid5s 2014-10-31 12:18:58.71 Server 2014-10-31 12:18:59.22 spid5s 2014-10-31 12:18:59.24 spid5s 2014-10-31 12:18:59.81 spid5s 2014-10-31 12:18:59.98 spid5s 2014-10-31 12:19:00.76 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 Server 2014-10-31 12:19:00.80 Server 2014-10-31 12:19:00.80 Server 2014-10-31 12:19:00.81 Server 2014-10-31 12:19:00.81 spid13s 2014-10-31 12:19:00.81 Server 2014-10-31 12:19:00.81 Server 2014-10-31 12:19:00.86 Server 2014-10-31 12:19:22.49 spid15s 2014-10-31 12:19:22.68 spid17s 2014-10-31 12:19:22.69 spid9s 2014-10-31 12:19:22.69 spid18s 2014-10-31 12:19:22.69 spid19s 2014-10-31 12:19:22.71 spid9s 2014-10-31 12:19:22.90 spid9s 2014-10-31 12:19:23.36 spid9s 2014-10-31 12:19:23.46 spid9s 2014-10-31 12:19:23.67 spid20s 2014-10-31 12:19:23.67 spid20s 2014-10-31 12:19:23.73 spid20s 2014-10-31 12:19:24.67 spid5s 2014-11-01 00:00:08.70 spid28s 2014-11-02 00:00:23.48 spid29s 2014-11-03 00:00:53.66 spid29s 2014-11-04 00:00:08.08 spid19s 2014-11-04 18:03:23.74 spid53 2014-11-04 18:03:23.79 spid53 2014-11-04 18:03:24.72 spid54 2014-11-04 18:03:24.78 spid54 2014-11-04 18:03:27.74 spid53 2014-11-04 18:28:12.10 spid52 2014-11-04 18:28:12.13 spid52 2014-11-05 00:00:26.82 spid18s a copy of my setup for a coworker in a different country to work with i can't make this two services to start. A timed out error shows and maybe the logs say something but i can't understand it.
Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Corporation
on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
(c) Microsoft Corporation.
All rights reserved.
Server process ID is 2540.
System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
Authentication mode is MIXED.
Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
Registry startup parameters:
SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf
SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG
SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
Command Line Startup Parameters:
SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
Detected 3071 MB of RAM. This is an informational message; no user action is required.
Using conventional memory in the memory manager.
This instance of SQL Server last reported using a process ID of 2532 at 31/10/2014 12:18:20 p.m. (local) 31/10/2014 06:18:20 p.m. (UTC). This is an informational message only; no user action is required.
Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
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.
Software Usage Metrics is disabled.
Starting up database 'master'.
CLR version v4.0.30319 loaded.
SQL Server Audit is starting the audits. This is an informational message. No user action is required.
SQL Server Audit has started the audits. This is an informational message. No user action is required.
SQL Trace ID 1 was started by login "sa".
Server name is 'WIN-3FNEFF25D4V'. This is an informational message only. No user action is required.
A self-generated certificate was successfully loaded for encryption.
Server is listening on [ 'any' <ipv6> 1435].
Server is listening on [ 'any' <ipv4> 1435].
Server is listening on [ 'any' <ipv6> 1433].
Server is listening on [ 'any' <ipv4> 1433].
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
Server is listening on [ ::1 <ipv6> 1434].
Server is listening on [ 127.0.0.1 <ipv4> 1434].
Dedicated admin connection support was established for listening locally on port 1434.
SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
SQL Server is now ready for client connections. This is an informational message; no user action is required.
The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/WIN-3FNEFF25D4V ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/WIN-3FNEFF25D4V:1433 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
A new instance of the full-text filter daemon host process has been successfully started.
Starting up database 'msdb'.
Starting up database 'mssqlsystemresource'.
Starting up database 'CMOVILBD'.
Starting up database 'ArgusTec'.
The resource database build version is 11.00.2100. This is an informational message only. No user action is required.
Starting up database 'model'.
Clearing tempdb database.
Starting up database 'tempdb'.
The Service Broker endpoint is in disabled or stopped state.
The Database Mirroring endpoint is in disabled or stopped state.
Service Broker manager has started.
Recovery is complete. This is an informational message only. No user action is required.
This instance of SQL Server has been using a process ID of 2540 since 31/10/2014 12:19:24 p.m. (local) 31/10/2014 06:19:24 p.m. (UTC). This is an informational message only; no user action is required.
This instance of SQL Server has been using a process ID of 2540 since 31/10/2014 12:19:24 p.m. (local) 31/10/2014 06:19:24 p.m. (UTC). This is an informational message only; no user action is required.
This instance of SQL Server has been using a process ID of 2540 since 31/10/2014 12:19:24 p.m. (local) 31/10/2014 06:19:24 p.m. (UTC). This is an informational message only; no user action is required.
This instance of SQL Server has been using a process ID of 2540 since 31/10/2014 12:19:24 p.m. (local) 31/10/2014 06:19:24 p.m. (UTC). This is an informational message only; no user action is required.
Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
Using 'xpsqlbot.dll' version '2011.110.2100' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
Using 'xpstar.dll' version '2011.110.2100' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
Starting up database 'Argus'.
Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
Using 'xplog70.dll' version '2011.110.2100' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
This instance of SQL Server has been using a process ID of 2540 since 31/10/2014 12:19:24 p.m. (local) 31/10/2014 06:19:24 p.m. (UTC). This is an informational message only; no user action is required.

Sorry i feel so stupid. Here it is. I can clearly see the errors now
2014-11-05 10:49:47.43 Server Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)
Mar 29 2009 10:11:52
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (VM)
2014-11-05 10:49:47.43 Server (c) 2005 Microsoft Corporation.
2014-11-05 10:49:47.43 Server All rights reserved.
2014-11-05 10:49:47.43 Server Server process ID is 4596.
2014-11-05 10:49:47.43 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2014-11-05 10:49:47.43 Server Authentication mode is MIXED.
2014-11-05 10:49:47.43 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2014-11-05 10:49:47.43 Server This instance of SQL Server last reported using a process ID of 5720 at 05/11/2014 10:28:35 a.m. (local) 05/11/2014 04:28:35 p.m. (UTC). This is an informational message only; no user action is required.
2014-11-05 10:49:47.43 Server Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2014-11-05 10:49:47.44 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-11-05 10:49:47.44 Server Detected 2 CPUs. This is an informational message; no user action is required.
2014-11-05 10:49:47.46 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.
2014-11-05 10:49:47.49 Server Node configuration: node 0: CPU mask: 0x0000000000000003 Active CPU mask: 0x0000000000000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014-11-05 10:49:47.50 spid7s Starting up database 'master'.
2014-11-05 10:49:47.59 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2014-11-05 10:49:47.60 spid7s SQL Trace ID 1 was started by login "sa".
2014-11-05 10:49:47.60 spid7s Starting up database 'mssqlsystemresource'.
2014-11-05 10:49:47.61 spid7s The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2014-11-05 10:49:47.67 spid7s Server name is 'WIN-3FNEFF25D4V\SQLEXPRESS'. This is an informational message only. No user action is required.
2014-11-05 10:49:47.67 spid10s Starting up database 'model'.
2014-11-05 10:49:47.68 spid7s Informational: No full-text supported languages found.
2014-11-05 10:49:47.68 spid7s Starting up database 'msdb'.
2014-11-05 10:49:47.76 spid10s Clearing tempdb database.
2014-11-05 10:49:47.83 Server A self-generated certificate was successfully loaded for encryption.
2014-11-05 10:49:47.83 Server Error: 26023, Severity: 16, State: 1.
2014-11-05 10:49:47.83 Server Server TCP provider failed to listen on [ 'any' <ipv6> 1433]. Tcp port is already in use.
2014-11-05 10:49:47.83 Server Error: 17182, Severity: 16, State: 1.
2014-11-05 10:49:47.83 Server TDSSNIClient initialization failed with error 0x2740, status code 0xa. Reason: Unable to initialize the TCP/IP listener.
2014-11-05 10:49:47.83 Server Error: 17182, Severity: 16, State: 1.
2014-11-05 10:49:47.83 Server TDSSNIClient initialization failed with error 0x2740, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors.
2014-11-05 10:49:47.83 Server Error: 17826, Severity: 18, State: 3.
2014-11-05 10:49:47.83 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2014-11-05 10:49:47.83 Server Error: 17120, Severity: 16, State: 1.
2014-11-05 10:49:47.83 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Changing sql server service and sql server agent service startup account in SQL Server hosting SharePoint DB

Hi
i have a sharepoint deployment with one SQL Server (running on VM) hosting the config DB and another SQL Server (Physical Host because VM was running out of space) to host the huge Content DBs. I need to schedule automatic backups of the Content DBs to a
network share. For that i need to run the SQL Server Service with an account having permissions to the share as suggested in https://support.microsoft.com/kb/207187?wa=wsignin1.0
I tried changing the logon as a service account to a domain
account which has permissions to the Network Share and is also in local Administrators group of SQL Server and has "public and sysadmin" roles in SQL Server but that caused an issue. the SharePoint Web Application started showing a White Screen so
I had to revert back to the default accounts i.e. NT Service\SQLSERVERAGENT and NT Service\MSSQLSERVER. I viewed the event logs . These are the types of error i got after changing the logon as a service account to a domain account
1) Information Rights Management (IRM): Retried too many times to initialize IRM client. Cannot retry more. Retried times is:0x5.
System
Provider
[ Name]
Microsoft-SharePoint Products-SharePoint Foundation
[ Guid]
{6FB7E0CD-52E7-47DD-997A-241563931FC2}
EventID
5148
Version
15
Level
2
Task
9
Opcode
0
Keywords
0x4000000000000000
TimeCreated
[ SystemTime]
2015-02-02T04:46:04.750899500Z
EventRecordID
176477
Correlation
[ ActivityID]
{8FACE59C-1E17-50D0-7135-25FDB824CDBE}
Execution
[ ProcessID]
6912
[ ThreadID]
8872
Channel
Application
Computer
Security
[ UserID]
S-1-5-21-876248814-3204482948-604612597-111753
EventData
hex0
0x5
2)
Unknown SQL Exception 0 occurred. Additional error information from SQL Server is included below.
The target principal name is incorrect. Cannot generate SSPI context.
System
Provider
[ Name]
Microsoft-SharePoint Products-SharePoint Foundation
[ Guid]
{6FB7E0CD-52E7-47DD-997A-241563931FC2}
EventID
5586
Version
15
Level
2
Task
3
Opcode
0
Keywords
0x4000000000000000
TimeCreated
[ SystemTime]
2015-02-02T07:01:35.843757700Z
EventRecordID
176490
Correlation
[ ActivityID]
{50B4E59C-5E3A-50D0-7135-22AD91909F02}
Execution
[ ProcessID]
6912
[ ThreadID]
5452
Channel
Application
Computer
Security
[ UserID]
S-1-5-17
EventData
int0
0
string1
The target principal name is incorrect. Cannot generate SSPI context.

Hi Aparna,
According to your description, you get the above two errors when scheduling backups of Content DB. Right?
Based on those two error messages, they are related to the service principal name(SPN) for SQL Server service. Please verify the if the SPN is registered successfully. You can view it in ADSI Edit or use command line. Please see:
http://blogs.msdn.com/b/psssql/archive/2010/03/09/what-spn-do-i-use-and-how-does-it-get-there.aspx
When installing SQL Server, those two services below should be registered:
MSSQLSvc/servername:1433
MSSQLSvc/servername
Please check if those SPNs or duplicated SPNs exist. You can use command to reset SPN or remove duplicated SPN and add new one. See:
Setspn.
We have also met this issue when this SPN is registered under Administrator. Please try to register it under Computer. You can add it in ADSI Edit.
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

Scheduling SSIS packages to run using SQL Server Agent Service

The job failed. The Job was invoked by Schedule 11 (run package). The last step to run was step 1 (Execute Package)". how do i resolve this?

Most probable causes: the developer runs the package in BI studio, it works. The job is deployed and runs in a schedule.
the sql job agent does not have same rights as the developer.
the test in BI studio was doen in 32-bit mode , the job by default ran in 64-bit mode. some oledb-odbc drivers may not work.
Jan D'Hondt - SQL server BI development

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

[Forum FAQ] How do I disable all subscriptions without disabling Reporting Services and SQL Server Agent?

Introduction
There is the scenario that users configured hundreds of subscriptions for reports. Now they want to disable all the subscriptions, but Reporting Services and SQL Server Agent service should be enable, so the subscriptions will not delivery reports to users
and users could run the reports and create jobs on the server.
Solution
To achieve this requirement, we need to list all subscriptions and their schedules by running query, then use loop statement to disable all the subscription schedules by Job name.
On the Start menu, point to All Programs, point to Microsoft SQL Server instance, and then click SQL Server Management Studio.
Type Server name and select Authentication, click Connect.
Click New Query in menu to open a new Query Editor window.
List all subscriptions and their schedules by running the following query:
Use ReportServer
go
SELECT   c.[Name] ReportName,
s.ScheduleID JobName,
ss.[Description] SubscriptionDescription,
ss.DeliveryExtension SubscriptionType,
c.[Path] ReportFolderPath,
row_number() over(order by s.ScheduleID) as rn
into
#Temp
FROM
ReportSchedule rs
INNER JOIN Schedule s ON rs.ScheduleID = s.ScheduleID
INNER JOIN Subscriptions ss ON rs.SubscriptionID = ss.SubscriptionID
INNER JOIN [Catalog] c ON rs.ReportID = c.ItemID AND ss.Report_OID = c.ItemID
select * from #temp
Use the loop statement to disable all the subscription schedules by Job name:
DECLARE
@count INT,
@maxCount INT
SET @COUNT=1
SELECT @maxCount=MAX(RN)
FROM
#temp
DECLARE
@job_name VARCHAR(MAX)
WHILE @COUNT <=@maxCount
BEGIN
SELECT @job_name=jobname FROM #temp WHERE RN=@COUNT
exec msdb..sp_update_job @job_name = @job_name,@enabled = 0
SET @COUNT=@COUNT+1   P
RINT @job_name
END
PRINT @COUNT
Reference
SQL Agent – Disable All Jobs
Applies to
Reporting Services 2008
Reporting Services 2008 R2
Reporting Services 2012
Reporting Services 2014
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Thanks,
Is this a supported scenario, or does it use unsupported features?
For example, can we call exec [ReportServer].dbo.AddEvent @EventType='TimedSubscription', @EventData='b64ce7ec-d598-45cd-bbc2-ea202e0c129d'
in a supported way?
Thanks! Josh

Starting SQL Server Agent service

Similar Messages

Maybe you are looking for