Is this something you can share for debugging purposes?

From: Matt Ziegler [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2008 12:42 PM
To: Windows Installer XML toolset developer mailing list
Subject: Re: [WiX-devs] Multiple instance patches

I was hoping to use the pure WiX patches routine as well as try to be able to 
change a patch's target on the command line, but I'll settle to get it working 
in the first place and then I'll go from there :).

I did create a patch using the <TargetProductCode /> element using MsiMsp.exe.  
The patch now runs and patches the base installation just fine but when it goes 
to patch the second instance I get a 1642 error.  The output from the log file 
is below (one finally generated).

Any help is greatly appreciated.

Thanks

Matt

MSI (c) (F0:44) [10:32:38:195]: Original package ==> 
C:\WINDOWS\Installer\16f38b31.msi
MSI (c) (F0:44) [10:32:38:195]: Package we're running from ==> 
C:\WINDOWS\Installer\16f38b31.msi
MSI (c) (F0:44) [10:32:38:195]: APPCOMPAT: looking for appcompat database entry 
with ProductCode '{48F7E3D3-4291-45B0-AA5E-8A78337D95FF}'.
MSI (c) (F0:44) [10:32:38:195]: APPCOMPAT: no matching ProductCode found in 
database.
MSI (c) (F0:44) [10:32:38:195]: Detected that this product uses a multiple 
instance transform.
MSI (c) (F0:44) [10:32:38:195]: MSCOREE not loaded loading copy from system32
MSI (c) (F0:44) [10:32:38:195]: Applying multiple instance transform 
':Instance2'...
MSI (c) (F0:44) [10:32:38:195]: Looking for storage transform: Instance2
<snip />
MSI (c) (F0:44) [10:32:38:195]: Original patch ==> 
C:\practice_partner\Installers\SiteInstaller\Patch testing\small test\patch.msp
MSI (c) (F0:44) [10:32:38:195]: Patch we're running from ==> 
C:\DOCUME~1\mziegler\LOCALS~1\Temp\459eb18.msp
MSI (c) (F0:44) [10:32:38:211]: Opening existing patch 
'C:\WINDOWS\Installer\44b1e86.msp'.
MSI (c) (F0:44) [10:32:38:211]: SequencePatches starts. Product code: 
{48F7E3D3-4291-45B0-AA5E-8A78337D95FF}, Product version: 1.0.1, Upgrade code: 
{D3B1F084-3B3E-4C8D-8017-A3BD418D31E1}, Product language 1033
MSI (c) (F0:44) [10:32:38:211]: PATCH SEQUENCER: verifying the applicability of 
minor upgrade patch C:\practice_partner\Installers\SiteInstaller\Patch 
testing\small test\patch.msp against product code: 
{48F7E3D3-4291-45B0-AA5E-8A78337D95FF}, product version: 1.0.1, product 
language 1033 and upgrade code: {D3B1F084-3B3E-4C8D-8017-A3BD418D31E1}
MSI (c) (F0:44) [10:32:38:211]: PATCH SEQUENCER: minor upgrade patch 
C:\practice_partner\Installers\SiteInstaller\Patch testing\small test\patch.msp 
is not applicable.
MSI (c) (F0:44) [10:32:38:211]: SequencePatches returns success.
MSI (c) (F0:44) [10:32:38:211]: Final Patch Application Order:
MSI (c) (F0:44) [10:32:38:211]: Other Patches:
MSI (c) (F0:44) [10:32:38:211]: Unknown\Absent: 
{0148E385-C0F9-4C51-846B-A6B393868862} - 
C:\practice_partner\Installers\SiteInstaller\Patch testing\small test\patch.msp
The upgrade patch cannot be installed by the Windows Installer service because 
the program to be upgraded may be missing, or the upgrade patch may update a 
different version of the program. Verify that the program to be upgraded exists 
on your computer an
d that you have the correct upgrade patch.
C:\WINDOWS\Installer\16f38b31.msi
MSI (c) (F0:44) [10:32:38:211]: Product: WiX Patch Example Product 2 - Update 
'{0148E385-C0F9-4C51-846B-A6B393868862}' could not be installed. Error code 
1642. Additional information is available in the log file 
C:\practice_partner\Installers\SiteInstaller\Patch testing\small 
test\patch2.log.

MSI (c) (F0:44) [10:32:38:211]: Windows Installer installed an update. Product 
Name: WiX Patch Example Product 2. Product Version: 1.0.1.<http://1.0.1.> 
Product Language: 1033. Update Name: {0148E385-C0F9-4C51-846B-A6B393868862}. 
Installation success or error status: 1642.

MSI (c) (F0:44) [10:32:38:211]: Note: 1: 1708
MSI (c) (F0:44) [10:32:38:211]: Product: WiX Patch Example Product 2 -- 
Installation failed.

MSI (c) (F0:44) [10:32:38:211]: Windows Installer installed the product. 
Product Name: WiX Patch Example Product 2. Product Version: 
1.0.1.<http://1.0.1.> Product Language: 1033. Installation success or error 
status: 1642.
On Thu, Nov 20, 2008 at 3:04 PM, John Nannenga <[EMAIL PROTECTED]<mailto:[EMAIL 
PROTECTED]>> wrote:

In your patch generation you need to target the patch for all the product codes 
[instances] you want it to be applicable to.



<TargetProductCode Id="PRODUCT_CODE_GUID"/>

<TargetProductCode Id="PRODUCT_CODE_GUID_INSTANCE1"/>

<TargetProductCode Id="PRODUCT_CODE_GUID_INSTANCE2"/>



Etc...











From: Matt Ziegler [mailto:[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>]
Sent: Thursday, November 20, 2008 3:50 PM
To: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>; 
[email protected]<mailto:[email protected]>
Subject: Re: [WiX-devs] Multiple instance patches



Any insight from anyone?

On Wed, Nov 19, 2008 at 2:58 PM, Matt Ziegler <[EMAIL PROTECTED]<mailto:[EMAIL 
PROTECTED]>> wrote:

I've been playing around with installing multiple instances of an application 
used the <InstanceTransforms /> element, works quite well.  I'm trying to 
create a patch between 2 versions and apply that one patch to multiple 
installed instances and according to 
http://msdn.microsoft.com/en-us/library/aa369528(VS.85).aspx<http://msdn.microsoft.com/en-us/library/aa369528%28VS.85%29.aspx>
 it is possible to do this by running the patch from the command line and 
passing in the product id of the installed instance you want to patch.  I have 
yet to be able to get a patch to install to a second instance correctly, 
installing to the base instances works just fine.  The error message I get is:

"The upgrade patch cannot be installed by the Windows Installer service because 
the program to be upgraded may be missing, or the upgrade patch may update a 
different version of the program."

The command line executed is: msiexec /update 1to2.msp /n 
{48F7E3D3-4291-45b0-AA5E-8A78337D95FF}
There is no log created even with /l*v

I included a <Validate /> element wondering if there was some check with the 
different product code for the patch that was holding back, no joy.
<PatchBaseline Id="RTM">
        <Validate ProductId="no" UpgradeCode="no" ProductVersion="Major" 
ProductVersionOperator="GreaterOrEqual"/>
</PatchBaseline>

Any help or insight would be greatly appreciated.

Thanks

Matt



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-devs mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/wix-devs

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs

Reply via email to