12 replies to this topic

[ColSnell]

Some of the patches that I have created won't apply. I get a 'The wizard was interrupted before Profund oPen Client could be completely installed' message just after the update button is clicked.

Some patches seem to work fine and others don't. I've looked up the 1603 error but I don't think that any of those things are happening.

I'm using Windows XP SP2.

The error in the log file :
Action ended 13:01:32: CostFinalize. Return value 3.
MSI © (E8:B0) [13:01:32:781]: Doing action: SetupCompleteError
Action start 13:01:32: SetupCompleteError.
Action 13:01:32: SetupCompleteError. Dialog created
MSI © (E8:DC) [13:01:32:862]: Note: 1: 2731 2: 0
Action ended 13:01:35: SetupCompleteError. Return value 2.
Action ended 13:01:35: INSTALL. Return value 3.
MSI © (E8:B0) [13:01:35:275]: Destroying RemoteAPI object.
MSI © (E8:CC) [13:01:35:285]: Custom Action Manager thread ending.

And the log file ends with :
=== Logging stopped: 21/02/2005 13:01:35 ===
MSI © (E8:B0) [13:01:35:465]: Product: Profund oPen Client - Update '{B454FC57-7903-11D4-B437-0800099A098E}' could not be installed. Error code 1603. Additional information is available in the log file D:\temp\1.5.3202.log.

MSI © (E8:B0) [13:01:35:465]: Note: 1: 1729
MSI © (E8:B0) [13:01:35:505]: Product: Profund oPen Client -- Configuration failed.

MSI © (E8:B0) [13:01:35:505]: Attempting to delete file C:\DOCUME~1\colins\LOCALS~1\Temp\c8bbd6.msp
MSI © (E8:B0) [13:01:35:505]: Unable to delete the file. LastError = 32
MSI © (E8:B0) [13:01:35:515]: Grabbed execution mutex.
MSI © (E8:B0) [13:01:35:515]: Cleaning up uninstalled install packages, if any exist
MSI © (E8:B0) [13:01:35:525]: MainEngineThread is returning 1603
=== Verbose logging stopped: 21/02/2005 13:01:35 ===

The full log file is attached (zipped because it's just over 100k).

Attached Files

•  1.5.3202.zip   16.63KB   228 downloads

[ColSnell]

Sorry, where are my manners!

Any help greatly appreciated as I'm totally stumped by this.

Thanks.

[Stefan Krueger]

2731 = Selection Manager not initialized.
Looks like some custom action or condition is placed too early in the sequence.

Does a repair/reinstall of the existing package (without patch) work properly?

[ColSnell]

I did a repair which seemed to run through okay but the patch still resuses to install.

The thing I don't understand is why this only happens with some patches and not others. The structure of the installer hasn't changed for a long time although we do add new files from time to time. There are certainly no new custom actions.

The problem does not happen on every PC. We have shipped many patches in the last year but I have only had 1 client come back with this problem on 1 PC. I generally test the installs on a clean PC and they work (including this one). It doesn't work on my own PC though.

I've just tried running the full install that the patch is based on and that won;t run either. It comes up with the message 'Another version of this product is already installed. Installation of this version cannot continue. To configure ore remove existing version of this product, use Add/Remove Programs on the Control Panel'. The 2 installers have the same upgrade codes and product codes but the version numbers are different (1.5.3000 and 1.5.3202). Does that sound right? I though this would do a small/minor update?

[Stefan Krueger]

For a minor update you need to launch msiexec with REINSTALLMODE=vomus REINSTALL=ALL

[ColSnell]

Oops, of course you have to do that. The upgrade works fine that way, just not with the patch.

[ColSnell]

Any ideas how to get the patch to work? I can include the msi file that the patch is based on if that will help.

I have to issue the patch rather than the full upgrade which is why I need to understand where this is going wrong. Clients prefer patches, especially as the full install is around 200Mb.

I have no idea how to proceed with this so any pointers on what I can look at will be appreciated.

Thank you.

[Stefan Krueger]

I'm running out of ideas, and analyzing and debugging your actual msi and msp goes beyond what I can do in this forum.

[ColSnell]

I've done a little more investigation and the problem only occurs with XP SP2. I built 2 clean virtual machines, one with plain XP and one with XP SP2. It works fine on the plain XP version but not in the the SP2 version. I can only assume this is something to do with SP2 using Windows Installer 3.

Anyone else had problems with XP SP2 or Windows Installer 3?

[JamieR]

I'm having the same problem at the moment.
CostFinalize is failing and I can't see why.
This only happens when using Windows Installer 3.
I've confirmed this on Win2K and XP

I've attached the log file if anyone would like to have a look at it.

Thanks,

Attached Files

•  log.zip   13.64KB   187 downloads

[SourceList]

[JamieR]

Not sure about that GetInstallDriver bit. I think it just ignores that error.
Plenty of disk space to.

I'm using InstallShield Dev 8 SP2, so yeah that would be pre MSI 3. It might have something to do with it.
I'll look in to that thanks.

[ColSnell]

I build the msi using IS Dev 8 but build the patches using WiX / MSIMSP.exe / patchwiz.dll tools from the Windows Installer SDK.

InstallShield is not on my own PC but the patching software is. My PC is XP SP2 with WI3 but the InstallShield PC still uses WI2.

The patches won't apply on the PC that built them. That said, I still use the 200 database format not the newer WI3 version (300 I presume).

I don't want to / can't force clients to upgrade to WI3. Many of them are on Windows 2000.