Issues that are resolved by the Operations Manager Module rollup update for System Center Operations Manager 2007 Service Pack 1: June 10, 2009

Article translations Article translations
Article ID: 959865 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

This Operations Manager Module update for System Center Operations Manager 2007 Service Pack 1 provides a resolution to the following issues and supersedes those updates that are listed in the More Information section:

Issue 1


On a Windows Server 2008-based failover cluster, the Operations Manager NTEventWorkflows are unloaded onto a virtual server. This occurs because of a problem in the detection of the physical computer name for the computer on which Operations Manager is running.

Additionally, the following event is logged in the Operations Manager event log on the active node:
Log Name:    Operations Manager
Source:       Health Service Modules
Date:         <date>
Event ID:      26004
Task Category:  None
Level:         Error
Keywords:     Classic
User:         N/A
Computer:     <computer name>
Description:
The Windows Event Log Provider is still unable to open the System event log on computer <computer name>. The Provider has been unable to open the System event log for 7000 seconds.
This issue was first documented as Issue 7 as described in KB 954049:
954049 Description of the hotfix rollup package for System Center Operations Manager 2007 Service Pack 1 and for System Center Essentials 2007 Service Pack 1: July 25, 2008

Issue 2


After a Windows Server 2003 or Windows Server 2008-based failover cluster node fails over to another node, old Operations Manager alerts are displayed in the Operations Manager console.

This problem occurs because of an issue in the Operations Manager NTEventLog module. When this issue occurs, the NTEventLog module cannot determine the last event log record for each Windows event log that is being monitored. Therefore, the module resets its pointer to the beginning of the monitored event log. This behavior can regenerate the alerts that are described in the monitored event log.

Issue 3


In a Microsoft failover cluster, resources that you want to make redundant are grouped into collections called resource groups. In these resource groups, you can have zero, one, or many network name resources. These network name resources are the names by which the network resources are addressed on the network.

By default, the Operations Manager agent selects only one network name for a resource group. That network name becomes the agentless managed entry for that resource group.

After you install this update, this default behavior can be overridden so that every network name resource in a resource group acn have a distinct agentless managed entry. To enable this behavior, follow the steps in the Enabling multiple entries for network name resources section.

Note When you enable this behavior, some duplicate alerts may occur. This is because the network names all correspond to the single physical node in the cluster. These alerts to come from the distinct agentless managed entries for the corresponding network names.

Issue 4


When Operations Manager monitors a plain text log file, the expected response from a monitor or rule does not occur if a null character was written to the plain text log file.

If an application writes a null character to a text file that Operations Manager is monitoring by using the ApplicationLog module, the module repeatedly reads the line that was logged before the null character. Therefore, no additional lines are read.

Note This issue was discovered while Operations Manager was monitoring some Oracle log files. This issue is not specific to monitoring log files on a failover cluster.

Issue 5


Depending on the operating system version and the configuration of a Microsoft Failover Cluster, events that are generated in the Windows Event Logs for clustered resources can be raised under the name of the physical node or under the network name that corresponds to the resource group.

By default, for all rules and monitors that use events as criteria, the Operations Manager agent implicitly filtered the event log to only show events that were raised from the network name for the resource group. Therefore, some events are not detected for clustered resources if the events were raised under the computer name of the physical nodes.

After you install this update, the default behavior is changed so that the implicit filter on the event log includes both the network name for the resource group and the computer name of the physical nodes.

RESOLUTION

Update Information

This fix is contained within the Microsoft System Center Operations Manager 2007 Service Pack 1 update. To see a list of issues are fixed and how to obtain the cumulative rollup, refer to this article in the Microsoft Knowledge Base:
971541 Description of System Center Operations Manager 2007 Service Pack 1

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:
http://support.microsoft.com/contactus/?ws=support
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 System Center Operations Manager 2007 Service Pack 1 installed on the computer. This hotfix must be applied to each computer that hosts any of the following:
  • Microsoft Operations Manager Root Management Server
  • Microsoft Operations Manager Management Server
  • Microsoft Operations Manager Gateway Server
  • Microsoft Operations Manually Installed Agent (Discover-based agent deployment not used)

Restart Requirement

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

Hotfix Replacement Information

This hotfix replaces the hotfix of the following KB articles:
  • 949875 When you run a task in the System Center Operations Manager 2007 Operations Console on a Russian version of Windows Server 2003, the task outputs are displayed in corrupted text
  • 950853 A memory leak occurs when you monitor Exchange Server 2007 by using the MOM 2007 agent in System Center Operations Manager 2007
  • 951380 Some computer properties for a cluster node may not be collected by the discovery process in System Center Operations Manager 2007 Service Pack 1
  • 954903 The Monitoringhost.exe process may consume all the CPU resources when a large amount of performance data is created by using a managed data source module in System Center Operations Manager 2007
  • 958254 You receive multiple "WMI Probe Module Failed Execution" alerts from Windows 2000-based computers after you install System Center Operations Manager 2007 S958254

