You are currently offline, waiting for your internet to reconnect

Description of Update Rollup 5 for System Center 2012 R2 Operations Manager

This article describes the issues that are fixed in Update Rollup 5 for Microsoft System Center 2012 R2 Operations Manager. This article also contains the installation instructions for Update Rollup 5 for System Center 2012 R2 Operations Manager.

Issues that are fixed in this update rollup

Operations Manager

  • Monitoringhost process crashes because of bind failures against Active Directory

    A fix was made to prevent Monitoringhost.exe from crashing when it cannot connect to Active Directory Domain Services (AD DS). The stack trace from the crash displays a "System.DirectoryServices.ActiveDirectory.ActiveDirectoryServerDownException" error.

  • RunAs accounts cannot be edited because of "Specified cast is invalid" exception

    RunAs accounts can be distributed only to a selected computer through the distribution tab of Run As Account properties. When a computer that is in the distribution list is decommissioned from Operations Manager and the Run As account is opened, you receive the following exception, and no computers are shown on the list:

    System.InvalidCastException: Specified cast is not valid. at Microsoft.EnterpriseManagement.Monitoring.Internal.MonitoringObjectGenerated.get_Id()

    This issue is fixed and the exception no longer occurs.

  • Application crashes when a search is finished without filter criteria on Distributed application designer

    A fix was made to make sure that the console does not crash when a search is finished without filter criteria on Distributed application designer.

  • MonitoringHost crashes with the exception - System.OverflowException: Value was either too large or too small for an Int32

    Changes to entities are tracked by using the EntityChangeLogId in the EntityChangelog table and the EntityChangeLogId is mastered in the table as an Int64 value. ManagedType tables that begin with a MT_* refer to the EntityChangeLogID. The code that was used to insert into the ManagedType table had an Int32 data type instead of an Int64 data type. When the EntityChangeLogID reached greater than the Int32 limit, the exception crashed the MonitoringHost. This is fixed and the MonitoringHost no longer crashes.

  • Support to troubleshoot PowerShell scripts

    When traces are collected to troubleshoot PowerShell scripts, the logs do not display the parameters that are passed to PowerShell scripts. A code change was made to log this information to make troubleshooting easy.

  • Operational Insights through Operations Manager

    System Center Advisor is improved with many exciting features and is rebranded as "Operational Insights." Learn more about the new Operational Insights feature. The product name is updated in the Operations Manager plug-in for System Center Advisor.

  • "Reset the Baseline," "Pause the baseline," and "Resume the baseline" tasks fail when they are run against an Optimized performance collection rule

    You receive the following exception when this problem occurs:

    Microsoft.EnterpriseManagement.ContainerException: The container could not find a component with name 'TaskRuntime' compatible with type 'Microsoft.EnterpriseManagement.ServiceDataLayer.ITaskRuntimeServiceInternal, Microsoft.EnterpriseManagement.DataAccessService.Core

  • An exception occurs when you edit subscriptions that contain deleted monitors or objects

    A subscription is created by using the "created by specific rules or monitors" criterion. When such a subscription is edited and the monitors or rules associated with them are deleted, you receive the following exception:

    System.NullReferenceException: Object reference not set to an instance of an object.
    at Microsoft.EnterpriseManagement.Mom.Internal.UI.Controls.SourceChooserCriteriaItem.GetSources()
    at Microsoft.EnterpriseManagement.Mom.Internal.UI.Controls.SourceChooserCriteriaItem.Search(CancelFlagWrapper cancelFlag)

    This is fixed not to throw an exception and display the other valid rules or monitors.

  • You can't set Widget column width

    When an explicit column width is set for a widget, the width is not honored in the grid that is displayed. This was caused because of an incorrect Regex validation expression. This has now been fixed and the explicit column width should start reflecting in the UI.

  • Event 4506: Data was dropped because of too much outstanding data

    When too much data is pushed into a module, Operations Manager logs 4506 messages and then drops data. The hardcoded limit is 5120 items globally (in the agent). This global limit is parameterized and exposed through the registry. You can set the value by creating one of the two following registry keys:

    Registry key 1Registry key 2
    Registry location:
    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\System Center\Health Service

    DWORD Name: Maximum Global Pending Data Count
    DWORD Value:nnnn

    (Where nnnn is the number of items globally. Set this value to more than 5120, as needed.)
    Registry location:

    DWORD Name: Maximum Global Pending Data Count
    DWORD Value:nnnn

    (Where nnnn is the number of items globally. Set this value to more than 5120, as needed.)

  • Support for handling Datawarehouse time-outs

    Operations Manager datawarehouse throws events such as 31551, 31552, 31553 when there are problems inserting data to the datawarehouse. One reason these events can occur are because of SQL time-out exceptions. When such events related to SQL time-out exceptions are logged, the logs now also contain information about how to extend these timeouts. You can read more about these exceptions here.

  • Can't continue scan with NOLOCK because of data movement

    When a component such as Orchestrator tries to call the Operations Manager database function fn_AlertViewChanges, it could throw the "Could not continue scan with NOLOCK because of data movement" exception. This is triggered by a redundant NOLOCK statement in the SQL SP. This is fixed, as are any failures that are caused by this exception.

  • $ScriptContext.Context does not persist the value in PowerShell widgets

    PowerShell widgets that use $ScriptContext.Context display a blank. With this fix, the context now persists.

  • Evaluation version alert

    Operations Manager previously displayed a Warning 60 days, 30 days, 1 day, and last-day hourly before the expiration of the evaluation period. This has been changed to an error so that you know Operations Manager will stop working as soon as the evaluation period is over. It also contains a link to a KB article that helps you convert the evaluation version to a registered version.

