We've had a wierd problem at a customer site.
On several of the customer's machines, when our installer runs (invoked using msiexec.exe with the /L*v parameter for verbose logging) the usually verbose log file is extremely terse, even though the installation is successful.
in fact, this is all that makes it into the log file:
=== Verbose logging started: 11/15/04 17:03:40 Build type: SHIP UNICODE 2.00.2600.02 Calling process: C:\WINNT\system32\msiexec.exe ===
MSI © (09:01): Resetting cached policy values
MSI © (09:01): Machine policy value 'Debug' is 0
MSI © (09:01): ******* RunEngine:
******* Product: C:\jmccdstmp\CPMClient.msi
******* Action:
******* CommandLine: **********
MSI © (09:01): Client-side and UI is none or basic: Running entire install on the server.
MSI © (09:01): Grabbed execution mutex.
MSI © (09:01): Incrementing counter to disable shutdown. Counter after increment: 0
MSI © (09:01): Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI © (09:01): MainEngineThread is returning 0
=== Verbose logging stopped: 11/15/04 17:03:50 ===
For example, I have an immediate mode custom action that attempts to write my own line to the log file near the end (IE, after InstallFinalize). It never makes it into the log file.
What could cause this? The actual install is successful.
Thanks,
Ken McKinney
Edited by kenmckinney, 10 December 2004 - 21:05.