3 nodes active/active/passive cannot failover

Hi,
I created 2 nodes active/passive and tested the failover.
It worked.
I added a 3rd nodes as active.
Now nothing can failover to the passive.
Any suggestions where I should start troubleshooting.
Thanks in advance.
I'd start by checking the NT eventlogs for any related error, and if
necessary checking the cluster log.
It would also help to observe more closely the behavior of the cluster when
you try to move the group to the 'passive node' Do you see certain resources
online there at least briefly? Does this happen to all the groups? If it's
just some group(s), it could be because you have not done the necessary setup
on the added node as required by the app in the group.
Linchi
"sqlapprentice" wrote:

> Hi,
> I created 2 nodes active/passive and tested the failover.
> It worked.
> I added a 3rd nodes as active.
> Now nothing can failover to the passive.
> Any suggestions where I should start troubleshooting.
> Thanks in advance.
|||Thank you Linchi,
I talked to MS premier support and I ran the SQLDiag.
They could not find anything.
SQLCluster services keeps failing.
Do I have a problem with my registry or ODBC or name resolution?
"Linchi Shea" wrote:
[vbcol=seagreen]
> I'd start by checking the NT eventlogs for any related error, and if
> necessary checking the cluster log.
> It would also help to observe more closely the behavior of the cluster when
> you try to move the group to the 'passive node' Do you see certain resources
> online there at least briefly? Does this happen to all the groups? If it's
> just some group(s), it could be because you have not done the necessary setup
> on the added node as required by the app in the group.
> Linchi
> "sqlapprentice" wrote:
|||Have you checked the Possible owners for the SQL resources?
SQLDiag is almost useless in troubleshooting a cluster issue. SQL
MPSReports gathers the information PSS needs.
Can the cluster resources move to all nodes?
32 bit or 64 bit?
Is this your setup?:
Instance one can live on node 1 or 2
Instance two can live on node 3 or 2
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.expertsrt.com - not your average tech Q&A site
"sqlapprentice" <sqlapprentice@.discussions.microsoft.com> wrote in message
news:BF44A9E3-A82D-4D1B-A4A3-0D45917C3E1E@.microsoft.com...[vbcol=seagreen]
> Thank you Linchi,
> I talked to MS premier support and I ran the SQLDiag.
> They could not find anything.
> SQLCluster services keeps failing.
> Do I have a problem with my registry or ODBC or name resolution?
> "Linchi Shea" wrote:
|||Can you do the following:
1. Stop the SQL Server
2. With the entire group shut down, move the group to another node
3. If it moves over, go to the Service Control applet, and start the SQL
Server service
4. Shut it down and repeat on the other node
5. If this works, then you cluster config is definitely the problem.
6. If something doesn't work, you are going to get an error of some kind in
the event logs that points to the issue
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:Ou2BG4AQGHA.5400@.TK2MSFTNGP09.phx.gbl...
> Have you checked the Possible owners for the SQL resources?
> SQLDiag is almost useless in troubleshooting a cluster issue. SQL
> MPSReports gathers the information PSS needs.
> Can the cluster resources move to all nodes?
> 32 bit or 64 bit?
> Is this your setup?:
> Instance one can live on node 1 or 2
> Instance two can live on node 3 or 2
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.expertsrt.com - not your average tech Q&A site
>
> "sqlapprentice" <sqlapprentice@.discussions.microsoft.com> wrote in message
> news:BF44A9E3-A82D-4D1B-A4A3-0D45917C3E1E@.microsoft.com...
>
|||Hi Michael,
I found out that the MDAC and the registry were missing the named instance
entries.
Not sure what happen.
I fixed the registry and MDAC and the clusters are working now.
I cannot understand why adding a third cluster node as active created so
much problems.
Thanks again for the great help.
"Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
news:Oi73qmNQGHA.4900@.TK2MSFTNGP09.phx.gbl...
> Can you do the following:
> 1. Stop the SQL Server
> 2. With the entire group shut down, move the group to another node
> 3. If it moves over, go to the Service Control applet, and start the SQL
> Server service
> 4. Shut it down and repeat on the other node
> 5. If this works, then you cluster config is definitely the problem.
> 6. If something doesn't work, you are going to get an error of some kind
in[vbcol=seagreen]
> the event logs that points to the issue
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
> news:Ou2BG4AQGHA.5400@.TK2MSFTNGP09.phx.gbl...
message[vbcol=seagreen]
necessary
>