RE: [WiX-users] "...file versioning rules would disable the component"

[Ross A. <ran...@cr...>]

Thanks for the quick answer, Chris.  Unfortunately, no =E2=80=93 the =
Attributes column for the file is 0.  The file is a sql server .mdf =
file.  So it doesn=E2=80=99t contain any checksum or versioning =
information (as far as windows installer should be concerned).  If I =
cause a reinstall before the file is modified, I get the following =
output:

=20

Disallowing installation of component: =
{846A216C-4DD7-4B6E-A1B5-1B7A222D6071} since the same component with =
higher versioned keyfile exists

=20

After the file is modified, I get the output I posted below.

=20

Scanning the log file, other than the REINSTALLMODE property, I =
couldn=E2=80=99t find anything else that suggested why this might be =
happening.  Very confusing.

=20

Ross

=20

From: Christopher Painter [mailto:ch...@ya...]=20
Sent: Thursday, June 01, 2006 9:54 AM
To: Ross Anderson; wix...@li...
Subject: Re: [WiX-users] "...file versioning rules would disable the =
component"

=20

You said pocmus.  C is:

Verify the checksum values, and reinstall the file if they are missing =
or corrupt. This flag only repairs files that have =
msidbFileAttributesChecksum in the Attributes column of the File Table.

So I'm guessing you have the msidbFileAttributesChecksum attribute set =
for your key file, so even though the file is modified and default file =
versioing rule of omus would disallow the component the C tells it to =
respect that the hash is incorrect and reinstall it.

Just a quick guess...

Chris

Ross Anderson <ran...@cr...> wrote:

Hi,

=20

Apologies if this is more msi than wix, but this group is a lot more =
active than platformsdk.msi, and people seem to get away with asking a =
few non-wix specific questions here=C3=A2=E2=82=AC=C2=A6

=20

I have a question about a reinstall triggered by an advertised shortcut. =
 Looking at the log file, the reinstall is triggered with =
REINSTALLMODE=3Dpocmus.

=20

One of the components in my package has an unversioned file as the =
keyfile.  During the reinstall, the following line is output to the log:

=20

Allowing installation of component: =
{846A216C-4DD7-4B6E-A1B5-1B7A222D6071} even though a modified =
unversioned keyfile exists and file versioning rules would disable the =
component

=20

I do not want the file to be reinstalled if the file already on the =
system is modified - I want the installer to follow the versioning =
rules.  Why is it choosing NOT to follow them?  Google =
didn=C3=A2=E2=82=AC=E2=84=A2t turn up anything of interest, and the msi =
documentation didn=C3=A2=E2=82=AC=E2=84=A2t clear it up for me either.

=20

Thanks!

=20

Ross=20

=20

=20

  _____ =20

How low will we go? Check out Yahoo! Messenger=E2=80=99s low PC-to-Phone =
<http://us.rd.yahoo.com/mail_us/taglines/postman8/*http:/us.rd.yahoo.com/=
evt=3D39663/*http:/voice.yahoo.com>  call rates.