Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 885725 - Last Review: October 27, 2006 - Revision: 1.2
An alert that is generated by using managed code displays the property text name instead of the event information in Microsoft Operations Manager 2005
An alert that is generated by using managed code might display the Microsoft Operations Manager (MOM) 2005 property text name instead of the identifying details from the event. For example, the alert that is generated by using managed code might display "$
Source Name$" instead of the identifying details from the event.
This problem occurs because the property resource name is not translated to its corresponding ID when the response query is inserted in the MOM database. The managed code response user interface lets you specify the parameters that are passed to the managed code method. When you specify a MOM property, the MOM property text name is stored in the MOM database. Therefore, the property that the managed code response receives contains the text of the MOM property instead of the corresponding data.
To work around this problem, you must use the property ID when you create a managed code response.
For example, use $05$ instead of $
Source Name$ in your managed code response.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The following lists contain commonly-used MOM property text names and the corresponding
parameter value.
Event parameters
Collapse this tableExpand this table
| Property Name | Parameter value |
| Event Number | 01 |
| Full Event Number | 02 |
| Event Type | 03 |
| Message Dll | 04 |
| Source Name | 05 |
| Provider Name | 06 |
| Provider Type | 30 |
| Description (Message) | 07 |
| Message Dll File Version | 08 |
| Logging Computer | 09 |
| Category | 10 |
| Event Time | 11 |
| Source Computer | 12 |
| User Name | 13 |
| User Domain Name | 26 |
| Logging Domain | 14 |
| Source Domain | 15 |
| Repeat Count | 17 |
| First Time | 18 |
| Last Time | 19 |
| Start Time | 20 |
Alert parameters
Collapse this tableExpand this table
| Property Name | Parameter value |
| Source (Culprit) | 50 |
| Name | 62 |
| Description | 63 |
| Owner | 51 |
| Severity | 52 |
| ResolutionState | 53 |
| AlertTime | 54 |
| Computer | 55 |
| Domain | 56 |
| Alert Rule Group ID | 64 |
| Custom Field1 | 57 |
| Custom Field2 | 58 |
| Custom Field3 | 59 |
| Custom Field4 | 60 |
| Custom Field5 | 61 |
Performance parameters
Collapse this tableExpand this table
| Property Name | Parameter value |
| Object | 21 |
| Counter | 22 |
| Instance | 23 |
| Time | 24 |
| Value | 25 |
APPLIES TO
- Microsoft Operations Manager (MOM) 2005
| kbopmanreporting kbopmaneventmgmt kbopmanalerts kbopman2005bug kbtshoot kbbug kbdatabase kbreport kbschema kbeventlog kbevent kbnofix KB885725 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate