When upgrading from DLP 11.6.2 to 12.0 (On Windows Platform), we were receving following error :
The upgrader precheck has detected one or more inaccessible files. The upgrade has been canceled. Your system remains on the current version. For further assistance, see the Troubleshooting section of the Upgrade Guide for solutions.
Troubleshooting Performed :
1) The log files downloaded from the Upgrade Wizard does not contain “inaccessible_files.log”.
2) The logs folder in C:\SymantecDLP\Protect\Updates\enforceupgrade12.0 (which contains extracted JAR file for 12.0 upgrade) also does not indicate any error related to this issue.
3) Users protect and protect_update has Full Control on E:\SymantecDLP and sub-folders.
4) Running the EnforceUpgradeInstaller64.exe manually also results in the same error as above.
5) Process Monitor logs collected when the pre-check was in process, shows below mentioned entry :
Time of Day Process Name PID Operation Path Result Detail
38:32.5 EnforceUpgradeInstaller64.exe 4648 SetRenameInformationFile E:\SymantecDLP\Protect\logs ACCESS DENIED ReplaceIfExists: False, FileName: E:\SymantecDLP\Protect\logs-1370875112468
6) Assigned explicit permission to protect and protect_update users explicitly on E:\SymantecDLP\Protect\logs.
7) Logged in as a Local Administrator (Customer was logging in as a Domain User earlier) and then ran the upgrade. Received same error.
8) As per TECH221020, commented all the filenames in permissioncheck.txt, however it resulted in same error while upgrading.
However, none of the above steps helped fix the issue.
1) Found that in the "temp" directory of the currently logged on user, a log file gets generated with the name "i4j_log_EnforceUpgradeInstaller_...........log" which contains exact error like
[ERROR] I4jScript_Internal_30: Failed to rename: E:\SymantecDLP\Protect\logs
2) In this case, assigned "Log On Locally" privilege to "protect" and "protect_update" from Group Policy Editor ("Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment" ) and rebooted the Enforce server.
3) After above step, the upgrade was successful.
This resolution was successfully applied in Cases #04496531 and #05171154.