go to SQL Server configuration manager and check the protocols
madhu
See the screencast on my site for more information about enabling the protocols.
Jens K. Suessmeyer.
---
http://www.sqlserver2005.de
---
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
I have checked the protocols and change them. But the problem remains.
Nice idea those Screencasts.
Regards, Iztok
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
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
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