Update Rollup 5 for System Center 2012 SP1 - Operations Manager includes all previous update rollups for System Center 2012 SP1 - Operations Manager.
Issues that are fixed in this update rollup
Operations Manager
Issue 1An 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
By default, data warehouse bulk-insert commands use an unchangeable 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
Diagram component does not publish location information in the component state.
Issue 5
Renaming a group works correctly on the console. However the group appears with the old name 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.
Operations Manager - UNIX and Linux Monitoring (Management Pack Update)
Issue 1
In rare cases, the agent on a Solaris Zone that is configured to use dynamic CPU allocation with Dynamic Resource Pools may hang during routine monitoring.
Note This issue can occur on any monitored Solaris Zone that is configured to use Dynamic Resource Pools and a "dedicated-cpu" configuration that involves a range of CPUs.
Issue 2
If the agent fails to retrieve process arguments from the getargs subroutine on an AIX-based computer, the monitored daemons may be incorrectly reported as offline. An error message that resembles the following is logged in the agent log:
Calling getargs() returned an error
Issue 3
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 4
The Universal Linux agent fails to install on Linux computers with 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:
/opt/microsoft/scx/bin/tools/.scxsslconfig: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
Issue 5
Spurious errors that are related to the InstanceID property of the SCX_Endpoint are logged in the System log every four hours.
Installation instructions
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 (except on the Agent and Gateway roles), the updates do not appear in the Add or Remove Programs item in Control Panel.
- After you apply Update Rollup 5, the Operations Manager console has to be reopened in order to apply the Alert Attachment Management Pack fix.
- After you install the update rollup package, the version number of the console is not changed.
- If the ACS update package is installed, uninstalled then re-installed the database upgrade script that's included in this update will not run, because the database version is changed during the first installation of the ACS update. This could trigger a server crash if the user reuses a partition with the partition still in place.
The partition can be closed manually by using SQL Server Studio, navigating to the ACS database and running the following script in a query editor window:begin tran -- mark all active partitions for closing if (select count(*) from dtPartition where Status = 0) > 0 update dtPartition set Status = 1 where Status = 0 commit tran
- 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.
This posting is provided "AS IS" with no warranties.
