Msiexec Log File Example
As part of a continuous delivery pipeline I'd like to install an msi on a given machine. msiexec plus psexec does this perfectly, but it seems that msiexec can only log to a file and I need it to log to stdout/stderr.
Log file and create various color-coded HTML reports based on a log file. By default, an MSI log file contains a return value for each built-in and custom action. The following sections describe how to write more detailed information into the log file. Note that these techniques do not create an MSI log file or initiate logging, but instead. The Silent Install options for the Windows installer (msiexec) /quiet, /q, qn. Silently install the msi package and write the installation log to file C: msilog. Silently install the msi package and write the installation log to file C: msilog.txt. For example, to generate a log file that logs everything verbosely, use the following: /L.v 'C: MyLogFiles package.log' /p Use the /p option to apply a patch to an installed product. To patch an installed administrative image, combine this option with /a as shown: /p PatchPackage /a Package /q n b r f.
Right now, to get the output back into our CI software I'll have to add a second step to echo the contents of the log, which seems a bit pointless.
Has anybody faced this issue before (and overcome it?)
Thanks in advance for any help here.
Mark
3 Answers
I checked this again, and here is some updated information:
It is possible to suppress the MSI GUI and set an external GUI implemented by a third party. This external GUI is able to receive messages from msiexec.exe as it performs the installation. This is mostly to implement a custom progress bar, but it seems you can also intercept most other error messages and status messages: MsiSetExternalUI function.
The interesting parameter is the dwMessageFilter. By setting this you can, for example, receive only the error messages that occur during the installation - or so it would seem. I suppose this can be enough for most purposes.
Regrettably I do not have sample code for this at the moment. I will test this later, when I get my system set up properly. The MsiEnableLog function is a related function call that will enable logging to file. Update: Here is what looks like a working SDK example.
If nothing is found, try entering program name WITHOUT its version number.4) Try entering only a PART of program name instead of whole name.5) Make sure to put SPACES between words.6) Enter the program name and its version number EXACTLY as it appears on About screen or program's official website.FreeSerials.com - Free Serials and Cracks:You are welcome to send us your.All cracks are processed manually and scanned for viruses by antivirus programs. Antivirus information is updated regularly.If you are using AVG ANTIVIRUS, be prepared to hundreds of FALSE positivies on CRACK files.If you still suspect you found a virus or trojan in a file downloaded from our site, please immediately to halt spreading of infection.InformationLast database added: 19.4.2011Serials in Database: 22356Misc.http://www.requestcracks.com/. Free software cracks and serials. It is still advised that you use your own antivirus to scan downloaded files for viruses.We recommend using either Kaspersky Anti-Virus or Norton AntiVirus. Search Rules:1) If the program name is ' Google Earth 1.0', don't search ' Earth version 1.0', write a full name!Example: ' Google Earth v1.0'.2) Do not write words such as: ' serials', ' cracks', ' cd key' and etc.3) Try entering program name and only first digits of it's version number.
At the command line interface level, you can also set logging to flush its buffer immediately to file by adding the ! parameter:
This means the log file is written continuously so no log buffer is lost if msiexec.exe crashes. The cost is a significantly slower installer due to the IO overhead.
Stein ÅsmulStein ÅsmulMsiExec can only log to a file, so you will have to keep echoing the content of that file after the installer finished.
I would rather cache the MSI log file on the local system permanently in a common location for each install, and then just register the exit code of the whole setup. If the setup reports success, the log file is pretty uninteresting? Just more 'noise'?
Other than that there are several software delivery systems that will capture the log information for an MSI install and store it centrally. One example is SCCM (Microsofts renamed Systems Management Server - SMS).
Msiexec Download
Setting up logging for all MSI files, see section 'Globally for all setups on a machine': http://www.installsite.org/pages/en/msifaq/a/1022.htm
Stein ÅsmulStein Åsmul