Microsoft windows failoverclustering 2051
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
yesterday I added a LUN to our hyper-v cluster from an fc storage (eva 4100), and added it to our cluster storage.
This needed the newest MPIO Driver and Qlogic Driver from HP, aswell as adding MPIO Role.
Everything works fine, Failover of Storage, Failover of VM’s, rebooting, no troubles, tried it several times.
The Cluster check went fine with the storage which I tried before moving over the VM’s.
Just our logs turn crazy with those 5 messages reappearing on each cluster node constantly.
I tried to search up some information about this error, but the results are usually cases where failover is not working.
But besides the logs that I don’t want to ignore, all seems to work fine.
HYPERV2 2050
Warning Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:58
[ClRtl] SsCoreShareAdd(): status = 2118 share = 5a226444-0bb5-45ef-9579-3594ee536745-135266304$ server = (null)
HYPERV2 2050 Warning Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:58
[ClRtl] SsCoreShareAdd(): status = 2118 share = CSV$ server = (null)
HYPERV2 2051 Error Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:57
[RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)’ because of ‘Startup routine for ResType MSMQ returned 21.’
HYPERV2 2050 Warning Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:57
[RCM] Failed to load restype ‘MSMQ’: error 21.
HYPERV2 2050 Warnung Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:57
[RCM] Failed to load restype ‘MSMQTriggers’: error 21.
HYPERV2 2051 Fehler Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:57
[RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)’ because of ‘Startup routine for ResType MSMQTriggers returned 21.’
We also have this hotfix installed (as first we used iscsi and had troubles with backups, that where gone). We had version 1 installed, today I tried version 2, just to be sure it’s not related. I doubt it is, but worth to mention. Hotfix: KB2813630 — v2
Microsoft windows failoverclustering 2051
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I have deployed Server 2012 Cluster (CSV) for SQL Server 2012. Everythings working fine but some warning and error events generating continuously.
NODE01 2050 Warning Microsoft-Windows- FailoverClustering Microsoft-Windows- FailoverClustering /Diagnostic
[RCM] ResourceControl ( SET_COMMON_PROPERTIES) to SQL Server Agent (MSTUDIODB) returned 5024
NODE01 2051 Error Microsoft-Windows- FailoverClustering Microsoft-Windows- FailoverClustering /Diagnostic
[RCM] [GIM] ResType Virtual Machine has no resources, not collecting local utilization info
Answers
Thanks for the question.
Regarding the errors, please update the BIOS/firmware and device drivers to the latest on the server node and see how it works.
Best Regards
Jeremy Wu
All replies
Thanks for the question.
Regarding the errors, please update the BIOS/firmware and device drivers to the latest on the server node and see how it works.
Best Regards
Jeremy Wu
I would like to check if you need further assistance.
Best Regards
Jeremy Wu
Devin Berard I.T Support Renfrew Victoria Hospital, Renfrew ON berardd@renfrewhosp.com
Hi I am also getting this on a SQL 2012 Cluster, Virtual Servers on ESXI.
So there are no drivers or Bios to update .
any help would be appreciated
Same issue here.
Virtual machines on ESXi v5.5 cluster. Two MS 2012r2 clustered machines for File Server role.
Could this be related to a problem with the Cluster Aware Update Virtual Name Object (VNO)? I see mine has some Kerberos issues that soon I will have to recreate it with a pre-created VNO instead of letting the CAU wizard create the computer object for me.
I realize this is old, but wanted to provide some direction for those who may be seeing this error and don’t know why. At a high level, the cluster logging process uses a set of cluster resources types that it queries for health/status info. You can see these by running the PowerShell command Get-ClusterResourceType. The problem is if you do not have a resource that matches the type, it will return an error when you have debug logging enabled. Meaning, if you are running a SQL Failover Cluster, your cluster resource type would be «SQL Server». The error you are seeing is because there are no Virtual Machine resource types, which would come in to play in a Hyper-V cluster. You are running SQL, not Hyper-V, so the error can be ignored, or if you know you will not be running Hyper-V at any time on the cluster, you can simply remove that cluster resource type by running the following in and admin PowerShell prompt.
Remove-ClusterResourceType «Virtual Machine»
There is an even more frequent and seemingly worse error about MSMQ. Same deal there. You can remove the cluster resource types MSMQ and MSMQTriggers. Hope this helps someone else who sees these errors.
Microsoft windows failoverclustering 2051
Вопрос
I have deployed Server 2012 Cluster (CSV) for SQL Server 2012. Everythings working fine but some warning and error events generating continuously.
NODE01 2050 Warning Microsoft-Windows- FailoverClustering Microsoft-Windows- FailoverClustering /Diagnostic
[RCM] ResourceControl ( SET_COMMON_PROPERTIES) to SQL Server Agent (MSTUDIODB) returned 5024
NODE01 2051 Error Microsoft-Windows- FailoverClustering Microsoft-Windows- FailoverClustering /Diagnostic
[RCM] [GIM] ResType Virtual Machine has no resources, not collecting local utilization info
Ответы
Thanks for the question.
Regarding the errors, please update the BIOS/firmware and device drivers to the latest on the server node and see how it works.
Best Regards
Jeremy Wu
Все ответы
Thanks for the question.
Regarding the errors, please update the BIOS/firmware and device drivers to the latest on the server node and see how it works.
Best Regards
Jeremy Wu
I would like to check if you need further assistance.
Best Regards
Jeremy Wu
Devin Berard I.T Support Renfrew Victoria Hospital, Renfrew ON berardd@renfrewhosp.com
Hi I am also getting this on a SQL 2012 Cluster, Virtual Servers on ESXI.
So there are no drivers or Bios to update .
any help would be appreciated
Same issue here.
Virtual machines on ESXi v5.5 cluster. Two MS 2012r2 clustered machines for File Server role.
Could this be related to a problem with the Cluster Aware Update Virtual Name Object (VNO)? I see mine has some Kerberos issues that soon I will have to recreate it with a pre-created VNO instead of letting the CAU wizard create the computer object for me.
I realize this is old, but wanted to provide some direction for those who may be seeing this error and don’t know why. At a high level, the cluster logging process uses a set of cluster resources types that it queries for health/status info. You can see these by running the PowerShell command Get-ClusterResourceType. The problem is if you do not have a resource that matches the type, it will return an error when you have debug logging enabled. Meaning, if you are running a SQL Failover Cluster, your cluster resource type would be «SQL Server». The error you are seeing is because there are no Virtual Machine resource types, which would come in to play in a Hyper-V cluster. You are running SQL, not Hyper-V, so the error can be ignored, or if you know you will not be running Hyper-V at any time on the cluster, you can simply remove that cluster resource type by running the following in and admin PowerShell prompt.
Remove-ClusterResourceType «Virtual Machine»
There is an even more frequent and seemingly worse error about MSMQ. Same deal there. You can remove the cluster resource types MSMQ and MSMQTriggers. Hope this helps someone else who sees these errors.
Microsoft windows failoverclustering 2051
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I just took a quick look at my Event Viewer on my Windows Server 2012 Standard server hosting Exchange 2013 and see the following errors. every 5 minutes for days now. Im not aware of any updates installed so Im not sure what could be causing this or where to troubleshoot quite honestly;
The server is running on VMware Virtual Platform.
Log Name: Microsoft-Windows-FailoverClustering/Diagnostic
Source: Microsoft-Windows-FailoverClustering
Date: 6/8/2015 10:55:33 AM
Event ID: 2051
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: XCH1Server.Domain.local
Description:
[RCM] [GIM] ResType Virtual Machine has no resources, not collecting local utilization info
Now that I look at all my 6 exchange servers running Windows Server 2012 Standard, I see the same in those event logs also.
