More on the MOM Issue

Here is Roger's Post:
As you know MOM currently has an issue on W2K3 Server SP1 where you may
experience error warnings in remote MOM Admin Consoles which will prevent
the maintenance of the 'Computer Groups' in your MOM system.  Specifically
clicking on the Computer Groups node displays an error message "0x800706be:
The remote procedure call failed" and the computer groups are not displayed
and the console crashes.

The MOM Product Group is actively working on the fix for this issue and will
be making this available as soon as possible.  The issue seems to be in the
way we are freeing allocated memory when a computer group properties field
is set to NULL and that computer group, because of its name, is the first to
show in the query we run to enumerate those names in the right pane of MMC.

This is most commonly seen when Configuration Group names are alphabetically
before any other computer groups that have been created.  For example:  If
during installation on a W2K3 SP1 machine I create a configuration group
named 'Config_1' and then try and connect via a remote administrator console
I would possibly see this issue.  This is because the MOM MP is the only one
imported and the 8 computer groups which are currently there start with
'Microsoft Operations Manager'.

For the time being there is a possible workaround you could use to help
mitigate this issue until a fix is available.  You can go to the MOM Server
you are trying to remotely connect through and using a MOM Admin account and
the local MOM Administrators Console on that server (if one is not there you
will need to install one) you can create a Computer Group with a name
starting with an '_' character.  This will reorder the offending
Configuration group name out of first position and should allow you to
conduct business as usual.

--
Roger Porter
MOM Test Manager