RE: Event IDs 1069 and 1082 on MSDTC When Moving Cluster Group to Pass

Cathy, I am sure you have heard this before but you should never add any
resources in the Cluster Group, always leave that alone. Have you
read/applied the KB articles KB301600 and KB817064, this may help you? I
would create another group just for this, use a small disk and go from there.

Hope that helps.
--
Mark


"" wrote:

> Yesterday I took the passive node in my Operations Manager RMS cluster down to remove a modem board and replace it with a new one. Ever since it came back up, I'm unable to fail over the Cluster Group (specifically the MSDTC resource) to the passive node. Whenever I try, I get these two errors.
>
> Type: Error
> Source: ClusSvc
> Event ID: 1069
> Event Time: 11/12/2008 10:26:04 AM
> User: n/a
> Computer: MTSCOMRMS01
> Description:
> Cluster resource 'MSDTC' in Resource Group 'Cluster Group' failed.
>
>
> Type: Error
> Source: ClusSvc
> Event ID: 1082
> Event Time: 11/12/2008 10:26:04 AM
> User: n/a
> Computer: MTSCOMRMS01
> Description:
> Cluster service failed to restore a registry key for resource MSDTC when it
> was brought online. This error code was 3. Some changes may be lost.
>
> A technet article advised me to use the ClusterRecover.exe utilty to recover the resource. I tried recovering just MSDTC. No joy, so I tried recovering all resources. Same result. A reboot of the passive node didn't help either.
>
> One post I read said the user deleted the resource and recreated it, but I'd rather not go there unless I have to.
>
> The active node is running just fine, but I need to be able to fail over to the passive node for maintenance. My local cluster expert has never run into this.
>
> I'd appreciate any light that can be shed on this.
>
> Cathy
>

I have heard it before, but followed instructions from a consultant we hired
to help us implement SCOM. Oh, well. I'm off to rebuild MSDTC on my
cluster.

Thanks, Mark.

Cathy

"Mark" <> wrote in message
news:A850038C-D31A-4A18-A4CA-...
> Cathy, I am sure you have heard this before but you should never add any
> resources in the Cluster Group, always leave that alone. Have you
> read/applied the KB articles KB301600 and KB817064, this may help you? I
> would create another group just for this, use a small disk and go from
> there.
>
> Hope that helps.
> --
> Mark
>
>
> "" wrote:
>
>> Yesterday I took the passive node in my Operations Manager RMS cluster
>> down to remove a modem board and replace it with a new one. Ever since
>> it came back up, I'm unable to fail over the Cluster Group (specifically
>> the MSDTC resource) to the passive node. Whenever I try, I get these two
>> errors.
>>
>> Type: Error
>> Source: ClusSvc
>> Event ID: 1069
>> Event Time: 11/12/2008 10:26:04 AM
>> User: n/a
>> Computer: MTSCOMRMS01
>> Description:
>> Cluster resource 'MSDTC' in Resource Group 'Cluster Group' failed.
>>
>>
>> Type: Error
>> Source: ClusSvc
>> Event ID: 1082
>> Event Time: 11/12/2008 10:26:04 AM
>> User: n/a
>> Computer: MTSCOMRMS01
>> Description:
>> Cluster service failed to restore a registry key for resource MSDTC
>> when it
>> was brought online. This error code was 3. Some changes may be lost.
>>
>> A technet article advised me to use the ClusterRecover.exe utilty to
>> recover the resource. I tried recovering just MSDTC. No joy, so I tried
>> recovering all resources. Same result. A reboot of the passive node
>> didn't help either.
>>
>> One post I read said the user deleted the resource and recreated it, but
>> I'd rather not go there unless I have to.
>>
>> The active node is running just fine, but I need to be able to fail over
>> to the passive node for maintenance. My local cluster expert has never
>> run into this.
>>
>> I'd appreciate any light that can be shed on this.
>>
>> Cathy
>>

Well, rebuilding the DTC resource fixed it. Although, it took an hour or so
before the cluster would fail over cleanly after the new resource was
brought on line.

Thanks, again, for your help, Mark.

Cathy

<> wrote in message
news:...
>I have heard it before, but followed instructions from a consultant we
>hired to help us implement SCOM. Oh, well. I'm off to rebuild MSDTC on my
>cluster.
>
> Thanks, Mark.
>
> Cathy
>
> "Mark" <> wrote in message
> news:A850038C-D31A-4A18-A4CA-...
>> Cathy, I am sure you have heard this before but you should never add any
>> resources in the Cluster Group, always leave that alone. Have you
>> read/applied the KB articles KB301600 and KB817064, this may help you? I
>> would create another group just for this, use a small disk and go from
>> there.
>>
>> Hope that helps.
>> --
>> Mark
>>
>>
>> "" wrote:
>>
>>> Yesterday I took the passive node in my Operations Manager RMS cluster
>>> down to remove a modem board and replace it with a new one. Ever since
>>> it came back up, I'm unable to fail over the Cluster Group (specifically
>>> the MSDTC resource) to the passive node. Whenever I try, I get these
>>> two errors.
>>>
>>> Type: Error
>>> Source: ClusSvc
>>> Event ID: 1069
>>> Event Time: 11/12/2008 10:26:04 AM
>>> User: n/a
>>> Computer: MTSCOMRMS01
>>> Description:
>>> Cluster resource 'MSDTC' in Resource Group 'Cluster Group' failed.
>>>
>>>
>>> Type: Error
>>> Source: ClusSvc
>>> Event ID: 1082
>>> Event Time: 11/12/2008 10:26:04 AM
>>> User: n/a
>>> Computer: MTSCOMRMS01
>>> Description:
>>> Cluster service failed to restore a registry key for resource MSDTC
>>> when it
>>> was brought online. This error code was 3. Some changes may be lost.
>>>
>>> A technet article advised me to use the ClusterRecover.exe utilty to
>>> recover the resource. I tried recovering just MSDTC. No joy, so I
>>> tried recovering all resources. Same result. A reboot of the passive
>>> node didn't help either.
>>>
>>> One post I read said the user deleted the resource and recreated it, but
>>> I'd rather not go there unless I have to.
>>>
>>> The active node is running just fine, but I need to be able to fail over
>>> to the passive node for maintenance. My local cluster expert has never
>>> run into this.
>>>
>>> I'd appreciate any light that can be shed on this.
>>>
>>> Cathy
>>>
>
>