Post reply

Network libraries TCP/IP Named Pipes

  • May 12, 2003 at 12:43 pm

    #59172

    Any input will be appreciated!!!

    **We have a SQL Server 2000 Cluster.

    **Server Network Utility is configured the same on both nodes.

    **Client Network utilities are configured the same on both nodes.

    **There are 4 application servers that access the clustered database.

    Last week all of the connections were using the TCP/IP libraries. We moved SQL Server to the other node, and now the connections are using a both Named Pipes and TCP/IP. Plus, we are not losing any connections now.

    Please, please, please, share any thoughts or opinions.

    Thanks,

    Jeff


    "Keep Your Stick On the Ice" ..Red Green

  • May 12, 2003 at 12:47 pm

    #456878

    Ooops

    I never said what I was looking for... I am hoping to find all/any reasons why there was a change in the use of the network libraries..

    << Jeff


    "Keep Your Stick On the Ice" ..Red Green

  • May 12, 2003 at 1:03 pm

    #456879

    Do you have any workstations configured with named pipe in client network utility to access SQL Serevr without going through your application servers?

    You can change the network access order by clicking the up and down arrow in client network library. Please make sure TCP/IP is set before the named pipe.

    Use following statement to find out who are using named pipe.

    select hostname, nt_domain, nt_username, net_library, loginame

    from sysprocesses

    where net_library <> ' '

    order by net_library

    Edited by - Allen_Cui on 05/12/2003 1:09:48 PM

  • May 12, 2003 at 1:39 pm

    #456882

    The client configuration never changed. Only the active node of the cluster. All client's are set with TCP/IP first. The odd thing is that the named pipe connections are working...TCP/IP were failing at random.

    Still trying to figure out why the use of the network libraries changed when the cluster was failed over.


    "Keep Your Stick On the Ice" ..Red Green

  • May 12, 2003 at 1:44 pm

    #456883

    when you installed SS2K was tcp/ip and named pipes enabled/selected?

  • May 12, 2003 at 1:48 pm

    #456884

    quote:

    TCP/IP were failing at random.

    Do you see any error messages for above failing?

    Check the network protocols configuration to see whether they are same on both nodes in Windows 2000.

  • May 12, 2003 at 1:52 pm

    #456886

    Nope. No errors on the SQL Server side. Only errors visible came through SAP.


    "Keep Your Stick On the Ice" ..Red Green

  • May 12, 2003 at 2:14 pm

    #456891

    We are running SAP too and the application servers connect to database using TCP/IP. Maybe you should search SAP notes for those errors.

  • May 13, 2003 at 3:10 am

    #456935

    Had a similar problem recently after an SP3 upgrade (SKL2K Active/Active cluster).

    With Named Pipes installed, the automatic TCP/IP port detection stopped working, and the only way to connect using TCP/IP was to create an alias server for the server with the actual TCP/IP port number using the Client Network Utility.

    After removing Named Pipes from both server and client, we were able to remove the Alias and the automatic port detection worked again!!

  • May 13, 2003 at 10:40 am

    #457006

    Is that W2K SP3 or SQL Server SP3?

    Just checking. Thanks!!


    "Keep Your Stick On the Ice" ..Red Green

  • May 14, 2003 at 1:39 am

    #457070

    The error was after a SQL2K upgrade to SP3.

  • May 14, 2003 at 7:48 am

    #457101

    This KB should answer your question.

    http://support.microsoft.com/default.aspx?scid=kb;en-us;328383

  • May 14, 2003 at 11:38 am

    #457140

    We installed a new instance of SQL2K. No one could connect to it. I checked and the client utilities all listed TCP/IP over named pipes. I changed the order so that named pipes was first and viola! people were able to connect.

    Patrick

    Quand on parle du loup, on en voit la queue

  • May 14, 2003 at 11:42 am

    #457142

    Check SQL Server errorlog to see whether you have an entry "SQL server listening on TCP, Shared Memory, Named Pipes.".

    Select * from sysprocesses to verify which protocol your users connect to SQL Server.

  • May 14, 2003 at 5:06 pm

    #457192

    ians,

    Did you check the failover capability after removing named pipes.We had a simillar problem and from what i understood from microsoft was that you do need named pipes for failover. we had to undergo registry changes. Can you please let me know about your failover capability at present and also let me know if you need any details for the registry change we underwent.

Viewing 15 posts - 1 through 15 (of 21 total)

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