Adding uninstall log to ARP (using MSI)
I have an MSI installer for my application. I have need of adding a log file to the ARP uninstall. I've tried modifiying some of the registry keys but to no avail. Does anyone have a suggestion?
thanks in advance
- jb[8D]
thanks in advance
- jb[8D]
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
turbokitty
17 years ago
Are you adding it to the MSI so it logs on uninstall on all your machines or are you trying to do it on a test machine?
If the latter, why? Just run the uninstall command from the run line and you'll get the same result...
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{yourappsguid}]
"UninstallString"="MsiExec.exe /x{yourappsguid} /l*v "C:\msi.log""
I've never tried that, but I'm assuming it'd work.
If the latter, why? Just run the uninstall command from the run line and you'll get the same result...
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{yourappsguid}]
"UninstallString"="MsiExec.exe /x{yourappsguid} /l*v "C:\msi.log""
I've never tried that, but I'm assuming it'd work.
Posted by:
spartacus
17 years ago
Have you tried the FAQ article on enabling logging?
This could be useful to you during testing because using this method generates a verbose log file for all windows installer activities - installations, maintenance operations (repairs) as well as uninstallations which is your own particular requirement.
On the down side, this level of logging can sometimes slow down installations and uninstallations - especially with larger MSI packages - so it's not generally recommended to leave this enabled permanently.
As an aside, Windows Installer 4.0 offers the MsiLogging and MsiLogFileLocation properties to enable verbose logging on a per-package basis - but this will only be available to you if you are packaging for Vista.
Regards,
Spartacus
This could be useful to you during testing because using this method generates a verbose log file for all windows installer activities - installations, maintenance operations (repairs) as well as uninstallations which is your own particular requirement.
On the down side, this level of logging can sometimes slow down installations and uninstallations - especially with larger MSI packages - so it's not generally recommended to leave this enabled permanently.
As an aside, Windows Installer 4.0 offers the MsiLogging and MsiLogFileLocation properties to enable verbose logging on a per-package basis - but this will only be available to you if you are packaging for Vista.
Regards,
Spartacus
Posted by:
jamsek19
17 years ago
Hello.
You can also change group policy to always creating log file (if not specified in command line).
Start -> Run: gpedit.msc
Under Computer Configuration -> Administrative templates -> Windows Components -> Windows Installer -> Logging: select Enable and in text box write "voicewarmup" (without quotes).
Explanation of each character in "voicewarmup" is nearby in the same window.
As I said before, if log file is not specially specified in command line this setting creates log file in %temp% folder. Log file name is in format MSI<random_number>.log
Using this settings Log files are created when installing, upgrading or uninstalling application.
This setting is specially useful as a group policy in an Active directory to assure that you can find log file on every system in a domain which this settings belong to.
Best regards
Andreo
You can also change group policy to always creating log file (if not specified in command line).
Start -> Run: gpedit.msc
Under Computer Configuration -> Administrative templates -> Windows Components -> Windows Installer -> Logging: select Enable and in text box write "voicewarmup" (without quotes).
Explanation of each character in "voicewarmup" is nearby in the same window.
As I said before, if log file is not specially specified in command line this setting creates log file in %temp% folder. Log file name is in format MSI<random_number>.log
Using this settings Log files are created when installing, upgrading or uninstalling application.
This setting is specially useful as a group policy in an Active directory to assure that you can find log file on every system in a domain which this settings belong to.
Best regards
Andreo
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.