named 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"?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"kreit" <kreit@.mail.ru> wrote in message
news:1118052606.954693.185910@.g47g2000cwa.googlegr oups.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 =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
> Have you run cliconfg.exe on both nodes, not just the "primary"?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118052606.954693.185910@.g47g2000cwa.googlegr oups.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?
>=20
>=20
>=20
> Thanks in advance.
> Andrew
|||This sounds strange. Have you tried removing the aliases from the client
machines?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"kreit" <kreit@.mail.ru> wrote in message
news:1118228154.834811.10600@.o13g2000cwo.googlegro ups.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"?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118052606.954693.185910@.g47g2000cwa.googlegr oups.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
|||If i remove - i just can't connect..
Andrew
Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):[vbcol=seagreen]
> This sounds strange. Have you tried removing the aliases from the client
> machines?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118228154.834811.10600@.o13g2000cwo.googlegro ups.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 =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
|||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.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"kreit" <kreit@.mail.ru> wrote in message
news:1118242276.507481.291570@.f14g2000cwb.googlegr oups.com...
If i remove - i just can't connect..
Andrew
Tom Moreau писал(а):[vbcol=seagreen]
> This sounds strange. Have you tried removing the aliases from the client
> machines?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118228154.834811.10600@.o13g2000cwo.googlegro ups.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 писал(а):
|||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 =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
> 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, ensu=
re
> that your clients are using TCP/IP. Check out their Client Network Utili=
ty[vbcol=seagreen]
> to confirm.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "kreit" <kreit@.mail.ru> wrote in message
> news:1118242276.507481.291570@.f14g2000cwb.googlegr oups.com...
> If i remove - i just can't connect..
> Andrew
> Tom Moreau =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
nt[vbcol=seagreen]
ql[vbcol=seagreen]
s?[vbcol=seagreen]
|||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
|||kreit wrote:
> 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?
>
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\p ipename 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.
Hans
|||kreit wrote:
> 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
>
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.
Hans
sql