JDK-6714867 : Clicking Cancel in "File In Use" dialog show's error dialog for both install and uninstall
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 6u10
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2008-06-16
  • Updated: 2010-04-06
  • Resolved: 2009-03-04
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6u14Resolved
Related Reports
Duplicate :  
JDK-6775670 - Need to send unique ping and exit gracefully when user cancels install via FilesInUse
Description
How to reproduce.
1.) Install JRE promoted b26
2.) Open some applet in Browser
3.) Now uninstall from Add/Remove
4.) It will Show File In Use Dialog (attachement - FIU_Uninstall.JPG)
5.) Clcik on Cancel button in the above dialog

Expected behaviour
Uninstllation process should be killed

Actual Behaviour:
It show's error dialog (attachement - ErrorDialogOnUninstall.JPG), followed by "fatel error duiring installation" error message dialog.

There are two issues:
1.) Uninstall process should be killed without showing any error.
2.) Wrong message on uninsatllation "fatel error duiring installation". It should be "fatel error duiring uninstallation"
Comments
EVALUATION This CR will be handled via 6775670.
04-03-2009
EVALUATION Targeting this for 6u12.
14-08-2008
EVALUATION This seems too risky for 6u11, and there's not enough time for proper testing. Also, there isn't much benefit to the fix, because it only happens when the user cancels.
13-08-2008
EVALUATION After further investigation, the preferred method of fixing this issue will be to call a DLL function from MSI, which then streams FilesInUse.exe and calls CreateProcessAsUser() for the exe. In this way, will be able to start the FIU process, and also have appropriate return code handling via MSI. We will use the existing RegUtilsMSI.dll for the above.
23-06-2008
EVALUATION This is expected behavior from MSI. We had to change the FIU dialog from a DLL to an EXE because of some limitations to the WINAPI created with the Vista release. Because the installer is now calling an EXE, return code handling is different. When anything but ERROR_SUCCESS is returned by the EXE, the installer will throw 1722. A possible workaround is to return ERROR_SUCCESS on a cancel, but prior to doing so set a flag (regkey, touch a file, etc) and create another custom action that is executed immediately after FIU to ping the flag and take appropriate action. This way the cancel could be trapped and executed without throwing errors. Targeting this workaround for 6u11...not a showstopper for 6u10.
16-06-2008