Update Rollup 5 for System Center 2012 R2 was recently released, and after installing the update in some of my environments, I’d like to draw attention to a few observations. I won’t go into too much detail about a step-by-step installation strategy because the good Kevin Holman has that covered.
The ONLY addition I’d make to Kevin’s article is to install the updated management packs for UNIX/ Linux before updating your UNIX/ Linux agents
The key issues that are fixed in this rollup include:[Source: Microsoft Support Articles]
- 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.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 1
Registry key 2Registry location:HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\System Center\Health ServiceDWORD Name: MaximumGlobalPendingDataCount
(Where nnnn is the number of items globally. Set this value to more than 5120, as needed.)
DWORD Name: MaximumGlobalPendingDataCount
(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 Updates:
- 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).
Let’s Delve Into it:
The supported order of installation according to the KB is as follows:
- 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
- Apply SQL scripts
- Import the update rollup management packs
- Apply agent updates from the Pending Management view in the Operations Console and install agent update on manually installed agents
- Download the updated UNIX/ Linux Management pack
- Update UNIX/ Linux MPs and Agents
As mentioned above, Kevin’s article is very detailed, and an excellent reference, so I won’t reinvent the wheel.
If however, you make use of Azure Operational Insights (OpInsights), and grabbed the update rollup Advisor management pack bundles, then you might have noticed the long overdue updates to the SCOM plug-in for Azure Operational Insights, in the form of a rebranding of the plug-in name from the old System Center Advisor name to the new Operational Insights name.
After Importing, notice the rebranding of the OpInsights plugin
And the Azure Operational Insights page has received a face lift.
I look forward to more exciting news from the AOI team, especially around new monitoring scenarios with IPs, and search data/ syntax improvements. Cheers!
Latest posts by Chiyo Odika (see all)
- Zero Trust and the Azure Firewall service - July 9, 2019
- Making the move to Azure Security Center and Azure Sentinel - July 9, 2019
- Azure Monitor Management solution for RDS, Windows VDI and Citrix - February 28, 2019