After you configure a Collect Specific Events (Collection) rule in Microsoft Operations Manager (MOM) 2005, the following symptoms occur:

• The MOM service (MOMservice.exe) stops unexpectedly. If you try to start the MOM service, you receive the following error message:
  Could not start the MOM service on Local Computer. Error 1067: The process terminated unexpectedly.
• The following events are logged in the Application log:

  Event Type: Error
  Event Source: Microsoft Operations Manager
  Event Category: None
  Event ID: 9014
  Date: date
  Time: time
  User: N/A
  Computer: ComputerName
  Description: The Microsoft Operations Manager service (MOMService.exe) terminated due to an unhandled exception. It will attempt to restart itself.
  For more information, see Help and Support Center at <http://go.microsoft.com/fwlink/events.asp>.

  Event Type: Error
  Event Source: Microsoft Operations Manager
  Event Category: None
  Event ID: 9015
  Date: date
  Time: time
  User: N/A
  Computer: ComputerName
  Description: The Microsoft Operations Manager service (MOMService.exe) received an unexpected exception.
  
  Thread Id: 0xf40
  Thread Name: MSB3904
  Exception code: 0x00000000c0000005
  Exception description: Access Violation
  Exception address: 025EB79C
  Exception flags: 0x0
  
  For more information, see Help and Support Center at <http://go.microsoft.com/fwlink/events.asp>.

This problem may occur if the Collect Specific Events (Collection) rule is configured to collect security event parameters. In this scenario, the Collect Specific Events (Collection) rule may occasionally collect more parameters than requested. This behavior may cause the MOM service to stop.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have MOM 2005 Service Pack 1 (SP1) installed on the computer.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You do not have to restart the computer after you apply this hotfix.

However, you must apply this hotfix to the MOM 2005 management server. When you apply this hotfix, the MOM service automatically restarts.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

To work around this problem, configure the Collect Specific Events (Collection) rule so that it does not collect any event parameters. To do this, follow these steps:

1. Start the MOM 2005 Administrator Console, and then expand Management Packs.
2. Expand Rule Groups, expand the appropriate rule group, and then click Event Rules.
3. In the results pane, locate and then double-click the Collect Specific Events (Collection) rule with which you experience the problem.
4. In the Collection Rule Properties ManagementGroupName - RuleName box, click the Parameter Storage tab.
5. Click Store no event parameters, and then click OK.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base: