[WiX-users] bootstrapping .net 451 with burn doesn't show progress messages
Hi, I am trying to install .NET 4.5.1 as a prerequisite to our Wix bootstrapper, and we don't see any messages about the packages installed (e.x KB, VC runtime etc). It just shows Installing dot net 4.5.1 . Can someone help me outline the steps required to get the status messages in Bootstrapper standard UI. I get the progress but not the status messages. (Like Applying patch x...) I call the .NET installer from wix with Protocol=netfx4. More details: When i checked the command line, it has some parameter like "slash pipe NetFx.someguid". But when i used the pipelist utility , it didn't show any pipe created with the name mentioned. I have basically two questions. 1. Is the messages being piped at all ? 2. Is there an UI element i miss that when added to my UI will show messages. Thanks Soundararajan P.S . This is the same problem when i install isolated shell 2013 with Protocol=burn -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
In my case, my CA dll is built as AnyCPU. So it seems I need to build it separately for x86 and x64. I will try that. Thanks! -Original Message- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: Friday, November 14, 2014 10:38 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage and by "will be built with the caller's architecture" I mean "JIT compiled to the caller's architecture" because this is happening at run time. --- Phil Wilson On Fri, Nov 14, 2014 at 10:29 AM, Phil Wilson wrote: > Just to add something that may be the issue with your setup. The call > stack is driven by the architecture of the starting process or Dll, so > if you have a 32-bit CA Dll then msiexec will be a 32-bit process to > call it. Your Dll then calls other Dlls. and If all these other Dlls > are AnyCpu then yes, they will "work" in the sense that you said they > can run on any architecture and so will be built with the callers > architecture, so you'll get a 32-bit Dll call stack on a 64-bit > system. That all works fine until it doesn't because it needs to do > something in the 64-bit world, such as look inside a 64-bit process. > --- > Phil Wilson > > > On Fri, Nov 14, 2014 at 10:10 AM, Phil Wilson wrote: >> Yes something is checking the platform setting. Your comment is >> otherwise too vague. Since you need separate setups for 32-bit and >> 64-bit systems it's often best to make sure that all the code that >> runs during the install is of the appropriate bitness. You don't want >> a 32-bit (64-bit) hosting process or Dll trying to call a 64-bit >> (32-bit) Dll or some other invalid cross architecture thing. >> --- >> Phil Wilson >> >> >> On Fri, Nov 14, 2014 at 9:42 AM, Asbjørn Mikkelsen >> wrote: >>> So something is checking the platform setting on the dll ?, With >>> VS2012 and VS2013, I'm getting problems if I start to set platform >>> to anything else than anycpu on dll's now, what gives? >>> >>> On Fri, Nov 14, 2014 at 6:38 PM, Phil Wilson wrote: >>> To expand on what Rob said, it all just works. On an x64 system the MSI service will be 64-bit. If you have a 32-bit CA you'll get a 32-bit msiexec process launched to host it. If you have another CA that requires impersonation, you'll see another msiexec process running impersonated. The error you're seeing is nothing to do with the with this architecture. It's just invalid for a 32-bit process to access 64-bit modules. You are enumerating processes or you have a process id that's 64-bit and you're using it from 32-bit code to access the process? As Jacob says, if you're on a 64-bit system and you want to do whatever you're doing, make a 64-bit version of your Dll. --- Phil Wilson On Fri, Nov 14, 2014 at 8:35 AM, John Cooper wrote: > That is the technique I use and it is necessary when access > 64-bit-only file system locations and the like. > > -- > John Merryweather Cooper > Senior Software Engineer | Enterprise Service Applications | > Continuing Development > Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 > | jocoo...@jackhenry.com > > > > -Original Message- > From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] > Sent: Friday, November 14, 2014 10:32 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit > msiexec.exe for a 64-bit MsiPackage > > What is the bitness of your CA DLL? Just a stab in the dark but > you might need to have it compiled twice, once as 32 and once as 64, and have the respective MSI package use the right CA DLL. > > > -Original Message- > From: Rob Mensching [mailto:r...@firegiant.com] > Sent: Friday, November 14, 2014 9:53 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit > msiexec.exe for a 64-bit MsiPackage > > Custom actions are hosted by Windows Installer in a separate > custom action host process based on custom action type. > > _ > Short replies here. Complete answers over there: http://www.firegiant.com/ > > > -Original Message- > From: Ryan Waller [mailto:rwal...@microsoft.com] > Sent: Friday, November 14, 2014 7:43 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit > msiexec.exe for a 64-bit MsiPackage > > Yes, Orca Summary shows it with Platform x64. > > ---
Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
and by "will be built with the caller's architecture" I mean "JIT compiled to the caller's architecture" because this is happening at run time. --- Phil Wilson On Fri, Nov 14, 2014 at 10:29 AM, Phil Wilson wrote: > Just to add something that may be the issue with your setup. The call > stack is driven by the architecture of the starting process or Dll, so > if you have a 32-bit CA Dll then msiexec will be a 32-bit process to > call it. Your Dll then calls other Dlls. and If all these other Dlls > are AnyCpu then yes, they will "work" in the sense that you said they > can run on any architecture and so will be built with the callers > architecture, so you'll get a 32-bit Dll call stack on a 64-bit > system. That all works fine until it doesn't because it needs to do > something in the 64-bit world, such as look inside a 64-bit process. > --- > Phil Wilson > > > On Fri, Nov 14, 2014 at 10:10 AM, Phil Wilson wrote: >> Yes something is checking the platform setting. Your comment is >> otherwise too vague. Since you need separate setups for 32-bit and >> 64-bit systems it's often best to make sure that all the code that >> runs during the install is of the appropriate bitness. You don't want >> a 32-bit (64-bit) hosting process or Dll trying to call a 64-bit >> (32-bit) Dll or some other invalid cross architecture thing. >> --- >> Phil Wilson >> >> >> On Fri, Nov 14, 2014 at 9:42 AM, Asbjørn Mikkelsen >> wrote: >>> So something is checking the platform setting on the dll ?, With VS2012 and >>> VS2013, I'm getting problems if I start to set platform to anything else >>> than anycpu on dll's now, what gives? >>> >>> On Fri, Nov 14, 2014 at 6:38 PM, Phil Wilson wrote: >>> To expand on what Rob said, it all just works. On an x64 system the MSI service will be 64-bit. If you have a 32-bit CA you'll get a 32-bit msiexec process launched to host it. If you have another CA that requires impersonation, you'll see another msiexec process running impersonated. The error you're seeing is nothing to do with the with this architecture. It's just invalid for a 32-bit process to access 64-bit modules. You are enumerating processes or you have a process id that's 64-bit and you're using it from 32-bit code to access the process? As Jacob says, if you're on a 64-bit system and you want to do whatever you're doing, make a 64-bit version of your Dll. --- Phil Wilson On Fri, Nov 14, 2014 at 8:35 AM, John Cooper wrote: > That is the technique I use and it is necessary when access 64-bit-only file system locations and the like. > > -- > John Merryweather Cooper > Senior Software Engineer | Enterprise Service Applications | Continuing Development > Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 | jocoo...@jackhenry.com > > > > -Original Message- > From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] > Sent: Friday, November 14, 2014 10:32 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage > > What is the bitness of your CA DLL? Just a stab in the dark but you might need to have it compiled twice, once as 32 and once as 64, and have the respective MSI package use the right CA DLL. > > > -Original Message- > From: Rob Mensching [mailto:r...@firegiant.com] > Sent: Friday, November 14, 2014 9:53 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage > > Custom actions are hosted by Windows Installer in a separate custom action host process based on custom action type. > > _ > Short replies here. Complete answers over there: http://www.firegiant.com/ > > > -Original Message- > From: Ryan Waller [mailto:rwal...@microsoft.com] > Sent: Friday, November 14, 2014 7:43 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage > > Yes, Orca Summary shows it with Platform x64. > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users
Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
Just to add something that may be the issue with your setup. The call stack is driven by the architecture of the starting process or Dll, so if you have a 32-bit CA Dll then msiexec will be a 32-bit process to call it. Your Dll then calls other Dlls. and If all these other Dlls are AnyCpu then yes, they will "work" in the sense that you said they can run on any architecture and so will be built with the callers architecture, so you'll get a 32-bit Dll call stack on a 64-bit system. That all works fine until it doesn't because it needs to do something in the 64-bit world, such as look inside a 64-bit process. --- Phil Wilson On Fri, Nov 14, 2014 at 10:10 AM, Phil Wilson wrote: > Yes something is checking the platform setting. Your comment is > otherwise too vague. Since you need separate setups for 32-bit and > 64-bit systems it's often best to make sure that all the code that > runs during the install is of the appropriate bitness. You don't want > a 32-bit (64-bit) hosting process or Dll trying to call a 64-bit > (32-bit) Dll or some other invalid cross architecture thing. > --- > Phil Wilson > > > On Fri, Nov 14, 2014 at 9:42 AM, Asbjørn Mikkelsen > wrote: >> So something is checking the platform setting on the dll ?, With VS2012 and >> VS2013, I'm getting problems if I start to set platform to anything else >> than anycpu on dll's now, what gives? >> >> On Fri, Nov 14, 2014 at 6:38 PM, Phil Wilson wrote: >> >>> To expand on what Rob said, it all just works. On an x64 system the >>> MSI service will be 64-bit. If you have a 32-bit CA you'll get a >>> 32-bit msiexec process launched to host it. If you have another CA >>> that requires impersonation, you'll see another msiexec process >>> running impersonated. The error you're seeing is nothing to do with >>> the with this architecture. It's just invalid for a 32-bit process to >>> access 64-bit modules. You are enumerating processes or you have a >>> process id that's 64-bit and you're using it from 32-bit code to >>> access the process? As Jacob says, if you're on a 64-bit system and >>> you want to do whatever you're doing, make a 64-bit version of your >>> Dll. >>> --- >>> Phil Wilson >>> >>> >>> On Fri, Nov 14, 2014 at 8:35 AM, John Cooper >>> wrote: >>> > That is the technique I use and it is necessary when access 64-bit-only >>> file system locations and the like. >>> > >>> > -- >>> > John Merryweather Cooper >>> > Senior Software Engineer | Enterprise Service Applications | Continuing >>> Development >>> > Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 | >>> jocoo...@jackhenry.com >>> > >>> > >>> > >>> > -Original Message- >>> > From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] >>> > Sent: Friday, November 14, 2014 10:32 AM >>> > To: General discussion about the WiX toolset. >>> > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe >>> for a 64-bit MsiPackage >>> > >>> > What is the bitness of your CA DLL? Just a stab in the dark but you >>> might need to have it compiled twice, once as 32 and once as 64, and have >>> the respective MSI package use the right CA DLL. >>> > >>> > >>> > -Original Message- >>> > From: Rob Mensching [mailto:r...@firegiant.com] >>> > Sent: Friday, November 14, 2014 9:53 AM >>> > To: General discussion about the WiX toolset. >>> > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe >>> for a 64-bit MsiPackage >>> > >>> > Custom actions are hosted by Windows Installer in a separate custom >>> action host process based on custom action type. >>> > >>> > _ >>> > Short replies here. Complete answers over there: >>> http://www.firegiant.com/ >>> > >>> > >>> > -Original Message- >>> > From: Ryan Waller [mailto:rwal...@microsoft.com] >>> > Sent: Friday, November 14, 2014 7:43 AM >>> > To: General discussion about the WiX toolset. >>> > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe >>> for a 64-bit MsiPackage >>> > >>> > Yes, Orca Summary shows it with Platform x64. >>> > >>> > >>> -- >>> > Comprehensive Server Monitoring with Site24x7. >>> > Monitor 10 servers for $9/Month. >>> > Get alerted through email, SMS, voice calls or mobile push notifications. >>> > Take corrective actions from your mobile device. >>> > >>> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >>> > ___ >>> > WiX-users mailing list >>> > WiX-users@lists.sourceforge.net >>> > https://lists.sourceforge.net/lists/listinfo/wix-users >>> > >>> > >>> -- >>> > Comprehensive Server Monitoring with Site24x7. >>> > Monitor 10 servers for $9/Month. >>> > Get alerted through email, SMS, voice calls or mobile push notifications. >>>
Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
Yes something is checking the platform setting. Your comment is otherwise too vague. Since you need separate setups for 32-bit and 64-bit systems it's often best to make sure that all the code that runs during the install is of the appropriate bitness. You don't want a 32-bit (64-bit) hosting process or Dll trying to call a 64-bit (32-bit) Dll or some other invalid cross architecture thing. --- Phil Wilson On Fri, Nov 14, 2014 at 9:42 AM, Asbjørn Mikkelsen wrote: > So something is checking the platform setting on the dll ?, With VS2012 and > VS2013, I'm getting problems if I start to set platform to anything else > than anycpu on dll's now, what gives? > > On Fri, Nov 14, 2014 at 6:38 PM, Phil Wilson wrote: > >> To expand on what Rob said, it all just works. On an x64 system the >> MSI service will be 64-bit. If you have a 32-bit CA you'll get a >> 32-bit msiexec process launched to host it. If you have another CA >> that requires impersonation, you'll see another msiexec process >> running impersonated. The error you're seeing is nothing to do with >> the with this architecture. It's just invalid for a 32-bit process to >> access 64-bit modules. You are enumerating processes or you have a >> process id that's 64-bit and you're using it from 32-bit code to >> access the process? As Jacob says, if you're on a 64-bit system and >> you want to do whatever you're doing, make a 64-bit version of your >> Dll. >> --- >> Phil Wilson >> >> >> On Fri, Nov 14, 2014 at 8:35 AM, John Cooper >> wrote: >> > That is the technique I use and it is necessary when access 64-bit-only >> file system locations and the like. >> > >> > -- >> > John Merryweather Cooper >> > Senior Software Engineer | Enterprise Service Applications | Continuing >> Development >> > Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 | >> jocoo...@jackhenry.com >> > >> > >> > >> > -Original Message- >> > From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] >> > Sent: Friday, November 14, 2014 10:32 AM >> > To: General discussion about the WiX toolset. >> > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe >> for a 64-bit MsiPackage >> > >> > What is the bitness of your CA DLL? Just a stab in the dark but you >> might need to have it compiled twice, once as 32 and once as 64, and have >> the respective MSI package use the right CA DLL. >> > >> > >> > -Original Message- >> > From: Rob Mensching [mailto:r...@firegiant.com] >> > Sent: Friday, November 14, 2014 9:53 AM >> > To: General discussion about the WiX toolset. >> > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe >> for a 64-bit MsiPackage >> > >> > Custom actions are hosted by Windows Installer in a separate custom >> action host process based on custom action type. >> > >> > _ >> > Short replies here. Complete answers over there: >> http://www.firegiant.com/ >> > >> > >> > -Original Message- >> > From: Ryan Waller [mailto:rwal...@microsoft.com] >> > Sent: Friday, November 14, 2014 7:43 AM >> > To: General discussion about the WiX toolset. >> > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe >> for a 64-bit MsiPackage >> > >> > Yes, Orca Summary shows it with Platform x64. >> > >> > >> -- >> > Comprehensive Server Monitoring with Site24x7. >> > Monitor 10 servers for $9/Month. >> > Get alerted through email, SMS, voice calls or mobile push notifications. >> > Take corrective actions from your mobile device. >> > >> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >> > ___ >> > WiX-users mailing list >> > WiX-users@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/wix-users >> > >> > >> -- >> > Comprehensive Server Monitoring with Site24x7. >> > Monitor 10 servers for $9/Month. >> > Get alerted through email, SMS, voice calls or mobile push notifications. >> > Take corrective actions from your mobile device. >> > >> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >> > ___ >> > WiX-users mailing list >> > WiX-users@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/wix-users >> > NOTICE: This electronic mail message and any files transmitted with it >> are intended >> > exclusively for the individual or entity to which it is addressed. The >> message, >> > together with any attachment, may contain confidential and/or privileged >> information. >> > Any unauthorized review, use, printing, saving, copying, disclosure or >> distribution >> > is strictly prohibited. If you have received this message in error, >> please >> > immediately advise the sender by reply emai
Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
So something is checking the platform setting on the dll ?, With VS2012 and VS2013, I'm getting problems if I start to set platform to anything else than anycpu on dll's now, what gives? On Fri, Nov 14, 2014 at 6:38 PM, Phil Wilson wrote: > To expand on what Rob said, it all just works. On an x64 system the > MSI service will be 64-bit. If you have a 32-bit CA you'll get a > 32-bit msiexec process launched to host it. If you have another CA > that requires impersonation, you'll see another msiexec process > running impersonated. The error you're seeing is nothing to do with > the with this architecture. It's just invalid for a 32-bit process to > access 64-bit modules. You are enumerating processes or you have a > process id that's 64-bit and you're using it from 32-bit code to > access the process? As Jacob says, if you're on a 64-bit system and > you want to do whatever you're doing, make a 64-bit version of your > Dll. > --- > Phil Wilson > > > On Fri, Nov 14, 2014 at 8:35 AM, John Cooper > wrote: > > That is the technique I use and it is necessary when access 64-bit-only > file system locations and the like. > > > > -- > > John Merryweather Cooper > > Senior Software Engineer | Enterprise Service Applications | Continuing > Development > > Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 | > jocoo...@jackhenry.com > > > > > > > > -Original Message- > > From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] > > Sent: Friday, November 14, 2014 10:32 AM > > To: General discussion about the WiX toolset. > > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe > for a 64-bit MsiPackage > > > > What is the bitness of your CA DLL? Just a stab in the dark but you > might need to have it compiled twice, once as 32 and once as 64, and have > the respective MSI package use the right CA DLL. > > > > > > -Original Message- > > From: Rob Mensching [mailto:r...@firegiant.com] > > Sent: Friday, November 14, 2014 9:53 AM > > To: General discussion about the WiX toolset. > > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe > for a 64-bit MsiPackage > > > > Custom actions are hosted by Windows Installer in a separate custom > action host process based on custom action type. > > > > _ > > Short replies here. Complete answers over there: > http://www.firegiant.com/ > > > > > > -Original Message- > > From: Ryan Waller [mailto:rwal...@microsoft.com] > > Sent: Friday, November 14, 2014 7:43 AM > > To: General discussion about the WiX toolset. > > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe > for a 64-bit MsiPackage > > > > Yes, Orca Summary shows it with Platform x64. > > > > > -- > > Comprehensive Server Monitoring with Site24x7. > > Monitor 10 servers for $9/Month. > > Get alerted through email, SMS, voice calls or mobile push notifications. > > Take corrective actions from your mobile device. > > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > -- > > Comprehensive Server Monitoring with Site24x7. > > Monitor 10 servers for $9/Month. > > Get alerted through email, SMS, voice calls or mobile push notifications. > > Take corrective actions from your mobile device. > > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > NOTICE: This electronic mail message and any files transmitted with it > are intended > > exclusively for the individual or entity to which it is addressed. The > message, > > together with any attachment, may contain confidential and/or privileged > information. > > Any unauthorized review, use, printing, saving, copying, disclosure or > distribution > > is strictly prohibited. If you have received this message in error, > please > > immediately advise the sender by reply email and delete all copies. > > > > > > > -- > > Comprehensive Server Monitoring with Site24x7. > > Monitor 10 servers for $9/Month. > > Get alerted through email, SMS, voice calls or mobile push notifications. > > Take corrective actions from your mobile device. > > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users >
Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
To expand on what Rob said, it all just works. On an x64 system the MSI service will be 64-bit. If you have a 32-bit CA you'll get a 32-bit msiexec process launched to host it. If you have another CA that requires impersonation, you'll see another msiexec process running impersonated. The error you're seeing is nothing to do with the with this architecture. It's just invalid for a 32-bit process to access 64-bit modules. You are enumerating processes or you have a process id that's 64-bit and you're using it from 32-bit code to access the process? As Jacob says, if you're on a 64-bit system and you want to do whatever you're doing, make a 64-bit version of your Dll. --- Phil Wilson On Fri, Nov 14, 2014 at 8:35 AM, John Cooper wrote: > That is the technique I use and it is necessary when access 64-bit-only file > system locations and the like. > > -- > John Merryweather Cooper > Senior Software Engineer | Enterprise Service Applications | Continuing > Development > Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 > |jocoo...@jackhenry.com > > > > -Original Message- > From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] > Sent: Friday, November 14, 2014 10:32 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for > a 64-bit MsiPackage > > What is the bitness of your CA DLL? Just a stab in the dark but you might > need to have it compiled twice, once as 32 and once as 64, and have the > respective MSI package use the right CA DLL. > > > -Original Message- > From: Rob Mensching [mailto:r...@firegiant.com] > Sent: Friday, November 14, 2014 9:53 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for > a 64-bit MsiPackage > > Custom actions are hosted by Windows Installer in a separate custom action > host process based on custom action type. > > _ > Short replies here. Complete answers over there: http://www.firegiant.com/ > > > -Original Message- > From: Ryan Waller [mailto:rwal...@microsoft.com] > Sent: Friday, November 14, 2014 7:43 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for > a 64-bit MsiPackage > > Yes, Orca Summary shows it with Platform x64. > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > NOTICE: This electronic mail message and any files transmitted with it are > intended > exclusively for the individual or entity to which it is addressed. The > message, > together with any attachment, may contain confidential and/or privileged > information. > Any unauthorized review, use, printing, saving, copying, disclosure or > distribution > is strictly prohibited. If you have received this message in error, please > immediately advise the sender by reply email and delete all copies. > > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list Wi
[WiX-users] Feature condition never evaluating
Hi, How do I use a property set to RadioButton in a Feature condition? I have a Secure property called UNICODETYPE which gets set to the value of radio button selection. I want to use that property to decide which feature to install. Do the Level of parent feature matter, note it is 200. My understanding is that any Level less than the parent feature level should be installed as long as it is not 0. Also, the level can be overridden with a condition. The install level in the logs show 100, not sure if that matters here. The parent feature (PrivacyAuditor) gets installed fine, but none of the sub-features install. Any suggestions on what is missing/incorrect in the code below? thanks, sangeeta -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RadioButton-property-not-evaluating-correctly-in-Components-Condition-tp7597915p7597949.html Sent from the wix-users mailing list archive at Nabble.com. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX Installation fails to Install Certificate to Root Certification Authorities for Some machines
Thanks. I will check to see if the user has the root certificate already. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-Installation-fails-to-Install-Certificate-to-Root-Certification-Authorities-for-Some-machines-tp7597941p7597948.html Sent from the wix-users mailing list archive at Nabble.com. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
That is the technique I use and it is necessary when access 64-bit-only file system locations and the like. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Friday, November 14, 2014 10:32 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage What is the bitness of your CA DLL? Just a stab in the dark but you might need to have it compiled twice, once as 32 and once as 64, and have the respective MSI package use the right CA DLL. -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Friday, November 14, 2014 9:53 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage Custom actions are hosted by Windows Installer in a separate custom action host process based on custom action type. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Ryan Waller [mailto:rwal...@microsoft.com] Sent: Friday, November 14, 2014 7:43 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage Yes, Orca Summary shows it with Platform x64. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
What is the bitness of your CA DLL? Just a stab in the dark but you might need to have it compiled twice, once as 32 and once as 64, and have the respective MSI package use the right CA DLL. -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Friday, November 14, 2014 9:53 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage Custom actions are hosted by Windows Installer in a separate custom action host process based on custom action type. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Ryan Waller [mailto:rwal...@microsoft.com] Sent: Friday, November 14, 2014 7:43 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage Yes, Orca Summary shows it with Platform x64. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX Installation fails to Install Certificate to Root Certification Authorities for Some machines
This might be a regression, though I haven't dug to history to see if it was
intentionally changed back.
Ref:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Certificate-install-to-local-machine-fails-with-code-26352-td1121050.html
>From the current certutil.cpp
if (!::CertAddCertificateContextToStore(hStore, pCertContext,
CERT_STORE_ADD_REPLACE_EXISTING, NULL))
{
ExitWithLastError(hr, "Failed to add certificate to the store.");
}
And from the linked thread the suggestion was:
To fix this, you should just be able to change the calls in the IIS
extension source (scacertexec.cpp and scacert.cpp) to
CertAddCertificateContextToStore. Instead of using
CERT_STORE_ADD_REPLACE_EXISTING, you can use
CERT_STORE_ADD_USE_EXISTING. This updates the current cert instead of
duplicating it, and the test case detailed above should pass. You will
notice that the certificate will be listed in both the registry and
group policy physical stores, but I don't think there's anything we can
do about that.
-Original Message-
From: KaburagiS [mailto:skabur...@ntst.com]
Sent: Friday, November 14, 2014 9:27 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WIX Installation fails to Install Certificate to Root
Certification Authorities for Some machines
We have created a WIX installation MSI that installs certificates to machine
store. It installs a root certificate (GoDaddy Class 2 Certification
Authority) to the Trusted Root Certification Authorities. It works for most of
machines, but it fails some machines. We suspected the group policy
restrictions( http://technet.microsoft.com/en-us/library/cc754841.aspx), but
the change did not resolve the problem. Below is a WIX definition and a portion
of the log file that shows where the error occurs.
MSI (s) (B4:08) [11:58:21:952]: Executing op:
CustomActionSchedule(Action=RollbackAddMachineCertificate,ActionType=11521,Source=BinaryData,Target=**,CustomActionData=**)
MSI (s) (B4:08) [11:58:21:953]: Executing op:
ActionStart(Name=AddMachineCertificate,,) Action 11:58:21:
AddMachineCertificate. MSI (s) (B4:08) [11:58:21:953]: Executing op:
CustomActionSchedule(Action=AddMachineCertificate,ActionType=11265,Source=BinaryData,Target=**,CustomActionData=**)
MSI (s) (B4:40) [11:58:21:980]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI3EE3.tmp, Entrypoint: AddMachineCertificate MSI (s)
(B4:D0) [11:58:21:981]: Generating random cookie. MSI (s) (B4:D0)
[11:58:21:982]: Created Custom Action Server with PID 9920 (0x26C0). MSI (s)
(B4:90) [11:58:22:042]: Running as a service. MSI (s) (B4:90)
[11:58:22:043]: Hello, I'm your 32bit Elevated custom action server.
AddMachineCertificate: Deleting certificate that begin with friendly name:
GoDaddy Class 2 Certificate_wixCert_ AddMachineCertificate: Adding
certificate: GoDaddy Class 2 Certificate_wixCert_1 AddMachineCertificate:
Error 0x80070005: Failed to add certificate to the store. MSI (s) (B4!0C)
[11:58:22:173]: Note: 1: 2205 2: 3: Error MSI (s) (B4!0C) [11:58:22:173]:
Note: 1: 2228 2: 3: Error 4: SELECT Message FROM Error WHERE Error = 26352 The
installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 26352. The
arguments are: -2147024891, , MSI (s) (B4!0C) [11:58:27:816]: Note: 1: 2205
2: 3: Error MSI (s) (B4!0C) [11:58:27:816]: Note: 1: 2228 2: 3: Error 4:
SELECT Message FROM Error WHERE Error = 1709 MSI (s) (B4!0C) [11:58:27:816]:
Product: Netsmart VR BA Prerequisites -- The installer has encountered an
unexpected error installing this package. This may indicate a problem with this
package. The error code is 26352. The arguments are: -2147024891, ,
AddMachineCertificate: Error 0x80070005: Failed to install certificate.
AddMachineCertificate: Error 0x80070005: Failed to install per-machine
certificate. CustomAction AddMachineCertificate returned actual error code
1603 (note this may not be 100% accurate if translation happened inside
sandbox) Action ended 11:58:27: InstallFinalize. Return value 3. MSI (s)
(B4:08) [11:58:27:961]: User policy value 'DisableRollback' is 0 MSI (s)
(B4:08) [11:58:27:962]: Machine policy value 'DisableRollback' is 0 MSI (s)
(B4:08) [11:58:27:972]: Executing op:
Header(Signature=1397708873,Version=500,Timestamp=1163681610,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
We are puzzled as to what causes this problem. If you have any idea as to what
causes this problem, it would be greatly appreciated.
Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-Installation-fails-to-Install-Certificate-to-Root-Certification-Authorities-for-Some-machines-tp7597941.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
OK, so, is there a way I can achieve what I need to achieve? Run this CA in a 64-bit process? -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Friday, November 14, 2014 7:53 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage Custom actions are hosted by Windows Installer in a separate custom action host process based on custom action type. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Ryan Waller [mailto:rwal...@microsoft.com] Sent: Friday, November 14, 2014 7:43 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage Yes, Orca Summary shows it with Platform x64. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
Custom actions are hosted by Windows Installer in a separate custom action host process based on custom action type. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Ryan Waller [mailto:rwal...@microsoft.com] Sent: Friday, November 14, 2014 7:43 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage Yes, Orca Summary shows it with Platform x64. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
Yes, Orca Summary shows it with Platform x64. -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Friday, November 14, 2014 6:33 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage When you open your "64 bit package" with Orca and look at the Summary Information does it indicate that it is a 64 bit package? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WixStdBA-launches-32-bit-msiexec-exe-for-a-64-bit-MsiPackage-tp7597932p7597940.html Sent from the wix-users mailing list archive at Nabble.com. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WIX Installation fails to Install Certificate to Root Certification Authorities for Some machines
We have created a WIX installation MSI that installs certificates to machine store. It installs a root certificate (GoDaddy Class 2 Certification Authority) to the Trusted Root Certification Authorities. It works for most of machines, but it fails some machines. We suspected the group policy restrictions( http://technet.microsoft.com/en-us/library/cc754841.aspx), but the change did not resolve the problem. Below is a WIX definition and a portion of the log file that shows where the error occurs. MSI (s) (B4:08) [11:58:21:952]: Executing op: CustomActionSchedule(Action=RollbackAddMachineCertificate,ActionType=11521,Source=BinaryData,Target=**,CustomActionData=**) MSI (s) (B4:08) [11:58:21:953]: Executing op: ActionStart(Name=AddMachineCertificate,,) Action 11:58:21: AddMachineCertificate. MSI (s) (B4:08) [11:58:21:953]: Executing op: CustomActionSchedule(Action=AddMachineCertificate,ActionType=11265,Source=BinaryData,Target=**,CustomActionData=**) MSI (s) (B4:40) [11:58:21:980]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI3EE3.tmp, Entrypoint: AddMachineCertificate MSI (s) (B4:D0) [11:58:21:981]: Generating random cookie. MSI (s) (B4:D0) [11:58:21:982]: Created Custom Action Server with PID 9920 (0x26C0). MSI (s) (B4:90) [11:58:22:042]: Running as a service. MSI (s) (B4:90) [11:58:22:043]: Hello, I'm your 32bit Elevated custom action server. AddMachineCertificate: Deleting certificate that begin with friendly name: GoDaddy Class 2 Certificate_wixCert_ AddMachineCertificate: Adding certificate: GoDaddy Class 2 Certificate_wixCert_1 AddMachineCertificate: Error 0x80070005: Failed to add certificate to the store. MSI (s) (B4!0C) [11:58:22:173]: Note: 1: 2205 2: 3: Error MSI (s) (B4!0C) [11:58:22:173]: Note: 1: 2228 2: 3: Error 4: SELECT Message FROM Error WHERE Error = 26352 The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 26352. The arguments are: -2147024891, , MSI (s) (B4!0C) [11:58:27:816]: Note: 1: 2205 2: 3: Error MSI (s) (B4!0C) [11:58:27:816]: Note: 1: 2228 2: 3: Error 4: SELECT Message FROM Error WHERE Error = 1709 MSI (s) (B4!0C) [11:58:27:816]: Product: Netsmart VR BA Prerequisites -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 26352. The arguments are: -2147024891, , AddMachineCertificate: Error 0x80070005: Failed to install certificate. AddMachineCertificate: Error 0x80070005: Failed to install per-machine certificate. CustomAction AddMachineCertificate returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Action ended 11:58:27: InstallFinalize. Return value 3. MSI (s) (B4:08) [11:58:27:961]: User policy value 'DisableRollback' is 0 MSI (s) (B4:08) [11:58:27:962]: Machine policy value 'DisableRollback' is 0 MSI (s) (B4:08) [11:58:27:972]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1163681610,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1) We are puzzled as to what causes this problem. If you have any idea as to what causes this problem, it would be greatly appreciated. Thanks. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-Installation-fails-to-Install-Certificate-to-Root-Certification-Authorities-for-Some-machines-tp7597941.html Sent from the wix-users mailing list archive at Nabble.com. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
When you open your "64 bit package" with Orca and look at the Summary Information does it indicate that it is a 64 bit package? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WixStdBA-launches-32-bit-msiexec-exe-for-a-64-bit-MsiPackage-tp7597932p7597940.html Sent from the wix-users mailing list archive at Nabble.com. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Automatically 'harvest' files in VS 2013
"Brian the Wix documentation defines both a "HeatDirectory Target" and a "HeatDirectory Task". " I provided incorrect information in this thread and I appreciate John's prompt to go research this in more detail. There is a HarvestDirectory target and a HeatDirectory task. Here is an example of how to use the HarvestDirectory target to harvest more than one folder tree: true true true true true Dir1Id transfrom1.xslt Dir1Group var.Dir1Var false true true true false Dir2Id transfrom2.xslt Dir2Group var.Dir2Var false true true true false The generated wxs files end up in ..\obj\$(Configuration) and a ComponentGroupRef needs to be added to the project's authoring. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Automatically-harvest-files-in-VS-2013-tp7597592p7597939.html Sent from the wix-users mailing list archive at Nabble.com. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Domain Admin check in wix installer
1) immediate custom action since it does not change machine state (and you want to set properties); 2) have an input property containing either the possible domain account or a reference to a property containing the possible domain account; 3) use C# in the usual manner -- you can adapt code like this to do your business: http://stackoverflow.com/questions/6653151/how-to-check-whether-user-is-domain-administrator-in-c-sharp 4) if the possible domain account is a domain admin, set an output property to "#1"; 5) else, clear the output property by setting it to string.Empty; -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: sourabh_1987 [mailto:sourabh_1...@live.com] Sent: Thursday, November 13, 2014 11:38 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Domain Admin check in wix installer Hi John, Can you please explain how it can be done with custom action? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Domain-Admin-check-in-wix-installer-tp7597895p7597937.html Sent from the wix-users mailing list archive at Nabble.com. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
