|Issue summary||Summary details|
|The Product Knowledge tab is displayed as the Company Knowledge tab after you import a language pack for System Center Operations Manager 2007 R2.||You import a language pack for a management pack on a computer that is running System Center Operations Manager 2007 R2. After you do this, you experience the issue when you use Operations Manager Administration Console or Web Console to view rules or to view monitors that are contained in the management pack.|
|An agent cannot be removed successfully from a Windows Cluster service node.||After an agent is deployed to a Windows Cluster service node by using the discovery-based installation, it cannot be uninstalled from the Operations console. Additionally, the following error is returned:|
Agent is managing other devices and cannot be uninstalled
|The Heathservice.exe process on a Windows Cluster service passive node may have excessive CPU utilization.||The Healthservice.exe process may have high CPU utilization on all the passive nodes of a monitored Windows Cluster service. This issue is caused by an incorrect determination of the correct Healthservice ID when this process tries to initialize dependency monitors. The passive node Healthservice ID is used instead of the active node ID. |
|The Healthservice.exe process may crash when it uses the OLE DB module to run multiple queries.||When the Healthservice.exe process uses the OLE DB probe to run multiple queries and to update operations, the process may encounter an access violation error if some records from a query are expected but no records are returned.|
|The workflows that use the OLE DB data source may unload themselves if the underlying provider returns a null string or an empty string.||If an OLE DB provider returns an error to the Operations Manager OLE DB module but does not return an error string, the module incorrectly unloads itself.|
|An instance of the MonitoringHost.exe process may cause a memory leak in nonpaged pool memory.||When you try to monitor a generic text log file or a generic CSV log file in a folder that does currently not exist, a nonpaged pool memory leak occurs when a directory change notification is received for the parent directory.|
|The notification subscriptions do not work if they are configured to parse a CustomField field or an AlertOwner field.||When you create a notification subscription that has the "with specific text in Custom Field" criteria or that has the "assigned to a specific owner" criteria, the subscription does not generate a notification. |
|The Operations console loses the status as the current object that is in focus when a search filter is applied.||Consider the following scenario:|
In this scenario, the Operations console loses the status as the current object that is in focus as the console reloads. This update allows the object to remain in focus in this scenario, in some other selected operations, and in some other selected tasks.
- You click the Find command that is in the Operations console.
- You type a string in the Look for text box, and then you click Find Now. There are multiple objects that are returned.
- You select a returned object.
|The SRSUpgradeTool.exe process returns an error that states “Failed while updating registry entry for reporting code MSI component” when you try to upgrade SQL Reporting Services 2005 to SQL Reporting Services 2008.||An updated version of the SRSUpgradeTool.exe file is in the SupportTools folder of this update. This file was originally supplied in the SupportTools folder of the Operations Manager 2008 R2 distribution media.|
The 32-bit version and the 64-bit version that is provided in this update support the upgrade for the reporting role host from SQL Server Reporting Services 2005 to SQL Server Reporting Services 2008.
|The Operations Manager user interface (UI) may crash when the Connector column and the Forwarding Status column are added to an Alert view.||When you customize an Alert view by adding the Connector column or the Forwarding status column to the view, the Operations Console may crash.|
|The agents may re-process old Windows event log entries and then incorrectly generate new alerts.||In a scenario where an agent exits maintenance mode or where an agent is upgraded, the event log module may re-process old events from the Windows event log. Therefore, alerts might be re-generated for these previously processed events.|
|Health state reliability fixes and improvements.||An incorrect health state for a unit monitor may appear in the Operations console, in the Web Console, or in the Health Explorer after the object has entered and then exited maintenance mode.|
Because of a race condition, an aggregate monitor may display an incorrect health state. However, its child-dependency monitor and contributors display the correct state.
|The Operations Manager Audit Collection Service (ADTServer.exe) does not start on an ACS Collector if the operating system is upgraded to Windows Server 2008 R2.||The AdtServer service does not start and logs the following event ID 4672 in the Operations Manager event log:|
AdtServer encountered the following problem during startup: Apply this Cumulative Update to the ACS Collector role to resolve this issue. This update can be applied before or after you upgrade the operating system.
Task: Open Audit Database
Failure: An error occurred connecting to the database
Error Message:The system cannot find the file specified.
Error2: The system cannot find the file specified when we attempt to start the service manually.
|When you export a performance report, the list of object instances do not appear. When you export a performance report to a file format such as the Portable Document Format (PDF), the object instances do not appear in the report.||An updated version of the management pack library that should be manually imported is in this update.|
The fixes for some issues that are mentioned in Knowledge Base (KB) article 974722 "Support for Windows Server 2008 R2 and Windows 7 in System Center Operations Manager 2007" are also included in this update
The following fixes that are discussed in KB article 974722 are included in this update:
|Operations Manager services stop unexpectedly on a root management server whose operating system was upgraded to Windows Server 2008 R2|| Apply the hotfix update for KB article 974144 to the root management server after the operating system is upgraded to Windows Server 2008 R2.|
Note If the update for KB article 974144 has already been applied to the root management server, it can be safely reapplied to correct this issue.
|The Operations Manager Audit Collection Service (ADTServer.exe) does not start after you upgrade the operating system to Windows Server 2008 R2.|| Apply hotfix update for KB article 974144 to the computer after you upgrade the operating system (OS) of the computer to Windows Server 2008 R2.|
If the hotfix update for KB article 974144 has already been applied to the computer before the OS upgrade, then you do not have to reapply the update.
List of known issues for this update
|When you apply the ACS Server update, you may have to restart the server if a file is found to be in use. Additionally, the following error is returned:|
Error 2803: Dialog View did not find a record for dialog
|Restart the computer that is running ACS Server after you apply the update.|
|During the cumulative update installation on an RMS or an MS role if a file to be updated is currently in use you will receive the following dialog request: "For the configuration changes made to System Center Operations Manager 2007 R2 to take effect you must restart you system. to restart now click Yes, or click No if you plan to manually restart at a later time." If you click No to this dialog, the computer will restart and the agent updates are not applied.||Install the cumulative update on the RMS or the MS role with the "Run Server Update" option. If the above dialog is displayed choose the No option. When the update has installed completely, exit the System Center Operations Manager 2007 Software Update screen and restart computer.|
|Applying the cumulative update to the Gateway server role does not copy the agent updates to the <Operations Manager installation root>\AgentManagement\<platform> folders.||After applying the update to a Gateway server role via the "Run Gateway Update" option manually copy the agent updates to the AgentManagement\<platform> folders using the following steps:|
- Locate the update installation folder: Program Files\System Center 2007 R2 Hotfix Utility\KB974144
- Copy the KB974144-x86-Agent.msp, KB974144-x64-Agent.msp, and KB974144-IA64-Agent.msp files from the Agent folder contained beneath the update installation folder to the correct AgentManagement\<Platform> folder of the Gateway server.
Copy KB974144-x64-Agent.msp to the <Operations Manager installation root folder>\AgentManagement\Amd64 folder.
Copy KB974144-x86-Agent.msp to the <Operations Manager installation root folder>\AgentManagement\x86 folder.
Copy KB974144-IA64-Agent.msp to the <Operations Manager installation root folder>\AgentManagement\IA64 folder.
Released fixes that are not included in this update
The following released Operations Manager 2007 R2 hotfixes are not included in this update because they include SQL Server Transact-SQL scripts, because they include SQL Stored Procedure updates, or because they include cross platform agent updates. Refer to the individual KB articles for information about how to obtain a fix for these issues. For up-to-date information, refer to KB article 973583.
|KB article||Article title|
|KB973583||Description of the System Center Operations Manager 2007 R2 Cross Platform Agent Update|
This update must be applied to each computer that meets any of the following conditions:
- Hosts a Microsoft Operations Manager Root Management Server
- Hosts a Microsoft Operations Manager Management Server
- Hosts a Microsoft Operations Manager Gateway Server
- Hosts a Microsoft Operations Manager Operations console
- Hosts a Microsoft Operations Manager Web Console server
- Hosts a Microsoft Operations Manager agent that was manually installed
- Hosts a Microsoft Operations Manager Audit Collection Service
Before you apply this update, we recommend that you back up the Operations database.
Recommended installation order
We recommend that you install this cumulative update in your environment in the following order:
- Root Management Server (RMS)
- Manual update of the Operations Manager database together with the included stored procedure file that is discussed later
- Manual import of the Management Pack library that is discussed later
- Secondary Management Servers
- Gateway Servers
- Deploy the agent update to the agents that used a discovery-based installation
- Operations console role computers (Choose the Run Server Update option from the Software Update dialog)
- Web Console server role computers
- Audit Collection Service role computers
- Apply the agent update to manually installed agents
To extract the files that are contained in this update, follow these steps:
- Copy the following file to either a local folder or to an available network-shared folder:
- Then runthis file locally on each applicable computer that meets the conditions that were mentioned earlier.
You can run this file by using either Windows Explorer or by using a command prompt.
Note To run this file on a computer that is running Windows Server 2008, you must use an elevated command prompt. An elevated command prompt is a command prompt that was started by using the Run as Administrator option. If you do not run this Windows-based installer file under an elevated command prompt, the System Center Operations Manager 2007 Software Update splash screen does not allow for the installation of the hotfix.
- On the System Center Operations Manager 2007 Software Update window, select the update option that is appropriate for the role that will be updated.
If a file to be updated is found to be in use during the MSI update you may receive a dialog message "For the configuration changes made to System Center Operations Manager 2007 R2 to take effect you must restart your system. To restart now click Yes, or click No if you plan to manually restart at a later time". Choose the "No" option if presented with this dialog. Allow MSI installation to complete and then exit the "System Center Operations Manager 2007 Software Update" before restarting the computer.
This update affects the following files:
- ADTSrvdll.dll (Version 6.1.7221.13)
- FormatTracing.cmd (Not versioned)
- HealthService.dll (Version 6.1.7221.13)
- Microsoft.EnterpriseManagement.DataWarehouse.DataAccess.dll (Version 6.1.7221.13)
- Microsoft.EnterpriseManagement.OperationsManager.DataAbstrationLayer.dll (Version 6.1.7221.13)
- Microsoft.EnterpriseManagement.OperationsManager.dll (Version 6.1.7221.13)
- Microsoft.EnterpriseManagement.OperationsManager.Web.ConsoleFramework.dll (Version 6.1.7221.13)
- Microsoft.EnterpriseManagement.UI.Authoring.dll (Version 6.1.7221.13)
- Microsoft.Mom.DiscoveryDatabaseAccess.dll (Version 6.1.7221.13)
- Microsoft.Mom.RecorderBarBHO.dll (Version 184.108.40.206)
- Microsoft.MOM.UI.Common.dll (Version 6.1.7221.13)
- Microsoft.Mom.UI.Components.dll (Version 6.1.7221.13)
- MobileWebConsole.dll (Version 6.1.7221.13)
- MOMBidLdr.dll (Version 5.2.3790.1290)
- MOMConnector.dll (Version 6.1.7221.13)
- MOMModules.dll (Version 6.1.7221.13)
- MOMNetworkModules.dll (Version 6.1.7221.13)
- RootWebConsole.dll (Version 6.1.7221.13)
- RSSWebConsole.dll (Version 6.1.7221.13)
- SRSUpgradeTool.exe (Version 6.1.7221.13)
- DiscoveryEntitySProcs.sql (Not versioned)
- Microsoft.SystemCenter.DatawareHouse.Report.Library.mp (Version 6.1.7221.13)
Date Time Version Size File name -------------------------------------------------------------- 08-Jan-2010 11:40 6.1.7221.13 385,416 Adtsrvdll.dll 14-Nov-2009 10:06 4,808 Formattracing.cmd 22-Sep-2009 11:17 108,204 Discoveryentitysprocs.sql 22-Sep-2009 11:17 108,204 Discoveryentitysprocs.sql 07-Jan-2010 20:38 6.1.7221.13 63,368 SRSUpgradeTool.exe 08-Jan-2010 11:57 6.1.7221.13 1,586,568 Healthservice.dll 08-Jan-2010 10:59 6.1.7221.13 227,208 Microsoft.enterprisemanagement.datawarehouse.dataaccess.dll 08-Jan-2010 11:38 6.1.7221.13 247,688 Microsoft.enterprisemanagement.operationsmanager.dataabstractionlayer.dll 08-Jan-2010 10:59 6.1.7221.13 2,262,920 Microsoft.enterprisemanagement.operationsmanager.dll 08-Jan-2010 11:38 6.1.7221.13 894,856 Microsoft.enterprisemanagement.operationsmanager.web.consoleframework.dll 08-Jan-2010 11:00 6.1.7221.13 6,723,464 Microsoft.enterprisemanagement.ui.authoring.dll 08-Jan-2010 11:00 6.1.7221.13 161,672 Microsoft.mom.discoverydatabaseaccess.dll 08-Jan-2010 10:36 220.127.116.11 37,888 Microsoft.mom.recorderbarbho.dll 08-Jan-2010 11:00 6.1.7221.13 2,250,632 Microsoft.mom.ui.common.dll 08-Jan-2010 11:00 6.1.7221.13 4,687,752 Microsoft.mom.ui.components.dll 08-Jan-2010 11:54 6.1.7221.13 77,704 Mobilewebconsole.dll 08-Jan-2010 10:36 5.2.3790.1289 50,176 Mombidldr.dll 08-Jan-2010 11:57 6.1.7221.13 466,824 Momconnector.dll 08-Jan-2010 11:57 6.1.7221.13 1,915,272 Mommodules.dll 08-Jan-2010 11:19 6.1.7221.13 638,344 Momnetworkmodules.dll 08-Jan-2010 11:54 6.1.7221.13 357,256 Rootwebconsole.dll 08-Jan-2010 11:54 6.1.7221.13 38,280 Rsswebconsole.dll 08-Jan-2010 11:11 6.1.7221.13 702,344 Microsoft.systemcenter.datawarehouse.report.library.mp
Date Time Version Size File name -------------------------------------------------------------- 07-Jan-2010 16:35 6.1.7221.13 522,632 Adtsrvdll.dll 19-Nov-2009 14:54 4,808 Formattracing.cmd 22-Sep-2009 11:17 108,204 Discoveryentitysprocs.sql 07-Jan-2010 20:38 6.1.7221.13 63,368 SRSUpgradeTool.exe 07-Jan-2010 17:22 6.1.7221.13 2,711,432 Healthservice.dl 07-Jan-2010 15:45 6.1.7221.13 227,208 Microsoft.enterprisemanagement.datawarehouse.dataaccess.dll 07-Jan-2010 16:31 6.1.7221.13 247,688 Microsoft.enterprisemanagement.operationsmanager.dataabstractionlayer.dll 07-Jan-2010 15:45 6.1.7221.13 2,262,920 Microsoft.enterprisemanagement.operationsmanager.dll 07-Jan-2010 16:31 6.1.7221.13 894,856 Microsoft.enterprisemanagement.operationsmanager.web.consoleframework.dll 07-Jan-2010 15:45 6.1.7221.13 6,723,464 Microsoft.enterprisemanagement.ui.authoring.dll 07-Jan-2010 15:45 6.1.7221.13 161,672 Microsoft.mom.discoverydatabaseaccess.dll 07-Jan-2010 15:13 18.104.22.168 50,176 Microsoft.mom.recorderbarbho.dll 07-Jan-2010 15:45 6.1.7221.13 2,250,632 Microsoft.mom.ui.common.dll 07-Jan-2010 15:45 6.1.7221.13 4,687,752 Microsoft.mom.ui.components.dll 07-Jan-2010 16:54 6.1.7221.13 77,704 Mobilewebconsole.dll 07-Jan-2010 15:13 5.2.3790.1289 51,712 Mombidldr.dll 07-Jan-2010 17:22 6.1.7221.13 732,552 Momconnector.dll 07-Jan-2010 17:22 6.1.7221.13 2,904,456 Mommodules.dll 07-Jan-2010 16:09 6.1.7221.13 923,016 Momnetworkmodules.dll 07-Jan-2010 16:54 6.1.7221.13 357,256 Rootwebconsole.dll 07-Jan-2010 16:54 6.1.7221.13 38,280 Rsswebconsole.dll 07-Jan-2010 15:59 6.1.7221.13 702,344 Microsoft.systemcenter.datawarehouse.report.library.mp
Date Time Version Size File name -------------------------------------------------------------- 11-Nov-2009 13:56 4,808 Formattracing.cmd 07-Jan-2010 11:36 6.1.7221.13 4,381,064 Healthservice.dll IA64 07-Jan-2010 10:35 5.2.3790.1289 109,568 Mombidldr.dll IA64 07-Jan-2010 11:36 6.1.7221.13 1,385,864 Momconnector.dll IA64 07-Jan-2010 11:36 6.1.7221.13 5,639,560 Mommodules.dll IA64 07-Jan-2010 11:36 6.1.7221.13 1,841,032 Momnetworkmodules.dll IA64
Operations that must be performed manually after you update the root management server
The following supplied management pack must be imported manually and is located in the ManagementPacks
The MSI file that is released for each localized version of Operations Manager contains the appropriate localized version of the management pack.
For example, the following file contains the management pack for the Japanese localized version of Operations Manager:
The following updated SQL Stored Procedure (also known as SPROC) file is included which must be manually installed:
We recommend that you apply this update to the Operations database after you have successfully applied the appropriate server update to the RMS role.
Steps to install DiscoveryEntitySPRocs.sql
To apply this database update by using the DiscoveryEntitySPRocs.sql file, you may have to follow two separate procedures. If the RMS role and the Operations database role reside on a single computer, and if the hotfix files are installed on the RMS role, you have to follow only Procedure 2.
The following is a summary of these procedures:
- Extract the hotfix files from the package by running the MSI file.
- Use Microsoft SQL Server Management Studio to run commands that are in the supplied Transact-SQL file against the Operations Manager Database server.
Details of these procedures are as follows.
Procedure 1: How to extract the hotfix files
This procedure can be performed on any computer that has SQL Server Management Studio installed and that can connect to the Operations Manager Operations database server.
To extract the management pack files that are contained in this hotfix, follow these steps:
- Copy the following file to either a local folder or to an available network-shared folder:
- Run this file for everyone. Note the installation path that is suggested in the installation.
The installation path is typically the following:
Program Files\System Center 2007 R2 Hotfix Utility
Procedure 2: How to use SQL Server Management Studio to run commands that are in the supplied DiscoveryEntitySProcs.sql file
- On the root management server, stop the System Center Management service, the System Center Management Configuration service, and System Center Data Access service.
- Log on to the computer that hosts the Operations Manager 2007 database server role as a user who has database owner rights (“dbo” rights) to the Operations Manager 2007 database. To perform the database update remotely, log on to a computer that hosts SQL Server Management Studio as a user who has appropriate "dbo" rights to the Operations Manager 2007 database. Run SQL Server Management Studio.
- In the Connect to Server dialog box, connect to the SQL Server that hosts the Operations Manager database.
- Click New Query on the toolbar.
- From the SQL Editor toolbar, use the Available databases option to select the Operations Manager database. For example, the "OperationsManager" database.
- On the File menu, click Open, and then browse for the path that was noted in Procedure 1 and that contains the DiscoveryEntitySProcs.sql file. Select this file, and then click Open.
- When the file is loaded, click Execute in the SQL Editor toolbar.
- View the Messages pane to check whether the Transact-SQL commands executed successfully.
- Exit SQL Server Management Studio.
- On the root management server, start the System Center Management service, the System Center Management Configuration service, and System Center Data Access service.
Updated Support Tools that are included
The following updated file that is located in the SupportTools
folder supports the upgrade from SQL Reporting Services 2005 to SQL Reporting Services 2008:
Use the appropriate platform version of this file instead of the file that is supplied in the SupportTools
folder of the Operations Manager 2008 R2 distribution media.
Recommended steps for applying this cumulative update on a clustered Root Management Server
- Log on to the first node of the cluster with an account that is a member of the Operations Manager Administrators role for your Operations Manager 2007 management group and open Cluster Administrator.
- In the navigation pane, expand the cluster name, expand Groups, and then click the Operations Manager group.
- In the results pane, examine the cluster resources listed in Name column and ensure they are online.
- In the results pane, in the Owner column, note which node is the owner node.
- Ensure that you have logged on to the owner node. If not, in the navigation pane, right-click the Operations Manager cluster group, click Move Group, and then select the node from the list representing the node you have logged onto.
- During the update of a multiple-node cluster, if a service is stopped during the update, the cluster might interpret this as a failure and fail over to another node. To prevent this issue, stop or pause the cluster service on all nodes except the one that you are updating. Alternately you can use steps 6a through 6c to limit the nodes that a service can run on to the specific node you are upgrading. This must be done for all resources listed.
- In the Cluster Administrator pane, right-click the service you want to change (for example, OpsMgr Health Service), and then click Properties.
- In the Properties dialog box, click Modify.
- In the Modify Preferred Owner dialog box, under Available nodes, select the node you are performing the upgrade on, make sure it is the only node listed under Preferred owners, and then click OK.
Note Step 6 must be followed on every node that is being updated. After the update of a particular node is complete, users should re-add failover nodes to the Available Nodes list. After all the nodes have been updated, configure your Operations Manager 2007 group to failover to the original primary node.
- Follow the Installation steps as documented above (main Installation Steps section for this update) for the Root Management Server (RMS) role, applying the update via the Run Server Update option.
- Repeat the update of this procedure on all nodes of the cluster. For each additional node, ensure that you log into the node you are upgrading and that all cluster groups have failed over to the node.