Showing posts with label SCOM2007 R2. Show all posts
Showing posts with label SCOM2007 R2. Show all posts

Tuesday, 13 August 2013

SCOM reports fail with error "System.ArgumentOutOfRangeException"

SCOM reports fail with error "System.ArgumentOutOfRangeException" 

Cause:

This issue can occur if the custom Short DateTime format being used on the console server.

For example, say the system locale on the Operations console server is ENC and the default short DateTime format for ENC locale is dd/MM/yyyy. If this short DateTime format is changed from dd/MM/yyyy to a different format such as yyyy-MM-dd, the error above may occur.


Resolution:

To resolve this issue, set the short DateTime format to the system locale's default value.

Thursday, 1 August 2013

How to get Rule Name from Instance ID.

Lot of times in SCOM you will get the Instance ID and Workflow name of the rule that is causing the error.

This is of no use in troubleshooting as you dont knwo the Rule that is causing the issue.

Follow the below steps to decode the Rule Name from WorkFlow Name


  • From the Error Copy the "WorkFlow Name"
  • Now connect to the "OperationsManager" database and run the below SQL query


               SELECT * FROM Rules WHERE RuleName = ‘MomUIGeneratedRulexxxxx’

 Replace "MomUIGeneratedRulexxxxx" with the data you got from WorkFlow Name


  • The query will retun lot of column's, you need to check the "RuleID field" coloum and copy the information



  • Now login to you SCOM RMS and open Command Shell and thpe the below command


                                  Get-Rule -Id XXXX-XXX-XXXX

Replace "XXXX-XXX-XXXX" with the info that you got from the "RuleID field" coloum of the SQL query


  • This command will return information about this rule, Copy the DisplayName and find the rule in the Operations Console and troubleshoot it.