Loading...

Knowledge Center


Performance Optimizer Known Issues
Technical Articles ID:   KB87291
Last Modified:  6/11/2019
Rated:


Environment

McAfee ePolicy Orchestrator (ePO) 5.x
McAfee Performance Optimizer 2.x, 1.x

Summary

Recent updates to this article:
Date Update
March 6, 2018 Added expand and collapse sections.

This article contains important information about known issues of high or medium rating that are outstanding with this product release. This article will be updated if new issues are identified post-release, or if additional information becomes available. To read the Release Notes, see:
Performance Optimizer Version Release to World (RTW) Release Notes
Performance Optimizer 2.2.0.112 (2.2.0 Update 1) October 31, 2017 PD27293
Performance Optimizer 2.2.0.111 October 16, 2017 PD27293
Performance Optimizer 2.1.0.116 October 27, 2016 PD26741
Performance Optimizer 2.0.0.126 July 25, 2016 PD26560
Performance Optimizer 1.0.1.110 March 20, 2015 PD25897

Issue resolutions in updates and major releases are cumulative; Technical Support recommends that you install the latest version. To find the most recent release for your product, visit the Product Downloads site at http://www.mcafee.com/us/downloads/downloads.aspx.


Contents
Click to expand the section you want to view:

There are currently no critical known issues.
Reference Number Related Article Found Version Resolved Version Issue Description
  KB90002 2.x   Issue: The 'Performance Optimizer Tables and Indexes' dashboard displays duplicate schema names with Microsoft SQL Server 2016 or later

Solution: See the related article.

The referenced article is available only to registered ServicePortal users.

To view registered articles:
  1. Log on to the ServicePortal at http://support.mcafee.com.
  2. Type the article ID in the search field on the home page.
  3. Click Search or press Enter.
    2.x   Issue: Hidden server tasks might display for the Performance Optimizer assessment drill-downs.

Explanation: Performance Optimizer evaluates all server tasks, including hidden tasks and tasks an ePO Administrator cannot change.
    2.2.0   Issue: Duplicate metrics appear in the dashboard query "Performance Optimizer: Database buffer pool usage."

Explanation: In version 2.2.0, the metric collection was changed for the buffer pool memory usage metrics. During the first few days that version 2.2.0 runs in ePO, these duplicate metrics display. After three days, they no longer appear on the dashboard query because of the time filter that is specified for the query.
1175995 KB88506 2.x 2.2.0.111 Issue: Performance Optimizer 2.1.0.116 does not properly analyze the ePO database and tempdb autogrowth configuration settings and, as a result, database growth is reported as requiring action.

Solution: This issue is resolved in Performance Optimizer 2.2.0.
1169553   2.x 2.2.0.111 Issue: If the SQL Server is configured for "Force Encryption," the Performance Optimizer database connection fails when alternate credentials are specified in the section Server Settings, Performance Optimizer.

Solution: This issue is resolved in Performance Optimizer 2.2.0.
1177150   2.x 2.2.0.111 Issue: The server task "Performance Optimizer: Analyze database index fragmentation and identity column usage" encounters the following error:
 
java.sql.SQLException: Numeric overflow in conversion of value <value> to INTEGER
 
Cause: An incorrect data type is used in the application.

Solution: This issue is resolved in Performance Optimizer 2.2.0.
  KB88004 2.0.0   Issue: An index that has been defragmented still appears in the listing of indexes to rebuild or reorganize.

Cause: The SQL Server organizes the rows of data into pages that are each 8k in size. Performance Optimizer uses a filter to only evaluate indexes that are larger than 100 pages of data. The purpose of this filter is to ignore smaller indexes because fragmentation is not as much of an issue. Sometimes, the small indexes might be using mixed extents and the fragmentation cannot be removed.

Occasionally, when a small index is rebuilt, the number of pages can be decreased. If the fragmented version of the index has more than 100 pages, Performance Optimizer lists it as requiring maintenance. But, if the index defragmentation reduces the page count below 100 pages, Performance Optimizer does not check it properly (because it now falls below the 100 page minimum).

The referenced article is available only to registered ServicePortal users.

