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: Files not replaced when using upgrade
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
Nov 15, 2011
03:48 AM
Files not replaced when using upgrade
Hi,
I am using installshield LE with upgrade paths.
I discovered a strange behaviour : sometimes dll files ( for example ) are not replaced when installing a new version.
How to resolve this ?
Regards,
Gregory
I am using installshield LE with upgrade paths.
I discovered a strange behaviour : sometimes dll files ( for example ) are not replaced when installing a new version.
How to resolve this ?
Regards,
Gregory
(7) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 15, 2011
08:17 AM
Hello Gregory,
Could you kindly provide MSI log of your installation process where some files are not being replaced?
To enable logging: Navigating to General Information View, Create MSI logs – Yes.
Also could you kindly let us know the exact steps which you are following to create Upgrade?
Thanks,
Bharath
Could you kindly provide MSI log of your installation process where some files are not being replaced?
To enable logging: Navigating to General Information View, Create MSI logs – Yes.
Also could you kindly let us know the exact steps which you are following to create Upgrade?
Thanks,
Bharath
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 17, 2011
05:09 AM
Hello Gregory,
From the log file I could see that some of the Components are being shared by another Product/application and hence the files are not being replaced in Upgrade.
Part of Log File:
MSI (s) (50:04) [19:32:08:576]: Disallowing uninstallation of component: {10B52016-982E-4D1F-9459-71F5314CC2EA} since another client exists
MSI (s) (50:04) [19:32:08:576]: Disallowing uninstallation of component: {42B8E0B5-C9BF-4D17-98A7-D33E467739CB} since another client exists
Could you kindly try to install the Setup on a different system and/or different location and check if the behavior persists?
Thanks,
Bharath
From the log file I could see that some of the Components are being shared by another Product/application and hence the files are not being replaced in Upgrade.
Part of Log File:
MSI (s) (50:04) [19:32:08:576]: Disallowing uninstallation of component: {10B52016-982E-4D1F-9459-71F5314CC2EA} since another client exists
MSI (s) (50:04) [19:32:08:576]: Disallowing uninstallation of component: {42B8E0B5-C9BF-4D17-98A7-D33E467739CB} since another client exists
Could you kindly try to install the Setup on a different system and/or different location and check if the behavior persists?
Thanks,
Bharath
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 17, 2011
07:12 AM
Hello Bharath
How can know which component is shared ? How to match {10B52016-982E-4D1F-9459-71F5314CC2EA} with something ?
I will try to install and upgrade after a full remove.
Regards,
Gregory
How can know which component is shared ? How to match {10B52016-982E-4D1F-9459-71F5314CC2EA} with something ?
I will try to install and upgrade after a full remove.
Regards,
Gregory
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 22, 2011
08:42 AM
Hello Gregory,
I’m currently looking into the issue and I would update you as soon as I have further information on this.
Thanks,
Bharath
I’m currently looking into the issue and I would update you as soon as I have further information on this.
Thanks,
Bharath
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 23, 2011
02:41 AM
Hello Gregory,
I gather that you had mentioned that you were using multiple upgrade paths, I have tried creating project with multiple upgrade paths and the projects were successfully installed.
Steps followed to create Sample Project are:-
1. Created Base Project (V 1.0) and then created Upgrade Project’s (V 2.0 and V 3.0) for the same by changing Product Version and Code.
2. Also added the Upgrade path for the same (V 1.0 , V2.0 for V 3.0)
Could you kindly provide us your project file (*.sln) so that we could test it in-house and investigate further?
Thanks,
Bharath
I gather that you had mentioned that you were using multiple upgrade paths, I have tried creating project with multiple upgrade paths and the projects were successfully installed.
Steps followed to create Sample Project are:-
1. Created Base Project (V 1.0) and then created Upgrade Project’s (V 2.0 and V 3.0) for the same by changing Product Version and Code.
2. Also added the Upgrade path for the same (V 1.0 , V2.0 for V 3.0)
Could you kindly provide us your project file (*.sln) so that we could test it in-house and investigate further?
Thanks,
Bharath