UNIX/Linux management pack

  • Updating the UNIX/Linux agent for Operations Manager resets deep monitoring status for JEE application servers.

    This issue applies to Java Application Server instances that have “Deep Monitoring” enabled. When you upgrade the UNIX/Linux agent for Operations Manager, the instances are no longer “Deep Monitored,” and they require another execution of the Enable Deep Monitoring management pack task.

  • By default, the rpcimap monitor for Red Hat Enterprise Linux 5 is now disabled.

    Red Hat Enterprise Linux 5.10 and later versions removes the default rpcimap daemon that's present in earlier Red Hat Enterprise Linux 5 releases. Critical alerts are generated for the rpcimap service that's not running on Red Hat Enterprise Linux 5.10. By default, the rpcimap monitor for Red Hat Enterprise Linux 5 is now disabled. However, it can be re-enabled by an override in the management pack.

  • Monitoring in time zone UTC +13 (for example, Auckland, New Zealand with daylight saving time) causes the “Unix Process Monitoring template” to fail.

    This issue applies to all UNIX/Linux servers that are located in the UTC +13 time zone. When you try to use the Unix Process Monitoring template for a server that's located in UTC +13 time zone, the following warning may be logged in the agent’s log (/var/opt/microsoft/scx/log/scx.log):

    Warning [scx.core.providers.provess_provider:266:2250:140361722332992] SCX_UnixProcess_Class_Provider: EnumerateInstances - Formal argument 'offsetFromUTC' is invalid: SCXRelativeTime: years=0 months=0 days=0 hours=0 minutes=780 microseconds=0 - [/home/serviceb/ScxCore_R2URNext_Debian50_x64/pal/source/code/scxcorelib/pal/scxtime/absolute.cpp:856]

  • When you use the "scxadmin -log-rotate" utility, this stops logging to the agent’s log (/var/opt/microsoft/scx/log/scx.log) after log rotation is completed.

    When you use the scxadmin program together with the -log-rotate option, logging in /var/opt/microsoft/scx/log/scx.log may not resume unless a restart is issued (scxadmin -restart).

How to obtain and install Update Rollup 5 for System Center 2012 R2 Operations Manager

Download information

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

Microsoft Update
To obtain and install an update package from Microsoft Update, follow these steps on a computer that has an Operational Manager 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 package, and then click OK.
  6. Click Install updates to install the update package.
Manual download of the update packages
Go to the following website to manually download the update packages from the Microsoft Update Catalog:

Installation instructions

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 multilanguage, 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 time-out 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 time-out.

    Registry location:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse

    DWORD name: Bulk Insert Command Time Out Seconds
    DWORD Value: 40

    Note Set this value in seconds. For example, for a 40-second time-out, set this value to 40.
Supported installation order
We recommend that you install this update rollup package by following these steps in the given order:
  1. Install the update rollup package on the following server infrastructure:
    • Management server or servers
    • Gateway servers
    • Web console server role computers
    • Operations console role computers

  2. Apply SQL scripts (see installation information).
  3. Manually import the management packs.
  4. Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.

