"Sandeep" <Sandeep@discussions.microsoft.com> wrote in message
news:E108A627-06C3-4C3E-84DE-D628FDE8527A@microsoft.com...
> Hi,
>
> I need urgent help on SQL 2000 cluster based on Windows 2003 SP1. I have
> SQl
> 2000 cluster with one virtual server on Windows 2003 connected to HP EVA
> 5000
> SAN. One of my node failed & did basic steps like Evict the node & so on
> from exisitng setup. Later I built the node again with OS. Later on
> configured the node for SAN to have access for shared resources if needed.
> Later I run cluster service setup from the node which had resources online
> &
> it successfully added the second node to the cluster. I could failover
> Cluster Group from node 1 to 2 & vice versa but not the sql group as it
> says
> node unavailable. I guess I have to add the new node to Virtual server as
> well. I than tried to Run SQL 2000 setup to add this second node to SQL
> virtual serverr. on the screen needed to add this node name, I see my new
> node in the options for "unavailable node". I can click next where it asks
> me
> clusteradmin account name but not sure if that would be correct as I do
> not
> get option to ass this new node. Would appreciate if you could let me know
> what could be an issue. One of the document on the net said the one needs
> to
> shutdown Active node first before running cluster service setup so that
> the
> newly build node could have access to quorum disk. I did not do that but
> still it could identify all resources
>
> Currently my sql server is one 1st node. I am not sure if I need to
> install
> SQL server agin on the new node I built or just the service pack. Please
> help..
>
> Regards,
> Sandeep

"Michael Hotek" wrote:

> That doesn't make any sense. If the node adds successfully into the cluster
> and you can fail the cluster resources over to it without any error
> messages, there shouldn't be any reason that SQL Server setup will not allow
> you to add the node in. The only thing I can think of is that there might
> be a pending reboot. Also, do you have MSDTC configured into the cluster?
>
> --
> Mike
> Mentor
> Solid Quality Learning
> http://www.solidqualitylearning.com
>
>
> "Sandeep" <Sandeep@discussions.microsoft.com> wrote in message
> news:E108A627-06C3-4C3E-84DE-D628FDE8527A@microsoft.com...
> > Hi,
> >
> > I need urgent help on SQL 2000 cluster based on Windows 2003 SP1. I have
> > SQl
> > 2000 cluster with one virtual server on Windows 2003 connected to HP EVA
> > 5000
> > SAN. One of my node failed & did basic steps like Evict the node & so on
> > from exisitng setup. Later I built the node again with OS. Later on
> > configured the node for SAN to have access for shared resources if needed.
> > Later I run cluster service setup from the node which had resources online
> > &
> > it successfully added the second node to the cluster. I could failover
> > Cluster Group from node 1 to 2 & vice versa but not the sql group as it
> > says
> > node unavailable. I guess I have to add the new node to Virtual server as
> > well. I than tried to Run SQL 2000 setup to add this second node to SQL
> > virtual serverr. on the screen needed to add this node name, I see my new
> > node in the options for "unavailable node". I can click next where it asks
> > me
> > clusteradmin account name but not sure if that would be correct as I do
> > not
> > get option to ass this new node. Would appreciate if you could let me know
> > what could be an issue. One of the document on the net said the one needs
> > to
> > shutdown Active node first before running cluster service setup so that
> > the
> > newly build node could have access to quorum disk. I did not do that but
> > still it could identify all resources
> >
> > Currently my sql server is one 1st node. I am not sure if I need to
> > install
> > SQL server agin on the new node I built or just the service pack. Please
> > help..
> >
> > Regards,
> > Sandeep
>
>