Along with performance issues, I also provide consultancy in other break-fix issues like service not starting etc. These are not run of the mill, but on specific cases only. I always suggest my clients to search on my blog first and then contact me if needed. This is a great way to scale and make people empowered when it comes to solving some of the trivial issues that they might have encountered for SQL Server Agent.
Here is the one of the situation where SQL Agent was not able to start in Clustered environment. When we try to start from the SERVICES.msc, it is going to run the state and then in 30 Sec or so stops automatically. As usual, I have asked for SQL Agent Log which is at the same location as SQL Server ERRORLOG.
Here is the content of SQLAgent.OUT file.
2016-05-07 06:44:03 – ?  Microsoft SQLServerAgent version 11.0.2100.60 (X64 unicode retail build) : Process ID 9252
2016-05-07 06:44:03 – ?  The SQL Server Agent startup service account is Super\SVC.
2016-05-07 06:44:34 – !  SQL Server does not accept the connection (error: 53). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2016-05-07 06:44:34 – !  Unable to connect to server ‘(local)’; SQLServerAgent cannot start
2016-05-07 06:44:40 – !  SQLServer Error: 53, Named Pipes Provider: Could not open a connection to SQL Server . [SQLSTATE 08001] 2016-05-07 06:44:40 – !  ODBC Error: 0, Login timeout expired [SQLSTATE HYT00] 2016-05-07 06:44:40 – !  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-05-07 06:44:40 – !  Logon to server ‘(local)’ failed (DisableAgentXPs)
2016-05-07 06:44:40 – ?  SQLServerAgent terminated (normally)
Based on above, it is clear that SQL Server Agent is not able to connect to SQL Server with below error.
A network-related or instance-specific error has occurred while establishing a connection to SQL Server. The 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.
This is a very generic error which can happen due to many reasons. One of my famous blog for this error is below
Solution / Fix:
For this client, I found that it is a SQL default instance running with Non-default port (port other than 1433). So I started SQL Server Browser service on both the nodes, but still there was no luck. Later found that this was due to name resolution issue with the DNS so to fix the issue, we added the TCP alias on both nodes and that fixed the issue.
SQLCLUSTER – SQL Server Virtual Server Name
Port – SQL listening port
Protocol – TCP/IP
Server – IP Address for SQL Clustered instance.
Did you face similar issue is clustered about resource not coming online? When did it happen for you and what did you do then? Please feel free to share your experience via the comments.
Reference: Pinal Dave (https://blog.sqlauthority.com)