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
- :
- Uninstall Problem - Installed Features No Removed
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
‎Oct 10, 2008
12:20 PM
Uninstall Problem - Installed Features No Removed
InstallScript MSI
Uninstall is not working. Several of the features/components that were installed were not removed. This results in several EXEs, DLLs, services, a virtual directory, registry entries and more left behind.
The only clue I have is the MSI Log. The log seems to indicate the a feature is not installed when in fact it is. The log indicates components that are part of feature are installed but for some reason the feature isn't. Here's a couple sample lines from the LOG.
MSI (s) (78:E8) [11:30:06:964]: Feature: Data_Collection; Installed: Absent; Request: Null; Action: Null
.
.
.
MSI (s) (78:E8) [11:30:06:968]: Component: Data_Collection; Installed: Local; Request: Null; Action: Null
The component "Data_Collection" is installed. It can only get installed as part of the "Data_Collection" feature.
Since I've changed, compiled and tested setup literally dozens of times, I think I might be facing a situation where the installer database is simply "confused". Is there a way to wipe out all references to my features/components/etc. from the installer database so I can retest from scratch? Wiping out the OS is not a realistic option at this point.
I desperate for an answer at this point.
Uninstall is not working. Several of the features/components that were installed were not removed. This results in several EXEs, DLLs, services, a virtual directory, registry entries and more left behind.
The only clue I have is the MSI Log. The log seems to indicate the a feature is not installed when in fact it is. The log indicates components that are part of feature are installed but for some reason the feature isn't. Here's a couple sample lines from the LOG.
MSI (s) (78:E8) [11:30:06:964]: Feature: Data_Collection; Installed: Absent; Request: Null; Action: Null
.
.
.
MSI (s) (78:E8) [11:30:06:968]: Component: Data_Collection; Installed: Local; Request: Null; Action: Null
The component "Data_Collection" is installed. It can only get installed as part of the "Data_Collection" feature.
Since I've changed, compiled and tested setup literally dozens of times, I think I might be facing a situation where the installer database is simply "confused". Is there a way to wipe out all references to my features/components/etc. from the installer database so I can retest from scratch? Wiping out the OS is not a realistic option at this point.
I desperate for an answer at this point.
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 13, 2008
04:28 PM
Does this behavior occur with a default setup.rul in your project? Also, is this behavior occurring on one machine or multiple machines?
You could try using the Windows Installer Cleanup utility or msizap.exe to try cleaning up the machine state.
You could try using the Windows Installer Cleanup utility or msizap.exe to try cleaning up the machine state.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 14, 2008
12:42 PM
I can't use an empty (default) setup.rul because I have a few MSI properties and path that must be set at run time. However, using your suggestion, I started with a default and added just the necessary 5 lines to setup.rul. The problem persists. This is actually a bit of a relief as the setup script is rather complicated.
I have used the windows installer cleanup utility. That doesn't solve the problem either.
To reiterate, first time isntallation works fine. My problems are with uninstall not deleting EXEs (and more) that it should remove.
I have used the windows installer cleanup utility. That doesn't solve the problem either.
To reiterate, first time isntallation works fine. My problems are with uninstall not deleting EXEs (and more) that it should remove.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 15, 2008
09:33 AM
As a follow up, the install/uninstall works just fine on my Win2K box. Must be something to do installation under Vista or my Vista configuration. It'll probably be a few days before I can test it against a fresh Vista OS.