I presently have multiple InstallShield project which all have Support Files. These files are added under the "Support Files/Language Independent" In the Online Help documentation it is said:"In your InstallScript code, support files are uncompressed into a temporary directory and then deleted when the installation is complete." So from what I understand, these files should not reside on the computer once the installation is completed. But it is not the case. This following action is the way I validated to see if these files were properly deleted once the installation was completed, I have opened a windows explorer and entered %temp% in the address bar. This action brought up the proper path where the Support files are supposed to be copied during the installation. If first deleted all files and folders, especially the {...} folder, in this temp directory, then ran the installation of my application that contained "Support Files". Then once the installation has been completed I looked at the temp folder to see that the Support Files where still under a {...} folder. I really don't understand why this support files are not deleted. If this was the only problem, it wouldn't be so bad. But in the case where I perform a major upgrade, if the support files where first deleted before executing this major upgrade. The files would not be copied back to this temp folder. Which in my case causes a crash of the installation when the major upgrade tries to access a previously copied dll. Is there something that can be done in order to make these support files deleted and copied back everytime the installation is performed. I've been working on this issue for a month. I really need support on this issue. Can anyone help me. It should be pretty simple to fix since the documentation seems to say that these support files are deleted by themselves, which probably means that they will be copied back on a major upgrade. thanks in advance ... View more

My problem is intermittent, Even rarely reproducible. But when the problem appears, it can be reproduced without any problem and get stuck in this behavior. So I try to call an Installscript Custom Action which ends up crashing the application. The windows Log indicates that the custom action returns 3 which represents an unprocessed custom action. Here is the output of the windows installer log: MSI (s) (D8:4C) [10:04:13:611]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIF51F.tmp, Entrypoint: f1 Action start 10:04:13: ManageFontInstall. InstallShield 10:04:14: Running InstallScript function f1 InstallShield 10:04:14: Opening stream of file C:\Windows\Installer\MSIF51F.tmp InstallShield 10:04:14: Extracting support file IsConfig.ini to C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\IsConfig.ini InstallShield 10:04:14: Extracted isconfig.ini to C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\IsConfig.ini InstallShield 10:04:14: Got '{70DDB886-7154-4798-8849-010C4ABE295B}' for TempPathGuid from isconfig.ini InstallShield 10:04:14: Attempting to use temp path 'C:\Users\mip5000\AppData\Local\Temp\{70DDB886-7154-4798-8849-010C4ABE295B}' InstallShield 10:04:14: Using temp folder C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7} InstallShield 10:04:14: Installing engine... InstallShield 10:04:14: Using product language 1033 InstallShield 10:04:14: Extracting support file setup.inx to C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\setup.inx InstallShield 10:04:14: Extracting support file ISRT.dll to C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\ISRT.dll InstallShield 10:04:14: Extracting support file _isres_0x0409.dll to C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\_isres_0x0409.dll InstallShield 10:04:14: Extracting support file String1033.txt to C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\String1033.txt InstallShield 10:04:14: Extracting support file _isuser_0x0409.dll to C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\_isuser_0x0409.dll InstallShield 10:04:14: Setting script cmdline... InstallShield 10:04:14: ProductCode is {9EDCF01C-5413-4CF3-9E12-8AB9551FAEAC} InstallShield 10:04:14: Initializing Engine InstallShield 10:04:15: Done Initializing... MSI (s) (D8!AC) [10:04:15:362]: Note: 1: 2732 2: 0 InstallShield 10:04:15: Registering Msi Server... InstallShield 10:04:15: Invoking script function ManageFonts InstallShield 10:04:15: CallScriptFunctionFromMsiCA() ends InstallShield 10:04:15: Cleaning up temp file C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\ISRT.dll InstallShield 10:04:15: Cleaning up temp file C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\IsConfig.ini InstallShield 10:04:15: Cleaning up temp file C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\String1033.txt InstallShield 10:04:15: Cleaning up temp file C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\_isres_0x0409.dll InstallShield 10:04:15: Cleaning up temp file C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\_isuser_0x0409.dll InstallShield 10:04:15: Cleaning up temp file C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\setup.inx Action ended 10:04:15: ManageFontInstall. Return value 3. Action ended 10:04:15: INSTALL. Return value 3. Then I have done a test where the first line of the Installscript custom action displays a Message box. The message box is never displayed when the crash happens. So I know that my InstallScript function is never called. The worst is that when doing a major upgrade, On the remove of the previous installation, this Installscript Custom Action is called and processed without any problem and returns 1. but on the second time, makes the application crash I have no clue what could be the problem. I've been working on this one for several days. Please help. thanks in advance. ... View more

