Post reply

new SQL2005 EE X64 instance -> unable to connect..

  • August 23, 2006 at 5:59 am

    #115108

    Scenario :

    2 node x64 Windows 2003 sp1

    2 instances of SQL2005 X64 sp1

    SQLBrowser running on both nodes

    All instances hosted at one node

    Install new sql2005 x64 instance at the "empty" node.

    ----

    After install (and activation) of another sql2005 x64 instance, noone is able to connect to the existing (and active) sql2005 instances of the cluster.

    After stop/start of SQLBrowser at the node, not hosting the new instance, everything works fine again.

    Is this by design

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • August 24, 2006 at 7:22 am

    #656560

    Have you tested this in x86 version?

    From BOL: When listening on IP_ANY, when you enable listening on specific IP's the user must configure the same TCP port on each IP, because SQL Server Browser returns the first IP/port pair it encounters.

    Does this mean that when you install a new clustered resource it will use a random port for the instance. You must then change the port of the instance to e.g. 1433, as the other instances, restart the instance sql service and then it will work? Probably a bug.

     

Viewing 2 posts - 1 through 1 (of 1 total)

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