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: MsiFileHash Keys not Synchronized in Minor 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
‎Apr 23, 2009
06:40 PM
MsiFileHash Keys not Synchronized in Minor Update
I have generated a minor update with InstallShield that contains several folders that use InstallShield's dynamic file linking. They're setup so that there is no KeyPath set in the Component table such that the folder specified in the Directory_ column is the keypath.
During creation of the minor update, everything appears to be properly synchronized between the original and minor update except the MsiFileHash keys with the file table. This includes the File table entries for the dynamic file linking. However, the entries in MsiFileHash do not match anything in and are thus flagged as errors by ICE03.
Has anyone else experienced this or knows what causes it? Unfortunately, I cannot repro it in a small installation. Mine is fairly large and has been upgraded through several versions of InstallShield.
During creation of the minor update, everything appears to be properly synchronized between the original and minor update except the MsiFileHash keys with the file table. This includes the File table entries for the dynamic file linking. However, the entries in MsiFileHash do not match anything in and are thus flagged as errors by ICE03.
Has anyone else experienced this or knows what causes it? Unfortunately, I cannot repro it in a small installation. Mine is fairly large and has been upgraded through several versions of InstallShield.
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 27, 2009
11:43 AM
A hotfix for this issue was previously posted in the following thread:
http://community.installshield.com/showpost.php?p=428612&postcount=8
http://community.installshield.com/showpost.php?p=428612&postcount=8
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 12, 2009
01:18 PM
That does not solve my problem. It simply leaves out the dynamic files from MsiFileHash.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 15, 2009
01:00 PM
The referenced fix addresses the original issue with MsiFileHash invalid foreign keys by walking the _Validation table of the MSI package being built for any foreign key references to the File table's File column and updates all as needed when file keys are synched to a previous package. Even if the _Validation table references were bad, that should leave invalid foreign keys in the MsiFileHash table, not drop them.
Can you provide any additional details or a way to reproduce this behavior?
Can you provide any additional details or a way to reproduce this behavior?