Aktion beendet um InstallFiles. Having the log file you may need to verify that a particular feature, component or file has been installed.
The verbose log includes an entry for each feature and component the installation package may install. The log tells what the state of that feature or component was prior to the installation, what state was requested by the installation, and in what state the installer left the feature or component.
Features and components entries appear in the log as in the following example:. The following table summarizes the possible component or feature states that can appear in the log:.
In order to check for the features and components states, please search for the InstallValidate standard action. After the standard action is marked as the current action which is being executed, on the following lines in the log, the features and components state is displayed.
The verbose log can give you useful information about the installation process and some explanation about this. For example:. Basically, this can happen if the same components are shared between multiple packages installed on the same machine. Windows Installer keeps a refcount for the components and does not allow removing them until all the applications that use them are removed. Also, this may happen if you duplicate the project file saved under a different name or used the "copy-paste" method.
To avoid this, you must use the Save as template option. If during an upgrade operation there are files missing from the installation folder, then search through the log for the following message:.
If you found it, then this is the reason why your file is not copied on the target machine. The upgrade process performs the following actions:. To overcome this behavior, you can enable the Always overwrite existing file option from the File Operations Tab of the File Properties.
This indicates that the installation package will not overwrite the existing file since is the same version as the one being installed. When performing an upgrade, you may encounter the case where the old installation package is left behind and the new package is listed side by side with the old one in the Programs and Features list.
This may happen if the previous version of the installation package is not detected. If an upgrade is not performed, the first step to start the investigation is to see if the installation packages have the same UpgradeCode, as is mandatory to have it the same.
A set of different versions of your application will have the same UpgradeCode. This enables newer versions of your application to search and upgrade previous versions installed on the same computer. If the same UpgradeCode is used, then you can start searching through the log and see if an older version is found.
During the FindRelatedProducts standard action, older or newer versions of the package are searched. In the log, it should be something like:. The old installation package is removed during the RemoveExistingProducts standard action.
After the installation is finished, the log is complete. The example command line uses the sample paths in this How-To. For your package you must use the path of your MSI file. After you use the logging command, you need to specify the log's complete path. If you want the log to be created next to the MSI, you can specify only the name of the log file:. When the package is included in an EXE bootstrapper, the command line no longer uses "msiexec". For example, the command line can look like this:.
Therefore, a command line which creates a log for an uninstall can look like this:. Information Title. URL Name. To obtain debug logging from an MSI install, use the following command from an Administrator command prompt: msiexec. This is a generic error and does not provide information specific to any issues that may have occurred. Suppose we can add that registry key during installation and remove it after completing installation.
You can write to the log file relatively easily, and you should be able to log to the Event Viewer as well - if you code it yourself. It depends on your actual scenario and what you need to achieve? With some coding you might be able to kick off the log file from the setup finish dialog? Do not meddle with that key during installation. Please see updated answer and the Installer. I have never used it, since I don't want to mess with the global logging configuration.
This proved actually useful for my recent problem analysis. Also I believe it shows information about MSI handle leaks and propably other useful stuff. I wouldn't enable it for regular logging as part of a normal setup though, as it could slow down the setup. Great idea. I will add that, and also the flush to log option! This flush to log option may drastically slow down installation. Show 1 more comment. Sign up or log in Sign up using Google. Sign up using Facebook.
Sign up using Email and Password. Post as a guest Name. Email Required, but never shown.
0コメント