I have an installation that we have seen several computer have an error 1603 message. This error does not happen on all computer. Plus It has only been seen during major upgrade. At first I had no clue what was the cause for this issue but after analysing the windows installer log of certain computer I may have found a clue. Usually when a log "Using new temp path" appears, it will be usually followed by a log "Attempting to use temp path" So here is the section of the log that seems to be erroneous. No trace of the "Using new temp path". Action start 10:04:13: ManageFontInstall. InstallShield 10:04:14: Running InstallScript function f1 InstallShield 10:04:14: Opening stream of file C:\Windows\Installer\MSIF51F.tmp InstallShield 10:04:14: Extracting support file IsConfig.ini to C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\IsConfig.ini InstallShield 10:04:14: Extracted isconfig.ini to C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\IsConfig.ini InstallShield 10:04:14: Got '{70DDB886-7154-4798-8849-010C4ABE295B}' for TempPathGuid from isconfig.ini InstallShield 10:04:14: Attempting to use temp path 'C:\Users\mip5000\AppData\Local\Temp\{70DDB886-7154-4798-8849-010C4ABE295B}' InstallShield 10:04:14: Using temp folder C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7} InstallShield 10:04:14: Installing engine... InstallShield 10:04:14: Using product language 1033 InstallShield 10:04:14: Extracting support file setup.inx to C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\setup.inx InstallShield 10:04:14: Extracting support file ISRT.dll to C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\ISRT.dll InstallShield 10:04:14: Extracting support file _isres_0x0409.dll to C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\_isres_0x0409.dll InstallShield 10:04:14: Extracting support file String1033.txt to C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\String1033.txt InstallShield 10:04:14: Extracting support file _isuser_0x0409.dll to C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\_isuser_0x0409.dll InstallShield 10:04:14: Setting script cmdline... InstallShield 10:04:14: ProductCode is {9EDCF01C-5413-4CF3-9E12-8AB9551FAEAC} InstallShield 10:04:14: Initializing Engine InstallShield 10:04:15: Done Initializing... MSI (s) (D8!AC) [10:04:15:362]: Note: 1: 2732 2: 0 InstallShield 10:04:15: Registering Msi Server... InstallShield 10:04:15: Invoking script function ManageFonts InstallShield 10:04:15: CallScriptFunctionFromMsiCA() ends InstallShield 10:04:15: Cleaning up temp file C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\ISRT.dll InstallShield 10:04:15: Cleaning up temp file C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\IsConfig.ini InstallShield 10:04:15: Cleaning up temp file C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\String1033.txt InstallShield 10:04:15: Cleaning up temp file C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\_isres_0x0409.dll InstallShield 10:04:15: Cleaning up temp file C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\_isuser_0x0409.dll InstallShield 10:04:15: Cleaning up temp file C:\Users\mip5000\AppData\Local\Temp\{2E37752C-CBD8-4023-8A26-ED7F01461EB7}\setup.inx Action ended 10:04:15: ManageFontInstall. Return value 3. And here is the same section without the problem. Action start 10:04:02: ManageFontInstall. InstallShield 10:04:04: Running InstallScript function f1 InstallShield 10:04:04: Opening stream of file C:\Windows\Installer\MSICD71.tmp InstallShield 10:04:04: Extracting support file IsConfig.ini to C:\Users\mip5000\AppData\Local\Temp\{84732526-FF1A-4385-A212-CD52F4E738A9}\IsConfig.ini InstallShield 10:04:05: Extracted isconfig.ini to C:\Users\mip5000\AppData\Local\Temp\{84732526-FF1A-4385-A212-CD52F4E738A9}\IsConfig.ini InstallShield 10:04:05: Got '{192DEAAC-6C6E-427B-9AFD-D3DC97618C80}' for TempPathGuid from isconfig.ini InstallShield 10:04:05: Attempting to use temp path 'C:\Users\mip5000\AppData\Local\Temp\{192DEAAC-6C6E-427B-9AFD-D3DC97618C80}' InstallShield 10:04:05: Using new temp path InstallShield 10:04:05: Cleaning up temp file C:\Users\mip5000\AppData\Local\Temp\{84732526-FF1A-4385-A212-CD52F4E738A9}\IsConfig.ini InstallShield 10:04:05: Using temp folder C:\Users\mip5000\AppData\Local\Temp\{192DEAAC-6C6E-427B-9AFD-D3DC97618C80} InstallShield 10:04:05: Installing engine... InstallShield 10:04:05: Using product language 1033 InstallShield 10:04:05: Setting script cmdline... InstallShield 10:04:05: ProductCode is {F9564D50-5BE6-4CE7-9A24-556E51961B0B} InstallShield 10:04:05: Initializing Engine InstallShield 10:04:05: Done Initializing... MSI (s) (D8!9C) [10:04:05:241]: Note: 1: 2732 2: 0 MSI (s) (D8!9C) [10:04:05:244]: Note: 1: 2732 2: 0 MSI (s) (D8!9C) [10:04:05:247]: Note: 1: 2732 2: 0 InstallShield 10:04:05: Registering Msi Server... InstallShield 10:04:05: Invoking script function ManageFonts InstallShield 10:04:06: CallScriptFunctionFromMsiCA() ends MSI (s) (D8:D8) [10:04:06:048]: Doing action: WindowsFolder.30729.01.Microsoft_VC90_CRT_x86.SP.D8D85FD0_537C_3A3A_9BEC_7A1B426637EC Action ended 10:04:06: ManageFontInstall. Return value 1. These section of log represents a call to a custom action which in the first section returns 3 which represents not completed. It should be returning 1 like the second section of the logs. So what is the real meaning when there is no log of the "Using new temp path" Could this be the cause for my 1603 error message? ... View more

