Issues that are fixed in System Center 2012 R2 Operations Manager Update Rollup 1

Operations Manager

Issue 1

An error occurs when you run the p_DataPurging stored procedure. This error occurs when the query processor runs out of internal resources and cannot produce a query plan.

Issue 2

Data warehouse BULK INSERT commands use an unchangeable, default 30-second time-out value that may cause query time-outs.

Issue 3

Many 26319 errors are generated when you use the Operator role. This issue causes performance problems.

Issue 4

The diagram component does not publish location information in the component state.

Issue 5

Renaming a group works correctly on the console. However, the old name of the group appears when you try to override a monitor or scope a view based on group.

Issue 6

SCOM synchronization is not supported in the localized versions of Team Foundation Server.

Issue 7

An SDK process deadlock causes the Exchange correlation engine to fail.

Issue 8

The "Microsoft System Center Advisor monitoring server" reserved group is visible in a computer or group search.

Issue 9

Multiple Advisor Connector are discovered for the same physical computer when the computer hosts a cluster.


Issue 10

A Dashboard exception occurs if the criteria that are used for a query include an invalid character or keyword.

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

Issue 1

On a Solaris-based computer, an error message that resembles the following is logged in the Operations Manager log. This issue occurs if a Solaris-based computer that has many monitored resources runs out of file descriptors and does not monitor the resources. Monitored resources may include file systems, physical disks, and network adapters.

Note The Operations Manager log is located at /var/opt/microsoft/scx/log/scx.log.

This issue occurs because the default user limit on Solaris is too low to allocate a sufficient number of file descriptors. After the rollup update is installed, the updated agent overrides the default user limit by using a user limit for the agent process of 1,024.

Issue 2

If Linux Container (cgroup) entries in the /etc/mtab path on a monitored Linux-based computer begin with the "cgroup" string, a warning that resembles the following is logged in the agent log.

Note When this issue occurs, some physical disks may not be discovered as expected.

Issue 3

Physical disk configurations that cannot be monitored, or failures in physical disk monitoring, cause failures in system monitoring on UNIX and Linux computers. When this issue occurs, logical disk instances are not discovered by Operations Manager for a monitored UNIX-based or Linux-based computer.

Issue 4

A monitored Solaris zone that is configured to use dynamic CPU allocation with dynamic resource pools may log errors in the agent logs as CPUs are removed from the zone and do not identify the CPUs currently in the system. In rare cases, the agent on a Solaris zone with dynamic CPU allocation may hang during routine monitoring. 

Note This issue applies to any monitored Solaris zones that are configured to use dynamic resource pools and a "dedicated-cpu" configuration that involves a range of CPUs.

Issue 5

An error that resembles the following is generated on Solaris 9-based computers when the /opt/microsoft/scx/bin/tools/setup.sh script does not set the library pathcorrectly. When this issue occurs, the omicli tool cannot run.

Issue 6

If the agent does not retrieve process arguments from the getargs subroutine on an AIX-based computer, the monitored daemons may be reported incorrectly as offline. An error message that resembles the following is logged in the agent log:

Issue 7

The agent on AIX-based computers considers all file cache to be available memory and does not treat minperm cache as used memory. After this update rollup is installed, available memory on AIX-based computer is calculated as: free memory + (cache – minperm).

Issue 8

The Universal Linux agent is not installed on Linux computers that have OpenSSL versions greater than 1.0.0 if the library file libssl.so.1.0.0 does not exist. An error message that resembles the following is logged:

Installation instructions for Operations Manager

Known issues for this update

• After you install the update rollup package on all roles on the server that is running System Center Operations Manager 2012 R2 (except on the Gateway roles), the updates do not appear in the Add or Remove Programs item in Control Panel.

• After you install the update rollup package, the version number of the console is not changed.

• After you install the update rollup package on a web console, you receive the following error message in Internet Explorer:
  
  

  Server Error in '/OperationsManager' Application.
  To resolve this issue, close and then restart Internet Explorer.

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, 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 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 webpages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0
  

• The fix for Issue 2 (Data warehouse BULK INSERT commands time-out issue) adds a registry key that can be used to set the time-out (in seconds) for the data warehouse BULK INSERT commands. These are the commands that insert new data into the data warehouse. The key name is as follows:
  

  HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse\
  
  The value name is as follows:
  

  Bulk Insert Command Timeout Seconds
  
  The value is a dword value. For example, the value name should be set to 40 for a 40-second time-out.

Supported installation order

We recommend that you install the update rollup package in the following 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.

Notes

• If the Connected MG/Tiering feature is enabled, first update the top tier of the Connected MG/Tiering feature.

• The Update Rollup 1 files have a version of 10226.1011.

Installation information

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 you can download the package from http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2904678

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 following SQL script against the OperationsManagerDB database:

4. • update_rollup_mom_db.sql

   
   Note These scripts are in the following location:
   
   %SystemDrive%\Program Files\System Center 2012 R2\Operations Manager\Server \SQL Script for Update Rollups\.

5. Import the following management packs:

   • Microsoft.SystemCenter.Advisor.mpb

   • Microsoft.SystemCenter.Advisor.Internal.mpb

   • Microsoft.SystemCenter.TFSWISynchronization.mpb. This management pack has the following dependency:
     

     • Microsoft.SystemCenter.AlertAttachment.mpb which should be installed from the System Center Operations Manager 2012 R2 RTM media.
       

   • Microsoft.SystemCenter.Visualization.Library.mpb

For information about how to import a management pack from a disk, go to the following Microsoft TechNet website:

How to Import an Operations Manager Management Pack
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

Uninstall information

To uninstall an update, run the following command:

msiexec /uninstall PatchCodeGuid /package RTMProductCodeGuid

Note In this command, the placeholder RTMProductCodeGuid represents one of the following GUIDs.

Additionally, the placeholder PatchCodeGuid represents one of the following GUIDs.

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

To install the updated monitoring packs and agents for UNIX and Linux operating systems, follow these steps:

1. Apply Update Rollup 1 to your System Center 2012 R2 Operations Manager environment.

2. Download and the updated management packs for System Center 2012 R2 from the following Microsoft website:
   

   System Center Monitoring Pack for UNIX and Linux Operating Systems

3. Install the management pack update package to extract the management pack files.

4. Import the updated Microsoft.Unix.Library management pack and the library management packs that are relevant to the Linux or UNIX platforms that you are monitoring in your environment.

5. Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment.

6. 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.