To view registered articles:
  1. Log on to the ServicePortal at http://support.mcafee.com.
  2. Type the article ID in the search field on the home page.
  3. Click Search or press Enter.
    2.1.0   Issue: Automatic responses are duplicated during upgrade, if they are enabled, or the definition has been updated.

Cause: This issue occurs when ePO extensions provide sample automatic responses.

During the upgrade, the ePO platform checks to see if the automatic response is already enabled or the definition is slightly different. In both of these cases, the ePO platform retains the previous sample and labels the new sample with the version of the product. For example, when upgrading to Performance Optimizer 2.1 you might see automatic responses with the label (2.1) added as a suffix to the name.
    2.1.0 Latest version of ePO Issue: When you use ePO 5.1.1, the dashboard query shows Maximum Value as a total of all data points in the displayed chart, rather than the actual maximum value.

Workaround: This issue occurs only when you use ePO 5.1.1. Upgrade to the latest version of the ePO platform to resolve this issue.
    2.1.0   Issue: Server Task Log shows a status of 'Completed' even though subsequent actions are running.

Cause: Performance Optimizer uses a status update that can cause the Server Task Log to indicate that the overall task has completed.

Workaround: To verify if the task is finished, drill down on the Server Task Log entry and review the latest messages.
  KB88237 2.1.0 ePO
5.9.0
Issue: The ePO performance counters are not available in Windows non-English locales.

Solution: This issue is resolved in ePO 5.9, which is available from the Product Downloads site at: http://mcafee.com/us/downloads/downloads.aspx

NOTE: You need a valid Grant Number for access. KB56057 provides additional information about the Product Downloads site, and alternate locations for some products.

Updates are cumulative; Technical Support recommends that you install the latest one.
    2.1.0   Issue: After you start the Orion Log Analyzer from the Server Settings page, an error message displays with a link to the Server Task Log.

Cause: This issue occurs when the maximum number of server tasks have already begun to execute.

The Server Settings page uses a remote command invocation to start the Orion Log Analyzer, which means that it runs as a server task. The task waits until the others have completed if the maximum number is running.

The setting for maximum server tasks can be found in the Scheduler Tasks category of the Server Settings.
    2.x As Designed Issue: After you restart or upgrade the ePO platform, the server task Performance Optimizer: Start Orion Log analyzer is no longer running.

Cause: The server task Performance Optimizer: Start Orion Log analyzer starts a background process that monitors the log messages sent to the orion.log. When the ePO Application Server is restarted or upgraded, you must restart the server task.

Workaround: Set a daily schedule for the server task 'Performance Optimizer: Start Orion Log analyzer' so the task automatically starts again at the scheduled time.
    2.x As Designed Issue: After you upgrade the ePO platform, the Performance Optimizer server tasks fail with the following message:


Database error occurred. Are valid credentials entered in the Server Settings?


Workaround: On the Server Settings page for Performance Optimizer, re-enter the database user account information, click Test Connection to verify the account information, and click Save.
    2.x As Designed Issue: The drill-down pages are empty for the "Agent Handler system distribution" and "ASCI settings" assessments.

Explanation: Some assessments do not provide any drill-down details unless an action is required. You can change the configuration for the assessments in the server task Performance Optimizer: Analyze ePO configuration, database configuration, and database backups.
    2.x As Designed Issue: Performance Optimizer JMX attributes cannot be used from some third-party monitoring tools. For some third-party monitoring tools, the length of JMX attribute names causes errors during attribute polling. The attribute name displays, but the third-party monitoring tool is unable to collect the value for the attribute because of the length of the attribute name.
    2.x As Designed Issue: Performance Optimizer drill-down pages display the following message:

Use the related dashboard to view the results of this assessment. More details can be viewed using the Queries & Reports and the Server Task Log.

Cause: The new metrics added in Performance Optimizer 2.x do not display drill-down details because the metrics collected are represented in queries placed on the relevant dashboards. The Server Task Log also contains details of each collected metric.
    2.x   Issue: An optical drive, such as a CD or DVD drive, shows as 100% utilized and is given a low score in the assessment for disk drive usage.

