Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Update Rollup 4 for System Center 2012 R2 Operations Manager

Update Rollup 4 for System Center 2012 R2 Operations Manager

View products that this article applies to.

This article describes the issues that are fixed in Update Rollup 4 for Microsoft System Center 2012 R2 Operations Manager. Additionally, this article contains the installation instructions for Update Rollup 4 for System Center 2012 R2 Operations Manager.

↑ Back to the top

Issues that are fixed in this update rollup

Operations Manager

Issue 1

It takes many minutes for the Microsoft.Windows.CheckNTServiceStateMonitorType function to determine that the service is down.

Issue 2

An attempt to apply sensitivity rules fails, and you receive the following error message:
The monitoring configuration contains errors and cannot be applied.
Exception: System.ApplicationException: Attribute 'regexCompare' is null
at Microsoft.EnterpriseManagement.Modules.Apm.LibraryConfigManager.Tools.XmlTools.GetMandatoryAttribute(String attributeName, XmlNode node)
at any attempt to apply sensitivity rules fails with the errorMicrosoft.EnterpriseManagement.Modules.Apm.LibraryConfigManager.Modules.ApmModule.Core.Actions.AgentHandlersConfig.HiddenRuleXmlDeserializer.Deserialize(XmlNode rowData)

Issue 3

GSM locations are geotagged incorrectly on Map Widget.

Issue 4

The MonitoringHost.exe process issues too many calls to System Center Failover Clustering.

Issue 5

The re-synchronization of all managed entities from Operations Manager to the Operations Manager Data Warehouse database causes duplicate entries, and an exception that resembles the following is thrown:
Data was written to the Data Warehouse staging area but processing failed on one of the subsequent operations.
Exception 'SqlException': Sql execution failed. Error 2627, Level 14, State 1, Procedure ManagedEntityChange, Line 367, Message: Violation of UNIQUE KEY constraint 'UN_ManagedEntityProperty_ManagedEntityRowIdFromDAteTime'. Cannot insert duplicate key in object 'dbo.ManagedEntityProperty'.

Issue 6

If data is truncated and is in Terminal status to a workflow, event ID 31551 is logged, and an exception that resembles the following is thrown:
Failed to store data in the Data Warehouse. The operation will be retried.
Exception 'InvalidOperationException': The given value of type String from the data source cannot be converted to type nvarchar of the specified target column.
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataWarehouse.CollectAlertData


Issue 7

An arithmetic overflow error occurs, and an exception that resembles the following is thrown:
Data was written to the Data Warehouse staging area but processing failed on one of the subsequent operations.
Exception 'SqlException': Sql execution failed. Error 8115, Level 16, State 2, Procedure RelationshipChange, Line 180, Message: Arithmetic overflow error converting expression to data type int.

Issue 8
You experience poor performance when Operations Manager searches for attributes. Additionally, when doing more than one search in a row, the cache file (momcache.mdb) keeps increasing.

Operations Manager - UNIX and Linux Monitoring (Management Pack Update)

Issue 1
SCX agent generates lots of warnings in the log file when a user is using Security-Enhanced Linux (SELinux).

Issue 2
By default, the Rpcimap monitor for Red Hat Enterprise Linux 6 is disabled.

Operations Manager - JEE Application Server Monitoring (Management Pack Update)

Issue 1
Apache Tomcat is not discovered if it is installed from an .rpm or .deb package.

Issue 2
IBM WebSphere Network Deployment is not discovered in Windows.

↑ Back to the top

Updates in this update rollup

Operations Manager - UNIX and Linux Monitoring (Management Pack Update)

Updated files to supported the following operating systems
Operating SystemManagement Pack
Red Hat Enterprise Linux 7 (x64)Microsoft.Linux.RHEL.7.mpb
CentOS Linux 7 (x64)Microsoft.Linux.UniversalR.1.mpb
Oracle Linux 7 (x64)Microsoft.Linux.UniversalR.1.mpb

Operations Manager - JEE Application Server Monitoring (Management Pack Update)

Updated files to support the following new JEE application servers
Operating SystemManagement Pack
JBoss Application Server 7
JBoss Enterprise Application Platform 6		Microsoft.JEE.JBoss.7.mp
Wildfly Application Server 8Microsoft.JEE.Wildfly.8.mp
Apache Tomcat 8Microsoft.JEE.Tomcat.8.mp


↑ Back to the top

How to obtain and install Update Rollup 4 for System Center 2012 R2

Update packages for Operations Manager are available from Microsoft Update or by manual download.

Note You do not have to install previous released update for System Center 2012 R2 Operations Manager when you install Update Rollup 4.

Microsoft Update

To obtain and install an update package from Microsoft Update, follow these steps on a computer that has an applicable System Center 2012 R2 component installed:
  1. Click Start, and then click Control Panel.
  2. In Control Panel, double-click Windows Update.
  3. In the Windows Update window, click Check Online for updates from Microsoft Update.
  4. Click Important updates are available.
  5. Select the Update Rollup 4 package, and then click OK.
  6. Click Install updates to install the selected update packages.

