locked
SQL Server 2005 Cluster setup RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi all 

     

    I tried to setup SQL Server 2005 on windows server 2003 R2 clustered but failed setup progress not start, I try the following method install SQL Server on “Node A” only and start join the other nodes (B ,and C ) I successfully join Node B but every time i tried to start setup in order join node C get the following message 

     

    Setup failed to start on the remote machine. Check the Task scheduler event 
    log on the remote machine.'

     

    Kindly note that, I check the task scheduler services is running on both nodes

    No one log on the third node during installation “Node C”

    I restart the node C multiple times to make sure no one log on the node

     

    Kindly I need advice regarding this issue urgently, thanks In advance

    Volcano , "DATA is the Focus, Business is the Target”"
    Friday, September 11, 2009 1:03 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Okay, lets not get carried away with saying things are wrong with the Cluster on NodeC. Lets look at some "DATA". It might be possible, the logs will clear that out for us.
    sql_guy, let me know if the symptoms I am listing are what you are observing :-

    a) As soon as you click on Add/Node, the SCC check runs and immediately fails
    b) The setup doesnt event start & the active node is telling you - passive node failed

    Please make sure the following are true :-

    1) The Remote Registry service is running on Node C
    2) The Task Scheduler is running on Node C
    3) The account you are logged into active node to do the add node operation has Admin rights on Node C

    A simple way to isolate the problem is this

    1) From the active node, access node C using \\nodeC\ and then go to scheduled tasks
    2) Created a test task to open cmd.exe and see if this works. If this doesnt something is wrong with your task scheduler on nodeC.
    3) If this works or not, either ways check the TAsk Scheduler logs. They are available in Advanced Menu -> View Log in the Scheduler Tasks Screen

    Above log will give you a Win32 Error to point you in the right direction. Let me know if the above helped ...
    Patience is a Virtue... So is "Delayed IO" :)
    Saturday, September 12, 2009 7:42 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Why aren't you just installing all three nodes of SQL at the same time like the installer lets you do? Doing it node by node makes no sense with that particular installer unless you have a good reason to do it that way. If we were talking SQL 2K8, it is a node-by-node, instance-by-instance install process.

    I would also check to see things like permissions, can Node C access the install point, etc.
    Allan Hirt Blog: http://www.sqlha.com/blog Author: Pro SQL Server 2008 Failover Clustering (out now!)
    Friday, September 11, 2009 4:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I already tried to Install all nodes together but i faced problem which is the setup progress not started,  so I use this way as described above

    Volcano , "DATA is the Focus, Business is the Target”"
    Friday, September 11, 2009 7:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It sounds like you have fundamental issues you need to resolve with your underlying cluster configuration since the install works just fine across all of the nodes - I've done 3 and 4 node clusters with SQL 2K5 numerous times.
    Allan Hirt Blog: http://www.sqlha.com/blog Author: Pro SQL Server 2008 Failover Clustering (out now!)
    Friday, September 11, 2009 9:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Okay, lets not get carried away with saying things are wrong with the Cluster on NodeC. Lets look at some "DATA". It might be possible, the logs will clear that out for us.
    sql_guy, let me know if the symptoms I am listing are what you are observing :-

    a) As soon as you click on Add/Node, the SCC check runs and immediately fails
    b) The setup doesnt event start & the active node is telling you - passive node failed

    Please make sure the following are true :-

    1) The Remote Registry service is running on Node C
    2) The Task Scheduler is running on Node C
    3) The account you are logged into active node to do the add node operation has Admin rights on Node C

    A simple way to isolate the problem is this

    1) From the active node, access node C using \\nodeC\ and then go to scheduled tasks
    2) Created a test task to open cmd.exe and see if this works. If this doesnt something is wrong with your task scheduler on nodeC.
    3) If this works or not, either ways check the TAsk Scheduler logs. They are available in Advanced Menu -> View Log in the Scheduler Tasks Screen

    Above log will give you a Win32 Error to point you in the right direction. Let me know if the above helped ...
    Patience is a Virtue... So is "Delayed IO" :)
    Saturday, September 12, 2009 7:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Did you ever get to try the steps I had outlined ?? If yes, please post back the results..
    Patience is a Virtue... So is "Delayed IO" :)
    Thursday, October 8, 2009 11:10 PM