Workaround: Performance Optimizer does not currently distinguish between optical drives and writeable storage. You need to purge the metric data to remove the reference to the optical drive disk usage.
    2.x As Designed Issue: Performance Optimizer server tasks can fail if the IP address of the system that hosts the McAfee ePolicy Orchestrator Application Server service is changed dynamically. For example, the server task Performance Optimizer: Analyze CPU and memory usage on the application and database servers fail with the error Connection timed out.

Cause: Performance Optimizer uses a JMX management bean interface to obtain certain metrics. If the IP address is dynamically changed, it can sometimes interfere with the ability to resolve the management bean.

Workaround: Restart the McAfee ePolicy Orchestrator Application Server service:
  1. Press Windows+R, type services.msc, and click OK.
  2. Right-click the following service and select Restart:
     
    McAfee ePolicy Orchestrator x.x.x Application Server
    2.x As Designed Issue: The ePO server becomes unresponsive after configuring a server task to run every second.

Cause: McAfee does not recommend that you schedule the Performance Optimizer server tasks to run every second. The smallest recommended schedule is to run every minute. During troubleshooting, it might be acceptable to schedule the tasks to run more frequently, but this change causes a significant load to be added to the ePO server and is not advised.
    2.0.0 As Designed Issue: The upgrade from the beta extension 2.0.0.124 fails on ePO 5.1.2 with the following message:
UniqueKey ('name of key here') exists in a read-only query.
 
Cause: ePO 5.1.2 is unable to allow the read-only queries to be updated in the manner that Performance Optimizer uses.

Workaround: Uninstall the beta extension 2.0.0.124 from the Extensions page in the ePO console, and then install the new version of Performance Optimizer as a fresh installation and not an upgrade.
    2.0.0 As Designed Issue: When you upgrade to Performance Optimizer 2.0.0 with ePO 5.1.1, the dashboard and queries are not updated to have the latest definitions.

Cause: ePO 5.1.1 is unable to allow the read-only queries to be updated in the manner that Performance Optimizer uses.

Workaround: Uninstall the Performance Optimizer extension from the Extensions page in the ePO console, and then install the new version of Performance Optimizer as a fresh installation and not an upgrade.
1150282   2.0.0 2.1.0.116 Issue: The assessment "Server tasks - Schedule settings" includes hidden ePO server tasks.

When you click the link in the drill-down page, a message displays to indicate that the user is not authorized to view the server task.
    2.0.0 2.1.0.116 Issue: The chart color scheme shows only red and white graph points when you use the Assessments or Assessment History result type.
1037377 KB84163 1.0.0 2.0.0
Issue: The Performance Optimizer server task fails to run correctly, and the Server Task Log records the following error message:
 
Incorrect syntax near '*'
 
Solution: This issue is resolved in Performance Optimizer 2.0.0.

See the related article for details.
1027526 KB83644 1.0.0 2.0.0
Issue: A performance scoring task fails. The ePO Server Task Log shows the following error:
 
Failed: Failed to populate ePO Performance scoresError: Data Truncation.
 
Solution: This issue is resolved in Performance Optimizer 2.0.0.

See the related article for details.
1023148 KB84186 1.0.0 2.0.0
Issue: The Performance Scores server task fails for Performance Optimizer. The ePO orion.log contains a data truncation exception.

Solution: This issue is resolved in Performance Optimizer 2.0.0.

See the related article for details.
1014010 KB84888 1.0.0 2.0.0
Issue: The following error displays in the Performance Optimizer dashboard when you select Server tasks - Length of run time:
 
An unexpected error occurred. Error Message: Internal Error: DBO setter threw exception
 
Solution: This issue was resolved in Performance Optimizer 2.0.0 and 2.1.0, but reappeared in 2.2.0.111. It is now fixed again in 2.2.0.112.

See the related article for details about how to resolve the issue for 2.2.0.111.

The referenced article is available only to registered ServicePortal users.

To view registered articles:
  1. Log on to the ServicePortal at http://support.mcafee.com.
  2. Type the article ID in the search field on the home page.
  3. Click Search or press Enter.


Back to Top

Rate this document

Languages:

This article is available in the following languages:

English United States
Spanish Spain
Japanese

Glossary of Technical Terms


 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.