This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Install logs for serviceability
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 31, 2009
11:43 AM
Install logs for serviceability
Here is a scenario:
A non-technical user does the following
1. Install an app
2. Upgrade the app
3. Uninstall the app
4. Install the app
5. And so on
Would it be possible to keep the logs from step 1 to 5 automatically without making the user having to use msiexec from command line? If I use a setup exe, I can pass the log parameter to the msi, but it will overwirte the log each time.
So is this possible for msi and setup exe? This will be required for a good serviceability.
Not: The target machines are using msi 3.0 or greater, definitely not all 4.0.
A non-technical user does the following
1. Install an app
2. Upgrade the app
3. Uninstall the app
4. Install the app
5. And so on
Would it be possible to keep the logs from step 1 to 5 automatically without making the user having to use msiexec from command line? If I use a setup exe, I can pass the log parameter to the msi, but it will overwirte the log each time.
So is this possible for msi and setup exe? This will be required for a good serviceability.
Not: The target machines are using msi 3.0 or greater, definitely not all 4.0.
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 31, 2009
12:43 PM
If you are installing on systems with Windows Installer 4.0 or later, the MsiLogging property will generate a new log for each execution. Unfortunately, this log will be in a temp folder with a randomly generated name. Outside of that or to control the location, you'd need to somehow specify the log file name, perhaps with a custom bootstrap, or it won't happen.
As an idea, perhaps you could try the environment variables %DATE% and/or %TIME% in your setup.exe command line to get changing names?
As an idea, perhaps you could try the environment variables %DATE% and/or %TIME% in your setup.exe command line to get changing names?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 31, 2009
03:47 PM
Good idea, thanks Michael, I will try that
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 01, 2009
09:33 AM
Unfortunately, this didnt work Michael... it just names the file like Log%DATE%.txt. It doesnt resolve the actual date or time. Plus even it resolved, it could still be a problem since date has '/' in between and time has ':'. Those characters are not allowed in folder names.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 01, 2009
10:02 AM
Perhaps these variables are different from the usual ones as they don't show up if one runs set in the command prompt. But good point on the invalid characters. Ah well; it was worth a try.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)