This article describes the issues that are fixed in Update Rollup 9 for Microsoft System Center 2012 R2 Operations Manager. It also includes the installation instructions for the update rollup.
Issues that are fixed in this update rollup
- SharePoint workflows fail with an access violation under APM
A certain sequence of the events may trigger an access violation in APM code when it tries to read data from the cache during the Application Domain unload. This fix resolves this kind of behavior.
- Application Pool worker process crashes under APM with heap corruption
During the Application Domain unload two threads might try to dispose of the same memory block leading to DOUBLE FREE heap corruption. This fix makes sure that memory is disposed of only one time.
- Some Application Pool worker processes become unresponsive if many applications are started under APM at the same time
Microsoft Monitoring Agent APM service has a critical section around WMI queries it performs. If a WMI query takes a long time to complete, many worker processes are waiting for the active one to complete the call. Those application pools may become unresponsive, depending on the wait duration. This fix eliminates the need in WMI query and significantly improves the performance of this code path.
- MOMAgent cannot validate RunAs Account if only RODC is available
If there's a read-only domain controller (RODC), the MomAgent cannot validate the RunAs account. This fix resolves this issue.
- Missing event monitor does not warn within the specified time range in SCOM 2012 R2 the first time after restart
When you create a monitor for a missed event, the first alert takes twice the amount of time specified time in the monitor. This fix resolves the issue, and the alert is generated in the time specified.
- SCOM cannot verify the User Account / Password expiration date if it is set by using Password Setting object
Fine grained password policies are stored in a different container from the user object container in Active Directory. This fix resolves the problems in computing resultant set of policy (RSOP) from these containers for a user object.
- SLO Detail report displays histogram incorrectly
In some specific scenarios, the representation of the downtime graph is not displayed correctly. This fix resolves this kind of behavior.
- APM support for IIS 10 and Windows Server 2016
Support of IIS 10 on Windows Server 2016 is added for the APM feature in System Center 2012 R2 Operations Manager. An additional management pack Microsoft.SystemCenter.Apm.Web.IIS10.mp is required to enable this functionality. This management pack is located in %SystemDrive%\Program Files\System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups alongside its dependencies after the installation of Update Rollup 9.
Important Note One dependency is not included in Update Rollup 9 and should be downloaded separately:Microsoft.Windows.InternetInformationServices.2016.mp
- APM Agent Modules workflow fails with Null Reference exception during workflow shutdown
The APM Agent Modules workflow may fail, causing MonitoringHost.exe to crash during module shutdown. Additionally, you receive the following error message:STACK_TEXT:
microsoft_enterprisemanagement_modules_apm_agentmodules!Microsoft.EnterpriseManagement.Modules.Apm.AgentModules.RetryManager.Dispose+0xb400000000`1b60f5b0 00007ff8`a5cc717b microsoft_enterprisemanagement_modules_apm_agentmodules!Microsoft.EnterpriseManagement.Modules.Apm.AgentModules.RetryManager.Finalize+0x8b
This fix resolves this issue.
- AEM Data fills up SCOM Operational database and is never groomed out
If you use SCOM’s Agentless Exception Monitoring to examine application crash data and report on it, the data never grooms out of the SCOM Operational database. The problem with this is that soon the SCOM environment will be overloaded with all the instances and relationships of the applications, error groups, and Windows-based computers, all which are hosted by the management servers. This fix resolves this issue. Additionally, the following management pack’s must be imported in the following order:
- The Downtime report from the Availability report does not handle the Business Hours settings
In the Downtime report, the downtime table was not considering the business hours. This fix resolves this issue and business hours will be shown based on the specified business hour values.
The updated RDL files are located in the following location:%SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Reporting
To update the RDL file, follow these steps:
- Go to http://MachineName/Reports_INSTANCE1/Pages/Folder.aspxMachineName //Reporting Server.
- On this page, go to the folder to which you want to add the RDL file. In this case, click Microsoft.SystemCenter.DataWarehouse.Report.Library.
- Upload the new RDL files by clicking the upload button at the top. For more information, see https://msdn.microsoft.com/en-us/library/ms157332.aspx.
Note As part of this fix, if you want to generate a Downtime report for a specific duration spanning more than one day, use the business hours option. To do this, set the business hours as 12:00AM & 11:59PM and set all the days as business days.
- Adding a decimal sign in an SLT Collection Rule SLO in the ENU Console on a non-ENU OS does not work
You run the System Center 2012 R2 Operations Manager Console in English on a computer that has the language settings configured to use a non-English (United States) language that uses a comma (,) as the decimal sign instead of a period (.). When you try to create Service Level Tracking, and you want to add a Collection Rule SLO, the value you enter as the threshold cannot be configured by using a decimal sign. This fix resolves the issue.
- SCOM Agent issue while logging Operations Management Suite (OMS) communication failure
An issue occurs when OMS communication failures are logged. This fix resolves this issue.
Issues that are fixed in the UNIX and Linux management packs
- Discovery of Linux computers may fail for some system locales
Using the Discovery Wizard or Windows PowerShell cmdlets to discover Linux computers may fail during the final Agent Verification step for computers that have some system locales, such as zh_TW.UTF-8. The scxadmin command that is used to restart the agent during the discovery process did not correctly handle Unicode text in the standard out-of-the-service command.
- The UNIX/Linux Agent intermittently closes connections during TLS handshaking
Symptoms include the following:
- Failed heartbeats for UNIX or Linux computers, especially when the SSLv3 protocol is disabled on the Management Servers.
- Schannel errors in the System log that contain text that resembles the following:
A fatal error occurred while creating an SSL client credentials. The internal error state is 10013.
- WS-Management errors in the event log that contain text that resembles the following: WSManFault
Message = The server certificate on the destination computer (<UNIX/LINUX-COMPUTER-NAME) has the following errors:
Encountered an internal error in the SSL library.
Error number: -2147012721 0x80072F8F
A security error occurred
UNIX and Linux management pack updateTo install the updated monitoring packs and agents for UNIX and Linux operating systems, follow these steps:
- Apply Update Rollup 9 to your System Center 2012 R2 Operations Manager environment.
- Download the updated management packs for System Center 2012 R2 from the following Microsoft website:
- Install the management pack update package to extract the management pack files.
- Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment.
- 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.
How to obtain and install Update Rollup 9 for System Center 2012 R2 Operations Manager
Download informationUpdate packages for Operations Manager are available from Windows Update or by manual download from the Microsoft Update Catalog.
Windows UpdateTo obtain and install an update package from Windows Update, follow these steps on a computer that has an Operational Manager component installed:
- Click Start, and then click Control Panel.
- In Control Panel, double-click Windows Update.
- In the Windows Update window, click Check Online for updates from Microsoft Update.
- Click Important updates are available.
- Select the update rollup package, and then click OK.
- Click Install updates to install the update package.