Loading...

Knowledge Center


ePolicy Orchestrator Pre-Installation Auditor Known Issues
Technical Articles ID:   KB88906
Last Modified:  12/5/2018
Rated:


Environment

McAfee ePolicy Orchestrator Pre-Installation Auditor (ePO PIA)

Summary

Recent updates to this article:
Date Update
December 5, 2018 Added new references: 1258139, 1255499, 1258515, 1254740, and 1257036 that are resolved with PIA 3.1.0.144.
September 18, 2018 Added PIA 3.1.0.140 to the "Product Release" section. Updated issues 1252001 and 1253067 as resolved in PIA 3.1.0.140, in the "Non-critical known issues" section.
August 31, 2018 Added PIA 3.1.0.133 details and an IMPORTANT statement. Added issue 1252001 in the "Non-critical known issues" section.
August 20, 2018 Added PIA 3.1.0 details and updated the Fixed column.
June 20, 2018 Added ePO 5.3 to product category. Title changed to cover all versions of PIA.

To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.

 
Product Release
Product Version Release Date Release Notes *
PIA 3.1.0.144 December 5, 2018 n/a
PIA 3.1.0.140 September 18, 2018 n/a
PIA 3.1.0.133 August 28, 2018 n/a
PIA 3.1.0.129 August 14, 2018 PD27907
PIA 2.2.0.129 March 1, 2018 n/a
PIA 2.2.0.126 December 14, 2017 n/a
PIA 2.1.0.106 September 6, 2017 n/a
PIA 2.0.0.320 April 26, 2017 n/a
PIA 2.0.0.310 March 15, 2017 n/a
PIA 2.0.0.295 March 14, 2017 PD26929

* Only major builds of the PIA tool are released with updated Release Notes.

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.


IMPORTANT:  
  • Before you install ePO, McAfee recommends for standalone usage of the PIA tool, that you always download the latest ePO PIA tool from either:
  • The ePO PIA tool is bundled with the ePO installer starting in ePO 5.10.0. For the ePO 5.10.0 installer to use the latest ePO PIA tool, follow the steps below:​
    1. Download the ePO PIA tool from one of the locations stated above.
    2. Unzip the PIA tool and copy the executable to the folder where ePO installation files are copied.
    3. Move or copy the existing PIA tool executable to a different folder, and copy the new PIA tool file to the ePO installer directory.
    4. ​Run the ePO installer (setup.exe) and follow the instructions.

Contents
Click to expand the section you want to view:

 
Reference
Number
Related
Article
Found 
PIA
Fixed
PIA
Issue Description
1258139 KB91033  3.1.0.140 3.1.0.144 Issue: ePO Preinstall auditor 3.1.0.140 crashed while checking DB collations.
Reference
Number
Related
Article
Found 
PIA
Fixed
PIA
Issue Description
1257036 - 3.0 3.1.0.144 Issue: Running the ePiP tool against the SQL database disables the xp_cmdshell, causing an outage for other applications.

Resolution: The Preinstall auditor tool now turns off xp_cmdshell when run against the SQL Server.
1254740 - - 3.1.0.144 Issue: ePO Preinstall Auditor check named 'Database High Availability/Disaster Recovery' points to the wrong article.
Resolution: The update now points to KB86152.
1258515  - - 3.1.0.144 Issue: ePO Preinstall auditor tool shows a failure for the high availability check if HADR (High Availability/Disaster Recovery) is enabled on the SQL Server though the ePO DB is not part of the HADR group.
1255499 - - 3.1.0.144 Issue: ePO Preinstall auditor tool run against SQL 2016 or later, shows a warning for trace flag 1118, though the trace flag 1118 is not applicable for SQL 2016 and later.
1252001 - 3.1.0.129 3.1.0.140 Issue: PIA incorrectly shows a database compatibility level of 100 as a pass when checking for an upgrade to ePO 5.10.
1253067
1253055
- 3.1.0.129 3.1.0.140 Issue: A SQL Collation check, which is needed for ePO 5.10, is missing from PIA.
1250023 - 3.1.0.129 3.1.0.133 Issue: A keystore validation error displays if the ca.keystore size is 1024 and the server.keystore size is 2048 when running the ePO PIA tool.
1240766 - 2.2.0 3.1.0.129 Issue: Using a domain account to connect to the SQL Server fails when not using the default port, even when the correct port is displayed.
1235726 - 2.0.0 3.1.0.129 Issue: ePO upgrade is interrupted when ePO Database mirroring is enabled during an upgrade.
1221922 - 2.2.0 3.1.0.129 Issue: A 'Local user group ePO Pre Checker Grp' created by PIA after entering the Windows account for ePO database connection is not deleted.
1182562 KB88745 2.2.0.126 3.1.0.129 Issue: ePO installer does not continue the installation process if a required Windows update is not installed correctly. (Happens if some Windows updates are not present on the server.)
1226131 - 2.1.0.106 3.1.0.129 Issue: While running checks, PIA stops working (crashes) in some environments.

