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
- :
- Issue with uninstall after upgrading from earlier version
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
‎Aug 03, 2011
06:14 AM
Issue with uninstall after upgrading from earlier version
Hi,
I have a strange situation with uninstalling after a major upgrade from an earlier version. I'll describe some situations (All on clean Windows 7):
Note: version 2.6 is major upgrade of version 2.5
Situation A:
- Install version 2.5
- Install version 2.6 (which does of course an uninstall of version 2.5 first)
- Uninstall version 2.6
Situation B:
- Install version 2.5
- Remove version 2.5 manualy with 'Add/Remove programs'
- Install version 2.6
- Uninstall version 2.6
Situation C:
- Install version 2.6
- Uninstall version 2.6
The strange difference is that in Situation A all files of components that have a key file assigned are left on the system and in situation B and C all files are removed. All files of components without key file are removed in Situation A.
Hope anyone has an idea why this is occuring.
Regards,
Erik
I have a strange situation with uninstalling after a major upgrade from an earlier version. I'll describe some situations (All on clean Windows 7):
Note: version 2.6 is major upgrade of version 2.5
Situation A:
- Install version 2.5
- Install version 2.6 (which does of course an uninstall of version 2.5 first)
- Uninstall version 2.6
Situation B:
- Install version 2.5
- Remove version 2.5 manualy with 'Add/Remove programs'
- Install version 2.6
- Uninstall version 2.6
Situation C:
- Install version 2.6
- Uninstall version 2.6
The strange difference is that in Situation A all files of components that have a key file assigned are left on the system and in situation B and C all files are removed. All files of components without key file are removed in Situation A.
Hope anyone has an idea why this is occuring.
Regards,
Erik
(9) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 03, 2011
10:35 PM
For situation A, you will have to take a closer look at the verbose installation and uninstallation logs of 2.6 to figure out why it is doing that.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 04, 2011
01:57 AM
This is a line from situation A:
MSI (s) (B0:4C) [10:04:46:154]: Component: Logistic.exe; Installed: Local; Request: Absent; Action: Null
and this is the same line from situation B:
MSI (s) (D4:30) [10:34:19:765]: Component: Logistic.exe; Installed: Local; Request: Absent; Action: Absent
Can't find any other significant difference between the two logs actually regarding this.
MSI (s) (B0:4C) [10:04:46:154]: Component: Logistic.exe; Installed: Local; Request: Absent; Action: Null
and this is the same line from situation B:
MSI (s) (D4:30) [10:34:19:765]: Component: Logistic.exe; Installed: Local; Request: Absent; Action: Absent
Can't find any other significant difference between the two logs actually regarding this.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 04, 2011
02:24 AM
Read this for analysing your log:
http://msdn.microsoft.com/en-us/library/aa367858(v=vs.85).aspx
This means no action was taken. That means in an uninstall your file remains as such. In this case you need to check further if you have marked the component as SHARED etc...
This means your file has been removed.
http://msdn.microsoft.com/en-us/library/aa367858(v=vs.85).aspx
MSI (s) (B0:4C) [10:04:46:154]: Component: Logistic.exe; Installed: Local; Request: Absent; Action: Null
This means no action was taken. That means in an uninstall your file remains as such. In this case you need to check further if you have marked the component as SHARED etc...
MSI (s) (D4:30) [10:34:19:765]: Component: Logistic.exe; Installed: Local; Request: Absent; Action: Absent
This means your file has been removed.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 04, 2011
03:36 AM
Thanks for the link, I'm still new to reading the log so I'll try to find a little more about what's going on.
But my main concern is that I don't see any reason why the result between situation A and B should be different. I expect the same result regardless what happens (or mistakes I made) in my installer.
But my main concern is that I don't see any reason why the result between situation A and B should be different. I expect the same result regardless what happens (or mistakes I made) in my installer.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 04, 2011
02:18 PM
Which log is this line from? Installation of 2.6? Or uninstallation?
Erik S wrote:
This is a line from situation A:
MSI (s) (B0:4C) [10:04:46:154]: Component: Logistic.exe; Installed: Local; Request: Absent; Action: Null
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 04, 2011
04:03 PM
The line is from the uninstallation of 2.6
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 04, 2011
04:32 PM
One possibility is the ref count of component is incorrect, hence file in the component isn't removed after uninstalling 2.6. The installation log of 2.6 will shed more light on the cause of this behavior.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 05, 2011
04:01 AM
MSIYER wrote:
This means no action was taken. That means in an uninstall your file remains as such. In this case you need to check further if you have marked the component as SHARED etc...
TsungH wrote:
One possibility is the ref count of component is incorrect, hence file in the component isn't removed after uninstalling 2.6. The installation log of 2.6 will shed more light on the cause of this behavior.
Thanks both for the info! The SHARED of the components was indeed still set to Yes, that caused this behaviour. Spent 30 minutes to set all components shared properties to No. :mad:
But am I right that this seems an error by the Windows Installer? As I stated earlier I would expect the exact same result in Situation A en Situation B.
And last but not least: Why is the component SHARED property set to Yes by default :eek: ?? Googled for an answer and the only hits I find are related to people asking the same question for years...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 05, 2011
06:24 AM
But am I right that this seems an error by the Windows Installer? As I stated earlier I would expect the exact same result in Situation A en Situation B.
Yes, the end result should be same in both situations.
Somehow when upgrading(uninstall and install together) the ref count is not properly updated. When manually uninstalling the ref count is properly updated. I do not know what caused the error. Might be an error on Installer's part.
Why is the component SHARED property set to Yes by default
Ref count is internally maintained by Windows Installer Engine. There is no need for the shared bit in the modern world. Its still there for legacy compatibility. I too am not happy with this default option. So I make it a point to disable it the moment I create a component.