I can't get my MSDTC instance to move to another node. . . .unless I down
the node where it's running. Then, the instance will travel. What's up
with that?

Can I just create another instance?

I've got three nodes in my W2K8 cluster. I have no other problems except
this one. Well, one other. You see, the cluster hosts two instances of
SQL2K8 and two of SQL2K5, and the SQL2K5 instances won't run if they're not
on the same node as MSDTC. So they're trapped wherever the MSDTC runs.

Check the MSDTC dependencies.

MSDTC needs to be dependent on both a disk resource and on a network name
resource. Otherwise it isn't a real clustered MSDTC instance.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Robert Hindla" <rhindla (AT) panix (DOT) com> wrote

Yes.


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Robert Hindla" <rhindla (AT) panix (DOT) com> wrote

Sorry, man, those params are there. Looks like another job for the
maintenance magician. Umm, can I just kill off the old MSDTC instance and
put another one?


On 3/19/10 9:18 AM, in article #gpAa92xKHA.5132 (AT) TK2MSFTNGP05 (DOT) phx.gbl, "Geoff
N. Hiten" <SQLCraftsman (AT) gmail (DOT) com> wrote:

OK, so my SQL2K5 instances were having difficulty running without the sole
instance of MSDTC in the W2K8 cluster running on their server.

HA! (As Dr. Who would say -- very loudly.)

I knew when I installed MSDTC that it had to be configured to allow inbound
and outbound network traffic. I learned that yea long years ago, from our
programming group, as a pre-requisite for their code to run.

BUT on the new OS I couldn't find the check boxes. I figured, well, some
smart person just realized that it SHOULD be on by default and removed the
check boxes.

Then, browsing through a white paper about how to set up a cluster on W2K8 I
saw that they'd MOVED the check boxes, not abolished them.

I have now checked those boxes. I haven't had a chance to try them yet,
but I bet they fix the problem, a basic inaccessibility of MSDTC.


On 3/18/10 9:04 AM, in article C7C79D33.1EBEA%rhindla (AT) panix (DOT) com, "Robert
Hindla" <rhindla (AT) panix (DOT) com> wrote: