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 8 for System Center 2012 Operations Manager Service Pack 1

Update Rollup 8 for System Center 2012 Operations Manager Service Pack 1

View products that this article applies to.

Introduction

This article describes the issues that are fixed in Update Rollup 8 for Microsoft System Center 2012 Operations Manager Service Pack 1 (SP1). Additionally, this article contains the installation instructions for Update Rollup 8 for System Center 2012 Operations Manager SP1.

↑ Back to the top

Issues that are fixed in this update rollup

Operations Manager

  • The Health Service bouncing that is caused by high memory usage in the MonitoringHost process.
  • This update includes a fix to prevent resynchronization of all managed entities from the Operations Manager to the Operations Manager Data Warehouse (OMDW) database and to prevent the failure to sync that this causes because of duplicate entries. The duplicate entries cause the following exception to occur:

    Description:
    Data was written to the Data Warehouse staging area but processing failed on one of the successive 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'.

  • The import of Visualization.component.library and Visualization.library binary files (.mpb) fails. The import succeeds on a successive try.
  • System Center Operations Manager agents randomly time out when authenticating to the Gateway or Management Server because of domain controller or network performance issues. The time-out value was set to 1 second earlier. A fix was made to increase server time out to-20 seconds and client time out to 5 minutes.

For issues that were fixed in previous update rollups that are included in this rollup, see the following articles in the Microsoft Knowledge Base:

Supported operating systems

The following new Linux operating system version is supported:

Operating systemManagement pack
Red Hat Enterprise Linux 7 (x64)New Microsoft.Linux.RHEL.7.mpb

↑ Back to the top


How to obtain and install Update Rollup 8 for System Center 2012 Service Pack 1

Download information

The 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 applicable System Center 2012 SP1 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 package
The following file is available for manual download from the Microsoft Update Catalog:

Download Download the Operations Manager update package now.

↑ 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 multilanguage, and the updates for these components are not localized.
  • You must run the update rollup as an administrator.
  • If you do not want to restart the computer after you apply the console update, you should 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 the update rollup package immediately after you install the System Center 2012 SP1 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. After you install the web console update, you should 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"/>
    To learn about how to add a line to the <system.web> section of the web.config file, see the "Workaround" section of 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 that is described in Update Rollup 5 for System Center 2012 Operations Manager Service Pack 1 describes a registry key that the user can add to set the time-out (in seconds) for the data warehouse bulk insert commands. The following is the registry setting that controls the time-out value when new data is inserted into the data warehouse.

    The registry subkey is as follows:

    Registry key:HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse
    DWORD Name: Bulk Insert Command Timeout Seconds
    Value data:nn

    Note The placeholder nn represents a value in seconds. For example, set the value data to 40 for a 40-second time-out.
Installation instructions for Operations Manager
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 servers
    • Gateway servers
    • Web Console Server role computers
    • Operations Console role computers
  2. Apply SQL scripts. (See the installation information for the update.)
  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.

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.
  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 Datawarehouse SQL script on Datawarehouse server against the OperationsManagerDW database:
    • UR_Datawarehouse.sql


    Note The path of the script is as follows:

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

  4. Run the following database SQL script on the database server against the OperationsManagerDB database:
    • Update_rollup_mom_db.sql
  5. Import the following management packs:
    • Microsoft.SystemCenter.AlertAttachment.mpb
    • Microsoft.SystemCenter.IntelliTraceProfiling.mpb

      Note This pack has the following dependencies:
      • Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb. This should be installed from SCOM 2012 SP1.
      • MediaMicrosoft.Windows.InternetInformationServices.Common.mpb. This should be installed from the Microsoft Online Catalog.

    • Microsoft.SystemCenter.Visualization.Library.mpb
    • Microsoft.SystemCenter.Image.Library.mp
    • Microsoft.SystemCenter.Advisor.Internal.mpb
    • Microsoft.SystemCenter.Apm.Infrastructure.Monitoring.mp
    • Microsoft.SystemCenter.Apm.Infrastructure.mpb
    • Microsoft.SystemCenter.Apm.Library.mpb
    • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
    • Microsoft.SystemCenter.DataWarehouse.Reports.mp
    • Microsoft.SystemCenter.DataWarehouse.ServiceLevel.Report.Library.mp
    • Microsoft.SystemCenter.TFSWISynchronization.mpb
    • Microsoft.SystemCenter.Visualization.Component.Library.mpb

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 SP1\Operations Manager\Server\Management Packs for Update Rollups

↑ Back to the top

Files that are updated
File nameFile sizeVersion
MomConnector.dll683 KB7.0.9538.1123
MOMModules.dll2.49 MB7.0.9538.1123
Microsoft.EnterpriseManagement.DataWarehouse.DataAccess.dll230 KB7.0.9538.1123
Microsoft.EnterpriseManagement.HealthService.Modules.DataWarehouse.dll1.05 MB7.0.9538.1123
Microsoft.SystemCenter.Visualization.Component.Library.mpb284 KB7.0.9538.1123
Microsoft.Linux.RHEL.7.mpb15,716 KB7.4.4348.0

↑ Back to the top

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

↑ Back to the top

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