 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Clustering / June 2005named pipes
The cluster consists of two nodes and of two instances. One default sql instance and one another named instanse. To connect to the named instance all the clients have alias(done by cliconfg.exe), but when the instance fails over to another node no one can't connect to this named instance anymore. If i edit the alias to use the default instance pipe name, this helps! It seems named pipes don't fail over to another node.. Any suggestions? Thanks in advance. Andrew Have you run cliconfg.exe on both nodes, not just the "primary"?  SignatureTom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA SQL Server MVP Columnist, SQL Server Professional Toronto, ON Canada www.pinpub.com . The cluster consists of two nodes and of two instances. One default sql instance and one another named instanse. To connect to the named instance all the clients have alias(done by cliconfg.exe), but when the instance fails over to another node no one can't connect to this named instance anymore. If i edit the alias to use the default instance pipe name, this helps! It seems named pipes don't fail over to another node.. Any suggestions? Thanks in advance. Andrew I run cliconfg.exe on the clients side. The problem is that our end-user applications aren't ms sql instances aware of and i need to provide an alias. i can change the alias on the user machines via some kind of gpo etc.. Andrew Tom Moreau =BF=D1(): > Have you run cliconfg.exe on both nodes, not just the "primary"? > [quoted text clipped - 20 lines] > Thanks in advance. > Andrew This sounds strange. Have you tried removing the aliases from the client machines? SignatureTom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA SQL Server MVP Columnist, SQL Server Professional Toronto, ON Canada www.pinpub.com . I run cliconfg.exe on the clients side. The problem is that our end-user applications aren't ms sql instances aware of and i need to provide an alias. i can change the alias on the user machines via some kind of gpo etc.. Andrew Tom Moreau писал(а): > Have you run cliconfg.exe on both nodes, not just the "primary"? > [quoted text clipped - 20 lines] > Thanks in advance. > Andrew If i remove - i just can't connect.. Andrew Tom Moreau =D1(): > This sounds strange. Have you tried removing the aliases from the client > machines? [quoted text clipped - 42 lines] > > Thanks in advance. > > Andrew This sounds like either a DNS issue or that SQL Server is not listening on TCP/IP. Check out the Server Network Utility on your cluster - or the SQL Server errorlog to see what protocols SQL Server will "hear". Also, ensure that your clients are using TCP/IP. Check out their Client Network Utility to confirm. SignatureTom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA SQL Server MVP Columnist, SQL Server Professional Toronto, ON Canada www.pinpub.com . If i remove - i just can't connect.. Andrew Tom Moreau писал(а): > This sounds strange. Have you tried removing the aliases from the client > machines? [quoted text clipped - 43 lines] > > Thanks in advance. > > Andrew with tcp/ip everything is ok. I've a problem with named pipes. Our application isn't tcp/ip aware, just named pipes - thats all. Andrew Tom Moreau (): > This sounds like either a DNS issue or that SQL Server is not listening on > TCP/IP. Check out the Server Network Utility on your cluster - or the SQL [quoted text clipped - 65 lines] > > > Thanks in advance. > > > Andrew ok, for example Active-Active cluster. One instance server1, another one - server2\instance Since my application isnt't cluster aware i create an alias to connect via named pipes. - server alias: server2 - server name: server2\instance - pipe name: \\server2\pipe\MSSQL$INSTANCE\sql\query when server2 fails over to server1 i can't use my application. At this moment I can ping server2 successfully. If i change on the client the alias server2: - server alias: server2 (it's the same) - server name: server1 - pipe name: \\server1\pipe\\sql\query I can connect and can't use my application > ok, for example > Active-Active cluster. One instance server1, another one - [quoted text clipped - 15 lines] > > I can connect and can't use my application Just to make very sure, you do know the difference between the virtual server name and the node name? 'when server2 fails over to server1 i can't use my application' should be: 'when virtual server2 fails over to node1 i can't use my application' Clients should connect to the virtual server name and not to the not to the name of the physical server. SignatureHans Yes, you are right, i was wrong and should have said: "when virtual server2 fails over to node1 i can't use my application' " Clients do connect to the virtual server names Andrew I encountered the same thing today on a colleague's machine. He claimed that he had applied the most-recent service pack. In actual fact, NO service packs had ever been applied. I'd go with SP3a for now. SP4 has a couple of issues. SignatureTom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA SQL Server MVP Columnist, SQL Server Professional Toronto, ON Canada www.pinpub.com . Yes, you are right, i was wrong and should have said: "when virtual server2 fails over to node1 i can't use my application' " Clients do connect to the virtual server names Andrew Hi Tom, Indeed, sql sp4 has been applied already.. Andrew Tom Moreau =BF=D1(): > I encountered the same thing today on a colleague's machine. He claimed > that he had applied the most-recent service pack. In actual fact, NO [quoted text clipped - 17 lines] > > Andrew I'm sorry... reread my own article - i was wrong - sql sp 4 wasn't applied. was applied server 2003 sp1. Go to SP3a for now and then see if it persists. SignatureTom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA SQL Server MVP Columnist, SQL Server Professional Toronto, ON Canada www.pinpub.com . I'm sorry... reread my own article - i was wrong - sql sp 4 wasn't applied. was applied server 2003 sp1. Actually it has already been applied - Microsoft SQL Server 2000 - 8.00.818, no results.. Andrew > The cluster consists of two nodes and of two instances. One default sql > instance and one another named instanse. [quoted text clipped - 5 lines] > > It seems named pipes don't fail over to another node.. Any suggestions? Maybe some of the registry is not replicated. In the cluster registry there should be about 7 registry entries for each sql server resource which are used to replicate some of the sql registry keys. Check if they exist. Also check the contents of software\microsoft\microsoft sql server\instance\mssqlserver\supersocketnetlib\np\pipename on the problem node when sql is running there. The service account of the default instance should be able to read the registry key's of the named instance and vice versa. Sqlservers log mentions its listening on named pipes? What I think is kind of strange is that you are able to use the client network tools aliases but not tcp\ip. Your program should not even know about named pipes or tcp/ip. It just needs to talk to the sqldriver. Maybe its time to instal ethereal (http://www.ethereal.com/) on one of the clients. SignatureHans Thank you for your prompt reply! i checked registry settings - they are exist. I tried pipelist.exe to check pipes behaviour when moving the cluster groups - named pipes are moved between the nodes properly.. The Service account does have appropriate rights and SQL server is listening on TCP, Shared Memory, Named Pipes... as logs say.. Andrew > Thank you for your prompt reply! > [quoted text clipped - 4 lines] > The Service account does have appropriate rights and SQL server is > listening on TCP, Shared Memory, Named Pipes... as logs say.. Well, then the only hope is networkscanning wil reveal something. SignatureHans |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.