slalande501.5524917511981086E12 asked a question.
"Using new temp path" not in windows installer log after "Attempting to use temp pat"
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?
So basically the new temp path retrieved from the isconfig.ini is not used for the following execution, as you can see from the logs.:confused: