This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi all,
I'm migrating a Failover Cluster resource from Windows Server 2012 R2 to Windows Server 2022, and am running into issues with the resource failing to come online. It is setup as an "Other Resource" for clustering. The Failover Cluster itself looks fine (Server, DNS, IP come online, both nodes show as up) but when I try to start the role, the resource starts, fails and stops. The Windows service that is configured for the cluster role can start up fine on its own as a service, but when trying to bring the role online it just starts for a brief second before stopping.
I've tried re-installing the Windows service in question, tried reconfiguring the role, and have rebooted the machines, but nothing has changed. The behavior is the same on both Cluster Nodes, and attempting to failover to the other doesn't do anything.
I've also run psSDP, and there were no standout errors in the xray failure. A ProcDump of the process also failed to give additional information.
This is a snippet of what happens in cluster logs:
INFO [RCM] Res *** Resource: OnlinePending -> Online( StateUnknown )
INFO [RCM] TransitionToState(*** Resource) OnlinePending-->Online.
INFO [RCM] rcm::RcmGroup::UpdateStateIfChanged: (***, Pending --> Online)
INFO [RCM] HandleMonitorReply: FAILURENOTIFICATION for '*** Resource', gen(2) result 1/0.
INFO [RHS-WER] Scheduling WER ERROR report in 10.000.
INFO [RCM] Res *** Resource: Online -> ProcessingFailure( StateUnknown )
INFO [RCM] TransitionToState(*** Resource) Online-->ProcessingFailure.
INFO [RCM] rcm::RcmGroup::UpdateStateIfChanged: (***, Online --> Pending)
WARN [RCM] rcm::RcmResource::HandleFailure: (*** Resource)
INFO [RCM] resource *** Resource: failure count: 2, restartAction: 0 persistentState: 1.
INFO [RCM] resource *** Resource will not be restarting; isLowPriority: false; numDependents: 0
INFO [RCM] Res *** Resource: ProcessingFailure -> WaitingToTerminate( Failed )
INFO [RCM] TransitionToState(*** Resource) ProcessingFailure-->[WaitingToTerminate to Failed].
INFO [RCM] Res *** Resource: [WaitingToTerminate to Failed] -> Terminating( Failed )
INFO [RCM] TransitionToState(*** Resource) [WaitingToTerminate to Failed]-->[Terminating to Failed].
INFO [RCM] Will NOT try to long delay restart *** Resource.
INFO [RCM] HandleMonitorReply: TERMINATERESOURCE for '*** Resource', gen(3) result 0/0.
INFO [RCM] Res *** Resource: [Terminating to Failed] -> Failed( StateUnknown )
INFO [RCM] TransitionToState(*** Resource) [Terminating to Failed]-->Failed.
INFO [RCM] rcm::RcmGroup::UpdateStateIfChanged: (***, Pending --> Failed)
Please let me know of any suggestions to look at, thanks!
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.
Hi Jimmy,
Hope you're doing well.
What is the mode of migration? Was the Migration done using Storage Migration Service?
Best Regards
Hi Xu,
We're not actually migrating via a tool, just re-installing / configuring up the new servers from scratch.
Hi Jimmy,
Thanks for your update.
Could you please provide us the error screenshots and error messages? Thanks.
Best Regards
Hi Xu,
Here's the screenshot of the errors. I've included the failures from the cluster log in my original post. Let me know if any other information would be helpful.
Hi Jimmy,
Happy new year!
According to our experience, these errors are common and do not point to the issue.
Have you tried to reconfigure this role? Or did you see any other errors?
Please let me know if you have any questions without hesitation. And you can also choose to go to the Microsoft Customer Service Center to open a case so that with their permission level and resource, Microsoft could provide you with better help on your request.
Best Regards