Note If the Connected MG/Tiering feature is enabled, you should first update the top tier of the Connected MG/Tiering feature.
Operations Manager Update
To download the update rollup package and extract the files that are contained in the update rollup package, 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 the Microsoft Download 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. Execute the flowing Datawarehouse SQL script on Datawarehouse Server against OperationsManagerDW database:


    Note This script is located in the following path:

    %SystemDrive%\Program Files\System Center 2012 R2\Operations Manager\Server \SQL Script for Update Rollups

  4. Execute the following Database sql script on the Database server against the OperationsManagerDB database:


  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.Advisor.Resources.LANGUAGECODE_3LTR.mpb

For information about how to import a management pack from a disk, see the How to Import an Operations Manager Management Pack topic on the Microsoft TechNet website.

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 Management Pack update
To install the updated monitoring packs and agents for UNIX and Linux operating systems, follow these steps:
  1. Apply Update Rollup 5 to your System Center 2012 R2 Operations Manager environment.
  2. Download the updated management packs for System Center 2012 R2 from the following Microsoft website:

  3. Install the management pack update package to extract the management pack files.
  4. Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment.
  5. Upgrade each agent to the latest version by using either the Update-SCXAgent Windows PowerShell cmdlet or the UNIX/Linux Agent Upgrade Wizard in the Administration pane of the Operations Console.

Uninstall information

To uninstall an update, run the following command:

msiexec /uninstall PatchCodeGuid /package RTMProductCodeGuid

Note In this command, PatchCodeGuid is a placeholder that represents one of the following GUIDs:

Additionally, RTMProductCodeGuid is a placeholder that represents one of the following GUIDs:
Console (AMD64){041C3416-87CE-4B02-918E-6FDC95F241D3}
Console (x86){175B7A24-E94B-46E5-A0FD-06B78AC82D17}
WebConsole (AMD64){B9853D74-E2A7-446C-851D-5B5374671D0B}
SCX-ACS (AMD64){46B40E96-9631-11E2-8D42-2CE76188709B}
SCX-ACS (x86){46B40E96-9631-11E2-8D42-2CE76188709B}
Agent {786970C5-E6F6-4A41-B238-AE25D4B91EEA}

Files updated in this update rollup

Operations Manager update
Files that are changedVersionSize
Microsoft.EnterpriseManagement.UI.Authoring.dll7.1.10226.10529.9 MB
HealthServiceRuntime.dll7.1.10213.0320 KB
Microsoft.EnterpriseManagement.DataAccessService.core.dll7.5.3079.277711 KB
Microsoft.Mom.UI.Components7.1.10226.10526.15 MB
Microsoft.EnterpriseManagement.Modules.PowerShell.dll7.1.10213.097.4 KB
Microsoft.EnterpriseManagement.DataAccessService.OperationsManager.dll7.1.10226.1052580.4 KB
Microsoft.EnterpriseManagement.RuntimeService.dll7.1.10226.1052395.9 KB
Microsoft.EnterpriseManagement.Utility.WorkflowExpansion.dll7.1.10226.105272.4 KB
Microsoft.Mom.Common.dll7.1.10226.1052248.5 KB
Microsoft.Mom.DiscoveryDatabaseAccess.dll7.5.3079.277170.6 KB
Microsoft.Mom.Sdk.Authorization.dll7.5.3079.277195 KB
Microsoft.EnterpriseManagement.DataWarehouse.DataAccess.dll7.1.10226.1052236 KB
Microsoft.SystemCenter.2007.mp7.1.10226.1052432 KB
update_rollup_mom_db.sql7.1.10226.105290 KB
Microsoft.EnterpriseManagement.Presentation.Controls.dll7.1.10226.10521.78 MB
Microsoft.SystemCenter.Advisor.mpb7.1.10226.1052356 KB
Microsoft.SystemCenter.Visualization.Component.Library.mpb7.1.10226.1052294.9 KB
Microsoft.EnterpriseManagement.UI.Administration.dll7.1.10226.10524.47 MB
Microsoft.EnterpriseManagement.UI.Administration.resources.dll7.1.10226.10522.53 MB
Microsoft.SystemCenter.Advisor.Resources.(LANGUAGECODE_3LTR).mpb7.1.10226.105073.7 KB
UNIX/Linux Management Pack update
Files that are changedFile sizeVersion


Article ID: 3023138 - Last Review: 03/18/2015 01:27:00 - Revision: 4.0

Microsoft System Center 2012 R2, Microsoft System Center 2012 R2 Operations Manager

  • kbqfe kbfix kbexpertiseinter atdownload KB3023138