Exceptions in Operations Manager
Updated: May 22, 2009
Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1, System Center Operations Manager 2007
The base exception class that all the other Operations Manager exceptions are derived from is the MonitoringException class.
Query criteria errors
When you are defining a query string for monitoring objects or monitoring classes, you must make sure the query string is using the correct syntax or grammar. For information about querying for objects, see Using Operations Manager Data Queries. When you use the defined query to retrieve monitoring objects or monitoring classes, the QueryGrammarException can be thrown if the query string is invalid.
Management Pack errors
A ManagementPackException can be thrown when there is an error in importing or parsing a Management Pack. This type of exception has an ExceptionCode property, and this property value can be used with the ManagementPackExceptionCode enumeration to look up the type of Management Pack exception that occurred. The error code can also be passed to the GetMessage method of the ManagementPackExceptionMessages class to determine the localized Management Pack exception message.
SDK Connection errors
Before you start using the Operations Manager SDK classes, you must connect to the SDK service. There are a few exceptions that can be thrown and handled while you are connecting to the service. For more information, see How to Connect an Operations Manager SDK Client to the SDK Service. The most common exceptions that occur due to connection errors are:
If an SDK client attempts to access a method that is not allowed by the current user's profile, an UnauthorizedAccessMonitoringException is thrown. The SDK client can handle this exception to notify users that they do not have the appropriate privileges for the requested operation.
List of SDK exceptions
The following list contains all the exception classes for the Operations Manager 2007 SDK: