Event ID 6230 on Failover Cluster VM
-
Tuesday, May 01, 2012 1:23 PM
Hi everyone, I have a boatload of warnings that continually repeat and it appears to be DFS related.
Setup: 2 VM's configured as file and print servers with failover clustering between them on Server 2008 R2 SP1. These are running on 4 Server 2008 R2 Core SP1 cluster nodes.
Here are the errors I am getting:
Event ID 6230
Failover Cluster WMI Provider detected an invalid character. The private property name 'Replication Group Name' had an invalid character and has been changed to 'Replication0x20Group0x20Name'. Valid characters for WMI property names are A-Z, a-z, 0-9, and '_'.
Failover Cluster WMI Provider detected an invalid character. The private property name 'Replicated Folder Root Path' had an invalid character and has been changed to 'Replicated0x20Folder0x20Root0x20Path'. Valid characters for WMI property names are A-Z, a-z, 0-9, and '_'.
Failover Cluster WMI Provider detected an invalid character. The private property name 'Staging Path' had an invalid character and has been changed to 'Staging0x20Path'. Valid characters for WMI property names are A-Z, a-z, 0-9, and '_'.
Failover Cluster WMI Provider detected an invalid character. The private property name 'Replicated Folder ID' had an invalid character and has been changed to 'Replicated0x20Folder0x20ID'. Valid characters for WMI property names are A-Z, a-z, 0-9, and '_'.
And many others with basically the same info - I'm not sure how to resolve it. Any help, as always, is greatly appreciated!
All Replies
-
Tuesday, May 15, 2012 7:31 AM
Hello,
Seems you need to install below hotfix to resolve your issue.
http://support.microsoft.com/kb/974930
Refer below thread for more details, hope your issue is similar to this.http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2highavailability/thread/bae84aea-5a80-4637-989b-c31bbc1aa55a
Regards, Ravikumar P
Click Vote As Helpful, if the post solved your problem- Edited by Ravikumar PulagouniMicrosoft Community Contributor Tuesday, May 15, 2012 7:50 AM
-
Wednesday, May 30, 2012 1:25 PMThank you, EXRAPUL. I'll give it a try and see what happens. I wasn't sure about that hotfix since my event IDs are different, but it does sound remarkably similar.
- Edited by waingro Wednesday, May 30, 2012 1:27 PM
-
Saturday, July 14, 2012 3:04 PM
Is your issue solved or still it is there?
Regards, Ravikumar P
- Edited by Ravikumar PulagouniMicrosoft Community Contributor Saturday, July 14, 2012 3:04 PM
-
Thursday, September 20, 2012 6:20 PMOK, so after much procrastination and other high priority things I tied to apply this update, but it says "not applicable to your server." :-/
-
Friday, November 09, 2012 12:05 PM
Hi,
have you found a solution to this? Did you get the hotfix installed? We have the same issue, where the log is filled with this warnings evere fifth minute.

