IztokZ


I have successfully installed SQL 2005 on W2K3 Cluster.
The problem is that SQL Server Agent won't start.
Below are the lines from SQLAGENT.OUT:

2007-03-15 09:40:02 - ! [298] SQLServer Error: 2, Named Pipes Provider: Could not open a connection to SQL Server [2]. [SQLSTATE 08001]
2007-03-15 09:40:02 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
2007-03-15 09:40:02 - ! [298] SQLServer Error: 2, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
2007-03-15 09:40:02 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2007-03-15 09:40:07 - ! [298] SQLServer Error: 2, Named Pipes Provider: Could not open a connection to SQL Server [2]. [SQLSTATE 08001]
2007-03-15 09:40:07 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
2007-03-15 09:40:07 - ! [298] SQLServer Error: 2, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
2007-03-15 09:40:07 - ! [382] Logon to server '(local)' failed (DisableAgentXPs)
2007-03-15 09:40:08 - [098] SQLServerAgent terminated (normally)

I have tried starting Agent with Domain Admin account. No luck. SQL Server is started.

Regards, Iztok



Re: SQLServerAgent cannot start

Madhu K Nair


go to SQL Server configuration manager and check the protocols

madhu







Re: SQLServerAgent cannot start

Jens K. Suessmeyer

See the screencast on my site for more information about enabling the protocols.

Jens K. Suessmeyer.

---
http://www.sqlserver2005.de
---






Re: SQLServerAgent cannot start

IztokZ

I have checked the protocols and change them. But the problem remains.

I have changed Local and Remote connections to Using TCP/IP only but lines in log are still the same.

2007-03-19 10:36:36 - ! [298] SQLServer Error: 2, Named Pipes Provider: Could not open a connection to SQL Server [2]. [SQLSTATE 08001]
2007-03-19 10:36:36 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
2007-03-19 10:36:36 - ! [298] SQLServer Error: 2, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
2007-03-19 10:36:36 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2007-03-19 10:36:42 - ! [298] SQLServer Error: 2, Named Pipes Provider: Could not open a connection to SQL Server [2]. [SQLSTATE 08001]
2007-03-19 10:36:42 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
2007-03-19 10:36:42 - ! [298] SQLServer Error: 2, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
2007-03-19 10:36:42 - ! [382] Logon to server '(local)' failed (DisableAgentXPs)
2007-03-19 10:36:42 - [098] SQLServerAgent terminated (normall

Do you have any other idea

Regards, Iztok





Re: SQLServerAgent cannot start

IztokZ

I have checked the protocols and change them. But the problem remains.

Nice idea those Screencasts.

Regards, Iztok





Re: SQLServerAgent cannot start

IztokZ

Additional info:

When I change Log on account in SQL Server Configuration Manager i get

WMI Provider Error. The server threw an exception. [0x80010105]

I was already searching if there are additional steps when SQL Server is installed on domain controller but didn't find any.

Any help would be very helpful.

Regards, Iztok





Re: SQLServerAgent cannot start

IztokZ

Problem solved thanks to excelent Microsoft's Support.

Have added virtual server's name as value in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\SQLServerAgent\ServerHost.

Regards, Iztok





Re: SQLServerAgent cannot start

dakotad

I have been perusing the Internet for this solution and it worked on our Cluster install. Man this was a lifesaver



Re: SQLServerAgent cannot start

mandan

I had this same issue. I did not change the registry. The "SQL Server Agent Properties" had a wrong "Alias local host server". I removed the wrong entry and left it empty. Restarted the cluster sql instance and worked just fine.

-Mani