Knowledge Base

Event ID 9014 and Event ID 9015 are logged and MOMservice.exe stops unexpectedly after you configure a Collect Specific Events (Collection) rule in Microsoft Operations Manager 2005

Article ID: 930770

Article Last Modified on 8/9/2007

APPLIES TO

Microsoft Operations Manager (MOM) 2005

SYMPTOMS

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 ID 9014

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 ID 9015

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>.

CAUSE

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.

RESOLUTION

Hotfix information

A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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:

905416 How to obtain the latest Microsoft Operations Manager 2005 service pack

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 any other hotfixes.

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.

File name	File version	File size	Date	Time	Platform
Momactions.dll	5.0.2911.38	905,608	26-Jan-2007	08:47	Not applicable
Momdbconnector.dll	5.0.2911.38	1,631,112	26-Jan-2007	08:47	Not applicable
Momengine.dll	5.0.2911.38	1,649,544	26-Jan-2007	08:47	Not applicable

WORKAROUND

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:

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

STATUS

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

MORE INFORMATION

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

904748 The MOM service process (Momservice.exe) unexpectedly shuts down and you receive an event in the Application log on the Microsoft Operations Manager 2005 Management Server

824684 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbbug kbfix kbhotfixserver kbqfe kbpubtypekc KB930770

Microsoft KB Archive/930770

Contents