[msmom] Issue with Health Service Unloaded System Rules Alert [jahaig]
-----Original Message-----
From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf
Of Snyder, Robert W.
Sent: Thursday, January 08, 2009 11:16 AM
To: msmom@lists.myitforum.com
Subject: RE: [msmom] Issue with Health Service Unloaded System Rules Alert
Just an fyi in case anyone else runs into this. We seem to have found
the resolution. It appears to have been a time zone issue with the
Brasilia time zone. Here's what we did.
For testing purposes, we changed the time zone to -2:00 GMT instead of
-3:00 GMT. Repaired the agent. Problem went away.
So then we found the following KB article. We had previously patched all
our servers for time zone issues, but it appears there was a new patch
released in December.
http://support.microsoft.com/kb/955839 We applied this patch to the 3 servers in Brazil, then just for good
measure I uninstalled and re-installed the agent. All three are now
working properly again.
I'm glad to have this resolved, though it isn't very clear to me why
Operations Manager agents should have been affected by a time zone
issue. Especially, that the problem would manifest itself on Dec. 31st
at midnight GMT. Would have thought a "time zone" patch would have only
come into play when there are time changes.
Robert Snyder
Sr. Technical Programmer/Analyst
Global Server Support
robert.snyder@timken.com
-----Original Message-----
From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On
Behalf Of Snyder, Robert W.
Sent: Tuesday, January 06, 2009 3:42 PM
To: msmom@lists.myitforum.com
Subject: [msmom] Issue with Health Service Unloaded System Rules Alert
Having a very weird issue here with one particular site. We have a site
in Brazil that has an AD domain controller, an SMS server, and a DHCP
server. Starting at 7:00 pm Eastern Time on December 31st, all three
servers at this site started getting the Health Service Unloaded System
Rules alert. We are also getting the following two Event id's in
continual spurts on all three servers.
-----------------------------------------
Event Type:Warning
Event Source:HealthService
Event Category:Health Service
Event ID:1103
Date:1/6/2009
Time:6:31:48 PM
User:N/A
Computer:COMPUTER1
Description:
Summary: 1 rule(s)/monitor(s) failed and got unloaded, 1 of them reached
the failure limit that prevents automatic reload. Management group
"ManagementGroup". This is summary only event, please see other events
with descriptions of unloaded rule(s)/monitor(s).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-----------------------------------------
Event Type:Error
Event Source:Health Service Modules
Event Category:None
Event ID:11251
Date:1/6/2009
Time:6:31:48 PM
User:N/A
Computer:COMPUTER1
Description:
The Microsoft Operations Manager Scheduler Data Source Module has some
invalid configuration.
Config Context: Scheduler/Init
Error: 0x80070057
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DiscoverWindowsServerDCComputer
Instance name: COMPUTER1.domain.com
Instance ID: {D39C1BF1-05DA-DD45-7F05-63693430C3C8}
Management group: ManagementGroup
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-----------------------------------------
What makes no sense is the following:
1) I've completely uninstalled the agents and re-installed them and it
made no difference.
2) We have close to 300 servers being monitored some with similar roles
to these three boxes and it is only these three that are complaining, so
I do not believe it is an operations manager or a management pack issue,
otherwise we'd be seeing it elsewhere.
3) The servers otherwise seem to be communicating fine back to the
corporate head quarters. In fact when I re-install the agent I get the
1210 event id, new configuration active message which would imply that
the agent is able to talk to the RMS ok.
4) It seems a very bizarre coincidence that 7:00 pm EST would correspond
to midnight GMT time on December 31st. Makes me wonder if something
expired at that point, but I don't have any idea where to even look.
5) I'm 99.9% sure that there would have been no one manually making any
configuration changes at that time.
We are at a loss at this point to figure out why this is happening.
Robert Snyder
Sr. Technical Programmer/Analyst
Global Server Support
robert.snyder@timken.com
-----------------------------------------
This message and any attachments are intended for the individual or
entity named above. If you are not the intended recipient, please
do not forward, copy, print, use or disclose this communication to
others; also please notify the sender by replying to this message,
and then delete it from your system. The Timken Company / The
Timken Corporation
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/
Trackbacks
No Trackbacks
Comments
No Comments
