The PatchGroup element is used to ensure that new files get added to the end of
the sequence. That has been able to solve all the sequencing problems people
have brought up in the past so can you be more specific about what files you're
finding are out of sequence?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sandip Shahane
Sent: Wednesday, June 13, 2007 3:47 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] error 1334 on installing a patch.
So, how do I control the file sequencing? PatchGroup attribute seems like
something for files that are newly added by the patch (correct me if wrong). So
here is the scenario and problem I am facing: There is an original MSI with a
File table snap shot for couple of files as below and an updated package that
has some new files, some existing files and some updated files. Also in updated
MSI File table the file sequence is completely different than the RTM one.
Probably because of this I am getting, error 1334 for the below files while
installing a patch. Now, since I am using WIX, I want to know is there any way
I can make sure the file sequence remains same for the files that are not
updated in the new package? Also is there a way to know how and why the
sequence might have changed in the first place?
Any help will be greatly appreciated,
Thanks and Regards,
Sandip
From: Heath Stewart
Sent: Wednesday, June 13, 2007 2:55 PM
To: Sandip Shahane; Carolyn Napier; Windows Installer Support (MS Internal)
Cc: Aaron Gaskill
Subject: RE: error 1334 on installing a patch.
WiX questions need to go to
wix-users@lists.sourceforge.net<mailto:wix-users@lists.sourceforge.net>. See
http://wix.
I will say you should take a look at the wix.chm file for the File element's
PatchGroup attribute.
Heath Stewart
Technical Lead
Deployment Technologies Group, Microsoft
http://blogs.msdn.com/heaths
From: Sandip Shahane
Sent: Wednesday, June 13, 2007 1:18 PM
To: Carolyn Napier; Windows Installer Support (MS Internal)
Cc: Aaron Gaskill
Subject: RE: error 1334 on installing a patch.
I am not sure how to actually control the file sequencing using WIX. Could you
tell what do I need to do to preserve the file sequencing so that the existing
files keep same sequence number and new ones are added at the end of the table
in updated package.
Thanks and Regards,
Sandip
From: Carolyn Napier
Sent: Wednesday, June 13, 2007 11:25 AM
To: Sandip Shahane; Windows Installer Support (MS Internal)
Cc: Aaron Gaskill
Subject: RE: error 1334 on installing a patch.
File sequence numbers should stay the same. WiX authoring has the ability to
help enforce this. Note that the sequence number is especially important when
dealing with cabinets. The sequence number identifies the order of the files
in the cabinets.
According to RTM authoring, Sdk.diagrams.dll comes before Sdk.dll in the
cabinet. However, by your updated MSI authoring, you have now made Sdk.Diagrams
come after Sdk.dll in the cabinet.
With the patch applied, the file won't be found in the cabinet. In particular,
Sdk.Diagrams won't be found because it will have already been bypassed in the
seek for Sdk.dll.
In short, sequence numbers should not change in patches unless the file is
being updated via a full-file update (in which case, the attributes column also
changes).
From: Sandip Shahane [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 13, 2007 10:28 AM
To: Windows Installer Support (MS Internal)
Cc: Aaron Gaskill
Subject: error 1334 on installing a patch.
Hi,
I have created a patch for MOM V3 to SP1 upgrade and while
running the update it gives error 1334 "The file cannot be installed because
the file cannot be found in the cabinet." I applied the patch using orca to
notice few things. The file in question had no changes in the File table other
than the sequence number (there were number of such files.). Some search about
this issue points me that this has something to do with file sequence numbers.
here is how the File tables of two MSIs and MSP looks like:
Original MSI:
F_Microsoft.VisualStudio.Modeling.Sdk.Diagrams.dll.1349CC4A_5003_4833_A142_36725FE46FEA
C_Microsoft.VisualStudio.Modeling.Sdk.Diagrams.dll.1349CC4A_5003_4833_A142_36725FE46FEA
DSLDiag.dll|Microsoft.VisualStudio.Modeling.Sdk.Diagrams.dll
822136 8.1.50727.42 0 0 136
F_Microsoft.VisualStudio.Modeling.Sdk.dll.1349CC4A_5003_4833_A142_36725FE46FEA
C_Microsoft.VisualStudio.Modeling.Sdk.dll.1349CC4A_5003_4833_A142_36725FE46FEA
DSLSDK.dll|Microsoft.VisualStudio.Modeling.Sdk.dll 416632
8.1.50727.42 0 0 138
Updated MSI:
F_Microsoft.VisualStudio.Modeling.Sdk.Diagrams.dll.1349CC4A_5003_4833_A142_36725FE46FEA
C_1
DSLDiag.dll|Microsoft.VisualStudio.Modeling.Sdk.Diagrams.dll 822136
8.1.50727.42 0 0 108
F_Microsoft.VisualStudio.Modeling.Sdk.dll.1349CC4A_5003_4833_A142_36725FE46FEA
C_Microsoft.VisualStudio.Modeling.Sdk.dll.1349CC4A_5003_4833_A142_36725FE46FEA
DSLSDK.dll|Microsoft.VisualStudio.Modeling.Sdk.dll 416632
8.1.50727.42 0 0 106
MSP:
F_Microsoft.VisualStudio.Modeling.Sdk.Diagrams.dll.1349CC4A_5003_4833_A142_36725FE46FEA
C_Microsoft.VisualStudio.Modeling.Sdk.Diagrams.dll.1349CC4A_5003_4833_A142_36725FE46FEA
DSLDiag.dll|Microsoft.VisualStudio.Modeling.Sdk.Diagrams.dll
822136 8.1.50727.42 0 0 108
F_Microsoft.VisualStudio.Modeling.Sdk.dll.1349CC4A_5003_4833_A142_36725FE46FEA
C_Microsoft.VisualStudio.Modeling.Sdk.dll.1349CC4A_5003_4833_A142_36725FE46FEA
DSLSDK.dll|Microsoft.VisualStudio.Modeling.Sdk.dll 416632
8.1.50727.42 0 0 106
Note that the delta shows only sequence number changed (from 136 and 138 to 108
and 106 and hence shown in the MSP also). I have set FileSequence number as 550
in the ImageFamilies of the pcp file and the files having delta on version or
file size in the two MSIs are listed in the patch from that number onwards. But
I noticed that almost all files before this number are also there in the delta
on sequence number only, in the File Table (there is no other change e.g. file
size and version are same in both MSIs).
Is this the reason for the error? if so how do I make sure the sequence numbers
are not changed if they are not supposed to be listed in the patch delta? Or
any other solution to fix this.
Thanks and Regards,
Sandip
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
