July 30, 2015 at 2:29 pm
My login Dom1\mylogin is added to the sysadmin role but when I try to run the SQL Server Agent I get the following error
2015-07-30 15:02:48 - ? [495] The SQL Server Agent startup service account is NT Service\SQLSERVERAGENT.
2015-07-30 15:02:48 - ! [150] SQL Server does not accept the connection (error: 18456). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2015-07-30 15:02:48 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2015-07-30 15:02:48 - ! [298] SQLServer Error: 18456, Login failed for user 'V010\servername$'. [SQLSTATE 28000]
2015-07-30 15:02:48 - ! [382] Logon to server '(local)' failed (DisableAgentXPs)
2015-07-30 15:02:48 - ? [098] SQLServerAgent terminated (normally)
July 30, 2015 at 3:00 pm
did you check the services?
July 30, 2015 at 3:31 pm
The services was using the built in account tried to change is to the service account through the services properties window but getting an Access denied error now.
July 31, 2015 at 8:21 am
Have a look at the permissions to the directory where the SQLAgent.exe is stored.
Default is: C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn
I've had similar problems where there have been issues around that.
July 31, 2015 at 10:05 am
The issue is resolved. Changed the SQL SEVER agent user to a new service account and it started to work.
July 31, 2015 at 10:36 am
Thanks for posting the resolution
August 4, 2015 at 5:00 am
Hi,
Remember that SQL Server service user account must be always changed using the SQL Server configuration console, not the Windows service console.
June 23, 2016 at 1:52 am
Hi,
Got the similar issue. Below is the Agent log details. Agent is starting and stopping automatically. Can some one provide me the resolution.
Agent Log details:
2016-06-23 02:19:07 - ? [100] Microsoft SQLServerAgent version 12.0.2568.0 (X64 unicode retail build) : Process ID 2584
2016-06-23 02:19:07 - ? [495] The SQL Server Agent startup service account is *****.
2016-06-23 02:19:39 - ! [150] SQL Server does not accept the connection (error: 53). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2016-06-23 02:19:39 - ! [000] Unable to connect to server 'MSSQLSERVER'; SQLServerAgent cannot start
2016-06-23 02:19:47 - ! [298] SQLServer Error: 53, Named Pipes Provider: Could not open a connection to SQL Server [53]. [SQLSTATE 08001]
2016-06-23 02:19:47 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
2016-06-23 02:19:47 - ! [298] SQLServer Error: 53, 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]
2016-06-23 02:19:47 - ! [382] Logon to server 'MSSQLSERVER' failed (DisableAgentXPs)
2016-06-23 02:19:47 - ? [098] SQLServerAgent terminated (normally)
Error Log details:
2016-06-23 00:00:25.030spid30sThis instance of SQL Server has been using a process ID of 6064 since 6/22/2016 11:41:29 PM (local) 6/23/2016 4:41:29 AM (UTC). This is an informational message only; no user action is required.
2016-06-23 00:22:06.330spid53Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2016-06-23 00:22:06.550spid53Using 'xpstar.dll' version '2014.120.2568' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2016-06-23 02:12:26.900spid54Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2016-06-23 02:12:26.980spid54Using 'xplog70.dll' version '2014.120.2000' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2016-06-23 02:14:56.250spid53Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2016-06-23 02:15:27.400spid53Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
Event viewer details:
Event ID: 103
SQLServerAgent could not be started (reason: Unable to connect to server 'MSSQLSERVER'; SQLServerAgent cannot start).
Action Items:
Enabled the agent by using sp_configure 'Agent XPs',1
Validated the alias there are no alias in configuration manager.
Shared memory, NamedPipes, TCPIP protocols are enabled.
Provided the sysadmin privileges to the service account
Provided the full control to the drive where sqlagent.exe is available
We could see ServerHost MSSQLSERVER in registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\SQLServerAgent
Thanks,
I’m nobody but still I’m somebody to someone………….
June 23, 2016 at 2:13 am
Is this for a new installation? If so, have you changed the service account after completing the installation, or did you specify the one you are using during the installation? If it was changed, was it done using SQL Server Configuration Manager?
Is SQL Server running on the default port or has it been changed? Have you tried restarting the SQL Server instance?
Also check to make sure that the account being used for the SQL Server agent service has the run as a service permission.
Have you looked in the SQL log (not agent) to see if there may be more info there, or the Windows event log?
June 23, 2016 at 3:22 am
Yes, it is for 2014 new installation on 2012 R2
Installation procedure:
After installing SQL 2014 DB engine was not online
Disabled the SSL and TSL
Updated CU13
DB engine was online
Followed the below article and installed all the client components.
https://support.microsoft.com/en-us/kb/3135244
Security Accounts which i have given at the time of installation were not reflected
Added the security accounts by bringing the server in single user mode and able to connect
Yes, SQL server is running on default port.
Yes restarted SQL Server and machine many times
Windows and error log details are updated in the above comment
Thanks,
I’m nobody but still I’m somebody to someone………….
June 23, 2016 at 4:57 am
It's probably worth changing the SQL Agent account temporarily to see if it will run under a different account; I would suggest changing it to the virtual account installed alongside SQL Server, which should just be 'NT SERVICE\SQLSERVERAGENT'.
If you do that and it works successfully then it is likely down to the configuration of your account. Just double check that within Windows it is assigned the run as a service permission.
If that does not work then I would try doing a repair of the installation.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply