Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: After SLAScorecard install - WMI Performance Adapter messages

9 views
Skip to first unread message

Pete Zerger

unread,
Apr 8, 2006, 12:31:19 AM4/8/06
to
Hello GarthLogic,

We had this same issue. The rule is firing based on an event ID (7036 I believe).
I changed the rule to only fire for UNEXPECTED service stoppages by using
a regular expression, as that service will stop / start frequently during
normal operation. The Win HTTP Proxy will do the same thing.

I just did this yesterday at a client site that I cant remote into right
now, so ping me offline to remind me @ pete.zerger AT gmail.com if you want
the expression and I'll get it to you.

Kind Regards,

Pete Zerger MCSE(Messaging)
mail:pete....@nospam.gmail.com
BLOG:http://www.it-jedi.net/

> Sine installing the SQL Scorecard for Exchange, I have been getting
> these messages from my Exchange server:
>
> The WMI Performance Adapter service entered the running state.
>
> The source is:
> Rule (enabled): Microsoft SLA Scorecard v1.0 Solution
> Accelerator\Exchange
> 2003\Service Control Manager Event for Service Stopped/Started
> Is this "normaL"? Should I disable the rule? Any one else seen this?
>
> Thanks!
>
> Garth
>


Pete Zerger

unread,
Apr 10, 2006, 11:51:08 AM4/10/06
to
In the Exchange SLA Rule Group, Exchange 2003 Subgroup

Find the rule labeled Service Control Manager ....

Update the Advanced Criteria with the following:

Event Number | matches regular expression |^(7021|7024|7031|7032|7034)$

Kind Regards,


Pete Zerger MCSE(Messaging)
mail:pete.zer...@nospam.gmail.com
BLOG:http://www.it-jedi.net/

Pete Zerger

unread,
Apr 10, 2006, 12:31:18 PM4/10/06
to
FYI - Here's the syntax

Under the Exchange SLA MP rules for Exchange 2003, find the Service
Control Manager Start/Stopped, and add

Event Number | matches regular expression |
^(7021|7024|7031|7032|7034)$

Regards,
Pete

Pete Zerger

unread,
Apr 15, 2006, 11:08:08 AM4/15/06
to
Guys,

I have concerns about the impact of this change on accracy of Exchange
SLA availability report results. Please see detailed explanation an
alternate workaround here:

http://www.it-jedi.net/2006/04/tuning-alert-noise-from-exchange-sla.html

In short, the workarouns is rather than adding regex to flag only
unexpected service stoppage, simply set the startup type of the
offending services to AUTOMATIC. The offending services (WMI
Performance Adapter and WinHTTP Proxy are set to MANUAL by default and
stop repeatedly during normal operation). This kills the alert noise
without impacting accuracy of SLA availability report results.

0 new messages