Reference
Number |
Related
Article |
Found
PIA |
Fixed
PIA |
Issue Description |
| EPO-9298 |
- |
3.1.0.189 |
3.1.0.227
(RTS) |
Issue: When you use the PIA tool 3.1.0.189, the temporary sample user isn't deleted.
Resolution: With PIA 3.1.0.227, no sample user is displayed in the lusrmgr.msc window after the PIA tool is closed. |
| EPO-8958 |
KB93066 |
- |
3.1.0.222 |
Issue: The PIA tool doesn't undertake a collation check after it performs a disaster recovery snapshot restore procedure. |
| EPO-8999 |
- |
- |
3.1.0.222 |
Issue: The ePO change password window doesn't display after you change your password. This issue is seen when the password doesn't match the criteria set from the PIA tool. |
| 1257036 |
- |
3.0 |
3.1.0.144 |
Issue: Running the PIA tool against the SQL database disables the xp_cmdshell, which causes 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: The PIA check named 'Database High Availability/Disaster Recovery' directs you to the wrong article.
Resolution: The update now directs you to KB86152. |
| 1258515 |
- |
- |
3.1.0.144 |
Issue: The PIA tool shows a failure for the high availability check if HADR is enabled on the SQL Server. It shows this failure even though the ePO database isn't part of the HADR group.
HADR = High Availability Disaster Recovery |
| 1255499 |
- |
- |
3.1.0.144 |
Issue: The PIA tool runs against SQL 2016 or later, shows a warning for trace flag 1118, although the trace flag 1118 isn't 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 it looks for an upgrade to ePO 5.10. |
1253067
1253055 |
- |
3.1.0.129 |
3.1.0.140 |
Issue: An 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. (Errors displayed when you run 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 you don't use 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' that's created by PIA after entering the Windows account for the ePO database connection isn't deleted. |
| 1182562 |
KB88745 |
2.2.0.126 |
3.1.0.129 |
Issue: The ePO installer doesn't continue the installation process if a needed Windows update isn't installed correctly. (This issue occurs if some Windows updates aren't present on the server.) |
| 1226131 |
- |
2.1.0.106 |
3.1.0.129 |
Issue: While running checks, PIA stops working (crashes) in some environments.
The 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 is displayed:
Database connection failed. Check your configuration
|
| 1222455 |
- |
2.2.0.295 |
2.2.0.126 |
Issue: PIA 2.2 stops working (crashes) while it collects SQL information. |
| 1197370 |
- |
2.0.0.320 |
2.1.0.106 |
Issue: PIA can stop working when run in the 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 can stop working when you change the password in the tool. |
| 1199491 |
- |
2.0.0.320 |
2.1.0.106 |
Issue: PIA returns incorrect platform or 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. With a good computer, and little data in the ePO DB folder, this process takes about 30 minutes. It then continues 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 aren't 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 doesn't accept the load balancer credentials of the clustered database. PIA doesn't 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's 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 isn't supported on clustered SQL servers. We're evaluating the inclusion of 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 isn't 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 don't 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 mustn't be. |