I have a problem with a taskbar application that can be idle in the taskbar Notification area. At first when doing a major upgrade or uninstall of the application when the application is idle with its icon in the Taskbar notification area, the InstallShield process did not detect that it was running. So after reading on the web about this process, I have come to the conclusion that any application running in the background hidden by a icon in the taskbar Notification may not necessarily be detected by the Installer, you need to validate at one point during the uprade to see whether the Application is locked or not with the following function IS(FILE_LOCKED, application_path). This has been properly implemented and works sometimes but not all the times. In some case the executable is properly overwritten in the case of an upgrade but if the application is running on the taskbar notification area. If you double click on it once the upgrade is completely done. The application that will open will be the one from the previous release. Then if you completely exit the application and exit from the taskbar notification area, then if you reexecute the application, it will then be the new application from the new release. So my first question. Is this the best method and is there any other way to detect if an application is running in the back with its icon in the taskbar notification area? And my second question. If for some reason, we cannot fully detect that an application is running in the back hidden by the taskbar notification area, is there a way to kill the application or exit the process that is running in the background. thanks alot ... View more

We are currently developing a new font for our application. I have easily been able to install this new font via InstallShield by adding it to the Font Table. My InstallShield project is a InstallScript MSI project. So when I install my application, the font is nicely installed without any problem on my computer. If I do a remove of my application, It is removed without any problem. The problem I come up with is that if ever this font is used by another application such as Microsoft Word. The font seems to be locked and cannot be removed. But there is no notification that the font cannot be removed from my PC. Now the real problem may come up at one point where we want to do a major upgrade and the font would have changed, this would not be good since the new font would not be installed on the computer and the old font would still be used without any notice to the user. So is there a way to force the uninstall of a font by InstallShield? thanks ... View more