Update Rollup 5 for System Center 2012 R2 Operations Manager

Update Rollup 5 for System Center 2012 R2 Operations Manager has been released.

More information can be found here.

Issues that are fixed in this update rollup:

  • 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” exceptionRunAs 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 designerA 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 Int32Changes 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 scriptsWhen 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 ManagerSystem 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 ruleYou 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 objectsA 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 widthWhen 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 dataWhen 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 1
Registry location:HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\System Center\Health Service

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

Registry key 2
Registry location:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\


DWORD Name: MaximumGlobalPendingDataCount 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 movementWhen 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 widgetsPowerShell widgets that use $ScriptContext.Context display a blank. With this fix, the context now persists.
  • Evaluation version alertOperations 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 help you convert the evaluation version to a registered version.



UNIX/Linux management pack

  • Updating the SCX Agent causes deep monitoring status for the JEE Application Server to be reset.
  • By default, the Rpcimap monitor for Red Hat Enterprise Linux 5 is now disabled.
  • Monitoring in UTC +13 causes Unix Process Monitoring template to fail.
  • Using scxadmin -log-rotate causes logging to stop after log rotation.



This entry was posted in Operations Manager, Update Rollup and tagged , , , , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s