Manual download of the update packages

To manually download the update packages, go to the following Microsoft Update Catalog website:

Download Download the Operations Manager package now.

Installation information

↑ Back to the top

Installation notes
  • This update rollup package is available from Microsoft Update in the following languages:
    • Chinese Simplified (CHS)
    • Japanese (JPN)
    • French (FRA)
    • German (DEU)
    • Russian (RUS)
    • Italian (ITA)
    • Spanish (ESN)
    • Portuguese (Brazil) (PTB)
    • Chinese Traditional (CHT)
    • Korean (KOR)
    • Czech (CSY)
    • Dutch (NLD)
    • Polish (POL)
    • Portuguese (Portugal) (PTG)
    • Swedish (SWE)
    • Turkish (TUR)
    • Hungarian (HUN)
    • English (ENU)
    • Chinese Hong Kong (HK)
  • Some components are multi-language, and the updates for these components are not localized.
  • You must run this update rollup as an administrator.
  • If you do not want to restart the computer after you apply the console update, close the console before you apply the update for the console role.
  • To start a new instance of Microsoft Silverlight, clear the browser cache in Silverlight, and then restart Silverlight.
  • Do not install this update rollup package immediately after you install the System Center 2012 R2 server. Otherwise, the Health Service state may not be initialized.
  • If User Account Control is enabled, run the .msp update files from an elevated command prompt.
  • You must have System Administrator rights on the database instances for the Operational Database and Data warehouse to apply updates to these databases.
  • To enable the web console fixes, add the following line to the %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config file:

    <machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

    Note Add the line under the <system.web> section, as described in the following article in the Microsoft Knowledge Base:

    911722 You may receive an error message when you access ASP.NET Web pages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0
  • The fix for the data warehouse BULK insert commands timeout issue described in Update Rollup 1 for System Center 2012 R2 Operations Manager adds a registry key that can be used to set the time-out value (in seconds) for the data warehouse BULK insert commands. These are the commands that insert new data into the data warehouse.

    Note This key must be manually added on any management server on which you want to override the default BULK insert command timeout.

    Registry location:HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Data WarehouseDWORD name: Bulk Insert Command Timeout Seconds
    DWORD Value: 40

    Note     Set this value in seconds. For example, for a 40-second time-out, set this value to 40.
Installation instructions
To download the update rollup package and extract the files that are contained in it, follow these steps:
  1. Download the update packages that Microsoft Update provides for each computer. Microsoft Update provides the appropriate updates according to the components that are installed on each computer. Or download from Microsoft Update Catalog.
  2. Apply the appropriate MSP files on each computer.

    Note MSP files are included in the update rollup package. Apply all MSP files that relate to a specific computer. For example, if the web console and console roles are installed on a management server, apply the MSP files on the management server. Apply one MSP file on a server for each specific role that the server holds.
  3. Run the following SQL script on the Database Server against the OperationsManagerDB database:

    update_rollup_mom_db.sql

    Note The path of the script is:

    %SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server \SQL Script for Update Rollups\
  4. Run the following SQL script on the Database Server against the OperationsManagerDW database:

    UR_Datawarehouse.sql

  5. Import the following management packs:
    • Microsoft.SystemCenter.TFSWISynchronization.mpb, which has the following dependency:
      • Microsoft.SystemCenter.AlertAttachment.mpb, which should be installed from the System Center Operations Manager 2012 R2 media.

    • Microsoft.SystemCenter.Visualization.Library.mpb
    • Microsoft.SystemCenter.Visualization.Component.Library.mpb
    • Microsoft.SystemCenter.Advisor.mpb
    • Microsoft.SystemCenter.Advisor.Internal.mpb
    • Microsoft.SystemCenter.2007.mp

Learn about how to import a management pack from a disk.

Note Management packs are included in the Server component updates in the following path:

%SystemDrive%\Program Files\System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups
UNIX/Linux update

This update must be installed on all computers that have the Operations Manager console installed. Additionally, to apply this hotfix, you must have version 7.5.1025.0 or later of the UNIX/Linux Process Monitoring, UNIX/Linux Log File Monitoring, and UNIX/Linux Shell Command Template management pack bundles.
Management Pack bundle update

