SCOM 2012 SP1 UR4 is out!!!


All in the link below you will see the new UR4 and I suggest to implement it!  With all the amazing fixes this is a great one!

 

http://support.microsoft.com/kb/2879276

 

Operations Manager (KB2880799)

Issue 1

When you try to run a Windows PowerShell script or module in an AllSigned environment, you receive the following error message:

The PowerShell script failed with below exception
System.Management.Automation.CmdletInvocationException: AuthorizationManager
check failed.

Issue 2

Location points are not displayed on the GSM Map dashboard because of an SQL time-out error. When this problem occurs, the following events are logged in the Operations Manager log.

Event ID 33333

Event ID: 33333
Task Category: None
Source: DataAccessLayer
Description:

Data Access Layer rejected retry on SqlError: Request: Composite_Select_Seed_90abbed0-9744-b360-2908-8bb6e00a0e63
Class: 16
Number: 8622
Message: Query processor could not produce a query plan because of the hints defined in this query. Resubmit the query without specifying any hints and without using SET FORCEPLAN.

Event ID 26319

Event ID: 26319
Task Category: None
Source: OpsMgr SDK Service
Description:

An exception was thrown while processing GetProjectionsByCriteria for session ID uuid:e3999b5c-870f-42cb-9e78-f7a0850a7c29;id=1175.Exception message: Query processor could not produce a query plan because of the hints defined in this query. Resubmit the query without specifying any hints and without using SETFORCEPLAN.Full Exception: Query processor could not produce a query plan
because of the hints defined in this query. Resubmit the query without specifying any hints and without using SET FORCEPLAN.

Issue 3

An incorrect message description is generated when security event 5140 is monitored. For example, the message contains incorrect information for Source Address, Source Port, and Share Name.

Issue 4

An empty target group is created when endpoints are enumerated. Additionally, a message that resembles the following is logged in the event trace log (.etl):

[Microsoft.EnterpriseManagement.Modules.Apm.ServerDiscovery] [] [Verbose]
:TemplateAgentDiscoveryProbeAction.ProcessDataItem{templateagentdiscoveryprobeaction_cs148}( 00000000038E0B6A )Application instances for the next application components were not found in the system:

Issue 5

By default, when a generic performance report is exported, the object information (such as server name, disk label, and so on) is collapsed, and the information is missing.

Issue 6

When you start the network node dashboard on a computer that's running a 32-bit edition of Windows 7 Service Pack 1, CPU usage is near 99 percent, and the console may stop responding.

Issue 7

A user role that is created by using Windows PowerShell on a non-United States locale-based system does not show the Display name and Description fields in the console.

Issue 8

When you create an override on a group or when you use a cmdletadd to a group, you receive the following message:

The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information.

Issue 9

When you select objects on the dashboard, you receive the following error message:

Microsoft.EnterpriseManagement.Presentation.DataAccess.DataAccessDataNotFoundException: Exception reading objects ---> Microsoft.EnterpriseManagement.Common.UnknownDatabaseException:
The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions.

Issue 10

When network discovery is run, duplicate entries for the same device may be added to the database. This problem occurs when a different device key is found for the same device.

Issue 11

Availability Reports may be displayed as blank because the vStateDailyFull aggregate is returned empty. This problem occurs when the time zone on the data warehouse server is set to UTC+0X:30.

Issue 12

The monitored health state of the System Center Advisor agent is always in a "Warning" state on the Advisor Health State dashboard.

Issue 13

Application Performance Monitoring (APM) is not functional when you upgrade to later versions of Operations Manager.

Issue 14

A website cannot be discovered or monitored on a system that's running Internet Information Services 8 if the HTTP binding is missing from the website configuration.

Operations Manager - UNIX and Linux Monitoring (part of KB2880799)

Issue 1

In rare cases, the Monitoringhost.exe process on the Management Server may crash with an access violation 0xc0000005 when log files are monitored on UNIX and Linux computers. When this crash
occurs, it causes the managed UNIX or Linux computers to become unmonitored and in a "Critical" state.

Issue 2

When discovering a Linux computer, discovery fails during secure shell (SSH) discovery, or the operating system name and version are determined incorrectly. This issue can
occur when multiple *-release files exist in the /etc directory, and one of the files is named os-release. Additionally, you receive an error message that resembles the following:

Failed during SSH
discovery. Exit code: 2

Standard Output:

Standard Error: line 1: syntax error near unexpected token `('

Operations Manager - UNIX and Linux Monitoring (Management Pack update)

Issue 1

A Solaris computer that uses lots of monitored resources such as file systems, physical disks, or network adapters, may run out of file descriptors and cannot monitor the resources. This is the result of the default user limit on Solaris being too low to allocate sufficient file descriptors. The updated agent now overrides the default user limit with a user limit for the agent process of 1,024.

Additionally, the Operations Manager agent's log file (/var/opt/microsoft/scx/log/scx.log) contains errors or warnings that resemble the following:

error = 24 (Too many open files)

Issue 2

A monitored Solaris Zone configured for dynamic CPU allocation with Dynamic Resource Pools may log errors in the agent logs and return incorrect values for Processor performance
counters.
This issue applies to any monitored Solaris Zones configured to use Dynamic Resource Pools and a "dedicated-cpu" configuration that involves a range of CPUs.

Issue 3

If Linux Container (cgroup) entries are in /etc/mtab directory, errors are logged when physical disk discovery is enabled, and some physical disks may not be discovered.
Additionally, errors that resemble the following may be logged in the Operations Manager agent's log file (/var/opt/microsoft/scx/log/scx.log):

Warning
[scx.core.common.pal.system.disk.diskdepend:418:29352:139684846989056] Did not find key 'cgroup' in proc_disk_stats map, device name was 'cgroup'.

Issue 4

Physical disk
configurations that cannot be monitored or failures in physical disk monitoring for UNIX and Linux computers, may cause failures in Logical Disk instances
(File Systems) monitoring.

New support included in this update


  • Debian GNU/Linux 7

  • Java Enterprise
    Edition (JEE) Application servers:
  • IBM WebSphere 8.0
  • IBM Websphere 8.5
  • Oracle Weblogic 12c

Note The JEE application server additions are a separate Management Pack release. However, they depend on updates to the UNIX/Linux agent.


Comments (0)

Skip to main content