Move to node 1 to node2 automatically disconnect SQL SERVER connection

Question

Move to node 1 to node2 automatically disconnect SQL SERVER connection

SQL Galaxy

One Orange Chip

Points: 29472
More actions
October 14, 2011 at 12:50 am

#249409

1. windows 2008 R2 Enterprise edition
2. SQL SERVER 2008 R2 Enterprise edition.
Two server network configuration as below
1. Public N/W
2. Backup N/W
3. Heart beat connected between two server.
this cluster setup configured at ISCSI
1. windows Cluster object
2. MSDTC cluster object - static IP config & connected to shared storage volume at NAS
3. SQL SERVER cluster Object.- static IP config & data, log, tempdb files are connected to shared storage volume at NAS
after that I have successfully installed cluster failover setup in corporate domain controller. also add second node.
for the testing purpose during data insert total(20000 records) into database, I changed and move to Node 2 through Failover Cluster Manager. In this case I got the error like as below
Msg 2, Level 20, State 0, Line 0
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
after that I try to connect through SSMS at client side, but not able to connect & facing same error.
I got the connection after move Node 2 to Node 1.
Please tell me & suggestion, what could be issue when move to node 1 to node 2 then automatically disconnect SQL SERVER connection?
Thanks in advance
ananda

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

Perry Whittle SSC Guru Points: 234013 More actions · Answer 1

ananda.murugesan (10/14/2011)
after that I have successfully installed cluster failover setup in corporate domain controller.

not sure what you mean by this?

ananda.murugesan (10/14/2011)
also add second node.

so you ran sql server setup on cluster node 2 and joined the clustered instance???

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

SQL Galaxy One Orange Chip Points: 29472 More actions · Answer 2

Perry Whittle (10/14/2011)
ananda.murugesan (10/14/2011)
after that I have successfully installed cluster failover setup in corporate domain controller.
not sure what you mean by this?
In first Node 1 - Install New SQL SERVER failover clustering setup, this one successfully installed after that applied SQL2KR2 SP1
ananda.murugesan (10/14/2011)
also add second node.
so you ran sql server setup on cluster node 2 and joined the clustered instance???

In Second Node 2 - Install Add Node to SQL SERVER failover Cluster. after that applied SQL2KR2 SP1

thanks

ananda

SQL Galaxy One Orange Chip Points: 29472 More actions · Answer 3

Please tell me & suggestion, what could be issue when move to node 1 to node 2 then automatically disconnect SQL SERVER connection in client side but server itself SQL running and able connect SSMS? current owner is Node 2.

thanks

ananda

Perry Whittle SSC Guru Points: 234013 More actions · Answer 4

You're going to need to supply more information.

Have you checked the windows event logs and the cluster.log

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

Perry Whittle SSC Guru Points: 234013 More actions · Answer 5

ananda.murugesan (10/14/2011)
after that I have successfully installed cluster failover setup in corporate domain controller.

not sure what you mean by this, can you explain further please?

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

SQL Galaxy One Orange Chip Points: 29472 More actions · Answer 6

Perry Whittle (10/15/2011)
ananda.murugesan (10/14/2011)
after that I have successfully installed cluster failover setup in corporate domain controller.
not sure what you mean by this, can you explain further please?

after that I have successfully installed cluster failover setup in corporate domain controller.

"This is for installed sql server 2K8 r2 new failover clustering in server, that server configured & mapping coporate AD and domain."

Devendrakumar SSC-Forever Points: 42493 More actions · Answer 7

Msg 2, Level 20, State 0, Line 0
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

At the moment I can suggest following:

•Crosscheck Public & Private network.

•Crosscheck ports availability

•Crosscheck the firewall

I am sure you might have missed on few of important steps for SQL Server 2008 clustering. Please go through these articles.

Before Installing Failover Clustering

http://msdn.microsoft.com/en-us/library/ms189910.aspx

Installing a SQL Server 2008 R2 Failover Cluster

http://msdn.microsoft.com/en-us/library/ms179410.aspx

How to: Add or Remove Nodes in a SQL Server Failover Cluster (Setup)

http://msdn.microsoft.com/en-us/library/ms191545.aspx

MysteryJimbo SSC-Insane Points: 24203 More actions · Answer 8

ananda.murugesan (10/14/2011)
Please tell me & suggestion, what could be issue when move to node 1 to node 2 then automatically disconnect SQL SERVER connection?
Thanks in advance
ananda

Some of the information you've given I dont fully understand. However, based on the above quote it seems you are surprised that you connection got killed when you failed over the cluster. This is expected as during failover all resources are shutdown and moved. Expected behaviour.

Shaneoneil142 SSC Rookie Points: 47 More actions · Answer 9

nice

<a href="http://www.visaexpress.net/russia/#11">visa to russia</a>
<a href="http://www.visaexpress.net/russia/#12">russian visa</a>
<a href="http://www.visaexpress.net/united-states-passport/#13">passport renewal</a>
<a href="http://www.visaexpress.net/#14">passport</a>

SQL Galaxy One Orange Chip Points: 29472 More actions · Answer 10

Hi,

Thanks to all for reply..

At the moment I can suggest following:

• Crosscheck Public & Private network.

• Crosscheck ports availability

• Crosscheck the firewall

Resolved issues, due to domain firewall is not disbaled in Node 2, after disabled it, It was working fine and no disconnect from Node 2 at client side.

thanks

ananda