If you have multiple management servers with agents configured for failover and one of the managment server goes off-line agents may be refused a connection to the failover management server. A hotfix is available from Microsoft to correct this issue.
PingBack from http://systemcenterforum.org/kb934441-event-id-26009-occurs-after-a-mom-2005-agent-tries-to-fail-over-to-the-secondary-mom-2005-server/
I have a customer that applied this HotFix but it did not update the Mommsgs.dll in the mom root directory only the Mommsgs.dll in the \x86 directory . Is there any article that says what to do in this case? It also gives the following error after applying it:
The description for Event ID ( 9010 ) in Source ( Microsoft Operations Manager ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details.
My issue is that the MOMMsgs.dll being used is the one in "C:\Program Files\Microsoft Operations Manager 2005" however the one this patch updated is in "C:\Program Files\Microsoft Operations Manager 2005\x86" when I replace the one being used my the MOM Service with this new version I get the in formation event in the event log "mslinda" is referring to. When i install this on a MOM Client, the MOMMsgs.dll does not get replaced either. Only one copy exists on our clients. The existing version is a straight SP1 version "2911.00" is this expected behavior? or is this an issue that will cause us problems? We have several Dozen MOM Management servers and thousands of clients, this will be distributed via SMS and therefore if i am forced to script a bunch of fixes in my SMS Job i need to know that up front. The release notes are rather vague and lacking any details.
I am looking into this issue and will report back when I know more.