SQL Server Performance

Instances not advertising

Discussion in 'SQL Server Clustering' started by digger, May 3, 2005.

  1. digger New Member

    Hi,
    Can anyone help:

    I have an Active / active cluster using windows 2003 & SQL 2000 sp3a. Each node has 2 instances on them at the moment. I am unable to connect to any of the instances unless I set up an alias on all the client machines including the port number that each instance is using. Our support company has come up with the suggestion of not enough memory effecting the advertising process or the need to completely rebuild the cluster.

    Any other ideas?

    digger
  2. derrickleggett New Member

    Log a Microsoft support ticket. It costs $249 if you don't have a support agreement. It sounds like your support company is crazy.

    MeanOldDBA
    derrickleggett@hotmail.com

    When life gives you a lemon, fire the DBA.
  3. Argyle New Member

    The instances are using dynamic ports since not all can use 1433. If you are not specifying a port in our connection string a request will be sent to port 1434 UDP asking for the ports the instances are currently using. If port 1434 UDP is blocked in a firewall or router (which is common after the slammer virus) you will not be able to connect to the instances without specifying the port in your connectionstring. Also your clients need MDAC 2.6 or higher to be able to connect to the instances using dynamic ports.

  4. digger New Member

    Thanks, Argyle. There is no firewall involved at the moment, the clients are on the same network. The clients are XP with MDAC 2.7.

    I'll check to see if I can detect port 1434 being open for listening on the cluster.
  5. derrickleggett New Member

    Wow, I was in a really bad mood that day. Sorry guys.

    MeanOldDBA
    derrickleggett@hotmail.com

    When life gives you a lemon, fire the DBA.
  6. joettu New Member

    I have been round and round with Microsoft for over a year on this same issue. Last I have heard was that this was actually a bug that was fixed at one time, but accidentally was not rolled into later builds. Therefore, it does not appear to be in the builds that some of us are running.

Share This Page