SQL 2005 Cluster Port change problem.

  • Hi ALL,

    We have Active - Passive CLuster

     I made a little mistake. on the Cluster SQL configuration.

     

      SQL server Configuration Manager --> SQL server 2005 Network Configuration --> Protocols for MYDB

     

      Right clicked on TCP/IP --> Properties --> IP Addresses (TAB)

     

      Here i changed the "TCP Dynamic Ports" and " TCP Port" with same port number (2977),  accidental mistake.

     

      Now SQL server is failed to start. I see the below in Eventlog.

     

     

      Event Type: Error

      Event Source: MSSQL$MYDB

      Event Category: (2)

      Event ID: 26023

      Date:  2/23/2007

      Time:  4:09:03 PM

      User:  N/A

      Computer: SQL2005_64CLUSTER

      Description:

      Server TCP provider failed to listen on [ xxx.xxx.xxx.xxx <ipv4 2977].

      Tcp  port is already in use.

     

      For more information, see Help and Support Center at

      http://go.microsoft.com/fwlink/events.asp.

     

     

  • I believe you can change with SQL configuration Manager...

    How to configure an instance of SQL Server to listen on a specific TCP port or a dynamic port

    http://support.microsoft.com/kb/823938

    MohammedU
    Microsoft SQL Server MVP

  • the article in reference did not help . for a cluster .

    I have identical probelem.

    Any help is appreciated.

    I saw one reference where one could use cluster.resrouces and some walk throughs but for SQL 2005 it is not working .

  • I just looked up in Google again for good measure and I saw this link and it worked for me.

    It was so quick and easy.

    http://www.sqldbadiaries.com/2010/10/25/addremove-checkpoints-manually-on-a-cluster/

    get teh list of cluster resources in teh host by typong cluster res and identify teh name of the resource.

    In my case the SQL instance is named instance and so I had to modify the line accordingly.

    remove checkpoint with:

    cluster res "SQL Server" /removecheck: "Software\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLSERVER"

    Make the port changes in the SQL Server Configuration manager for the TCP protocol and start teh instance .

    Then run the following to add teh checkpoint.

    cluster res "SQL Server" /addcheck: "Software\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLSERVER"

    Fail over form node to node to verify that all is well.

    It was that simple and very quick.

    By the way , next time , I will choose a random/different value for the port number for fixed port thatn the dynamic one showing on the configuration manager.

Viewing 4 posts - 1 through 3 (of 3 total)

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