Note Follow the installation instructions for Operations Manager - UNIX and Linux monitoring (Management Pack Update).
Files that are updated in Update Rollup 4 packages
Operations Manager
File nameFile sizeFile version
Microsoft.EnterpriseManagement.DataWarehouse.DataAccess.dll230 KB7.1.10226.1046
Microsoft.EnterpriseManagement.HealthService.Modules.DataWarehouse.dll1.05 MB7.1.10226.1046
Microsoft.EnterpriseManagement.UI.Authoring.dll9.44 MB7.1.10226.1046
Microsoft.EnterpriseManagement.Presentation.Controls.dll
(Silverlight: MonitoringPortal.xap)		1.70 MB7.1.10226.1046
Microsoft.EnterpriseManagement.Presentation.Controls.dll 1.70 MB7.1.10226.1046
mommodules.dll2.52 MB7.1.10211.0
Microsoft.SystemCenter.Visualization.Component.Library.mpb284 KB7.1.10226.1046
AgentHandlers.config120 KB7.1.10226.1046
Operations Manager – UNIX and Linux Monitoring (Management Pack Update)
File NameFile SizeVersion
Microsoft.AIX.5.3.mpb15,716KB7.5.1038.0
Microsoft.AIX.6.1.mpb15,726KB7.5.1038.0
Microsoft.AIX.7.mpb14,732KB7.5.1038.0
Microsoft.AIX.Library.mp31KB7.5.1038.0
Microsoft.HPUX.11iv2.mpb19,949KB7.5.1038.0
Microsoft.HPUX.11iv3.mpb19,839KB7.5.1038.0
Microsoft.HPUX.Library.mp31KB7.5.1038.0
Microsoft.Linux.Library.mp31KB7.5.1038.0
Microsoft.Linux.RedHat.Library.mp15KB7.5.1038.0
Microsoft.Linux.RHEL.4.mpb7,881KB7.5.1038.0
Microsoft.Linux.RHEL.5.mpb7,804KB7.5.1038.0
Microsoft.Linux.RHEL.6.mpb7,368KB7.5.1038.0
Microsoft.Linux.RHEL.7.mpb2,327KB7.5.1038.0
Microsoft.Linux.SLES.9.mpb3,794KB7.5.1038.0
Microsoft.Linux.SLES.10.mpb7,168KB7.5.1038.0
Microsoft.Linux.SLES.11.mpb4,699KB7.5.1038.0
Microsoft.Linux.SUSE.Library.mp15KB7.5.1038.0
Microsoft.Linux.Universal.Library.mp15KB7.5.1038.0
Microsoft.Linux.Universal.Monitoring.mp83KB7.5.1038.0
Microsoft.Linux.UniversalD.1.mpb14,084KB7.5.1038.0
Microsoft.Linux.UniversalR.1.mpb12,606KB7.5.1038.0
Microsoft.Solaris.9.mpb13,748KB7.5.1038.0
Microsoft.Solaris.10.mpb26,951KB7.5.1038.0
Microsoft.Solaris.11.mpb26,611KB7.5.1038.0
Microsoft.Solaris.Library.mp22KB7.5.1038.0
Microsoft.Unix.Library.mp83KB7.5.1038.0
Microsoft.Unix.LogFile.Library.mpb86KB7.5.1038.0
Microsoft.Unix.Process.Library.mpb98KB7.5.1038.0
Microsoft.Unix.ShellCommand.Library.mpb68KB7.5.1038.0
Operations Manager - JEE Application Monitoring (Management Pack update)

File NameFile SizeVersion
Microsoft.JEE.Library.mpb271 KB7.5.1038.0
Microsoft.JEE.Templates.Library.mpb115 KB7.5.1038.0
Microsoft.JEE.Templates.Library.resources.ENU.mpb60 KB7.5.1038.0
Microsoft.JEE.Templates.Library.Views.mp14 KB7.5.1038.0
Microsoft.JEE.JBoss.Library.mp43 KB7.5.1038.0
Microsoft.JEE.JBoss.4.mp55 KB7.5.1038.0
Microsoft.JEE.JBoss.5.mp55 KB7.5.1038.0
Microsoft.JEE.JBoss.6.mp55 KB7.5.1038.0
Microsoft.JEE.JBoss.7.mp55 KB7.5.1038.0
Microsoft.JEE.Wildfly.8.mp55 KB7.5.1038.0
Microsoft.JEE.Tomcat.Library.mp26 KB7.5.1038.0
Microsoft.JEE.Tomcat.5.mp51 KB7.5.1038.0
Microsoft.JEE.Tomcat.6.mp51 KB7.5.1038.0
Microsoft.JEE.Tomcat.7.mp51 KB7.5.1038.0
Microsoft.JEE.Tomcat.8.mp51 KB7.5.1038.0
Microsoft.JEE.WebLogic.Library.mp26 KB7.5.1038.0
Microsoft.JEE.WebLogic.10gR3.mp63 KB7.5.1038.0
Microsoft.JEE.WebLogic.11gR1.mp63 KB7.5.1038.0
Microsoft.JEE.WebLogic.12cR1.mp63 KB7.5.1038.0
Microsoft.JEE.WebSphere.Library.mp27 KB7.5.1038.0
Microsoft.JEE.WebSphere.7.0.mp51 KB7.5.1038.0
Microsoft.JEE.WebSphere.8.mp51 KB7.5.1038.0

Third-party information disclaimer
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

↑ Back to the top

Keywords: kb, kbnotautohotfix, atdownload, kbsurveynew, kbexpertiseinter, kbfix, kbqfe

↑ Back to the top

Article Info
Article ID : 2992020
Revision : 2
Created on : 4/9/2020
Published on : 4/9/2020
Exists online : False
Views : 322