locked
How to troubleshoot "Invalid value for alert severity used with configuration of the rule" RRS feed

  • Question

  • Hi,

    I'm seeing this event in the OpsMgr event log on some of my servers. I have read and tried to use Marius' troubleshooting tips from  here: http://blogs.msdn.com/mariussutara/archive/2007/12/17/alert-severity-and-priority-use-with-override.aspx in order to find out which rule or monitor which is incorrectly configured.

    I just don't get any data back in powershell, but maybe it's just me who doesn't understand how to use powershell.

    I have also tried looking for the instance ID in the rules and monitors tables directly in the OpsMgr DB but so far with out luck.



    ---------------
    Source= HealthService
    Event ID=5405
    Description=

    Invalid value for alert severity used with configuration of the rule. It was outside of allowed range and had to be adjusted to closest valid value.

    Alert: 2C9BE568-CDE9-B4D9-5A9F-9BFD1077B1A4
    Workflow: Microsoft.SystemCenter.Alert.ParamReplacementFailure
    Instance: <name of server>
    Instance ID: {9071675E-68F7-A7FB-4DED-851B20031E7E}
    Management Group: <name of mgt group>

    Used severity value: 3
    -----------------

    br
    Lars
    Monday, December 14, 2009 2:32 PM

Answers

  • Hi,

    Are you running this in powershell ? What does it return ?:

    $mo = Get-MonitoringObject –Id “9071675E-68F7-A7FB-4DED-851B20031E7E”
    
    $rule = Get-Alert -MonitoringObject $mo -Criteria "Id='2C9BE568-CDE9-B4D9-5A9F-9BFD1077B1A4'"
    
    $rule.Name
    
    $rule.MonitoringObjectFullName






    If you are running SCOM 2007 R2 and assuming the severity 3 is set by an override,  you can find your bad rule directly in the console. Go to the Authoring Pane and open the Overrides view. Make sure your are scoped to all object (change scope button at the top) and personalize your view (right click in the result pane) so that there are no grouping. You'll find easily your override by finding the value 3 in the Override Value column.

    Regards,
    François Dufour
    My Blog
    • Marked as answer by Villiam1001 Thursday, December 17, 2009 3:07 PM
    Tuesday, December 15, 2009 12:04 PM

All replies

  • Hi,

    Are you running this in powershell ? What does it return ?:

    $mo = Get-MonitoringObject –Id “9071675E-68F7-A7FB-4DED-851B20031E7E”
    
    $rule = Get-Alert -MonitoringObject $mo -Criteria "Id='2C9BE568-CDE9-B4D9-5A9F-9BFD1077B1A4'"
    
    $rule.Name
    
    $rule.MonitoringObjectFullName






    If you are running SCOM 2007 R2 and assuming the severity 3 is set by an override,  you can find your bad rule directly in the console. Go to the Authoring Pane and open the Overrides view. Make sure your are scoped to all object (change scope button at the top) and personalize your view (right click in the result pane) so that there are no grouping. You'll find easily your override by finding the value 3 in the Override Value column.

    Regards,
    François Dufour
    My Blog
    • Marked as answer by Villiam1001 Thursday, December 17, 2009 3:07 PM
    Tuesday, December 15, 2009 12:04 PM
  • Hi,

    Yes I am, absolutely nothing is returned.

    But you tip on using the Console was very help full. The override was easy to find.

    Thanks!

    br
    Lars
    Thursday, December 17, 2009 3:07 PM