Both of my Operations Manager instances (CU3 and CU5) have suddenly started to throw an Invalid Class error whenever I try to add or edit a subscriber address. Here is the full error: System.Management.ManagementException: Invalid class at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext() at Microsoft.EnterpriseManagement.Mom.Internal.UI.Notification.RecipientGeneralPage.QueryAdForEmail() at Microsoft.EnterpriseManagement.Mom.Internal.UI.Notification.RecipientDevicePage.EditDevice() Since it happened to both environments, I wonder if there was some sort of security patch or other global update that may have impacted them. Any thoughts would be helpful. thanks!

Hello David, Most likely it is a WMI issue affecting your Root Management Server Try and check the results of this WMI query>> Run > Wbemtest > connect to root\cimv2 > Query >>> select FullName from win32_useraccount A hotfix is available that improves the stability of the Windows Management Instrumentation repository in Windows Server 2003: http://support.microsoft.com/kb/933061Regards, Mazen Ahmed

I applied the patch and restarted, but it didn't seem to make a difference with this specific error. The WMI query does run and I can drill into all classes and see all properties. Is there any chance that clicking the add / edit subscriber button does some sort of AD query that is not completing? I'm just wondering why it would break the same way in two totally different domains at the same time.

Here's an interesting thing. Just discovered I can get around the invalid class error if on the first page of the new / edit subscriber I do a full lookup of an AD user account and let it keep that as the subscriber name (domain/user). Then when I get to the add address, it has no problems (and prepopulates the email address, but I can change it) and lets me walk all the way to the end. Then I can go back and just change the subscriber name to the adhoc one I wanted. So it does appear there is something new in the GUI that is expecting an AD lookup with the email address pre-populated. The workaround is fine for now, I don't have to add subscribers often, but it might be something to keep an eye on.

Here's an interesting thing. Just discovered I can get around the invalid class error if on the first page of the new / edit subscriber I do a full lookup of an AD user account and let it keep that as the subscriber name (domain/user). Then when I get to the add address, it has no problems (and prepopulates the email address, but I can change it) and lets me walk all the way to the end. Then I can go back and just change the subscriber name to the adhoc one I wanted. So it does appear there is something new in the GUI that is expecting an AD lookup with the email address pre-populated. The workaround is fine for now, I don't have to add subscribers often, but it might be something to keep an eye on.