Active1 month ago
- Msiexec Log File Example
- Msiexec Log File Example For Word
- .log File Extension
- Msiexec Log Verbose
- Hijackthis Log File
How can I enable logging in my MSI project and set
MsiLogFileLocation
? Now I am running my setup.msi
with command line arguments:I want to log my work always just running
setup.msi
without any arguments. Are there any ways to do that?Installing MQ using MSIEXEC on Windows. Scenario 2: Installing MQ on Windows for the first time Using Response File Alternatively, you can use the msiexec command with a parameter that calls a response file. A response file is an ASCII text file that contains the parameter values that you want to set for the installation. I have tried several times to install a quicktime package on several clients, if i type this command out in the Packages program command line it cuts off the transform and fails. What I had to do was created an Install.cmd script with this exact command line in it and it works?!?! There is a limit to the number of characters that can.
Mayur
MayurMayur
2 Answers
From the MSI SDK: 'You can enable verbose logging on the user's computer by using Command Line Options, the MsiLogging property, Logging policy, MsiEnableLog, and EnableLog method'.
Short Answer: So add the property MsiLogging property to your MSI's Property Table and maybe use
'vp'
as value (without the quotes).Hot Debugging Tip: Search for 'value 3' in the log file to find errors as explained by
Rob Mensching
(Wix & Orca author). MSI log files can be overwhelming otherwise. See more on log-interpretation below (yellow section).Express Logging (Verbose): Simplest possible, verbose logging from
cmd.exe
.Quick Parameter Explanation:
Debug Logging (Verbose): Advanced, slow logging for maximum details captured. The incredible hulk game 2008.
Quick Parameter Explanation:
All MSI Packages - Global Logging (policy)
Yes, you
enable logging globally on the machine
by setting the appropriate registry key. Each MSI launched will then cause a log file with a temporary name to be created in the TEMP
folder. Sort file list by change date to get the most recent one.Registry Key & Value: The actual registry settings:
How-To: Please see this FAQ-entry from installsite.org, section '
Globally for all setups on a machine
': http://www.installsite.org/pages/en/msifaq/a/1022.htm for the exact procedure.Heads-Up (technical detail):
This is a very technical problem that may have a bothersome and highly unexpected pragmatic effect
. A side-effect of this global logging is that any Session objects you instantiate from a script using the MSI-API will also create a log file in the TEMP folder. This can cause hundreds of log files to be created in the TEMP folder if you iterate all packages and instantiate a session object. Also in the Event Log (a big system administrator no-no!). Very specific problem, but just pointing it out. A cleanup of the temp folder and Event Log 'solves' the problem - or better yet - just avoid creation Session objects. Note that your deployment tool could instantiate session objects unexpectedly. Maybe check after enabling logging so you don't get this silly problem network-wide.Msiexec Log File Example
Package-Specific Logging
Apart from global settings and policies, you can customize the logging per package via properties or custom actions or just specify options and logging location via the msiexec.exe command line.
Command Line: In its simplest form:
msiexec.exe /i C:PathYour.msi /L*v C:Your.log
. Documentation for the msiexec.exe command line (look at section for switch: /L
)Properties: You can set the MsiLogging property in each package to customize logging. The MSI property MsiLogFileLocation holds the path to the log file. Use this if you want to open the log after installation.
Custom Action: You could investigate the
Installer.EnableLog method
of the MSI-API to customize the logging behavior for a specific MSI from a custom action. More: Windows Installer Logging.Interpreting MSI Log Files
On the topic of interpreting log files: How to interpret an MSI Log File.
Direct Link:
Direct PDF Link to Robert Macdonald's log guide
(resurrected from Wayback).Find Errors: And, as stated above: search for 'value 3' in the log file to find errors as explained by
Rob Mensching
(Wix & Orca author). MSI log files can be overwhelming otherwise.Advanced Installer: How Do I Read a Windows Installer Verbose Log File?
Some Links:
- Windows Installer Logging (lots of core information, do read)
- Windows Installer Best Practice (verbose logging for troubleshooting)
25.6k1515 gold badges6161 silver badges129129 bronze badges
To enable auto logging for
MSI
installer it needs to be edit with Orca
to set an appropriate value for MsiLogging
property. MSI
is editable with Orca
, the official MS tool for editing MSI
packages.MSI
packages are not executable binaries but rather a Database with data defining the installation process. We can add the MsiLogging
property with value v
.(ref)
MayurMayur
Not the answer you're looking for? Browse other questions tagged windows-installermsiexec or ask your own question.
Active1 year, 10 months ago
I have been trying to create a log file for an issue with our installer with the following commands:
and several other variations of the command, but it always pops up the window that states what command line parameters are valid for msiexec. What is the correct way to have the msi file create a log? I have windows installer 4.5.
Bender the Greatest
Bender the GreatestBender the Greatest5,0801010 gold badges4949 silver badges101101 bronze badges
2 Answers
The first and the last command lines are correct:
Msiexec Log File Example For Word
And you can drop quotes in this particular case.
Bender the Greatest5,0801010 gold badges4949 silver badges101101 bronze badges
Alexey IvanovAlexey Ivanov10.2k44 gold badges3333 silver badges5555 bronze badges
![Hijackthis log file Hijackthis log file](https://communities.bentley.com/cfs-file.ashx/__key/communityserver-wikis-components-files/00-00-00-01-63/1185.w5a.png)
If you are using Visual Studio 2008, use capital '
/L
' for the log option. Lower-case '/l
' is ignored.This appears to have been fixed in later versions of
msiexec
..log File Extension
Bender the Greatest5,0801010 gold badges4949 silver badges101101 bronze badges
Mark LakataMsiexec Log Verbose
Mark Lakata![Log Log](https://communities.bentley.com/resized-image.ashx/__size/690x0/__key/communityserver-wikis-components-files/00-00-00-01-63/1185.w5a.png)
15.2k55 gold badges7979 silver badges103103 bronze badges