Update Rollup 3 for Operations Manager 2012 SP1

2014-07-08T08:16:45
ID KB2852565
Type mskb
Reporter Microsoft
Modified 2014-07-08T08:16:45

Description

<html><body><p>Discusses Update Rollup 3 for Operations Manager 2012 SP1 and the issues that this update rollup fixes.</p><h2>Summary</h2><div class="kb-summary-section section">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: <div class="indent"><a href="https://support.microsoft.com/en-us/help/2836751" id="kb-link-1">2836751 </a> Description of Update Rollup 3 for System Center 2012 Service Pack 1 </div><h3 class="sbody-h3">Issues that are fixed in <span class="text-base">Operations Manager </span><span class="text-base">2012 SP1 Update Rollup 3</span></h3><h4 class="sbody-h4">Issue 1</h4>ACS dtPrincipal tables are sometimes missing the user's domain name.<br/><br/><span class="text-base">Symptom</span><br/><br/>ACS events sometimes have nothing in the <strong class="uiterm">HeaderDomain</strong> and <strong class="uiterm">ClientDomain</strong> columns.<br/><br/><h4 class="sbody-h4">Issue 2</h4>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.<br/><br/><span class="text-base">Symptom</span><br/><br/>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 <strong class="uiterm">RED</strong>, although everything was displayed as <strong class="uiterm">HEALTHY</strong> for the past two days.<br/><br/><h4 class="sbody-h4">Issue 3</h4>The Health Service stops collecting performance data on Windows Server 2008 R2.<br/><br/><span class="text-base">Symptom</span><br/><br/>You may see the following message in the event log: <br/><br/><h4 class="sbody-h4">Issue 4</h4>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.<br/><br/><span class="text-base">Symptom</span><span class="text-base"></span><br/><br/>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.<br/><br/><div class="sbody-error">Source: Application Error<br/><br/>Event ID: 1000<br/><br/>Task Category: (100)<br/><br/>Level: Error<br/><br/>Description:<br/><br/>Faulting application name: iexplore.exe, version: 9.0.8112.16421, time stamp: 0x4d76255d<br/><br/>Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000<br/><br/>Exception code: 0xc0000005<br/><br/>Fault offset: 0x2f002f00<br/><br/>Faulting process id: 0x8c8<br/><br/>Faulting application start time: 0x01cd44ac7f741747<br/><br/>Faulting application path: C:\Program Files (x86)\Internet Explorer\iexplore.exe<br/><br/>Faulting module path: unknown<br/></div><br/><br/><br/><div class="sbody-error">Source: .NET Runtime<br/><br/>Event ID: 1023<br/><br/>Task Category: None<br/><br/>Level: Error<br/><br/>Description:<br/><br/>Application: iexplore.exe<br/><br/>CoreCLR Version: 5.1.10411.0<br/><br/>Description: The process was terminated due to an internal error in the .NET Runtime at IP 63C375EB (63BF0000) with exit code 8013150a.</div><h4 class="sbody-h4">Issue 5</h4>A memory leak in the console occurs when the performance widgets dashboard is left open.<br/><br/><span class="text-base">Symptom</span><br/><br/>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.<br/><br/><h4 class="sbody-h4">Issue 6</h4>Using the Operator Role generates many 26319 events. This causes performance problems.<br/><br/><span class="text-base">Symptom </span><br/><br/>The Operations Manager event log may show Event ID 26319 when you take actions such as the following: <ul class="sbody-free_list"><li>GetReportsByCriteria </li><li>GetLinkedReportsByCriteria</li><li>GetTasksByCriteria"</li></ul><h4 class="sbody-h4">Issue 7</h4>HealthService Availability Reports are incorrect because of duplicate entries in the HealthServiceOutage table.<br/><br/><span class="text-base">Symptom </span><br/><br/>Availability reports for distributed applications are incorrect and display a status of <strong class="uiterm">UP(Monitoring Unavailable)</strong>. However, in Health Explorer, the applications appear to be healthy.<br/><br/><h4 class="sbody-h4">Issue 8</h4>An SDK process deadlock occurs under high load from the Orchestrator integration pack.<br/><br/><span class="text-base">Symptom</span><span class="text-base"></span><br/><br/>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.<br/><br/><h4 class="sbody-h4">Issue 9 </h4>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.</div></body></html>