We couldn’t sign you in
Select the account you want to use.


This article contains detailed information about issues in Microsoft Operations Manager 2012 Service Pack 1 (SP1). For more information about known issues, update installation and removal, and affected files, click the following article number to view the article in the Microsoft Knowledge Base: please visit the master System Center 2012 SP1 Update Rollup 3 KB Article:

2836751 Description of Update Rollup 3 for System Center 2012 Service Pack 1

Issues that are fixed in Operations Manager 2012 SP1 Update Rollup 3

Issue 1

ACS dtPrincipal tables are sometimes missing the user's domain name.


ACS events sometimes have nothing in the HeaderDomain and ClientDomain columns.

Issue 2

If you decide to view more than two days' data in a Service Level Dashboard view, the data is displayed from daily aggregated data. Therefore, the data that is displayed does not contain the last days' data.


If you create a new Service Level Object that has a class as target (for example, the target is "Health Service"), create a Service Level Dashboard view, and then decide to see data that is not older than two days, you will see correct results and accurate data. However, if you choose to see data that is older than two days (for example, data from past five days), inaccurate results are returned, and the health is displayed as RED, although everything was displayed as HEALTHY for the past two days.

Issue 3

The Health Service stops collecting performance data on Windows Server 2008 R2.


You may see the following message in the event log:

Issue 4

The web console crashes while it tries to access Active Alerts and the Windows Computer State view at the same time by using Internet Explorer 9.


If the user tries to switch views between Active Alerts and Windows Computers State two or three times, the web console crashes. Additonally, the following errors are logged in the Application log on the computer that was used to access the web console.

Source: Application Error

Event ID: 1000

Task Category: (100)

Level: Error


Faulting application name: iexplore.exe, version: 9.0.8112.16421, time stamp: 0x4d76255d

Faulting module name: unknown, version:, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x2f002f00

Faulting process id: 0x8c8

Faulting application start time: 0x01cd44ac7f741747

Faulting application path: C:\Program Files (x86)\Internet Explorer\iexplore.exe

Faulting module path: unknown

Source: .NET Runtime

Event ID: 1023

Task Category: None

Level: Error


Application: iexplore.exe

CoreCLR Version: 5.1.10411.0

Description: The process was terminated due to an internal error in the .NET Runtime at IP 63C375EB (63BF0000) with exit code 8013150a.

Issue 5

A memory leak in the console occurs when the performance widgets dashboard is left open.


If you leave the console open, open a dashboard that contains Performance Widgets, and leave the dashboard open during the night or for a couple of days, the RAM consumption will grow as large as several gigabytes.

Issue 6

Using the Operator Role generates many 26319 events. This causes performance problems.


The Operations Manager event log may show Event ID 26319 when you take actions such as the following:

  • GetReportsByCriteria

  • GetLinkedReportsByCriteria

  • GetTasksByCriteria"

Issue 7

HealthService Availability Reports are incorrect because of duplicate entries in the HealthServiceOutage table.


Availability reports for distributed applications are incorrect and display a status of UP(Monitoring Unavailable). However, in Health Explorer, the applications appear to be healthy.

Issue 8

An SDK process deadlock occurs under high load from the Orchestrator integration pack.


The Ops Mgr SDK process experiences a deadlock when Orchestrator uses Windows PowerShell to reset the health state of monitors for which Orchestrator wants to close alerts.

Issue 9

In the Advisor Connector Preview, groups do not appear in computer searches, alerts do not link to related Microsoft Knowledge Base articles, gateway and management servers are not monitored correctly, Windows PowerShell cmdlets have bugs, and the Connector health state is incomplete.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!