6 replies to this topic

[Al Robinson]

I was wondering if anyone had witnessed this behaviour, or worked round it. It's causing me some confusion.
We have a current release, which we then released a patch for. This first patch updated files a, b and c.
We are now develping a second patch, which should accumulate the first but also update files x, y and z.

However when we apply the second patch onto the original release only files x, y and z are updated.

The patch creation log indicates that it has picked up the updates to files a, b and c.

I have double checked that the reference msi file is correct. We have been building patches using the same mechanism in several past releases succesfully. The only change I can see is that we are now including whole files rather than binary difference (this was on the advice of InstallShield support).

(Sorry about the double posting, I got a 'mail error' and hit 'retry' which seems to have posted twice)

Edited by Al Robinson, 04 October 2007 - 14:41.

[Stefan Krueger]

Did you increment the ProductVersion between the relases?

[Al Robinson]

Hi,

Yes, it is incremented for every release/patch release.

[Stefan Krueger]

Maybe a log can help to identify the problem. But it might as well be related to this being a "installScript MSI" project.

[Al Robinson]

I have had a look at the log, but I cannot see anything relevant to this problem. The part of the log referencing the files to be replaced only has reference to files x, y and z and not a, b, and c.

We are moving to basic msi projects for our next release as we are sick of the complications that seem to arise from using InstallScript/MSI.
How possible is it that it may be a problem from using this project type?

Unfortunately I still have to deal with this type of project for patching our previous releases.

[Al Robinson]

More info.
I had another look at the log, specifically for two files that were added as part of the first patch, and should be in the second. They are referenced only once, which means the msp must know about them. The log is below, the files in question are moduledatacheck.txt, and moduledatacheck.inc

MSI © (F4:24) [13:54:50:479]: Note: 1: 2205 2: 3: Patch
MSI © (F4:24) [13:54:50:479]: Note: 1: 2228 2: 3: Patch 4: CREATE TABLE `Patch` ( `File_` CHAR(72) NOT NULL, `Sequence` INTEGER NOT NULL, `PatchSize` LONG NOT NULL, `Attributes` INTEGER NOT NULL, `Header` OBJECT, `StreamRef_` CHAR(72) PRIMARY KEY `File_`, `Sequence` )
MSI © (F4:24) [13:54:50:479]: Note: 1: 2262 2: Patch 3: -2147287038
MSI © (F4:24) [13:54:50:479]: Note: 1: 2715 2: moduledatacheck.txt
MSI © (F4:24) [13:54:50:479]: Note: 1: 2715 2: moduledatacheck.inc
MSI © (F4:24) [13:54:50:479]: Note: 1: 2262 2: PatchPackage 3: -2147287038
MSI © (F4:24) [13:54:50:479]: TRANSFORM: 'PatchPackage' table is missing or empty. No pre-transform fixup necessary.
MSI © (F4:24) [13:54:50:479]: TRANSFORM: Applying regular transform to database.

[Stefan Krueger]

2715: The specified File key ('[2]') not found in the File table.
and:
'PatchPackage' table is missing or empty

Maybe the previous patch didn't install properly?