File Information

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.
System Center Operations Manager 2007 SP1 x86

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.windows.cluster.library.mp6.0.6278.6921,38406-May-200909:32Not Applicable
Mommodules.dll6.0.6278.651,852,80007-Apr-200902:18x86
Mommodules2.dll6.0.6278.65252,80007-Apr-200902:18x86
Momagentinstaller.exe6.0.6278.56178,56009-Feb-200922:07x86

System Center Operations Manager 2007 SP1 IA-64

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.windows.cluster.library.mp6.0.6278.6921,38406-May-200909:32Not Applicable
Mommodules.dll6.0.6278.655,411,71207-Apr-200902:18IA-64
Mommodules2.dll6.0.6278.65592,28007-Apr-200902:18IA-64
Momagentinstaller.exe6.0.6278.56442,24009-Feb-200922:07IA-64

System Center Operations Manager 2007 SP1 X64

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.windows.cluster.library.mp6.0.6278.6921,38406-May-200909:32Not Applicable
Mommodules.dll6.0.6278.653,338,11207-Apr-200902:18x64
Mommodules2.dll6.0.6278.65363,39207-Apr-200902:18x64
Momagentinstaller.exe6.0.6278.56259,45609-Feb-200922:07x64

Installation Instructions



To extract the hotfix files that are contained in this hotfix, follow these steps:
  1. Copy the SystemCenterOperationsManager2007-SP1-KB959865-X86-X64-IA64-ENU.MSI file to either a local folder or available network shared folder.
  2. Run the SystemCenterOperationsManager2007-SP1-KB959865-X86-X64-IA64-ENU.MSI file locally on each computer that meets the criteria as described in the Prerequisites section.

    You can run the SystemCenterOperationsManager2007-SP1-KB959865-X86-X64-IA64-ENU.MSI file from Windows Explorer or at a command prompt.
  3. When the System Center Operations Manager 2007 Software Update dialog box appears, click Run Software Update.
  4. After the software update is successfully applied, open a copy of the Operations Manager console as an Operations Manager Administrator and browse to the Administration space.
  5. Under Device Management, select the Pending Management node.
  6. Select the agents under Agent Requires Update and then click the Approve button.

    Note The agents that are displayed under Agent Requires Update are the agents that were deployed by using Automatic discovery or by using Advanced discovery.

Note To run this Windows installer file on Windows Server 2008, you must run this file as an administrator at a command prompt. If you do not run this Windows installer file as an administrator, the System Center Operations Manager 2007 Software Update splash screen will not be displayed. Therefore, you cannot install the hotfix.

Enabling multiple entries for network name resources

To enable the functionality that is described in Issue 3 of the Symptoms section, follow these steps:

After you apply the update and import the supplied cluster Management Pack library, the cluster resource names will not be discovered automatically. The default functionality may be changed by setting the new Multiple Servers Discovery override setting to True. To do this, follow these steps:
  1. Install the update as described.
  2. Locate the updated Management Pack. The updated Management Pack is named Microsoft.Windows.Cluster.Library.MP.

    By default, the installation path on a 32-bit version of a Windows operating system is as follows:
    Program Files\System Center 2007 Hotfix Utility\Q959865

    By default, the installation path on a 64-bit version of a Windows operating system is as follows:
    Program Files (x86)\System Center 2007 Hotfix Utility\Q959865
  3. Import the updated Management Pack by using the Management Pack import wizard in the Operations Manager console.
  4. After the updated Management Pack is imported, browse to the Authoring space in the Operations Manager console and then select Object Discoveries in the Management Pack Objects node.
  5. Click Scope to display the Scope Objects dialog box.
  6. In the Look for: field type Virtual Server. Then, select the check box that is next to Virtual Server in the Target column.
  7. In the Look for: field, type Windows Cluster Service. Then, select the check box that is next to Windows Cluster Service in the Target column, and then click OK.
  8. In the Object Discoveries view, select Windows Clustering Discovery, and then select the override that you want under Action to Override the Object Discovery.
  9. From the Override Properties dialog box, select an existing Management Pack or create a new Management Pack to store the override.
  10. Check the override check box for Multiple Servers Discovery in the Override-controlled properties list, and then change the Override setting to True.
  11. Click OK to store the new override.

    Note After you do this, multiple network names for cluster resource groups that match the override criteria will be discovered.

STATUS

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

MORE INFORMATION

This update also supersedes certain module files in the following KB article:
957123 Hotfix for System Center Operations Manager 2007 S957123 enables monitoring support for IIS 7.0

However, KB 957123 must be installed so that Internet Information Service (IIS) 7.0 can use the new MOMIISModules.dll module.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 959865 - Last Review: October 8, 2011 - Revision: 5.0
APPLIES TO
  • Microsoft System Center Operations Manager 2007 Service Pack 1
Keywords: 
kbautohotfix kbexpertiseinter kbsurveynew kbbug kbfix kbqfe KB959865

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com