Category Archives: Update Rollup

SCOM 2012 R2: Update Rollup 6

Update Rollup 6 for SCOM 2012 R2 has just been released. As usual the update can be done through windows update or downloaded through the MS catalogue here. As always give this update a thorough test before deploying to your live environments.

Fixes in this update:

Operations Manager

  • The “Remove-DisabledClassInstance” Windows PowerShell command times out without completingThe cmdlet takes lots of time to complete in large SCOM installations and sometimes times out without completing its work. This is fixed by optimizing the query that is used for deletion.
  • Duplicate closed alertsThe Find option in a message view sometimes gives results of the current search together with the results from previous searches. This occurs because of an update issue in the grid and is fixed so that values are displayed that correspond only to the current search.
  • Topology widget objects lose location when they are opened in a console that has a different locale and decimal formatTopology widgets that are created in one locale but are viewed from another locale display an incorrect location because of the widget’s inability to interpret locale-specific formatting. This issue is fixed, and users can now create and view topology widgets from different locales.
  • WebConsole Details widget does not display anythingWhen you click a message in the Alert widget, the details of the message are not displayed in the details widget on WebConsole. This issue is fixed by fixing the XAML page of the details widget. The XAML page was preventing the data from being displayed on the page.
  • Top 10 Performance widgets (WebConsole) are sometimes emptyThe Top 10 Performance widgets (WebConsole) are sometimes empty because of a performance issue. This issue was fixed in Update Rollup 3 through an MPB file that requires a manual import. Because many users missed importing the MPB, a fix is included in this update rollup as an SQL query update.
  • Problem with decoding SCOM trace log filesSometimes Operations Manager trace logs do not decode but generate the error “Unknown(X ): GUID=XXX (No Format Information found).” This occurs because the latest TMF files that contain formatting information for the related traces are missing. All TMF files are updated to make sure that traces are formatted correctly.

Unix/Linux Management Pack

  • JEE: WebLogic 12.1.3 servers on Linux or Solaris are not discoveredWebLogic 12cR1 Rel3 Java Application Servers that are installed on Linux and Solaris are not discovered.

    Note The UNIX or Linux agent must be updated after you install the Management Pack update to resolve this issue.

    Relevant log messages:

    /var/opt/microsoft/scx/scx.log

    2015-02-04T15:28:18,797Z
    Trace [scx.core.common.pal.system.appserver.appserverenumeration:379:15739:139715041470400] Weblogic process does not contain the ‘platform.home’ or ‘weblogic.system.BootIdentityFile’ commandline argument.2015-02-04T15:28:18,797Z
    Trace [scx.core.common.pal.system.appserver.appserverenumeration:462:15739:139715041470400] Merging previously known instances with current running processes

  • In rare cases, lots of omiagent processes may be observed on a UNIX or Linux computerIf a single instance of data that is returned by an OMI provider is larger than 64 kilobytes (KB), the omiagent process becomes unresponsive, and additional omiagent processes are created. This issue can occur on a managed UNIX- or Linux-based computer if a rule or monitor returns an instance of data larger than 64 KB. This is most likely to be seen when a custom shell command or script rules return lots of data in StdOut.

    Note After you upgrade the Operations Manager UNIX/Linux agent to the version that is contained in this Management Pack update, an instance that exceeds 64 KB will be truncated and will generate the following message in the scx.log file. You can use the log message to identify and change the workflow that is returning too much data.

    ExecuteCommand: Exceeded maximum output size for provider (64k), output truncated. Monitoring will not be reliable! Command executed: “
  • The SSLv3 protocol cannot be disabled in OpenSSL as used by the UNIX and Linux agentsWith this update, you can now disable the SSLv3 protocol for the Operations Manager UNIX and Linux agents. You can do this by adding a property to omiserver.conf (/etc/opt/microsoft/scx/conf). If SSLv3 is disabled, the UNIX and Linux agent will reject connections that cannot be negotiated by using TLS encryption. If SSLv3 is enabled (this is the default configuration), SSLv3 will be used only if TLS encryption cannot be negotiated.

    omiserver.conf options for configuration SSLv3

    Collapse this tableExpand this table
    Property Description
    NoSSLv3=true|false Enable/Disables use of SSLv3

SCOM: Update Rollup for Microsoft Monitoring Agent KB 3032946

Microsoft has just announced a new update rollup for the Microsoft Monitoring Agent, the KB article and download link is here.

