Re: named pipes

Tech-Archive recommends: Fix windows errors by optimizing your registry

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@xxxxxxx> wrote in message
news:1118242276.507481.291570@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
If i remove - i just can't connect..

Andrew

Tom Moreau писал(а):
> 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@xxxxxxx> wrote in message
> news:1118228154.834811.10600@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> 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@xxxxxxx> wrote in message
> > news:1118052606.954693.185910@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > 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

.

Relevant Pages

  • RE: Cluster Configurations
    ... is there any advantage of creating a 8-Node cluster in SQL server then? ... I think we decided the 8-node configuration to better use the hardware. ... Named Instance -> Failover to Node 4 ...
    (microsoft.public.sqlserver.clustering)
  • Re: Setup fails..Please help...URGENT.
    ... Windows 2003-Based Cluster Fails ... Microsoft SQL Server MVP ... > In the NT 4 domain I was able to run the setup and create named instance ... or message DLL files to display messages from a remote computer. ...
    (microsoft.public.sqlserver.clustering)
  • C++ and Dot Net Jobs
    ... Please find the list of Active jobs with our Clients. ... Strong object-oriented analysis and design skills and experience. ... Experience developing applications under the Windows.NET framework ... Experience developing applications using SQL Server 2000. ...
    (comp.lang.cpp)
  • Re: named pipes
    ... Andrew ... > Columnist, SQL Server Professional ... > I run cliconfg.exe on the clients side. ... >> can't connect to this named instance anymore. ...
    (microsoft.public.sqlserver.clustering)
  • Re: MS Access Reports and VB.NET Program
    ... think that I want to ship a 30mb .NET framework to each of my clients? ... Barns & Noble has some books that could help you learn .NET. ... It is Access TIMES eCommerce TIMES Sql Server. ... that you actually posted how to execute the report using a macro. ...
    (microsoft.public.dotnet.languages.vb)