Update Rollup 3 for System Center 2012 R2 Operations Manager

Operations Manager

• A deadlock condition occurs when a database is connected after an outage. You may experience this issue may when one or more HealthServices services in the environment are listed as Unavailable after a database goes offline and then comes back online.

• The Desktop console crashes after exception TargetInvocationException occurs when the TilesContainer is updated. You may experience this issue after you leave the console open on a Dashboard view for a long time.

• The Password expiration monitor is fixed for logged events. To make troubleshooting easier, this fix adds more detail to Event IDs 7019 and 7020 when they occur.

• The Health service bounces because of high memory usage in the instance MonitoringHost: leak MOMModules!CMOMClusterResource::InitializeInstance. This issue may be seen as high memory usage if you examine monitoringhost.exe in Performance Monitor. Or, the Health service may restart every couple of days , depending on the load on the server.

• The Health service crashes in Windows HTTP Services (WinHTTP) if the RunAs account is not read correctly.

• Windows PowerShell stops working with System.Management.Automation.PSSnapInReader.ReadEnginePSSnapIns. You may see this issue as Event ID 22400 together with a description of "Failed to run the Powershell script."

• The PropertyValue column in the contextual details widget is unreadable in smaller widget sizes because the PropertyName column uses too much space.

• The update threshold for monitor "Health Service Handle Count Threshold" is reset to 30,000. You can see this issue in the environment, and the Health Service Handle Count Threshold monitor is listed in the critical state.

• An acknowledgement (ACK) is delayed by write collisions in MS queue when lots of data is sent from 1,000 agents.

• The execution of the Export-SCOMEffectiveMonitoringConfiguration cmdlet fails with the error "Subquery returned more than 1 value.”

• The MOMScriptAPI.ReturnItems method can be slow because a process race condition may occur when many items are returned, and the method may take two seconds between items. Scripts may run slowly in the System Center Operations Manager environment.

• When you are in the console and click Authoring, click Management Pack, click Objects, and then click Attributes to perform a Find operation, the Find operations seems unexpectedly slow. Additionally, the Momcache.mdb file grows very large.

• A delta synchronization times out on SQL operations with Event ID 29181.
  
  After you apply the hotfix mentioned in this article, you must add a registry subkey to fix this issue. To do this, add the following registry subkey on the server that is running System Center 2012 R2 Operations Manager:

  Registry location:HKEY_LOCAL_MACHINE\Software\Microsoft Operations Manager\3.0\Config Service
  DWORD name: CommandTimeoutSeconds
  DWORD Value:nn
  
  Note The default value for the nn placeholder is 30 seconds. Change this value to control the time-out for delta synchronization.
  
  

• Operations Manager grooms out the alert history before an alert is closed.

• The time-zone settings are not added to a subscription when non-English display languages are set. Additionally, time stamps on alert notifications are inaccurate for the time zone.

• Web Browser widget requires the protocol (http or https) to be included in the URL.

• You cannotaccess MonitoringHost's TemporaryStoragePath within the PowerShell Module.

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

• The TopNEntitiesByPerfGet stored procedure may cause an Operations Manager dashboard performance issue. This issue may occur when a dashboard is run together with multiple widgets. Additionally, you may receive the following error message after a time-out occurs:
  

  [Error] :DataProviderCommandMethod.Invoke{dataprovidercommandmethod_cs370}( 000000000371AA78 )
  An unknown exception was caught during invocation and will be re-wrapped in a DataAccessException. System.TimeoutException: The operation has timed out.
  at Microsoft.EnterpriseManagement.Monitoring.DataProviders.RetryCommandExecutionStrategy.Invoke(IDataProviderCommandMethodInvoker invoker)
  at Microsoft.EnterpriseManagement.Presentation.DataAccess.DataProviderCommandMethod.Invoke(CoreDataGateway gateWay, DataCommand command)

Known issues for this update rollup

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

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

• After you install this 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.

• Agent is not updated when you use Pending Patch view in the Operations Manager console.
  
  To work around this issue, deploy the update to agents by using the Repair option. To do this, expand Device Management in the Administration hierarchy, right-click Agent Managed, and then click Repair to repair the agents.

• Agent is not updated when you install from the gateway computer.
  
  To work around this issue, copy the agent update from the SCOM server to the gateway computer.
  
  For example, copy KB2929891-amd64-Agent.msp from the following: \\SCOM Server\Program Files\System Center Operations Manager\Gateway\AgentManagement\amd64
  
  Then, copy KB2929891-amd64-Agent.msp to the following: \\SCOM Gateway\Program Files\System Center Operations Manager\Gateway\AgentManagement\amd64
  
  Deploy the update to agents by using the Repair option. To do this, expand Device Management in the Administration hierarchy, right-click Agent Managed, and then click Repair to repair the agents.

• When you try to import Microsoft.SystemCenter.Visualization.Component.Library, the import fails because of missing dependencies.
  
  To resolve this issue, import Microsoft.SystemCenter.Visualization.Component.Library again.

UNIX/Linux update for System Center 2012 R2 Operations Manager

• Slow results are returned when you run the Get-SCXAgent cmdlet or view UNIX/Linux computers in the administration pane for lots of managed UNIX/Linux computers.
  
  Note 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.
  
  

• Accessing the UNIX/Linux computers view in the administration pane can sometimes trigger the following exception message:
  

  Microsoft.SystemCenter.CrossPlatform.ClientLibrary.Common.SDKAbstraction.ManagedObjectNotFoundException

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

UNIX/Linux Management Pack Bundle Update

Download instructions

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

Installation instructions