I have 2 environments which reside on virtual servers on a 2-node active/active cluster for SQL Server 2005.
They are both offline and cannot be brought online by the "Bring Online" or "Move Group" options in Cluster Administrator.
The software lies on Windows Server 2003, Service pack 2.
This is issue is very urgent, please assist.
Regards Sean.
Please see error details below:
"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. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)"
Details Product: SQL Server ID: 2 Source: MSSQLServer Version: 10.0 Component: SQLEngine Message: An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
Explanation SQL Server did not respond to the client request because the server is probably not started.
User Action Make sure that the server is started.
Version: 9.0 Component: SQLEngine Message: 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. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
Explanation SQL Server did not respond to the client request because the server is probably not started.
You need to use the MS SQL 2005 sql server configuration manager. Make sure you connect to the clustered instance to enable named pipes and/or tcp/ip. Or you may need to use the surface configuration tools. Unfortunately, it is not clear whether the issue is with the sql services not starting under the cluster administrator or something else is going on. Are the data drives accesible on the now "active node."
