Summary

Synopsis

Discussion

• The .rra temp file persists and the file is left unchanged, or
• The previous file is deleted and the .rra file is renamed to the latest version of the file.

If the file is in use a reboot prompt is expected and information in the client Registry is created to handle the post reboot process to update the file upon restart.

Workaround

1. Reboot the client after the installation. The expected behavior is after the reboot the locked files should be updated and the .rra files should be removed.
2. If your installation crashes or errors out unexpectedly, this may explain why .rra files are present on your system. Delete the .rra file(s) from your system and reinstall your application as needed.
3. Trap the locked or in use file with the OnFileLocked event. This approach faciliotates the installation to "fail" or provide an error message as required.
   • Open the InstallShield project.
   • Navigate under the 'Behavior and Logic->InstallScript' view. Selct the Setup.rul file.
   • Above the script editor window, click on the left-most drop down list and select 'Miscellaneous'.
   • From the right-most drop down list, select 'OnFileLocked' and this is expected to enable the OnFileLocked event in your script. Using custom script change the default behavior of returning ERR_PERFORM_AFTER_REBOOT and return a different return code and/or add a message.
4. Include a custom check in the beginning of your installation to see if your application is in use or lcoked. If so, prompt a dialog on the client to shut down the running process before proceeding. This way, the files should not be locked and can be overwriten without needing a reboot.

Related Documents

OnFileLocked