[wix-users] Publisher policy file missing in c:\windows\assembly\tmp folder when adding it through patch.

Sun Oct 13 00:44:30 PDT 2019

Hello folks,

The original msi on which patch should be applied doesn't contains any
policy at all. And policy component is totally new one.
So the file version is not the case as the patch does tries to install dll
which is keypath file of component.
I'm inclined to think that the trouble is that the config file is not key
path.

Moreover this looks like not a trouble of WIX because two installers
(original and with additional policy componet) created using WIX toolset
are working correctly.
But the patch created with MsiMsp.exe doesn't install not keypath file.
Maybe reinstall flag can help, but i can't reinstall all components, it
will breakes all changes done to already installed product. And as i
understood i can't run custom actions to move changes from unpatched
version patched one.

And yes patch way isn't as good as i was thinking about it, and starting
from version 2 we decided not to use it, but we still use it for hot fixes
on version 1. And we decided just to provide tool and instructions on how
to install policy assembly manually.

Thanks alot for help.

Best regards,
Vladimir Kolobkov

On Sun, 13 Oct 2019 at 06:16, Blair Murri via wix-users <
wix-users at lists.wixtoolset.org> wrote:

> Given what I know about patching, I'd guess it's because the
> module(s)/file(s) associated with the assembly weren't (re)installed when
> your patch ran.
>
> My suggestion: try incrementing the "file" version of your module(s)
> before creating your updated MSI/patch. Or, better yet, don't use patching
> to alter the structure of your installations (and yes, this is a structure
> alteration in my opinion).
>
> Blair Murri
>
> Get Outlook for Android<https://aka.ms/ghei36>
> ________________________________
> From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Rob
> Mensching via wix-users <wix-users at lists.wixtoolset.org>
> Sent: Friday, October 11, 2019 6:19:38 AM
> To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> Cc: Rob Mensching <rob at firegiant.com>
> Subject: Re: [wix-users] Publisher policy file missing in
> c:\windows\assembly\tmp folder when adding it through patch.
>
> Yes. See them both.
>
> Short replies here. Complete answers over there: http://www.firegiant.com/
>
> -----Original Message-----
> From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of
> Vladimir Kolobkov via wix-users
> Sent: Friday, October 11, 2019 12:56 AM
> To: wix-users at lists.wixtoolset.org
> Cc: Vladimir Kolobkov <vkolobkov at gmail.com>
> Subject: Re: [wix-users] Publisher policy file missing in
> c:\windows\assembly\tmp folder when adding it through patch.
>
> Dear Group,
>
> I have send message to mail group and didn't get same mail as described in
> subscription configuration which says "*Receive your own posts to the
> list?*"
> by default it is "Yes" and i didn't change it.
> So i'm wondering, did anybody get my message or not?
>
> Best regards,
> Vladimir Kolobkov
>
>
> On Thu, 10 Oct 2019 at 15:58, Vladimir Kolobkov <vkolobkov at gmail.com>
> wrote:
>
> > Hi folks,
> >
> > I have strange behavior while creating the patch with wix 3.11.0.1701.
> > I want to add publisher policy to the already installed application.
> > So i have added 2 new .net assemblies with increased versions and
> > generate policy assembly.
> >
> > Policy assembly was added as new component:
> >       <Component Guid="95297615-6284-40D4-BCC4-88F250F7F6D1"
> > Id="CMP_Policy1_1IcalInvoicesSapDll">
> >         <File KeyPath="yes" Assembly=".net"
> > Id="FILE_Policy1_1IcalInvoicesSapDll"
> > Source="$(var.IpaAssembliesDir)\policy.1.1.ICAL.Invoices.SAP.dll"
> > Name="policy.1.1.ICAL.Invoices.SAP.dll"/>
> >         <File Id="FILE_Policy1_1IcalInvoicesSapConfig"
> > Source="$(var.IpaAssembliesDir)\ICAL.Invoices.SAP.config"
> > CompanionFile="FILE_Policy1_1IcalInvoicesSapDll"
> > Name="ICAL.Invoices.SAP.config"/>
> >       </Component>
> >
> > After that i have created new msi(based on original). But the patch
> > installation fails with an error:
> > 10/10/2019 14:55:46.627 [7172]: Assembly Install: Failing with
> > hr=80131042 at CAssemblyCacheItem::LegacyCommit, line 1360
> >
> > MSI (s) (04:10) [14:55:46:633]: Assembly Error:A module specified in
> > the manifest of assembly '%1' could not be found.
> > MSI (s) (04:10) [14:55:46:633]: Note: 1: 1938 2:
> > {95297615-6284-40D4-BCC4-88F250F7F6D1} 3: 0x80131042 4:
> > IAssemblyCacheItem
> > 5: Commit 6:
> >
> policy.1.1.ICAL.Invoices.SAP,version="0.0.0.0",culture="neutral",publicKeyToken="0A00A7449EA4C480",processorArchitecture="MSIL"
> >
> > MSI (c) (2C:48) [14:55:46:634]: Transforming table Binary.
> >
> > MSI (c) (2C:48) [14:55:46:634]: Transforming table Binary.
> >
> > MSI (c) (2C:48) [14:55:46:634]: Note: 1: 2262 2: Binary 3: -2147287038
> > Error 1938. An error occurred during the installation of assembly
> >
> 'policy.1.1.ICAL.Invoices.SAP,version="0.0.0.0",culture="neutral",publicKeyToken="0A00A7449EA4C480",processorArchitecture="MSIL"'.
> > One or more modules of the assembly could not be found. HRESULT:
> > 0x80131042. assembly interface: IAssemblyCacheItem, function: Commit,
> > component: {95297615-6284-40D4-BCC4-88F250F7F6D1}
> > MSI (s) (04:10) [14:55:54:475]: Product: Kofax Invoice Processing
> > Agility
> > 1.1 -- Error 1938. An error occurred during the installation of
> > assembly
> 'policy.1.1.ICAL.Invoices.SAP,version="0.0.0.0",culture="neutral",publicKeyToken="0A00A7449EA4C480",processorArchitecture="MSIL"'.
> > One or more modules of the assembly could not be found. HRESULT:
> > 0x80131042. assembly interface: IAssemblyCacheItem, function: Commit,
> > component: {95297615-6284-40D4-BCC4-88F250F7F6D1}
> >
> > 10/10/2019 14:55:54.477 [7172]: Assembly Install: Failing with
> > hr=80070005 at RemoveDirectoryAndChildren, line 393
> >
> > 10/10/2019 14:55:54.478 [7172]: Detailed info about
> > C:\Windows\assembly\tmp\X36OJITA\policy.1.1.ICAL.Invoices.SAP.dll
> >
> > 10/10/2019 14:55:54.478 [7172]: File attributes: 00000080
> >
> > 10/10/2019 14:55:54.523 [7172]: Restart Manager Info: 1 entries
> >
> > 10/10/2019 14:55:54.523 [7172]: App[0]: (7172) Windows Installer
> > (msiserver), type = 3
> >
> > 10/10/2019 14:55:54.523 [7172]: Security info:
> >
> > 10/10/2019 14:55:54.524 [7172]: Owner: S-1-5-18
> >
> > 10/10/2019 14:55:54.524 [7172]: Group: S-1-5-18
> >
> > 10/10/2019 14:55:54.524 [7172]: DACL information: 4 entries:
> >
> > 10/10/2019 14:55:54.524 [7172]: ACE[0]: Type = 0x00, Flags = 010, Mask
> > = 001f01ff, SID = S-1-5-18
> >
> > 10/10/2019 14:55:54.525 [7172]: ACE[1]: Type = 0x00, Flags = 010, Mask
> > = 001f01ff, SID = S-1-5-32-544
> >
> > 10/10/2019 14:55:54.525 [7172]: ACE[2]: Type = 0x00, Flags = 010, Mask
> > = 001200a9, SID = S-1-5-32-545
> >
> > 10/10/2019 14:55:54.525 [7172]: ACE[3]: Type = 0x00, Flags = 010, Mask
> > = 001200a9, SID = S-1-15-2-1
> >
> > Action ended 14:55:54: InstallFinalize. Return value 3.
> >
> > I have checked the c:\windows\assembly\tmp folder and there was no
> > config file for policy assembly.
> > Meanwhile the installer which was used to create patch installs policy
> > without any errors.
> > Does anybody knows how i can achive policy into GAC through patch.
> >
> > Best regards,
> > Vladimir Kolobkov
> >
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>