Issues that are fixed in this update rollup

  • Proxy settings are added to the agent setup wizard.
    Users can now provide proxy settings while they complete the agent installation wizard.
  • Account validation steps are added to the wizard.
    After users enter an account and workspace to connect to Operational Insights, the wizard performs a test to verify that the account information is valid.
  • Connection status is added to Control Panel.
    A connection status feature is added to Control Panel settings for the Microsoft Monitoring Agent.

SCOM: Update Rollup 5 for System Center 2012 R2

Update Rollup 5 for System Center 2012 R2 has just been released, this KB article contains full information around the included fixes. The article also contains the installation instructions and download link.

A fix I am glad to see in here is the one around Specified cast is not valid when opening run as account properties which is an issue I blogged about 2 years ago.

All in all this seems like a good update, as always test before going live.

 

SCSM: Update Rollup 5 for System Center 2012 R2 Service Manager

Update Rollup 5 for System Center 2012 R2 Service Manager has just been released which means we should be seeing the update for other System Center products in the coming days.

It is available for download here.

Changes in this update:

    1. Change request still stays “in progress” when last activity is skipped and all previous activities are completed.
    2. ActualStartDate and ActualEndDate field values for Change Request and Release Request do not set.
    3. Multiple System Center Service Manager Connectors to System Center Configuration Manager execute and complete successfully. However, the start, finish and status property values are not updated in the Service Manager Console under the “Connectors” view and event 3334 is logged.
    4. Trying to delete a Service Request template that is being used by a Request Offering causes a cryptic and non-user friendly error message.
    5. The “Group By” functionality in a View does not work correctly when “Group By” column has empty fields.
    6. The Console crashes when the user tries to open an already opened attachment from a Work Item form.
    7. Opening the Views for Groups takes a long if there are large number of explicit members in the groups.
    8. The OM CI connector fails if one tries to import a distributed application that contains an instance of the ‘Hyper-V Virtual Network Adapter’ class.
    9. Monitoring Host process crashes if there exists a Notification after the user who created it was deleted or has moved to a hidden organizational unit (OU) in the Active Directory.
    10. An exception is raised if the user tries to open a sorted View which is created by using TypeProjection on custom Class that is neither Abstract and nor a first Concrete class.
    11. An Exception is thrown when a user tries to open the “Service Components” tab on the Service Maps form, when there are large number of services in CMDB.
    12. Enhanced in event logging for DW jobs.
      Logging the batch start and completion events for all DW job categories in event log. The start and completion event will include the following:
      Process Category

      1. Process Name
      2. Batch Id
      3. Batch Start or completion Time
    13. Enhanced in event logging for DW cube processing.
      1. Time taken by Cube’s batch id to complete will be logged in seconds.
      2. Information whether the cube is processed under Analysis Services that are running in SQL Server Standard Edition or the SQL Server Enterprise Edition.
      3. Event logs will be added during processing of each Dimension and Measure Group for each partition (if applicable) for both enterprise and standard SQL editions.
    14. Added a new PowerShell cmdlet Get-SCDWInfraLocations Cmdlet on the Service Manager management server to retrieve the following location information about its data warehouse infrastructure:
      1. Service Manager database
      2. Service Manager data warehouse database
      3. Service Manager Analysis server database
      4. Data Warehouse Reporting Server database and Report Server URL

SCOM 2012 SP1: Update Rollup 8

Microsoft has recently released a new update rollup for SCOM 2012 SP1, it’s good to see that they are continuing support for the clients that havent migrated to R2 yet.

The update is available for download here and fixes the following issues:

  • The Health Service bouncing that is caused by high memory usage in the MonitoringHost process.
  • This update includes a fix to prevent resynchronization of all managed entities from the Operations Manager to the Operations Manager Data Warehouse (OMDW) database and to prevent the failure to sync that this causes because of duplicate entries. The duplicate entries cause the following exception to occur:
    Description:
    Data was written to the Data Warehouse staging area but processing failed on one of the successive operations.
    Exception ‘SqlException’: Sql execution failed. Error 2627, Level 14, State 1, Procedure ManagedEntityChange, Line 367, Message: Violation of UNIQUE KEY constraint ‘UN_ManagedEntityProperty_ManagedEntityRowIdFromDAteTime’. Cannot insert duplicate key in object ‘dbo.ManagedEntityProperty’.

  • The import of Visualization.component.library and Visualization.library binary files (.mpb) fails. The import succeeds on a successive try.
  • System Center Operations Manager agents randomly time out when authenticating to the Gateway or Management Server because of domain controller or network performance issues. The time-out value was set to 1 second earlier. A fix was made to increase server time out to-20 seconds and client time out to 5 minutes.

