Wix custom actions that are affected by the XP SP2 requirement are all contained in extensions, and you can see if any of those extensions may have added any of these custom actions by looking in the Source column of the CustomAction table for values prefixed with "Wix", "IIs", "Sca", "NetFx", or "DIFxApp". The CAs in wix are built statically linking the C++ runtime so adding a runtime won't help. The problem is that the "newer" C++ runtimes have security enhancements that depend on a couple of entry points in Kernel32.dll that are not present in Win2K which causes the DLL to be unable to resolve those entrypoints thus failing LoadLibrary(). Either those custom actions would need to be recompiled against an older VC or redirect code for those missing runtime routines needs binary compiled into the CAs. Longstanding Wix standard practice is to use recent compiler tools to reduce the risk of security bugs and to only test on manufacturer-supported platforms. Other resources can, of course, provide additional support above and beyond what an open source all-volunteer group can reasonably do. I could set this up for you, but I don't have enough volunteer time to get it done in a timely fashion (however, I do have some flexibility currently in my billable schedule). If interested, please ping me directly and we can work out a quote, or you can use attempt a fix yourself or solicit any of several other people on this list or elsewhere on the web that work extending the WiX toolset. Blair Murri > From: andrew.jo...@alquist.co.uk > To: wix-users@lists.sourceforge.net > Date: Fri, 28 Jun 2013 01:28:35 +0100 > Subject: Re: [WiX-users] WiX-users Digest, Vol 85, Issue 138 > > > MSIs created by WiX toolset will run fine (as long as you target Windows > > Installer that supports Win2k). > > However, any WiX code that gets carried with your MSI (like custom actions > > or Burn) require WinXP SP2+. > > Looking at the verbose log files it looks as though some custom actions must > be at work behind the scenes. > > MSI (s) (EC:C0) [00:49:34:669]: Doing action: ConfigureUsers > Action 00:49:34: ConfigureUsers. > Action start 00:49:34: ConfigureUsers. > MSI (s) (EC:60) [00:49:34:713]: Invoking remote custom action. DLL: > C:\WINNT\Installer\MSI2.tmp, Entrypoint: ConfigureUsers > MSI (s) (EC:A0) [00:49:34:713]: Generating random cookie. > MSI (s) (EC:A0) [00:49:34:713]: Created Custom Action Server with PID 1108 > (0x454). > MSI (s) (EC:98) [00:49:34:768]: Running as a service. > MSI (s) (EC:5C) [00:49:34:780]: Hello, I'm your 32bit Impersonated custom > action server. > Action ended 00:49:34: ConfigureUsers. Return value 3. > > My installer is using these extensions. > > xmlns:netfx="http://schemas.microsoft.com/wix/NetFxExtension"; > xmlns:util="http://schemas.microsoft.com/wix/UtilExtension"; > xmlns:fw="http://schemas.microsoft.com/wix/FirewallExtension"; > > It's presumably these extensions that cannot run on Windows 2000 because it > has an old version of the Visual C++ runtime. > > Would installing a newer version of the VC++ runtime on the Windows 2000 > allow the installer to run? > > Andrew > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows:
Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
