Ok, so from my wixmst I get the following in my _SummaryInformation table
<row sectionId="*/*" sourceLineNumber="E:\dev\File.wxs*8">
<field>9</field>
<field>{5E2919A9-F948-4919-A5B1-308BB807A179}5.4.23.4809;{269AF2D8-5BA4-4D2C-9C53-27588F1D1A33}5.4.0.0;{CE1F01CC-4894-497F-A743-07DDA34618E0}</field>
</row>
>From my RTM WixPDB xml I have this in the Property table:
<row sectionId="*.ProductCode"
sourceLineNumber="E:\dev\File.wxs*7">
<field>ProductCode</field>
<field>{5E2919A9-F948-4919-A5B1-308BB807A179}</field>
</row>
I hope I'm going in the right direction. Maybe someone has some insights out
there? :)
-----Original Message-----
From: Tunney, Stephen [mailto:[email protected]]
Sent: June-08-15 3:48 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Patches no longer working for a specific RTM using WiX
3.7 + Pure WiX Patching
I have found an article written by Heath:
http://blogs.msdn.com/b/heaths/archive/2014/04/09/9546739.aspx
Excerpt:
Windows Installer will evaluate each patch against the specified product.
However, if installing the patch or patches using MsiApplyMultiplePatches()
with a specific ProductCode, Windows Installer will modify the PATCH property
to list only the patch packages with the specified ProdutCode in their Template
summary property. If you're not sure which patches apply to a product, this may
be desirable behavior. If you pass in the PATCH property yourself and even one
patch does not apply to the specified ProductCode, Windows Installer will
terminate and return ERROR_PATCH_TARGET_NOT_FOUND (1642).
I'm confused ever so slightly. Now which ProductCode would be in the patch
then? I can't see it in Orca? Would I look in the .wixmst for that detail
after the torch call in my PWP process?
-----Original Message-----
From: Tunney, Stephen [mailto:[email protected]]
Sent: June-08-15 3:45 PM
To: General discussion about the WiX toolset.
Cc: Tuchlinsky, Dave
Subject: Re: [WiX-users] Patches no longer working for a specific RTM using WiX
3.7 + Pure WiX Patching
More details on the patch I'm trying to run
I have set up a clean OS install (fresh from ISO) and am trying to apply the
patch.
I have SysInternals DebugView running and the HKLM Software Policies for
Windows\Installer Debug set to "7" as per:
https://support.symantec.com/en_US/article.HOWTO4103.html
I get the followin in DebugView
[1348] SHIMVIEW: ShimInfo(Complete)
[1348] MSI (c) (44:AC) [19:40:49:510]: Machine policy value 'Debug' is 7 [1348]
[1348] MSI (c) (44:AC) [19:40:49:510]: Entering MsiApplyPatch. Package:
.\MY-HF-244444-CAS.msp, Product: , Installtype: 0, Commandline:
[1348]
[1348] MSI (c) (44:AC) [19:40:49:510]: Machine policy value
'DisableUserInstalls' is 0 [1348] [1348] MSI (c) (44:AC) [19:40:49:510]:
MsiApplyPatch is returning: 1642 [1348]
What else would you guys like to see?
-----Original Message-----
From: Tunney, Stephen [mailto:[email protected]]
Sent: June-08-15 1:19 PM
To: General discussion about the WiX toolset.
Subject: [WiX-users] Patches no longer working for a specific RTM using WiX 3.7
+ Pure WiX Patching
Hello all,
I have run across quite the puzzle last week. We have been generating patches
for several RTM versions of our products since December or 2013 with Pure WiX
patching and 3.7. Just recently (about a week ago) the patch scripts are
generating MSPs for ONE of the versions that do not apply to its RTM. I'm
getting no Windows Installer logs, however Orca is reporting the following when
I try to "View Patch..."
---------------------------
Orca
---------------------------
This patch can not be applied to packages with the current Product Code.
---------------------------
OK
I see the ProductCode in the "Upgrade" MSI is different to that of the PC in
the RTM. Should this matter?
When attempting to apply the patch on a Server OS (2008 R2) I get the following:
Windows Installer
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
difference version of the program. Verify that the program to be upgraded
exists on your computer and that you have the correct upgrade patch.
What else should I be looking at from MSIExec?
I've been working on this for the better part of 5 days and can't figure out
what is going on. I can reproduce the issue on my dev box as well with a
newly built Upgrade MSI.
Thoughts please :(
Stephen
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