SCOM 2012 R2: Update Rollup 4

Microsoft has released Update Rollup 4 for System Center 2012 R2 Operations Manager. All in all a good update and as always test in your labs before deploying to production,

It is available for download here and contains fixes for the following issues:

Issue 1
It takes many minutes for the Microsoft.Windows.CheckNTServiceStateMonitorType function to determine that the service is down.

Issue 2
An attempt to apply sensitivity rules fails, and you receive the following error message:

The monitoring configuration contains errors and cannot be applied.
Exception: System.ApplicationException: Attribute ‘regexCompare’ is null
at Microsoft.EnterpriseManagement.Modules.Apm.LibraryConfigManager.Tools.XmlTools.GetMandatoryAttribute(String attributeName, XmlNode node)
at any attempt to apply sensitivity rules fails with the errorMicrosoft.EnterpriseManagement.Modules.Apm.LibraryConfigManager.Modules.ApmModule.Core.Actions.AgentHandlersConfig.HiddenRuleXmlDeserializer.Deserialize(XmlNode rowData)

Issue 3
GSM locations are geotagged incorrectly on Map Widget.

Issue 4
The MonitoringHost.exe process issues too many calls to System Center Failover Clustering.

Issue 5
The re-synchronization of all managed entities from Operations Manager to the Operations Manager Data Warehouse database causes duplicate entries, and an exception that resembles the following is thrown:

Data was written to the Data Warehouse staging area but processing failed on one of the subsequent operations.
Exception ‘SqlException’: Sql execution failed. Error 2627, Level 14, State 1, Procedure ManagedEntityChange, Line 367, Message: Violation of UNIQUE KEY constraint ‘UN_ManagedEntityProperty_ManagedEntityRowIdFromDAteTime’. Cannot insert duplicate key in object ‘dbo.ManagedEntityProperty’.

Issue 6
If data is truncated and is in Terminal status to a workflow, event ID 31551 is logged, and an exception that resembles the following is thrown:

Failed to store data in the Data Warehouse. The operation will be retried.
Exception ‘InvalidOperationException’: The given value of type String from the data source cannot be converted to type nvarchar of the specified target column.
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataWarehouse.CollectAlertData

Issue 7
An arithmetic overflow error occurs, and an exception that resembles the following is thrown:
Data was written to the Data Warehouse staging area but processing failed on one of the subsequent operations.
Exception ‘SqlException’: Sql execution failed. Error 8115, Level 16, State 2, Procedure RelationshipChange, Line 180, Message: Arithmetic overflow error converting expression to data type int.

Issue 8
You experience poor performance when Operations Manager searches for attributes. Additionally, when doing more than one search in a row, the cache file (momcache.mdb) keeps increasing.

Issue 9
SCX agent generates lots of warnings in the log file when a user is using Security-Enhanced Linux (SELinux).

Issue 10
By default, the Rpcimap monitor for Red Hat Enterprise Linux 6 is disabled.

SCOM 2012 R2: Update Rollup 3 Released

Microsoft have just released Update Rollup 3 for SCOM 2012 R2 it is available for download here or via windows updates.

There are a few known issues with this update so be sure to read the KB article and test thoroughly before implementing.

