December 5, 2008 at 8:32 am
We just installed our first 64 bit SQL Server on a two node cluster. When I try and run Surface Area Config I get an error:
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)(Microsoft SQL Server, Error:2).
I get this on the virtual server and on the active node.
In SSMS, virtual server name/properties/Connections has Allow remote connections to this server checked. Has anyone experienced this? Any ideas where else I should be looking?
A pic of the error message is attached.
December 5, 2008 at 12:50 pm
Change the connection from localhost to the actual SQL Server Virtual Name.
There is a change computer link next to the text "Configure Surface Area for localhost"
December 5, 2008 at 1:19 pm
I uninstalled & reinstalled sql server. Then instead of getting the named pipes provider error when trying Surface Area Config I was getting message "You must connect from the virtual server" or something to that effect. Even when I was on the virtual server. Still, it was just a message and not an error so I felt the reinstall was worthwhile.
So I was on the active node physical server and took the "change computer" option you mention in the Surface Area Config tool and connected to the virtual server. I was then able to run the utility without error. So yes, you are correct, that option works. Thanks for the response. I would have posted my findings earlier, but I was busy doing the same thing again on a second 'test' system.
December 5, 2008 at 1:44 pm
Cool. I think that the issue is essentially SQL uses the the machines windows server name env. variable to connect for the "locahost" instance. So it try's to connect to \MSSQLServer by default. However in the cluster this instance does not exist as it uses a virtual name and not the physical machines name. Even though you run from the active node it still pulls that nodes name vs the virtual name.... or atleast thats my understanding, so thats why it can not connect. Glad to see you got it working.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply