Showing posts with label 2nd. Show all posts
Showing posts with label 2nd. Show all posts

Tuesday, March 27, 2012

Cluster service fails

I'm not able to start the cluster service on the 2nd node of our cluster.
O/S is 2003, with SQL 2000. The 2nd node is passive, and appears to join the
cluster but then it terminates unexpectedly.
We've tried using the Administrator account to start the server, but with
the same results.
The cluster service is fine on node 1.
What can I try to do in order to get the service to start?
Thanks,
Chris
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:7FE6F3AD-B838-414C-B216-D0CC84AE28F0@.microsoft.com...
> I'm not able to start the cluster service on the 2nd node of our cluster.
> O/S is 2003, with SQL 2000. The 2nd node is passive, and appears to join
the
> cluster but then it terminates unexpectedly.
>
My guess is it's having trouble seeing the Quorum resource. Make sure it
can view all the resources.

> We've tried using the Administrator account to start the server, but with
> the same results.
> The cluster service is fine on node 1.
> What can I try to do in order to get the service to start?
> Thanks,
> Chris

Thursday, March 22, 2012

cluster install 2nd node unavailable

Hi all,

Try to install sql 2005 x64 on a Win2003r2 x64 two node cluster.
All looks fine as far I get to the "cluster node configuration" dialog.
My second node is always displayed as "unavailable node" reason "unknown".

- I checked the logfiles but could not find any error.
- Installation user & cluster user are both local admins.
- Tried with sql 2005 x32 version -> same result.

What do I miss out here?
Any help is highly appreciated.

TIA
acki

as mentioned above installing the sql 2005 x32 Version results in same state -> node unavailable reason unknown

If try to install sql 2000 x32 my two nodes show up as configured nodes installation would continue without errors.

Any help is highly appreciated !

TIA
acki

|||Check the SQL error log, cluster log and event viewer log for more information.|||

Satya,

None of the logs shows anything unusual !

|||Can you check thru this http://msdn2.microsoft.com/en-us/library/ms179530.aspx link and confirm whether you have following in same fashion.|||

Satya,
I know the mentioned kb article.
I'm not a newbe in installing sql server clusters, have done it a dozent times (x32) but never had troubles like this.

At the beginning setupjob checks BOTH nodes for possible installation. All looks fine there!
As mentioned already non of the logs (eventlog, clusterlog, sql inst. log) shows anything unusual or error (in my eyes).
Prerequisits and pre installation steps are all done...

The funny thing is installing a sql 2000 (x32) cluster would work (so there could nothing be wrong with the cluster inst.)

|||

ok, after setting up a packet sniffer and running behind the bits and bytes I finally found the solution to this problem.

Make sure the "Remote Registry" service is running on second (inactive) node!

HTH
acki

cluster install 2nd node unavailable

Hi all,

Try to install sql 2005 x64 on a Win2003r2 x64 two node cluster.
All looks fine as far I get to the "cluster node configuration" dialog.
My second node is always displayed as "unavailable node" reason "unknown".

- I checked the logfiles but could not find any error.
- Installation user & cluster user are both local admins.
- Tried with sql 2005 x32 version -> same result.

What do I miss out here?
Any help is highly appreciated.

TIA
acki

as mentioned above installing the sql 2005 x32 Version results in same state -> node unavailable reason unknown

If try to install sql 2000 x32 my two nodes show up as configured nodes installation would continue without errors.

Any help is highly appreciated !

TIA
acki

|||Check the SQL error log, cluster log and event viewer log for more information.|||

Satya,

None of the logs shows anything unusual !

|||Can you check thru this http://msdn2.microsoft.com/en-us/library/ms179530.aspx link and confirm whether you have following in same fashion.|||

Satya,
I know the mentioned kb article.
I'm not a newbe in installing sql server clusters, have done it a dozent times (x32) but never had troubles like this.

At the beginning setupjob checks BOTH nodes for possible installation. All looks fine there!
As mentioned already non of the logs (eventlog, clusterlog, sql inst. log) shows anything unusual or error (in my eyes).
Prerequisits and pre installation steps are all done...

The funny thing is installing a sql 2000 (x32) cluster would work (so there could nothing be wrong with the cluster inst.)

|||

ok, after setting up a packet sniffer and running behind the bits and bytes I finally found the solution to this problem.

Make sure the "Remote Registry" service is running on second (inactive) node!

HTH
acki