Issue : MSDTC' in Resource Group 'Cluster Group' failed and then immediately cluster resource came online. this occurs once in 5 to 7 Months, i have share all the logs and i could not get much help for the technical articles that was published by microsof
2003 cluster issue
issue : msdtc' in resource group 'cluster group' failed
cluster logs
=====================================================
fmpenumerategroupresources: exit group <a539af5c-9838-445f-8f21-a96806f0e706>....
000011ec.000011f8::2013/02/04-15:25:38.647 err distributed transaction coordinator <msdtc>: failed isalive test. current state 1.
00000c6c.00001200::2013/02/04-15:25:38.663 info [fm] notifycallbackroutine: enqueuing event
00000c6c.00001200::2013/02/04-15:25:38.663 info [fm] calling rmnotifychanges in monitor 11ec.
00000c6c.00000e04::2013/02/04-15:25:38.663 info [cp] cppresourcenotify resource msdtc
00000c6c.00000e08::2013/02/04-15:25:38.694 warn [fm] fmphandleresourcetransition: resource name = 96b27365-dcf4-49ca-bfff-7bef8cc313b8 [msdtc] old state=2 new state=4
00000c6c.00000e08::2013/02/04-15:25:38.694 info [gum] gumsendupdate: locker waiting type 0 context 8
00000c6c.00000e08::2013/02/04-15:25:38.694 info [gum] thread 0xe08 updatelock wait on type 0
00000c6c.00000e08::2013/02/04-15:25:38.694 info [gum] gumpdolockingupdate: lock free, granted 1
00000c6c.00000e08::2013/02/04-15:25:38.694 info [gum] gumpdolockingupdate successful, sequence=29752 generation=0
00000c6c.00000e08::2013/02/04-15:25:38.694 info [gum] gumsendupdate: locker dispatching seq 29752 type 0 context 8
00000c6c.00000e08::2013/02/04-15:25:38.694 info [gum] gumsendupdate: dispatching seq 29752 type 0 context 8 node 2
00000c6c.00000e08::2013/02/04-15:25:38.694 info [gum] gumsendupdate: locker updating seq 29752 type 0 context 8
00000c6c.00000e08::2013/02/04-15:25:38.694 info [gum] gumpdounlockingupdate releasing lock ownership
00000c6c.00000e08::2013/02/04-15:25:38.694 info [gum] gumsendupdate: completed update seq 29752 type 0 context 8
00000c6c.00000e08::2013/02/04-15:25:38.694 info [fm] fmppropagateresourcestate: resource 96b27365-dcf4-49ca-bfff-7bef8cc313b8 failed event.
00000c6c.00000e08::2013/02/04-15:25:38.694 info [fm] fmphandleresourcefailure: taking resource 96b27365-dcf4-49ca-bfff-7bef8cc313b8 , dependents offline
000011ec.00000e68::2013/02/04-15:25:38.694 info distributed transaction coordinator <msdtc>: in call commonterminate
000011ec.00000e68::2013/02/04-15:25:38.694 info distributed transaction coordinator <msdtc>: offline request.
000011ec.00000e68::2013/02/04-15:25:38.694 info distributed transaction coordinator <msdtc>: service died; status = 1062.
000011ec.00000ca4::2013/02/04-15:25:42.038 info distributed transaction coordinator <msdtc>: service on line
event type: error
event source: clussvc
event category: failover mgr
event id: 1069
date: 2/4/2013
time: 9:25:38 am
user: n/a
computer: snnhousql1
description:
cluster resource 'msdtc' in resource group 'cluster group' failed.
=====================================================
hello vasu,
please have at http://social.technet.microsoft.com/forums/en-us/winserverclustering/thread/3b6dcb89-969a-4772-a89d-608241aac081/ to resolve event id 1069.
regards, ravikumar p
Windows Server > High Availability (Clustering)
Comments
Post a Comment