Purpose (problem description)

When uninstalling CAST AIP, the following error is seen during filelockcheck.bat:

Further logs show the error:

launch_cmd is launching command _C:\Users\XXX\AppData\Local\Temp\{1E627851-8D98-486B-B041-A0A9F4BF4AC5}\fileLockCheck.bat_ with parameters:
_"C:\Program Files\CAST\8.3\"_
File Locked: Bad path for find command, it should be : C:\Windows\System32\find.exe: PATH variable is not good
launch_cmd returns from C:\Users\XXX\AppData\Local\Temp\{1E627851-8D98-486B-B041-A0A9F4BF4AC5}\fileLockCheck.bat ERRORLEVEL=1

Observed in CAST Version



8.3.x (tick)
Observed in RDBMS



Step by Step scenario
  1. Uninstall AIP
  2. Error during uninstall
Action Plan

The problem is with the result of the PATH environment variable.  If there is some other command in the path, that is the same one that CAST AIP is normally looking for in the windows system area, then it will not properly find the proper command path.  The solution is to modify the PATH environment variable so that the windows system path is found first.

For example, for find, it can be found in the windows system area or cygwin (Linux commands).

So that if the path is something like this:

Then it needs to be modified so that the system32 path is above the cygwin path.

From a command prompt you can also issue a 'where <command>' to see the location of the found executable.  In the above example for find, issuing 'where find' results in the following which shows the cygwin path first:

If the problem you are facing does not match any case listed in this page, contact CAST Technical Support with the following: relevant input.



Ticket # 24404

Related Pages