Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

verbose log file isn't!


1 reply to this topic

kenmckinney

kenmckinney
  • Members
  • 2 posts

Posted 10 December 2004 - 21:03

Hi,

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.


Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 14 December 2004 - 10:11

Your log only includes the Client side process as indicated by MSI ( c ).
All the Server side stuff MSI (s) is missing. Are you running this setup with privilege elevation? Looks like the log messages from the Server side don't get through to the Client side which will write them to the log. If you can upgrade the machine to MSI 3 this might solve the problem.