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
- :
- Update
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
‎Jan 25, 2010
04:17 AM
Update
Hello,
I have a problem with my setup.exe, when i want update my setup some composant are not installed. In the log, i have :
FOR FEATURE
MSI (s) (2C:48) [09:54:32:979]: Feature: XXX_Files; Installed: Advertise; Request: Reinstall; Action: Reinstall
AND for componant of the feature:
MSI (s) (2C:48) [09:54:32:979]: Component: XXX_OVERWRITE_xdll; Installed: Absent; Request: Null; Action: Null
And for my second feature, all is good, componants are updated.
Feature: YYY; Installed: Local; Request: Reinstall; Action: Reinstall
Component: YYY_files; Installed: Local; Request: Local; Action: Local
Other information :
Command Line: REINSTALL=ALL REINSTALLMODE=vamus IS_MINOR_UPGRADE=1
Who can help me, please.
I have a problem with my setup.exe, when i want update my setup some composant are not installed. In the log, i have :
FOR FEATURE
MSI (s) (2C:48) [09:54:32:979]: Feature: XXX_Files; Installed: Advertise; Request: Reinstall; Action: Reinstall
AND for componant of the feature:
MSI (s) (2C:48) [09:54:32:979]: Component: XXX_OVERWRITE_xdll; Installed: Absent; Request: Null; Action: Null
And for my second feature, all is good, componants are updated.
Feature: YYY; Installed: Local; Request: Reinstall; Action: Reinstall
Component: YYY_files; Installed: Local; Request: Local; Action: Local
Other information :
Command Line: REINSTALL=ALL REINSTALLMODE=vamus IS_MINOR_UPGRADE=1
Who can help me, please.
(7) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 25, 2010
05:23 AM
Try adding all the required features in ADDLOCAL property.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 25, 2010
07:15 AM
so, I have "ALL" as the value and the logs, it tells me that he took all my features
I forgot this information :
Dumping binary patch manager data...
MSI (s) (58:B4) [14:10:07:120]: The file represented by File table key 'xxx.dll' has no eligible binary patches
MSI (s) (58:B4) [14:10:07:121]: The file represented by File table key 'yyy.exe' has no eligible binary patches
MSI (s) (58:B4) [14:10:07:122]: The file represented by File table key 'zzz.dll' has no eligible binary patches
I forgot this information :
Dumping binary patch manager data...
MSI (s) (58:B4) [14:10:07:120]: The file represented by File table key 'xxx.dll' has no eligible binary patches
MSI (s) (58:B4) [14:10:07:121]: The file represented by File table key 'yyy.exe' has no eligible binary patches
MSI (s) (58:B4) [14:10:07:122]: The file represented by File table key 'zzz.dll' has no eligible binary patches
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 28, 2010
07:29 AM
Use the Update Validation Wizard to make sure no component/key file was removed from the most recent MSI package, compared to the previous version.
One good point to remember: if you have used Dynamic Links, some components/key files might have been removed without you realizing.
One good point to remember: if you have used Dynamic Links, some components/key files might have been removed without you realizing.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 29, 2010
07:52 AM
Thank you for your reply, but where can I find the "Update Validation Wizard"?
And another question: Do you believe a feature with full component is not installed because it lacks a file in a component?
And another question: Do you believe a feature with full component is not installed because it lacks a file in a component?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 29, 2010
08:12 AM
As you probably know, if your setup must support minor upgrades, you must not delete any component or component's key file.
If you do, performing the minor update will set the corresponding feature as advertised, although it was locally installed by the original setup.
Now think about the dynamic links: if the "Create best practice components" checkbox is disabled, they create components dynamically when you build, and choose the first file in each subfolder as key file.
If you removed one file in a folder that is dynamically linked, the build will not tell you that the file is missing, and your minor upgrade will go through, but some features might then be advertised.
It is a common problem when using dynamic links.
On top of that, the component names are randomly generated at each build when using these dynamic links. Another constraint of a minor upgrade is that you cannot change the name of a component. So, you need to tell InstallShield where your previous MSI package is before building your next release. In the Releases view, click on the media, then on the Build tab, and set the Previous Package.
This is where the upgrade validation wizard comes in handy!
in the menu: Build-->Validate-->Upgrade Validation Wizard...
The rest should be self explanatory.
There are quite a few threads about this problem
Note that some of these problems disappear if you set your dynamic links to "Create best practice components", but I am not sure this option is available in IS 2009. It definitely is in IS 2010.
I hope that helps.
Regards
If you do, performing the minor update will set the corresponding feature as advertised, although it was locally installed by the original setup.
Now think about the dynamic links: if the "Create best practice components" checkbox is disabled, they create components dynamically when you build, and choose the first file in each subfolder as key file.
If you removed one file in a folder that is dynamically linked, the build will not tell you that the file is missing, and your minor upgrade will go through, but some features might then be advertised.
It is a common problem when using dynamic links.
On top of that, the component names are randomly generated at each build when using these dynamic links. Another constraint of a minor upgrade is that you cannot change the name of a component. So, you need to tell InstallShield where your previous MSI package is before building your next release. In the Releases view, click on the media, then on the Build tab, and set the Previous Package.
This is where the upgrade validation wizard comes in handy!
in the menu: Build-->Validate-->Upgrade Validation Wizard...
The rest should be self explanatory.
There are quite a few threads about this problem
- http://community.acresso.com/showthread.php?t=182171
- http://community.acresso.com/showthread.php?t=179854
Note that some of these problems disappear if you set your dynamic links to "Create best practice components", but I am not sure this option is available in IS 2009. It definitely is in IS 2010.
I hope that helps.
Regards
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 01, 2010
02:47 AM
Merci pour votre aide, en effet, j'utilise "Dynamic Files" et 3 fichiers
ont été supprimés par quelqu'un
ont été supprimés par quelqu'un
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 01, 2010
03:53 AM
Il n'y a pas de quoi.
My recommendation: avoid using dynamic links. They are evil.
Regards
My recommendation: avoid using dynamic links. They are evil.
Regards