ePIPAPI.log records the following entries:
  • No file rename operations are pending,
  • Msg (Cannot create a file when that file exists)
Application event log records the following:
Application Error,
Application crash event: 1000,
Faulting application name: ePIP.exe, version: 2.1.0.106, time stamp: 0x5964ab59 
Faulting module name: ePIP.exe, version: 2.1.0.106, time stamp: 0x5964ab59
Exception code: 0xc0000005 
Fault offset: 0x0012af59 
Faulting process id: 0xdd0 
Faulting application start time: 0xePIP.exe0 
Faulting application path: ePIP.exe
Faulting module path: ePIP.exe
1227048 - 2.2.0.126 2.2.0.129 Issue: PIA fails to connect to SQL in some environments, even though valid information is provided. The following error displays:
 
Database connection failed. Check your configuration
1222455 KB90185 2.2.0.295 2.2.0.126 Issue: PIA 2.2 stops working (crashes) while collecting SQL information.
1197370 - 2.0.0.320 2.1.0.106 Issue: PIA could stop working when run in the McAfee ePO server.
1198152 - 2.0.0.320 2.1.0.106 Issue: RSA check is missing from the PIA checklist.
1184061 - 2.0.0.320 2.1.0.106 Issue: PIA could stop working when changing the password in the tool.
1199491 - 2.0.0.320 2.1.0.106 Issue: PIA returns incorrect platform/ePO version information about Japanese Windows operating systems.
1176225 - 2.0.0.310 - Issue: The upgrade time displays an incorrect output if the ePO data is unusually large.

Cause: The ePO upgrade process takes a backup of vital folders. Generally, with a good configuration computer and little data in the ePO DB folder, this process takes about 30 minutes to totally upgrade ePO, before continuing to the database upgrade.

If the configuration data in the DB folder or on the computer is low-end or unusually large, backup can take an extended amount of time. These scenarios were not considered while calculating the expected upgrade time, so incorrect estimate data can display.
1184020 - 2.0.0.310 - Issue: Installation Auditor is unable to obtain local administrator rights to the SQL Server, if a clustered SQL Server is used. The ePO PIA tool does not accept the load balancer credentials of the clustered database. PIA does not move to the checks page.

Cause: If a clustered SQL Server is used, PIA tries to authenticate to the virtual IP/Name of the cluster, because that is what ePO uses to connect to the cluster. PIA must connect to the actual active node of the SQL cluster to complete the checks.

NOTE: Currently, Installation Auditor is not supported on clustered SQL servers. We are evaluating including support in a future release.
1175859  KB87731 2.0.0.310 2.0.0.320  Issue: The SQL Server system RSA compatibility check fails, even if the cipher order is correct and all Microsoft updates are applied.

Cause: The logic of the check is incorrect, causing the check to fail in some environments.
1188877   - 2.0.0.310 2.0.0.320  Issue: ePO PIA reports that ePO 5.9 is not supported on Windows Server 2016.

Workaround: Ignore this warning; ePO 5.9 is supported on Windows Server 2016. 
1189632 - 2.0.0.310 2.0.0.320 Issue: PIA stops working, or crashes, when trying to export results in some environments.
1189431  - 2.0.0.310 2.0.0.320 Issue: PIA is unable to find the version for SQL 2016 Express.
1189085  - 2.0.0.310 2.0.0.320 Issue: The "SQL Server System RSA compatibility" check is missing when PIA runs on computers without ePO installed.
1188290 - 2.0.0.310 2.0.0.320 Issue: The PIA tool crashes when initiating checks in some environments.
1189634 - 2.0.0.310 2.0.0.320 Issue: The Change Password button is enabled, even when the passwords do not match.
1188991  - 2.0.0.310 2.0.0.320 Issue: The ePO Installed Version drop-down field is editable in the PIA tool, but must not be.

Rate this document

Beta Translate with

Select a desired language below to translate this page.

Glossary of Technical Terms


 Highlight Glossary Terms

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