Several issues are fixed with this update including those below:

  • A deadlock condition occurs when a database is connected after an outage. You may experience this issue may when one or more HealthServices services in the environment are listed as Unavailable after a database goes offline and then comes back online.
  • The Desktop console crashes after exception TargetInvocationException occurs when the TilesContainer is updated. You may experience this issue after you leave the console open on a Dashboard view for a long time.
  • The Password expiration monitor is fixed for logged events. To make troubleshooting easier, this fix adds more detail to Event IDs 7019 and 7020 when they occur.
  • The Health service bounces because of high memory usage in the instance MonitoringHost: leak MOMModules!CMOMClusterResource::InitializeInstance. This issue may be seen as high memory usage if you examine monitoringhost.exe in Performance Monitor. Or, the Health service may restart every couple of days , depending on the load on the server.
  • The Health service crashes in Windows HTTP Services (WinHTTP) if the RunAs account is not read correctly.
  • Windows PowerShell stops working with System.Management.Automation.PSSnapInReader.ReadEnginePSSnapIns. You may see this issue as Event ID 22400 together with a description of “Failed to run the Powershell script.”
  • The PropertyValue column in the contextual details widget is unreadable in smaller widget sizes because the PropertyName column uses too much space.
  • The update threshold for monitor “Health Service Handle Count Threshold” is reset to 30,000. You can see this issue in the environment, and the Health Service Handle Count Threshold monitor is listed in the critical state.
  • An acknowledgement (ACK) is delayed by write collisions in MS queue when lots of data is sent from 1,000 agents.
  • The execution of the Export-SCOMEffectiveMonitoringConfiguration cmdlet fails with the error “Subquery returned more than 1 value.”
  • The MOMScriptAPI.ReturnItems method can be slow because a process race condition may occur when many items are returned, and the method may take two seconds between items. Scripts may run slowly in the System Center Operations Manager environment.
  • When you are in the console and click Authoring, click Management Pack, click Objects, and then click Attributes to perform a Find operation, the Find operations seems unexpectedly slow. Additionally, the Momcache.mdb file grows very large.
  • A delta synchronization times out on SQL operations with Event ID 29181.
  • Operations Manager grooms out the alert history before an alert is closed.
  • The time-zone settings are not added to a subscription when non-English display languages are set. Additionally, time stamps on alert notifications are inaccurate for the time zone.
  • Web Browser widget requires the protocol (http or https) to be included in the URL.
  • You cannot access MonitoringHost’s TemporaryStoragePath within the PowerShell Module.
  • The TopNEntitiesByPerfGet stored procedure may cause an Operations Manager dashboard performance issue. This issue may occur when a dashboard is run together with multiple widgets. Additionally, you may receive the following error message after a time-out occurs:

Update Rollup 7 for System Center 2012 Operations Manager Service Pack 1 has also been released and is quite a minor update in comparison to the fixes for R2.

Below are the fixes for that update:

  • The Reset the baseline, Pause the baseline, and Resume the baseline actions fail when you run them against an optimized performance collection rule.
  • The DeltaSynchronizationengine work item times out on SQL operations, and Event ID 29181 is generated.
  • Execution of the Export-SCOMEffectiveMonitoringConfiguration cmdlet fails, and you receive the following error message:
    Subquery returned more than 1 value.
  • Time-zone settings are not added to subscriptions when non-English display languages are set.
  • The Operations Manager dashboard experiences a performance issue that is caused by the TopNEntitiesByPerfGet stored procedure.

SCOM 2012 R2: UR2 New Widgets

One of the additional features of the recent Update Rollup 2 for SCOM 2012 R2 is new widgets, these are made availible by completing the import of the new manegements packs portion of the Update Rollup process, which includes Microsoft.SystemCenter.Visualization.Library.mpb.

This article contains a list of the new widgets as well as a brief description of each. There are some welcome additions which should enable a much richer dashboard experience.

SCOM 2012 R2: Update Rollup 2 Released

Update Rollup 2 for SCOM 2012 R2 has been released and is availible for download here.

The update fixes the following issues:

Issue 1
This update rollup makes the stored procedure performance aggregate more robust against out-of-range values.

Issue 2
Adding multiple regular expressions (RegEx) to a group definition causes an SQL exception when the group is added or run.

Issue 3
Web applications fail when they are monitored by the System Center Operations Manager 2012 R2 APM agent.

Issue 4
Service Level Objectives (SLO) dashboards sometimes load in several seconds and sometimes take minutes to load. Additionally, the dashboard is empty after it loads in some cases.

Issue 5
Operations Manager Console crashes when you try to override the scope in the Authoring pane.

Issue 6
The System Center Operations Manager console is slow to load views if you are a member of a custom Operator role.

Issue 7
This update rollup includes a fix for the dashboard issue that was introduced in Update Rollup 1.

Issue 8
SQL Time Out Exceptions for State data (31552 events) occur when you create Data Warehouse workflows.

Issue 9
This update rollup includes a fix for the Event Data source

Operations Manager – UNIX and Linux Monitoring (Management Pack Update)

Issue 1

All IBM WebSphere application servers that run on Linux or AIX computers are not automatically discovered by the Management Pack for Java Enterprise Edition (JEE) if multiple application servers are defined in a single WebSphere profile.