Morning All
I am having a issue with my SQLServer install, were after a reboot of the VM the agent fails to start. Once manually starting the agent it runs fine.
Please see below SQLAgent log
2016-09-06 07:20:46 - ? [100] Microsoft SQLServerAgent version 12.0.4213.0 (X64 unicode retail build) : Process ID 2904 2016-09-06 07:20:46 - ? [495] The SQL Server Agent startup service account is DOMAIN\DBA_SQL_AGNT_PD. 2016-09-06 07:21:16 - ! [150] SQL Server does not accept the connection (error: 258). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start. 2016-09-06 07:21:16 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start 2016-09-06 07:21:17 - ? [000] Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install. [SQLSTATE 01000] (Message 15457) 2016-09-06 07:21:17 - ? [098] SQLServerAgent terminated (normally)
and please see SQLServer log during those times
2016-09-06 07:20:40.87 Server SQL Server detected 2 sockets with 2 cores per socket and 2 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required. 2016-09-06 07:20:40.87 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2016-09-06 07:20:40.87 Server Detected 4095 MB of RAM. This is an informational message; no user action is required. 2016-09-06 07:20:40.87 Server Using locked pages in the memory manager. 2016-09-06 07:20:41.21 Server Default collation: Latin1_General_CI_AS (us_english 1033) 2016-09-06 07:20:44.27 Server This instance of SQL Server last reported using a process ID of 1744 at 06/09/2016 07:18:54 (local) 06/09/2016 06:18:54 (UTC). This is an informational message only; no user action is required. 2016-09-06 07:20:44.27 Server The maximum number of dedicated administrator connections for this instance is '1' 2016-09-06 07:20:44.28 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 2016-09-06 07:20:44.28 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. 2016-09-06 07:20:44.35 spid7s Starting up database 'master'. 2016-09-06 07:20:44.74 Server CLR version v4.0.30319 loaded. 2016-09-06 07:20:44.88 spid7s Resource governor reconfiguration succeeded. 2016-09-06 07:20:44.89 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required. 2016-09-06 07:20:44.91 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required. 2016-09-06 07:20:45.13 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\. 2016-09-06 07:20:45.31 spid7s Error: 25602, Severity: 17, State: 22. 2016-09-06 07:20:45.31 spid7s The target, "5B2DA06D-898A-43C8-9309-39BBBE93EBBD.package0.event_file", encountered a configuration error during initialization. Object cannot be added to the event session. The operating system returned error 3: 'The system cannot find the path specified. ' while creating the file 'D:\DBAdmin\Extended Events\Waits\Waits_0_131176164452790000.xel'. 2016-09-06 07:20:45.34 spid7s Error: 25710, Severity: 16, State: 1. 2016-09-06 07:20:45.34 spid7s Event session "Waits" failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems. 2016-09-06 07:20:45.34 spid7s Error: 25709, Severity: 16, State: 1. 2016-09-06 07:20:45.34 spid7s One or more event sessions failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems. 2016-09-06 07:20:45.37 spid7s SQL Trace ID 1 was started by login "sa". 2016-09-06 07:20:45.48 spid7s Server name is 'MYSERVER'. This is an informational message only. No user action is required. 2016-09-06 07:20:45.79 spid15s A self-generated certificate was successfully loaded for encryption. 2016-09-06 07:20:45.80 spid15s Server is listening on [ 'any' <ipv6> 1433]. 2016-09-06 07:20:45.80 spid15s Server is listening on [ 'any' <ipv4> 1433]. 2016-09-06 07:20:45.80 spid15s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ]. 2016-09-06 07:20:45.80 spid15s Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ]. 2016-09-06 07:20:45.81 Server Server is listening on [ ::1 <ipv6> 1434]. 2016-09-06 07:20:45.81 Server Server is listening on [ 127.0.0.1 <ipv4> 1434]. 2016-09-06 07:20:45.81 Server Dedicated admin connection support was established for listening locally on port 1434. 2016-09-06 07:20:45.83 spid15s SQL Server is now ready for client connections. This is an informational message; no user action is required. 2016-09-06 07:20:45.84 Server 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. 2016-09-06 07:20:45.90 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/MYSERVER.domain.com ] for the SQL Server service. 2016-09-06 07:20:45.90 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/MYSERVER.domain.com:1433 ] for the SQL Server service. 2016-09-06 07:21:03.49 Logon Error: 18456, Severity: 14, State: 38. 2016-09-06 07:21:03.49 Logon Login failed for user 'DOMAIN\DBA_SQL_INST_PD'. Reason: Failed to open the explicitly specified database 'ReportServer'. [CLIENT: <local machine>] 2016-09-06 07:21:05.72 Logon Error: 18456, Severity: 14, State: 38. 2016-09-06 07:21:05.72 Logon Login failed for user 'DOMAIN\DBA_SQL_INST_PD'. Reason: Failed to open the explicitly specified database 'ReportServer'. [CLIENT: <local machine>] 2016-09-06 07:21:08.74 spid16s A new instance of the full-text filter daemon host process has been successfully started. 2016-09-06 07:21:08.97 spid17s Starting up database 'msdb'. 2016-09-06 07:21:08.97 spid11s Starting up database 'mssqlsystemresource'. 2016-09-06 07:21:08.97 spid20s Starting up database 'distribution'. 2016-09-06 07:21:08.97 spid21s Starting up database 'DB_ADMIN'. 2016-09-06 07:21:08.97 spid22s Starting up database 'ADMIN'. 2016-09-06 07:21:08.97 spid23s Starting up database 'ADMIN6'. 2016-09-06 07:21:08.97 spid24s Starting up database 'TTL_DB_MASTER'. 2016-09-06 07:21:08.97 spid27s Starting up database 'ADMIN5'. 2016-09-06 07:21:08.97 spid28s Starting up database 'ReportServer'. 2016-09-06 07:21:08.97 spid29s Starting up database 'ReportServerTempDB'. 2016-09-06 07:21:08.99 spid11s The resource database build version is 12.00.4100. This is an informational message only. No user action is required. 2016-09-06 07:21:09.00 spid26s Starting up database 'TTL_DB_ANALYSIS'. 2016-09-06 07:21:09.00 spid25s Starting up database 'TTL_DB_ADMIN'. 2016-09-06 07:21:09.19 spid11s Starting up database 'model'. 2016-09-06 07:21:09.69 spid11s Clearing tempdb database. 2016-09-06 07:21:10.43 Server Software Usage Metrics is enabled. 2016-09-06 07:21:11.93 spid11s Starting up database 'tempdb'. 2016-09-06 07:21:15.37 spid34s Server is listening on [ 'any' <ipv6> 4024]. 2016-09-06 07:21:15.37 spid34s Server is listening on [ 'any' <ipv4> 4024]. 2016-09-06 07:21:15.38 spid34s The Service Broker endpoint is now listening for connections. 2016-09-06 07:21:15.41 spid34s The Database Mirroring endpoint is in disabled or stopped state. 2016-09-06 07:21:15.60 spid34s Service Broker manager has started. 2016-09-06 07:21:15.98 spid7s Recovery is complete. This is an informational message only. No user action is required. 2016-09-06 07:21:16.02 spid7s Launched startup procedure 'sp_MSrepl_startup'. 2016-09-06 07:21:16.10 spid28s The activated proc '[MAIN].[PROCESS_SERVER_CONFIGURATION_EVENT]' running on queue 'DB_ADMIN.AUDIT.SERVER_CONFIGURATION_EVENT_NOTIFICATION_QUEUE' output the following: 'Invalid object name 'SERVER_CONFIGURATION_EVENT_NOTIFICATION_QUEUE'.'
i understand i could prorably just set the SQLAGENT service to a delayed start to get around this, but im keen to understand what is causing the holdup to prevent the agent connecting in the first place.
Thanks in advance