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
- :
- Re: Cleaning up after an error?
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
Apr 21, 2011
06:38 PM
Cleaning up after an error?
Hiya,
This may seem a really silly question, but I have an install for which only one machine is having problems. Lots of diagnostics later its shown that the machine in question has an extra 'use count' for many of the components of the product, and hence when uninstalling, non-file data isnt being removed.
Symptoms show an example component at uninstall time reports
Component XXXX - Installed: INSTALLSTATE_LOCAL Action: INSTALLSTATE_UNKNOWN
whereas a working component is showing:
Component XXXX - Installed: INSTALLSTATE_LOCAL Action: INSTALLSTATE_ABSENT
(this ties in with diagnostics I've seen when looking at multi instance install issues in the past hencemy belief its a use count issue)
Now I have no idea how this machine got into the state nor has the owner, and it could have been a bug introduced and fixed (this is a developers machine) or it might have been the owner cleaned up the machine somehow (badly!)...
However... understandably, the owner doesnt want to reinstall...
Is there anyway to
(a) remove these extra use cases for those components (ideally) or
(b) identify who MSI thinks owns that component now (there's none of my program in add/remove, and it doesnt have any shared components)
Thanks!
Jason
This may seem a really silly question, but I have an install for which only one machine is having problems. Lots of diagnostics later its shown that the machine in question has an extra 'use count' for many of the components of the product, and hence when uninstalling, non-file data isnt being removed.
Symptoms show an example component at uninstall time reports
Component XXXX - Installed: INSTALLSTATE_LOCAL Action: INSTALLSTATE_UNKNOWN
whereas a working component is showing:
Component XXXX - Installed: INSTALLSTATE_LOCAL Action: INSTALLSTATE_ABSENT
(this ties in with diagnostics I've seen when looking at multi instance install issues in the past hencemy belief its a use count issue)
Now I have no idea how this machine got into the state nor has the owner, and it could have been a bug introduced and fixed (this is a developers machine) or it might have been the owner cleaned up the machine somehow (badly!)...
However... understandably, the owner doesnt want to reinstall...
Is there anyway to
(a) remove these extra use cases for those components (ideally) or
(b) identify who MSI thinks owns that component now (there's none of my program in add/remove, and it doesnt have any shared components)
Thanks!
Jason
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 27, 2011
03:01 PM
Just a follow on comment, but if anyone can even give me guidance on how to manually clean up (registry?) it would be useful!
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)