Re: dcpromo'd cluster node to non-domain controller, now SQL server won't start

Ok, Yes, I did repoint the DNS to the new DC's. I have now uninstalled
DNS from the node.

MSDTC is the sticking point... I have deleted it, then the SQL group
fails back and forth like a charm. Then recreated it on the node that
it doesn't want to run on.. fine, bring it online, it won't come
online, whole group fails back to the other node...damn thing :-( so,
did a bunch of searching and reading... it's quite like
http://support.microsoft.com/kb/900216 ... the resoure GUID for MSDTC
key does not have the full control permission for Network Service set.
So, I set it to full control as per the KB... try to move it over again
MSDTC doesn't come online, it all fails back, go check the key and it's
changed the key back.. and crashed the cluster service on that node ...
geesh, seems like I am so close to getting this to work now, but I
don't want to DCPROMO the other node down until I get this resolved.
Currently I have deleted the MSDTC resource so it is working ok.. and
from what I understand, MSDTC is mostly used during install/upgrades on
clusters, which I don't have any coming up immediately that I know of,
things are sort of at an ok stage... but don't want to leave it here
for long.

Rodney, anyone? ideas? Will have to open a call if not I guess, but
would really like to fix this one on my own if possible.

Cheers

HA!!! :-) forgot to press the post button here... and in the mean
time, deleted MSDTC again.
Moved the SQL group back to the node that MSDTC wouldn't run on.
Created MSDTC resource. Didn't bring it online, went to the registry,
gave permission for Full Control to Network Service, brought MSDTC
online IT WORKED!!! failed group to the other node, failed it back..
all good FINALLY. Thanks Rodney, your advice got me thru this one...
not sure if this sequence of events was particular to my installation
or not, but if anyone else has the problem, I'd advise them to do it in
that particular sequence.

Cheers - going to let this run for a few days and make sure it's nice
and stable and DCPROMO the other node.


Rodney R. Fournier [MVP] wrote:

Did you repoint DNS to the new DC's and not to itself? Did you uninstall DNS
too?

Next issue, delete MSDTC from within the cluster and then recreate it on the
new non-DC server within the correct group.

Stick with it, you are doing the right thing here! Never cluster DC/GC's.
Cheers,

Rodney R. Fournier

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner


<william.dossett@xxxxxxxxx> wrote in message
news:1160574223.628356.74060@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,

As per Microsofts Advice, I am trying to remove domain controller from
my cluster nodes.

I have two new servers for domain controllers. I have moved global
catalog server to them, and all the operation masters roles. This all
seemed to be working fine... has been for several weeks.

Today I dcpromo'd the one of the nodes, it was not a GCserver nor did
it have any operation masters roles. That all went fine. I rebooted,
and then tried to move the cluster group that contains my SQL server to
the non-domain controller node. It won't go.. It's something to do
with SQL server as I can move groups with just network names, IP
numbers and physical disks to the non-domain controller node.

I have done this several times and the SQL Server, SQL Server Agent,
SQL Server Fulltext and DTC never comes fully online. During the
course of events in the system eventlog, I first get a cluster service
failure:


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date: 11/10/2006
Time: 14:16:18
User: N/A
Computer: SCRATCHY
Description:
The Cluster Service service terminated unexpectedly. It has done this
1 time(s). The following corrective action will be taken in 60000
milliseconds: Restart the service.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

then immediately following it the DTC fails:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 11/10/2006
Time: 14:16:18
User: N/A
Computer: SCRATCHY
Description:
The Distributed Transaction Coordinator service terminated with
service-specific error 3221229584 (0xC0001010).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I've followed the links but am non-plussed... I think it is the DTC
which is causing the failure, or at least some component of SQL because
as I have said, other groups can be moved to this node with no errors.
I have checked the SQL server service account, verified passwords and
user permissions... even made the SQL service account a domain admin,
just to make sure it wasn't permissions/user rights causing the
problems...

Am pretty much at the end of my rope and ready to open a call with MS,
but if anyone has any ideas on what else I can try, I would hugely
appreciate a little help here. Damn thing has run perfectly for years
with both nodes being DCs and I was just following MS best practices
and now this happens and I'm down to my last node :-( if that fails
tonight, all hell will break loose for me.

Thanks for your help


.