Menu
▾
▴
wix-users — Mailing list for questions/discussion about the Windows Installer XML toolset.
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
(98) |
May
(256) |
Jun
(66) |
Jul
(104) |
Aug
(74) |
Sep
(177) |
Oct
(309) |
Nov
(330) |
Dec
(377) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(268) |
Feb
(304) |
Mar
(337) |
Apr
(396) |
May
(516) |
Jun
(588) |
Jul
(475) |
Aug
(371) |
Sep
(460) |
Oct
(549) |
Nov
(465) |
Dec
(312) |
| 2006 |
Jan
(510) |
Feb
(656) |
Mar
(581) |
Apr
(465) |
May
(561) |
Jun
(593) |
Jul
(617) |
Aug
(663) |
Sep
(684) |
Oct
(840) |
Nov
(712) |
Dec
(598) |
| 2007 |
Jan
(857) |
Feb
(695) |
Mar
(1040) |
Apr
(1109) |
May
(1094) |
Jun
(949) |
Jul
(941) |
Aug
(808) |
Sep
(760) |
Oct
(906) |
Nov
(693) |
Dec
(497) |
| 2008 |
Jan
(752) |
Feb
(638) |
Mar
(679) |
Apr
(878) |
May
(1049) |
Jun
(886) |
Jul
(951) |
Aug
(747) |
Sep
(884) |
Oct
(1359) |
Nov
(924) |
Dec
(881) |
| 2009 |
Jan
(1055) |
Feb
(1096) |
Mar
(783) |
Apr
(826) |
May
(845) |
Jun
(928) |
Jul
(836) |
Aug
(683) |
Sep
(744) |
Oct
(1027) |
Nov
(857) |
Dec
(552) |
| 2010 |
Jan
(670) |
Feb
(703) |
Mar
(995) |
Apr
(840) |
May
(629) |
Jun
(776) |
Jul
(931) |
Aug
(636) |
Sep
(720) |
Oct
(446) |
Nov
(533) |
Dec
(435) |
| 2011 |
Jan
(682) |
Feb
(573) |
Mar
(659) |
Apr
(422) |
May
(415) |
Jun
(362) |
Jul
(543) |
Aug
(414) |
Sep
(362) |
Oct
(405) |
Nov
(475) |
Dec
(231) |
| 2012 |
Jan
(599) |
Feb
(366) |
Mar
(306) |
Apr
(456) |
May
(454) |
Jun
(541) |
Jul
(352) |
Aug
(563) |
Sep
(631) |
Oct
(681) |
Nov
(414) |
Dec
(354) |
| 2013 |
Jan
(591) |
Feb
(554) |
Mar
(563) |
Apr
(614) |
May
(640) |
Jun
(651) |
Jul
(625) |
Aug
(749) |
Sep
(475) |
Oct
(687) |
Nov
(596) |
Dec
(412) |
| 2014 |
Jan
(508) |
Feb
(537) |
Mar
(673) |
Apr
(447) |
May
(342) |
Jun
(396) |
Jul
(345) |
Aug
(382) |
Sep
(384) |
Oct
(441) |
Nov
(512) |
Dec
(326) |
| 2015 |
Jan
(313) |
Feb
(270) |
Mar
(330) |
Apr
(289) |
May
(298) |
Jun
(232) |
Jul
(143) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Phill H. <pho...@ri...> - 2015-07-28 21:35:41
|
Did you file your Feature request here <http://wixtoolset.org/issues/> ? Did you consider using a "addon" bundle? I currently create a bundle with A, B, and C. Then later I create another bundle with D (which releases on a different schedule). (And much later again I can add D into the original base bundle and not need the 'addon' bundle anymore.). In the 'base' bundle I have: <RelatedBundle Action='Detect' Id='A_GUID_Used_To_ID_This_Base_Bundle' /> (as a matter of practice I add the above to every bundle I produce, whether I plan to create an addon or not.) Then in the "addon" bundle I have: <RelatedBundle Action='Addon' Id='The_Same_GUID_Used_To_ID_The_Base_Bundle' /> I did not need to add any code to the mba, although there are handlers if you need to do something special. Once the 'Addon' bundle is installed it becomes a part of the base bundle and is uninstalled or repaired as part of that base bundle. Using the RelatedBundle element seems like a simple solution to what you are trying to achieve. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Feature-suggestion-Dynamic-Burn-bundle-tp7600934p7600938.html Sent from the wix-users mailing list archive at Nabble.com. |
|
From: Colin S. <Col...@ip...> - 2015-07-28 21:16:43
|
We're doing a major upgrade and RemoveExistingProducts may not be schedule in the most efficient place, i.e. between InstallValidate and InstallInitialize. I'll attach the upgrade log in a following email as it's 42MB in size and I'm not sure if it'll be allowed. -----Original Message----- From: Nir Bar [mailto:ni...@pa...] Sent: Wednesday, 29 July 2015 6:59 a.m. To: wix...@li... Subject: Re: [wix-users] (deprecated) Windows Installer Repair Failure I must say that the description doesn't seem right Can you post the full log with no inline comments? If this is a major upgrade then depending on the scheduling of RemoveExistingProducts <https://msdn.microsoft.com/en-us/library/aa371197(v=vs.85).aspx> you'll get a full uninstall then full install, or delete/overwrite/add files. For minor upgardes you will not get any removal, just overwrite/add files. The partial log you posted isn't enough for me to understand which- if any- upgrade is occuring. ----- Nir Bar Freelance Developer Mail: ni...@pa... Web: www.panel-sw.com - C++ On Windows, Linux and Embedded Platforms - WiX & InstallShield -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix-users-deprecated-Windows-Installer-Repair-Failure-tp7600931p7600936.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX...@li... https://lists.sourceforge.net/lists/listinfo/wix-users This e-mail contains IPFX information which may be privileged or confidential and is intended for use only by the individual(s) or entity named above. If you are not the intended recipient, note that disclosing, copying, distributing or using this information is prohibited. If you have received this e-mail in error, please advise immediately to the e-mail address above and permanently delete this message and any attachments. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. We monitor our e-mail system and may record your e-mails. Thank you. |
|
From: Nir B. <ni...@pa...> - 2015-07-28 18:58:45
|
I must say that the description doesn't seem right Can you post the full log with no inline comments? If this is a major upgrade then depending on the scheduling of RemoveExistingProducts <https://msdn.microsoft.com/en-us/library/aa371197(v=vs.85).aspx> you'll get a full uninstall then full install, or delete/overwrite/add files. For minor upgardes you will not get any removal, just overwrite/add files. The partial log you posted isn't enough for me to understand which- if any- upgrade is occuring. ----- Nir Bar Freelance Developer Mail: ni...@pa... Web: www.panel-sw.com - C++ On Windows, Linux and Embedded Platforms - WiX & InstallShield -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix-users-deprecated-Windows-Installer-Repair-Failure-tp7600931p7600936.html Sent from the wix-users mailing list archive at Nabble.com. |
|
From: Sean H. <r.s...@gm...> - 2015-07-28 14:05:35
|
I would bet that the problem is that the supportedFramework element is v3.5 (which is the 2.0 runtime) but there's no supportedRuntime element for the 2.0 CLR. P.S. Please use the new mailing list, information is at http://wixtoolset.org/documentation/mailinglist/ On Mon, Jul 27, 2015 at 2:10 PM, Brian C Cooke <ton...@gm...> wrote: > I am getting "Error loading prerequisite bootstrapper application because > managed host could not be loaded" in the logs of my custom bootstrapper. > Originally I was using burn 3.9.2, and receiving error code 0x80004001. On > the advice of this thread (http://tinyurl.com/pt9ym65) I tried upgrading > to > 3.10.0.1823 but am still receiving the same error, only with a different > error code: 0x80131700. > > My bootstrapper is targeting .NET 3.5 and is installing 4.5 as a > prerequisite. Curiously enough, I am initially able to install .NET 4.5, > and load my custom bootstrapper. However, if I subsequently uninstall .NET > via ARP, and run my bootstrapper a 2nd time, then I consistently get the > above error. The test environment is running Windows 7 with .NET 3.5 > enabled. Here is my bootstrappercore.config > > <?xml version="1.0" encoding="utf-8" ?> > <configuration> > > <configSections> > <sectionGroup name="wix.bootstrapper" > > type="Microsoft.Tools.WindowsInstallerXml.Bootstrapper.BootstrapperSectionGroup, > BootstrapperCore"> > <section name="host" > type="Microsoft.Tools.WindowsInstallerXml.Bootstrapper.HostSection, > BootstrapperCore" /> > </sectionGroup> > </configSections> > > <startup useLegacyV2RuntimeActivationPolicy="true"> > <supportedRuntime version="v4.0" /> > </startup> > > <wix.bootstrapper> > <host assemblyName="MyBootstrapperApplication"> > <supportedFramework version="v3.5" /> > </host> > </wix.bootstrapper> > > </configuration> > > Can someone please advise whether this is a WiX bug or I am doing something > wrong? Thanks in advance. > > Brian > > ------------------------------------------------------------------------------ > _______________________________________________ > WiX-users mailing list > WiX...@li... > https://lists.sourceforge.net/lists/listinfo/wix-users > |
|
From: Jiri T. <ka...@vo...> - 2015-07-28 07:13:51
|
I understand current Wix team statement that it's not possible to build Burn bundle with products A,B and C and then during execution get somewhere product D and install it in the bundle. The reason is security and I get it. But, what about allowing dynamic bundle where security is provided by certificate used to sing individual MSIs? Example: I create a bundle to which I provide a certificate that will be used for all packages that bundle can install. Bundle itself will have no payload. The MBA will contact download server and provides user the list of available products or updates to install. User selects items, MBA will download them and call Burn Engine to add these items to install chain. Burn checks signature of all these items and accepts them only if it's valid for the certificate used during compilation. This way it's secure and it allows to build really rich install/update platform that is fully data-driven. Current limitation which allows only installation of packages that are known during build-time is so limiting in my use case that I'm not able to use Burn. I would have to build new bundle every few days, have multiple of them to cover different product combinations etc. Being able to leverage Burn install platform with dynamic data would be just awesome. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Feature-suggestion-Dynamic-Burn-bundle-tp7600934.html Sent from the wix-users mailing list archive at Nabble.com. |
|
From: Brian C C. <ton...@gm...> - 2015-07-27 19:35:29
|
I am getting "Error loading prerequisite bootstrapper application because managed host could not be loaded" in the logs of my custom bootstrapper. Originally I was using burn 3.9.2, and receiving error code 0x80004001. On the advice of this thread (http://tinyurl.com/pt9ym65) I tried upgrading to 3.10.0.1823 but am still receiving the same error, only with a different error code: 0x80131700. My bootstrapper is targeting .NET 3.5 and is installing 4.5 as a prerequisite. Curiously enough, I am initially able to install .NET 4.5, and load my custom bootstrapper. However, if I subsequently uninstall .NET via ARP, and run my bootstrapper a 2nd time, then I consistently get the above error. The test environment is running Windows 7 with .NET 3.5 enabled. Here is my bootstrappercore.config <?xml version="1.0" encoding="utf-8" ?> <configuration> <configSections> <sectionGroup name="wix.bootstrapper" type="Microsoft.Tools.WindowsInstallerXml.Bootstrapper.BootstrapperSectionGroup, BootstrapperCore"> <section name="host" type="Microsoft.Tools.WindowsInstallerXml.Bootstrapper.HostSection, BootstrapperCore" /> </sectionGroup> </configSections> <startup useLegacyV2RuntimeActivationPolicy="true"> <supportedRuntime version="v4.0" /> </startup> <wix.bootstrapper> <host assemblyName="MyBootstrapperApplication"> <supportedFramework version="v3.5" /> </host> </wix.bootstrapper> </configuration> Can someone please advise whether this is a WiX bug or I am doing something wrong? Thanks in advance. Brian |
|
From: Colin S. <Col...@ip...> - 2015-07-26 22:19:52
|
We use a PowerShell script to upgrade our development servers and our product is contained in a 1.7GB MSI file. The PowerShell script copies the package from a network share to the local %TEMP% directory, then executes the MSI in silent mode. Upon successful installation the copy of the MSI in the %TEMP% directory is removed.
On development servers, it is typical for developers to replace components that are installed through the MSI with components they build themselves - these components generally will have a higher version number than that installed by the MSI. As a result, here is the scenario on upgrade and subsequently the error:
1. When upgrading some components are marked as "leave alone" because they have a higher version number than the new package.
2. The upgrade process performs an uninstall, which removes all components of existing package (including those that were marked as "leave alone" - this must be a bug in the Windows Install!!!).
3. The upgrade process performs an install; however, does not install the components that were previously marked as "leave alone".
4. When we first run an application from our product Windows Installer detects the missing component(s) and triggers a repair.
5. The repair initiates using the cached MSI under C:\Windows\Installer. However, when it comes time to replace the missing component:
i. it looks like the Windows Installer does another search for the MSI that contains the component (bizarre)
ii. fails to find the original copy as it's already been deleted
iii. finds the cached copy, which is already executing; hence locked, and pops up a dialog requesting the location of a source MSI file.
COME ON - THIS MUST TO BE A BUG!!!!
I have attached the full repair log, and snippets of what I thought were interesting below with my comments surround in square brackets. I would appreciate any feedback and possible work around. I would presume (many) others would've come across something like this before.
[Cached copy of installer found]
Original package ==> C:\Windows\Installer\14a4210d.msi
Package we're running from ==> C:\Windows\Installer\14a4210d.msi
[Not sure if this is a problem but seems weird to me]
MSI (s) (20:54) [07:32:29:318]: APPCOMPAT: looking for appcompat database entry with ProductCode '{FA2B343E-75B9-4EBB-A1C6-974E3B55775E}'.
MSI (s) (20:54) [07:32:29:318]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (20:54) [07:32:29:709]: Package name retrieved from configuration data: 'IPFX Server Install.msi'
[Repairing around here]
[Time to replace missing component - this is when things go south]
MSI (s) (20:54) [07:34:16:569]: Executing op: RegisterSharedComponentProvider(,,File=servicemanager.exe,Component={C750EF8F-87DA-4610-8658-8C513E1F8529},ComponentVersion=6.3.211.0,ProductCode={FA2B343E-75B9-4EBB-A1C6-974E3B55775E},ProductVersion=6.3.211,PatchSize=0,PatchAttributes=0,PatchSequence=0,SharedComponent=0,IsFullFile=0)
MSI (s) (20:54) [07:34:16:569]: Executing op: FileCopy(SourceName=SERVIC~1.EXE|servicemanager.exe,SourceCabKey=servicemanager.exe,DestName=servicemanager.exe,Attributes=16384,FileSize=3023656,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,Version=6.3.211.0,Language=5129,InstallMode=59113472,,,,,,,)
MSI (s) (20:54) [07:34:16:585]: File: C:\VMLocal\servicemanager.exe; To be installed; Won't patch; No existing file
MSI (s) (20:54) [07:34:16:600]: Resolving source.
MSI (s) (20:54) [07:34:16:600]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (20:54) [07:34:16:600]: User policy value 'DisableMedia' is 0
MSI (s) (20:54) [07:34:16:600]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (20:54) [07:34:16:600]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (20:54) [07:34:16:600]: SOURCEMGMT: Looking for sourcelist for product {FA2B343E-75B9-4EBB-A1C6-974E3B55775E}
MSI (s) (20:54) [07:34:16:600]: SOURCEMGMT: Adding {FA2B343E-75B9-4EBB-A1C6-974E3B55775E}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (20:54) [07:34:16:600]: SOURCEMGMT: Now checking product {FA2B343E-75B9-4EBB-A1C6-974E3B55775E}
MSI (s) (20:54) [07:34:16:600]: SOURCEMGMT: Media is enabled for product.
MSI (s) (20:54) [07:34:16:600]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (20:54) [07:34:16:600]: SOURCEMGMT: Trying source C:\Users\shanep\AppData\Local\Temp\.
[The original copy which no longer exists]
MSI (s) (20:54) [07:34:16:600]: Note: 1: 2203 2: C:\Users\shanep\AppData\Local\Temp\IPFX Server Install.msi 3: -2147287038
MSI (s) (20:54) [07:34:16:600]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (20:54) [07:34:16:600]: Note: 1: 1706 2: -2147483647 3: IPFX Server Install.msi
MSI (s) (20:54) [07:34:16:600]: SOURCEMGMT: Processing net source list.
MSI (s) (20:54) [07:34:16:600]: Note: 1: 1706 2: -2147483647 3: IPFX Server Install.msi
MSI (s) (20:54) [07:34:16:600]: SOURCEMGMT: Processing media source list.
MSI (s) (20:54) [07:34:17:725]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (20:54) [07:34:17:725]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (20:54) [07:34:17:725]: Note: 1: 1706 2: -2147483647 3: IPFX Server Install.msi
MSI (s) (20:54) [07:34:17:725]: SOURCEMGMT: Processing URL source list.
MSI (s) (20:54) [07:34:17:725]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (20:54) [07:34:17:725]: Note: 1: 1706 2: -2147483647 3: IPFX Server Install.msi
MSI (s) (20:54) [07:34:17:725]: Note: 1: 1706 2: 3: IPFX Server Install.msi
MSI (c) (BC:B0) [07:34:17:741]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (BC:B0) [07:34:17:741]: User policy value 'DisableMedia' is 0
MSI (c) (BC:B0) [07:34:17:741]: Machine policy value 'AllowLockdownMedia' is 0
MSI (c) (BC:B0) [07:34:17:741]: SOURCEMGMT: Media enabled only if package is safe.
MSI (c) (BC:B0) [07:34:17:741]: SOURCEMGMT: Prompting user for a valid source.
MSI (c) (BC:B0) [07:34:17:741]: Machine policy value 'DisableBrowse' is 0
MSI (c) (BC:B0) [07:34:17:741]: Machine policy value 'AllowLockdownBrowse' is 1
MSI (c) (BC:B0) [07:34:17:741]: SOURCEMGMT: Browsing is enabled.
MSI (c) (BC:B0) [07:34:17:772]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (BC:B0) [07:34:17:772]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (BC:B0) [07:34:17:772]: SOURCEMGMT: Now checking product {FA2B343E-75B9-4EBB-A1C6-974E3B55775E}
MSI (c) (BC:B0) [07:34:17:788]: SOURCEMGMT: Media is enabled for product.
MSI (c) (BC:B0) [07:34:17:788]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (c) (BC:B0) [07:34:17:788]: Note: 1: 1706 2: 3: IPFX Server Install.msi
MSI (c) (BC:B0) [07:34:17:788]: SOURCEMGMT: Processing net source list.
MSI (c) (BC:B0) [07:34:17:788]: Note: 1: 1706 2: -2147483647 3: IPFX Server Install.msi
MSI (c) (BC:B0) [07:34:17:788]: SOURCEMGMT: Processing media source list.
MSI (c) (BC:B0) [07:34:17:788]: SOURCEMGMT: Trying media source DISK1;1.
MSI (c) (BC:B0) [07:34:17:788]: Note: 1: 1706 2: 3: IPFX Server Install.msi
MSI (c) (BC:B0) [07:34:17:788]: SOURCEMGMT: Processing URL source list.
MSI (c) (BC:B0) [07:34:17:788]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (c) (BC:B0) [07:34:17:788]: Note: 1: 1706 2: -2147483647 3: IPFX Server Install.msi
MSI (c) (BC:B0) [07:34:17:788]: Note: 1: 1706 2: 3: IPFX Server Install.msi
[Eventually finds cached copy, which is what's executing]
MSI (c) (BC:B4) [07:45:23:837]: SOURCEMGMT: Trying source C:\Windows\Installer\14a4210d.msi.
MSI (c) (BC:B4) [07:45:23:868]: Note: 1: 2203 2: C:\Windows\Installer\IPFX Server Install.msiMSI (s) (20:BC) [07:45:33:305]: Running as a service.
MSI (s) (20:E4) [07:45:33:727]: Running as a service.
MSI (s) (20:E4) [07:45:33:743]: Generating random cookie.
MSI (s) (20:E4) [07:45:33:743]: Created Custom Action Server with PID 4764 (0x129C).
MSI (s) (20:BC) [07:45:33:868]: Running as a service.
MSI (s) (20:BC) [07:45:33:868]: Hello, I'm your 32bit Impersonated custom action server.
MSI (s) (20:E4) [07:45:54:399]: Server locked. Will skip uninstalled package cleanup, and allow locking install to perform cleanup.
MSI (s) (20:B4) [07:46:45:837]: Running as a service.
MSI (s) (20:B4) [07:46:45:837]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (20:B4) [07:46:45:837]: Specifed source is not already in a list.
MSI (s) (20:B4) [07:46:45:837]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (20:B4) [07:46:45:837]: Machine policy value 'DisableBrowse' is 0
MSI (s) (20:B4) [07:46:45:837]: Machine policy value 'AllowLockdownBrowse' is 1
MSI (s) (20:B4) [07:46:45:837]: Adding new sources is allowed.
MSI (s) (20:B4) [07:46:45:837]: Added new source 'C:\IPFX\' with index '2'
MSI (s) (20:B4) [07:46:45:837]: Set LastUsedSource to: C:\IPFX\.
MSI (s) (20:B4) [07:46:45:852]: Set LastUsedType to: n.
MSI (s) (20:B4) [07:46:45:852]: Set LastUsedIndex to: 2.
MSI (s) (20:54) [07:46:45:868]: SOURCEMGMT: Now checking product {FA2B343E-75B9-4EBB-A1C6-974E3B55775E}
MSI (s) (20:54) [07:46:45:868]: SOURCEMGMT: Media is enabled for product.
MSI (s) (20:54) [07:46:45:884]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (20:54) [07:46:45:884]: SOURCEMGMT: Trying source C:\IPFX\.
MSI (s) (20:54) [07:46:45:915]: SOURCEMGMT: Resolved source to: 'C:\IPFX\'
MSI (s) (20:54) [07:46:45:915]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'C:\IPFX\'.
MSI (s) (20:54) [07:46:45:915]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'C:\IPFX\'.
MSI (s) (20:54) [07:46:45:915]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{FA2B343E-75B9-4EBB-A1C6-974E3B55775E}'.
MSI (s) (20:54) [07:46:45:915]: SOURCEDIR ==> C:\IPFX\
MSI (s) (20:54) [07:46:45:915]: SOURCEDIR product ==> {FA2B343E-75B9-4EBB-A1C6-974E3B55775E}
MSI (s) (20:54) [07:46:45:946]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (20:54) [07:46:45:946]: Determining source type
MSI (s) (20:54) [07:46:45:946]: Source type from package 'IPFX Server Install.msi': 0
MSI (s) (20:54) [07:46:45:962]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{FA2B343E-75B9-4EBB-A1C6-974E3B55775E}
MSI (s) (20:54) [07:47:16:305]: Source for file 'servicemanager.exe' is compressed
3: -2147287038
MSI (c) (BC:B4) [07:45:23:868]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (c) (BC:B4) [07:45:23:868]: Note: 1: 1706 2: -2147483647 3: IPFX Server Install.msi
MSI (c) (BC:B4) [07:45:23:947]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (BC:5C) [07:46:45:758]: SOURCEMGMT: Trying source C:\IPFX.
MSI (c) (BC:5C) [07:46:45:837]: Cloaking enabled.
MSI (c) (BC:5C) [07:46:45:837]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (BC:5C) [07:46:45:837]: Connected to service.
MSI (c) (BC:B0) [07:46:45:868]: SOURCEMGMT: Resolved source to: 'C:\IPFX\'
MSI (s) (20:54) [07:47:16:337]: SOFTWARE RESTRICTION POLICY: Verifying object --> 'C:\IPFX\IPFX Server Install.msi' against software restriction policy
MSI (s) (20:54) [07:47:16:337]: SOFTWARE RESTRICTION POLICY: C:\IPFX\IPFX Server Install.msi has a digital signature
MSI (s) (20:54) [07:47:29:930]: SOFTWARE RESTRICTION POLICY: C:\IPFX\IPFX Server Install.msi is permitted to run at the 'unrestricted' authorization level.
This e-mail contains IPFX information which may be privileged or confidential and is intended for use only by the individual(s) or entity named above. If you are not the intended recipient, note that disclosing, copying, distributing or using this information is prohibited. If you have received this e-mail in error, please advise immediately to the e-mail address above and permanently delete this message and any attachments. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. We monitor our e-mail system and may record your e-mails. Thank you.
|
|
From: vcurran <vc...@ho...> - 2015-07-24 06:28:05
|
https://www.packtpub.com/packt/offers/free-learning -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-book-as-a-free-ebook-from-Packt-Publishing-today-only-tp7600930.html Sent from the wix-users mailing list archive at Nabble.com. |
|
From: Kashif Md. <mdk...@gm...> - 2015-07-24 05:02:39
|
I’ve been facing issues while updating a few companion files in a windows installer patch for which size does not change but checksum does change. I'm not going into details here because I know why bug happened and what was the core reason. The problem is that I went to MS paid support and they say that for companion file logic to work companion and its parent must be in the same feature. If parent and companion are in two different features then it is not a supported scenario. The documentation on MSDN does not say that both files must be from same feature. They also said that they won't document this on MSDN because anyone with basic installer knowledge will know it already. I don't consider myself a beginner and didn't know it. So I have come to the experts here (some of whom have probably earlier worked with MS on core installer engine): “Is it really mandatory that companion and its parent should always be in same feature”? How do I take advantage of companion file logic if my feature does not have any versioned file? Thanks and Regards, -kashif |
|
From: Marc B. <mbe...@ma...> - 2015-07-23 18:55:00
|
Ok, I'll modify my MSI accordingly... Thanks for the advice.. -----Original Message----- From: Phill Hogland [mailto:pho...@ri...] Sent: July-22-2015 4:59 PM To: wix...@li... Subject: Re: [wix-users] (deprecated) (deprecated) Difxapp Component Installation condition I think it would be advisable to follow the one-resource-per-component pattern. http://stackoverflow.com/questions/1602831/wix-one-file-per-component-or-sev eral-files-per-component -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-deprecated- Difxapp-Component-Installation-condition-tp7600925p7600926.html Sent from the wix-users mailing list archive at Nabble.com. ---------------------------------------------------------------------------- -- _______________________________________________ WiX-users mailing list WiX...@li... https://lists.sourceforge.net/lists/listinfo/wix-users |
|
From: Aaron B. <aa...@ja...> - 2015-07-23 17:12:01
|
I am having trouble getting my installation to work correctly. In my installation, the user needs to select 3 paths, the Program Installation folder, the Local data folder, and the Server data folder. The Local and Server data folders can be shared, or separate folders depending on the user. I have got the install to allow to select all three folders, and the properties are getting updated, but for some reason, it is not updating the sub-folders of my Server data folder. However, both the Program install and the Local data folders are updating correctly, and I am totally stumped as to what is happening. If anyone can help I would sincerely appreciate it. I am including copies of the WXS files as well as the relevant portion of the log file to help to try to determine what the problem is. I am assuming that the user is performing a full UI install, at the present point in time. I may allow for Minimal UI and Administrative installs later, but I need to get it working with the Full UI currently. I removed all GUIDs from the files and inserted "YOUR_GUID_HERE" instead. I also anonymized the folder names. I have attached the section of the install log showing where the local data folder path was updated, but the server data sub-folders were not, at the end of the message. WIX_UICustom: <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> <Fragment> <UIRef Id="WixUI_Common" /> <UI Id="WixUI_Custom"> <TextStyle Id="WixUI_Font_Normal" FaceName="Tahoma" Size="8" /> <TextStyle Id="WixUI_Font_Bigger" FaceName="Tahoma" Size="12" /> <TextStyle Id="WixUI_Font_Title" FaceName="Tahoma" Size="9" Bold="yes" /> <Property Id="DefaultUIFont" Value="WixUI_Font_Normal" /> <DialogRef Id="ErrorDlg" /> <DialogRef Id="FatalError" /> <DialogRef Id="FilesInUse" /> <DialogRef Id="MsiRMFilesInUse" /> <DialogRef Id="PrepareDlg" /> <DialogRef Id="ProgressDlg" /> <DialogRef Id="ResumeDlg" /> <DialogRef Id="UserExit" /> <Publish Dialog="ExitDialog" Control="Finish" Event="EndDialog" Value="Return" Order="999">1</Publish> <Publish Dialog="WelcomeDlg" Control="Next" Property="_InstallDirBrowserProperty" Value="PROGRAMFOLDER" Order="1">1</Publish> <Publish Dialog="WelcomeDlg" Control="Next" Property="_LocalJSDDirBrowserProperty" Value="DATAFOLDER" Order="1">1</Publish> <Publish Dialog="WelcomeDlg" Control="Next" Property="_ServerJSDDirBrowserProperty" Value="SERVERDATAFOLDER" Order="1">1</Publish> <Publish Dialog="WelcomeDlg" Control="Next" Event="NewDialog" Value="MyInstallDirDlg" Order="2">NOT Installed AND NOT PATCH</Publish> <Publish Dialog="WelcomeDlg" Control="Next" Event="NewDialog" Value="VerifyReadyDlg" Order="2">Installed AND PATCH</Publish> <Publish Dialog="MyInstallDirDlg" Control="Back" Event="NewDialog" Value="WelcomeDlg">1</Publish> <Publish Dialog="MyInstallDirDlg" Control="Next" Event="NewDialog" Value="VerifyReadyDlg">1</Publish> <Publish Dialog="VerifyReadyDlg" Control="Back" Event="NewDialog" Value="MyInstallDirDlg" Order="1">WixUI_InstallMode = "InstallComplete"</Publish> <Publish Dialog="VerifyReadyDlg" Control="Back" Event="NewDialog" Value="MaintenanceTypeDlg" Order="2">WixUI_InstallMode = "Repair" OR WixUI_InstallMode = "Remove"</Publish> <Publish Dialog="VerifyReadyDlg" Control="Back" Event="NewDialog" Value="WelcomeDlg" Order="1">WixUI_InstallMode = "Update"</Publish> <Publish Dialog="MaintenanceWelcomeDlg" Control="Next" Event="NewDialog" Value="MaintenanceTypeDlg">1</Publish> <Publish Dialog="MaintenanceTypeDlg" Control="RepairButton" Event="NewDialog" Value="VerifyReadyDlg">1</Publish> <Publish Dialog="MaintenanceTypeDlg" Control="RemoveButton" Event="NewDialog" Value="VerifyReadyDlg">1</Publish> <Publish Dialog="MaintenanceTypeDlg" Control="Back" Event="NewDialog" Value="MaintenanceWelcomeDlg">1</Publish> </UI> </Fragment> </Wix> The relevant portion of my Directories.wxs: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> <Fragment> <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="DATAFOLDER" Name="My_Data"> <Component Id="DataFolderComponent" Guid="YOUR_GUID_HERE" KeyPath="yes" NeverOverwrite="no" Permanent="no" Transitive="no" Win64="no" Location="either"> <CreateFolder/> </Component> <Component Id="DataFolderRegistry" Guid="YOUR_GUID_HERE"> <RegistryValue Root="HKLM" Key="SOFTWARE\My Software" Name="Data_Location" Action="write" Type="string" Value="[DATAFOLDER]"/> </Component> <Directory Id="LOGSFOLDER" Name="Logs"> <Component Id="LogsFolderComponent" Guid="YOUR_GUID_HERE" SharedDllRefCount="no" KeyPath="yes" NeverOverwrite="no" Permanent="no" Transitive="no" Win64="no" Location="either"> <CreateFolder/> </Component> </Directory> </Directory> <Directory Id="SERVERDATAFOLDER" Name="My_Data"> <Component Id="ServerDataFolderRegistry" Guid="YOUR_GUID_HERE"> <RegistryValue Root="HKLM" Key="SOFTWARE\My Software" Name="Server_Data_Location" KeyPath="yes" Action="write" Type="string" Value="[SERVERDATAFOLDER]" /> </Component> <Directory Id="SERVERUPDATESFOLDER" Name="Updates"> <Directory Id="AUTOLAUNCHERUPDATEFOLDER" Name="Auto Launcher"> <Component Id="ALUpdateFolder" Guid="YOUR_GUID_HERE" KeyPath="yes" NeverOverwrite="no" Permanent="no" Transitive="no" Win64="no" Location="either"> <CreateFolder /> </Component> </Directory> <Directory Id="AUTOUPDATERUPDATEFOLDER" Name="Auto Updater"> <Component Id="AUUpdateFolder" Guid="YOUR_GUID_HERE" KeyPath="yes" NeverOverwrite="no" Permanent="no" Transitive="no" Win64="no" Location="either"> <CreateFolder /> </Component> </Directory> <Directory Id="AUTODOWNLOADERUPDATEFOLDER" Name="Auto Downloader"> <Component Id="ADUpdateFolder" Guid="YOUR_GUID_HERE" KeyPath="yes" NeverOverwrite="no" Permanent="no" Transitive="no" Win64="no" Location="either"> <CreateFolder /> </Component> </Directory> </Directory> </Directory> <Directory Id="ProgramFilesFolder"> <Directory Id="PROGRAMFOLDER" Name="My Program Software"> <Component Id="MyFolder" Guid=" YOUR_GUID_HERE " SharedDllRefCount="no" KeyPath="yes" NeverOverwrite="no" Permanent="no" Transitive="no" Win64="no" Location="either"> <CreateFolder /> </Component> <Component Id="MyFolderRegistry" Guid=" YOUR_GUID_HERE "> <RegistryValue Root="HKLM" Key="SOFTWARE\My Software" Name="Program_Location" Action="write" Type="string" Value="[PROGRAMFOLDER]"/> </Component> <Directory Id="AUTOLAUNCHERFOLDER" Name="Jayhawk Auto Launcher"> <Directory Id="AUTOLAUNCHERICONSFOLDER" Name="Icons"/> </Directory> <Directory Id="AUTOUPDATERFOLDER" Name="Auto Updater" /> <Directory Id="AUTODOWNLOADERFOLDER" Name="Auto Downloader" /> </Directory> </Directory> . . . . . </Directory> </Fragment> </Wix> MyInstallDirDlg.wxs: <?xml version="1.0" encoding="utf-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> <Fragment> <UI> <Dialog Id="MyInstallDirDlg" Width="370" Height="270" Title="!(loc.MyInstallDirDlg_Title)" TrackDiskSpace="yes"> <Control Id="Back" Type="PushButton" X="192" Y="243" Width="56" Height="17" Text="!(loc.WixUIBack)" /> <Control Id="Next" Type="PushButton" X="248" Y="243" Width="56" Height="17" Default="yes" Text="!(loc.WixUINext)"> <Subscribe Event="SelectionNoItems" Attribute="Enabled" /> </Control> <Control Id="Cancel" Type="PushButton" X="304" Y="243" Width="56" Height="17" Cancel="yes" Text="!(loc.WixUICancel)"> <Publish Event="SpawnDialog" Value="CancelDlg">1</Publish> </Control> <Control Id="BannerBitmap" Type="Bitmap" X="0" Y="0" Width="370" Height="44" TabSkip="no" Text="!(loc.MyInstallDirDlgBannerBitmap)" /> <Control Id="BannerLine" Type="Line" X="0" Y="44" Width="370" Height="0" /> <Control Id="BottomLine" Type="Line" X="0" Y="234" Width="370" Height="2" /> <Control Id="Description" Type="Text" X="25" Y="23" Width="280" Height="15" Transparent="yes" NoPrefix="yes" Text="!(loc.MyInstallDirDlgDescription)" /> <Control Id="Title" Type="Text" X="15" Y="6" Width="210" Height="15" Transparent="yes" NoPrefix="yes" Text="!(loc.MyInstallDirDlgTitle)" /> <Control Id="InstallLocationLabel" Type="Text" X="10" Y="50" Width="345" Height="10" Text="!(loc.MyInstallDirDlgInstallLocationLabel)"> <Condition Action="hide">Installed</Condition> </Control> <Control Id="InstallLocation" Type="PathEdit" X="10" Y="67" Width="281" Height="20" Property="_InstallDirBrowserProperty" Indirect="yes"> <Condition Action="hide">Installed</Condition> </Control> <Control Id="InstallBrowse" Type="PushButton" X="296" Y="69" Width="66" Height="17" Text="!(loc.MyInstallDirDlgBrowse)"> <Publish Property="_BrowseProperty" Value="[_InstallDirBrowserProperty]" Order="1">1</Publish> <Publish Event="SpawnDialog" Value="BrowseDlg" Order="2">1</Publish> <Publish Event="SetTargetPath" Value="[_BrowseProperty]" Order="3">1</Publish> <Condition Action="hide">Installed</Condition> <Condition Action="disable">Installed</Condition> </Control> <Control Type="Line" Id="LineDivider1" Width="370" Height="2" X="0" Y="108" /> <Control Id="LocalJSDLocationLabel" Type="Text" X="10" Y="114" Width="345" Height="10" Text="!(loc.MyInstallDirDlgLocalJSDLocationLabel)"> <Condition Action="hide">Installed</Condition> </Control> <Control Id="LocalJSDLocation" Type="PathEdit" X="10" Y="131" Width="281" Height="20" Property="_LocalJSDDirBrowserProperty" Indirect="yes"> <Condition Action="hide">Installed</Condition> </Control> <Control Id="LocalJSDBrowse" Type="PushButton" X="296" Y="133" Width="66" Height="17" Text="!(loc.MyInstallDirDlgBrowse)"> <Publish Property="_BrowseProperty" Value="[_LocalJSDDirBrowserProperty]" Order="1">1</Publish> <Publish Event="SpawnDialog" Value="BrowseDlg" Order="2">1</Publish> <Publish Event="SetTargetPath" Value="[_BrowseProperty]" Order="3">1</Publish> <Condition Action="hide">Installed</Condition> <Condition Action="disable">Installed</Condition> </Control> <Control Type="Line" Id="LineDivider2" Width="370" Height="2" X="0" Y="172" /> <Control Id="ServerJSDLocationLabel" Type="Text" X="10" Y="178" Width="345" Height="10" Text="!(loc.MyInstallDirDlgServerJSDLocationLabel)"> <Condition Action="hide">Installed</Condition> </Control> <Control Id="ServerJSDLocation" Type="PathEdit" X="10" Y="195" Width="281" Height="20" Property="_ServerJSDDirBrowserProperty" Indirect="yes"> <Condition Action="hide">Installed</Condition> </Control> <Control Id="ServerJSDBrowse" Type="PushButton" X="296" Y="197" Width="66" Height="17" Text="!(loc.MyInstallDirDlgBrowse)"> <Publish Property="_BrowseProperty" Value="[_ServerJSDDirBrowserProperty]" Order="1">1</Publish> <Publish Event="SpawnDialog" Value="BrowseDlg" Order="2">1</Publish> <Publish Event="SetTargetPath" Value="[_BrowseProperty]" Order="3">1</Publish> <Condition Action="hide">Installed</Condition> <Condition Action="disable">Installed</Condition> </Control> </Dialog> </UI> </Fragment> </Wix> Install Log: (UNKNOWN) Action 11:06:51: WelcomeDlg. (UNKNOWN) Action start 11:06:51: WelcomeDlg. (UNKNOWN) Action 11:06:51: WelcomeDlg. Dialog created (CLIENT) MSI (c) (58:14) [11:06:51:374]: Note: 1: 2205 2: 3: _RemoveFilePath (CLIENT) MSI (c) (58:14) [11:06:51:389]: PROPERTY CHANGE: Modifying CostingComplete property. Its current value is '0'. Its new value: '1'. (CLIENT) MSI (c) (58:14) [11:06:51:389]: Note: 1: 2205 2: 3: BindImage (CLIENT) MSI (c) (58:14) [11:06:51:389]: Note: 1: 2205 2: 3: ProgId (CLIENT) MSI (c) (58:14) [11:06:51:389]: Note: 1: 2205 2: 3: PublishComponent (CLIENT) MSI (c) (58:14) [11:06:51:389]: Note: 1: 2205 2: 3: SelfReg (CLIENT) MSI (c) (58:14) [11:06:51:389]: Note: 1: 2205 2: 3: Extension (CLIENT) MSI (c) (58:14) [11:06:51:389]: Note: 1: 2205 2: 3: Font (CLIENT) MSI (c) (58:14) [11:06:51:389]: Note: 1: 2205 2: 3: Class (CLIENT) MSI (c) (58:14) [11:06:51:389]: Note: 1: 2205 2: 3: Icon (CLIENT) MSI (c) (58:14) [11:06:51:389]: Note: 1: 2205 2: 3: TypeLib (CLIENT) MSI (c) (58:14) [11:06:51:389]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:06:53:749]: PROPERTY CHANGE: Adding _InstallDirBrowserProperty property. Its value is 'PROGRAMFOLDER'. (CLIENT) MSI (c) (58:70) [11:06:53:749]: PROPERTY CHANGE: Adding _LocalJSDDirBrowserProperty property. Its value is 'DATAFOLDER'. (CLIENT) MSI (c) (58:70) [11:06:53:749]: PROPERTY CHANGE: Adding _ServerJSDDirBrowserProperty property. Its value is 'SERVERDATAFOLDER'. (CLIENT) MSI (c) (58:70) [11:06:53:749]: Note: 1: 2205 2: 3: Error (CLIENT) MSI (c) (58:70) [11:06:53:749]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2898 (UNKNOWN) Info 2898.For WixUI_Font_Title textstyle, the system created a 'Tahoma' font, in 0 character set, of 14 pixels height. (UNKNOWN) Action 11:06:53: MyInstallDirDlg. Dialog created (CLIENT) MSI (c) (58:70) [11:06:54:249]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:06:54:749]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:06:55:249]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:06:55:749]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:06:56:264]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:06:56:764]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:06:57:030]: PROPERTY CHANGE: Adding _BrowseProperty property. Its value is 'DATAFOLDER'. (CLIENT) MSI (c) (58:70) [11:06:57:046]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explore r 3: 2 (UNKNOWN) Action 11:06:57: BrowseDlg. Dialog created (CLIENT) MSI (c) (58:70) [11:07:01:249]: PROPERTY CHANGE: Modifying DATAFOLDER property. Its current value is 'c:\My_Data\'. Its new value: 'c:\My_Data2\'. (CLIENT) MSI (c) (58:70) [11:07:01:327]: PROPERTY CHANGE: Modifying LOGSFOLDER property. Its current value is 'c:\My_Data\Logs\'. Its new value: 'c:\My_Data2\Logs\'. (CLIENT) MSI (c) (58:70) [11:07:01:327]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:07:01:811]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:07:02:311]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:07:02:811]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:07:03:311]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:07:03:811]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:07:04:311]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:07:04:811]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:07:05:249]: PROPERTY CHANGE: Modifying SERVERDATAFOLDER property. Its current value is 'c:\My_Server_Data\'. Its new value: 'c:\My_Server_Data3\'. (CLIENT) MSI (c) (58:70) [11:07:05:311]: Note: 1: 2727 2: (UNKNOWN) Action 11:07:05: VerifyReadyDlg. Dialog created (CLIENT) MSI (c) (58:70) [11:07:05:842]: Note: 1: 2727 2: (CLIENT) MSI (c) (58:70) [11:07:06:342]: Note: 1: 2727 2: (UNKNOWN) Action ended 11:07:06: WelcomeDlg. Return value 1. (CLIENT) MSI (c) (58:A4) [11:07:06:342]: Doing action: ProgressDlg (CLIENT) MSI (c) (58:A4) [11:07:06:342]: Note: 1: 2205 2: 3: ActionText (UNKNOWN) Action 11:07:06: ProgressDlg. (UNKNOWN) Action start 11:07:06: ProgressDlg. (UNKNOWN) Action 11:07:06: ProgressDlg. Dialog created (UNKNOWN) Action ended 11:07:06: ProgressDlg. Return value 1. (CLIENT) MSI (c) (58:A4) [11:07:06:358]: Doing action: ExecuteAction (CLIENT) MSI (c) (58:A4) [11:07:06:358]: Note: 1: 2205 2: 3: ActionText (UNKNOWN) Action 11:07:06: ExecuteAction. (UNKNOWN) Action start 11:07:06: ExecuteAction. (CLIENT) MSI (c) (58:A4) [11:07:06:358]: PROPERTY CHANGE: Adding SECONDSEQUENCE property. Its value is '1'. (CLIENT) MSI (c) (58:A4) [11:07:06:405]: Grabbed execution mutex. (CLIENT) MSI (c) (58:A4) [11:07:06:405]: Incrementing counter to disable shutdown. Counter after increment: 0 (CLIENT) MSI (c) (58:A4) [11:07:06:405]: Switching to server: PROGRAMFOLDER="c:\Program Files (x86)\My Program Software\" DATAFOLDER="c:\My_Data2\" LOGSFOLDER="c:\My_Data2\Logs\" SERVERDATAFOLDER="c:\My_Data3\" AUTOLAUNCHERUPDATEFOLDER="c:\My_Data\Updates\Auto Launcher\" AUTOUPDATERUPDATEFOLDER="c:\My_Data\Updates\Auto Updater\" AUTODOWNLOADERUPDATEFOLDER="c:\My_Data\Updates\Auto Downloader\" AUTOLAUNCHERFOLDER="c:\Program Files (x86)\My Program Software\Auto Launcher\" AUTOLAUNCHERICONSFOLDER="C:\Program Files (x86)\My Program Software\Auto Launcher\Icons\" AUTOUPDATERFOLDER="C:\Program Files (x86)\My Program Software\Auto Updater\" AUTODOWNLOADERFOLDER="C:\Program Files (x86)\My Program Software\Auto Downloader\" TARGETDIR="c:\" SERVERUPDATESFOLDER="c:\My_Data\Updates\" CURRENTDIRECTORY="C:\Windows\system32" CLIENTUILEVEL="0" CLIENTPROCESSID="3416" USERNAME="TestUser" SOURCE |
|
From: Phill H. <pho...@ri...> - 2015-07-22 20:59:22
|
I think it would be advisable to follow the one-resource-per-component pattern. http://stackoverflow.com/questions/1602831/wix-one-file-per-component-or-several-files-per-component -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-deprecated-Difxapp-Component-Installation-condition-tp7600925p7600926.html Sent from the wix-users mailing list archive at Nabble.com. |
|
From: Marc B. <mbe...@ma...> - 2015-07-22 18:27:40
|
Thanks for the response, the issue was in my KeyPath file set. I had put my
'MainDrv64.sys' file as the key path in the component, changing it to the
INF allowed the installation to go through even though the hardware is not
present.
Here is my full component in case anyone has the same issue.
<Component Id='MainDrv64' Guid='f02c999a-8699-4499-9d99-999999999999'
Win64="yes">
<File Id='MainDrv64.sys' Name='MainDrv64.sys' DiskId='1'
Source='MainDrv64.sys' KeyPath='no' />
<File Id='OtherDrv64.sys' Name='OtherDrv64.sys' DiskId='1'
Source='OtherDrv64.sys' KeyPath='no' />
<File Id='MainDrv64.inf' Name='MainDrv64.inf' DiskId='1'
Source='MainDrv64.inf' KeyPath='yes'/>
<File Id='MainDrv64.cat' Name='MainDrv64.cat' DiskId='1'
Source='MainDrv64.cat' KeyPath='no'/>
<difx:Driver AddRemovePrograms="no" Legacy="yes" PlugAndPlayPrompt="no"
Sequence='1' />
</Component>
-----Original Message-----
From: Phill Hogland [mailto:pho...@ri...]
Sent: July-22-2015 12:59 PM
To: wix...@li...
Subject: Re: [wix-users] (deprecated) Difxapp Component Installation
condition
I use the WixDifxAppExtension to install multiple drivers in configurations
where in most cases the hardware will not exist, because they are different
types of printer drivers and no hardware, or one model of printer is
expected. Maybe the difference is related to the DifxApp flags. In my
Component which includes the INF file as the keypath, I also have:
<difx:Driver AddRemovePrograms="no" PlugAndPlayPrompt="no" />
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Difxapp-Compon
ent-Installation-condition-tp7600921p7600924.html
Sent from the wix-users mailing list archive at Nabble.com.
----------------------------------------------------------------------------
--
_______________________________________________
WiX-users mailing list
WiX...@li...
https://lists.sourceforge.net/lists/listinfo/wix-users
|
|
From: Phill H. <pho...@ri...> - 2015-07-22 17:07:48
|
I use the WixDifxAppExtension to install multiple drivers in configurations where in most cases the hardware will not exist, because they are different types of printer drivers and no hardware, or one model of printer is expected. Maybe the difference is related to the DifxApp flags. In my Component which includes the INF file as the keypath, I also have: <difx:Driver AddRemovePrograms="no" PlugAndPlayPrompt="no" /> -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Difxapp-Component-Installation-condition-tp7600921p7600924.html Sent from the wix-users mailing list archive at Nabble.com. |
|
From: Marc B. <mbe...@ma...> - 2015-07-22 16:44:49
|
Hello All, I am using Difxapp for the first time, my installation is successful as long as the hardware I am installing it present in the system. I searched and can't find an answer to my question, maybe my key words are incorrect. Please let me know if this is possible. The MSI I have installs a driver and other applications. Because of different possibilities, the hardware may in some cases not be present in the system. When this is the case my MSI fails the installation and Rolls back. Is it possible to ignore the success state of a specific component (in this case the one responsible for installing the device drive) to allow the installation to be successful regardless of whether the hardware is present in the system or not? Here is the solution I have in mind: Write a CA to scan the system for the device and attach this to a property and install the component based on the property's value. Is there a better way? Thanks for the advice, Marc |
|
From: Rob M. <ro...@fi...> - 2015-07-22 16:44:09
|
This mailing list has moved. Please sign up for the wix...@li... mailing list. More information can be found here: https://www.firegiant.com/blog/2015/7/21/new-wix-mailing-lists/ |
|
From: Phill H. <pho...@ri...> - 2015-07-22 12:50:30
|
My build process creates a bundle output folder tree with the sub folder
"x64" and "x86" under which there are platform specific driver packages:
bundle.exe
MSI1_Folder
MSI2_Folder
x64
Driver1Folder
Driver2Folder
x86
Driver1Folder
Driver2Folder
I have a situation where I need to create a MSI package which will include
the above Bundle output tree, so that these bundle files are installed to a
staging location as part of another bundle chain. Yesterday as I was
creating the MSI package to deploy the bundle files, and I encountered ICE99
"The directory name: x64 is the same as one of the MSI Public Properties
and can cause unforeseen side effects."
So yesterday I commented out those files and worked on a different aspect of
the project while I researched the issue. I did not find in the MSI
Property Reference
<https://msdn.microsoft.com/en-us/library/aa370905(v=vs.85).aspx> a
property of the same name.
Today I removed the comment indicators that I had used to hide the problem
and recompiled and now I never get the ICE99 error. I considered changing
the folder name to something like "x64_" but making such a change will have
a massive impact on many projects throughout my build process.
How important is it to make this change, given that the ICE99 is no longer
being reported, and we have gone through several release cycles using the
build process which produces the above output tree for all of our bundles?
Is this a real problem that I should address?
--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Advice-ICE99-duplicate-MSI-property-and-Directory-name-tp7600920.html
Sent from the wix-users mailing list archive at Nabble.com.
|
|
From: Phill H. <pho...@ri...> - 2015-07-22 12:15:29
|
"Util RegistrySearch has an attribute Winb64 that seems to be no by default. If this is set to Yes, Would it mean it would look in the 32 bit registry on 32bit OS and 64bit registry on 64 bit OS ? " Yes. but the attribute is RegistrySearch/@Win64. In the default situation where it is no or does not exist, I think the OS "redirects" registry access based on the bitness of the bundle.exe, which today is always a 32 bit bundle.exe. (There is dev discussion about creating a 64 bit version of Burn in a future release.) When RegistrySearch/@Win64='yes' the OS redirection, which would normally take place, is bypassed and the 64 bit registry is used. Generally I only provide this attribute when I specifically need to look for a registry key in the 64 bit area from my Burn bundle. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Util-RegistrySearch-Element-and-Win64-attribute-tp7584914p7600918.html Sent from the wix-users mailing list archive at Nabble.com. |
|
From: gapearce <mr_...@ya...> - 2015-07-22 04:07:42
|
Thanks for the reply Phil, I am now trying to figure out how that file vanishes (actually 'those files' - my tester has been able to cause this on a few VMs!?) Any ideas why this could happen (besides tampering?). These machines may be localized in different languages, too, but my tester insists that it all happens in English. Thanks again! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/upgrade-fails-with-1612-error-tp7600750p7600915.html Sent from the wix-users mailing list archive at Nabble.com. |
|
From: Sarvagya P. <sar...@gm...> - 2015-07-22 04:00:22
|
I have written a small program that will be installing the program in Program Files folder. In code, i have used pdf file, but in reality there will be an executable. The installer once installed will write logs in the folder created in LocalAppDataFolder and a custom action created in C++ will create a config file for that executable in same folder. Here is the link to my sample program => http://pastebin.com/TCmQNRsi But when I compile this program, I get following error: 1. Error 1 ICE38: Component SecondFile installs to user profile. It must use a registry key under HKCU as its KeyPath, not a file. E:\Sarvagya\LearningStuffs\ArkoInstaller\ArkoInstaller\Product.wxs 35 2. Error 2 ICE64: The directory PROGRAMLOCALFOLDER is in the user profile but is not listed in the RemoveFile table. E:\Sarvagya\LearningStuffs\ArkoInstaller\ArkoInstaller\Product.wxs 21 3. Warning 3 ICE91: The file 'Insurance_Claim_Form.pdf' will be installed to the per user directory 'PROGRAMLOCALFOLDER' that doesn't vary based on ALLUSERS value. This file won't be copied to each user's profile even if a per machine installation is desired. E:\Sarvagya\LearningStuffs\ArkoInstaller\ArkoInstaller\Product.wxs 36 But once I use CommonAppDataFolder insted of LocalAppDataFolder, it compiles correctly. Please correct me where I'm doing wrong. Thank you -- *Sarvagya Pant* *Kathmandu, Nepal* *+9779803468257* |
|
From: Edwin C. <eg...@gm...> - 2015-07-21 23:34:14
|
I'm using WixStandardBootstrapperApplication.HyperlinkSidebarLicense in my burn bundle. I have localized strings for a few languages. I'm looking into a bug reported against our Spanish localization. The expectation is that when the Alt + A is pressed, the focus would be received by the EULA checkbox and it would become selected. Instead, the EULA checkbox receives focus but it never becomes selected. The localized string begins as <String Id="InstallAcceptCheckbox">&Acepto ... I was trying to read the burn source code to understand how the acceleration key combination is setup based on what exists in the localized .wxl files but I have to admit I'm a little lost. It appears to me that burn doesn't parse the strings at all so that Windows API itself sets up the acceleration key combo itself. Is that accurate? If so, then I assume I'm doing something wrong but I don't know what it might be. The acceleration key for English works as expected and it begins as <String Id="InstallAcceptCheckbox">I &agree ... Is this simply a case sensitivity issue? I don't think so as I thought I tried using Alt + Shift + A with no change. -- Edwin G. Castro |
|
From: Moore, O. M. (MSFC-ER43)[MITS] <ric...@na...> - 2015-07-16 16:18:31
|
This is my first time on this list, so I am assuming I should reply to your email.
Here is the code that establishes the association with files with "vts" suffix with the application executable. This allows the user to double-click on the file which opens the app.
<!-- Establish file suffix-VTASC.exe association -->
<ProgId Id='VTASCModelFile' Description='VTASC File'>
<Extension Id='vts' ContentType='application/vts'>
<Verb Id='open' Command='Open' TargetFile='filABB38C272D0DDEA9627E512137AD83F6' Argument='"%1"' />
</Extension>
</ProgId>
Changing to perUser seems to have disallowed the above code to work.
-----Original Message-----
From: Rob Mensching [mailto:ro...@fi...]
Sent: Thursday, July 16, 2015 10:49 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] File extension association
What does this part mean "now the association between the application and its model file is no longer established at installation"?
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/
-----Original Message-----
From: Moore, Odric M. (MSFC-ER43)[MITS] [mailto:ric...@na...]
Sent: Thursday, July 16, 2015 7:22 AM
To: wix...@li...
Subject: [WiX-users] File extension association
I have a WiX 3.7 installation package that is operating fine using perMachine IntallScope. I want to change the installation so that it can be accomplished without admin privilege.
Changing to perUser has accomplished that, but now the association between the application and its model file is no longer established at installation.
Is this something that is not permitted under perUser?
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
WiX-users mailing list
WiX...@li...
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
WiX-users mailing list
WiX...@li...
https://lists.sourceforge.net/lists/listinfo/wix-users
|
|
From: boroda <bo....@ma...> - 2015-07-16 16:17:08
|
I think a plaintext of logs looks better
The first installation
----------------------------
[0D44:0D48][2015-07-16T06:55:45]i001: Burn v3.9.1006.0, Windows v6.1 (Build 7600: Service Pack 0), path: C:\Users\admin\Desktop\OLD.exe, cmdline: ''
[0D44:0D48][2015-07-16T06:55:45]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\admin\AppData\Local\Temp\OLD_20150716065545.log'
[0D44:0D48][2015-07-16T06:55:45]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\admin\Desktop\OLD.exe'
[0D44:0D48][2015-07-16T06:55:45]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\admin\Desktop\'
[0D44:0D48][2015-07-16T06:55:45]i000: Setting string variable 'WixBundleName' to value 'OLD'
[0D44:0D5C][2015-07-16T06:55:45]i000: Setting version variable 'WixBundleFileVersion' to value '1.0.0.0'
[0D44:0D48][2015-07-16T06:55:45]i100: Detect begin, 2 packages
[0D44:0D48][2015-07-16T06:55:45]i101: Detected package: Driver, state: Absent, cached: None
[0D44:0D48][2015-07-16T06:55:45]i101: Detected package: Main, state: Absent, cached: None
[0D44:0D48][2015-07-16T06:55:45]i199: Detect complete, result: 0x0
[0D44:0D5C][2015-07-16T06:55:47]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1
[0D44:0D48][2015-07-16T06:55:47]i200: Plan begin, 2 packages, action: Install
[0D44:0D48][2015-07-16T06:55:47]w322: Skipping cross-scope dependency registration on package: Driver, bundle scope: PerUser, package scope: PerMachine
[0D44:0D48][2015-07-16T06:55:47]i000: Setting string variable 'WixBundleRollbackLog_Driver' to value 'C:\Users\admin\AppData\Local\Temp\OLD_20150716065545_0_Driver_rollback.log'
[0D44:0D48][2015-07-16T06:55:47]i000: Setting string variable 'WixBundleLog_Driver' to value 'C:\Users\admin\AppData\Local\Temp\OLD_20150716065545_0_Driver.log'
[0D44:0D48][2015-07-16T06:55:47]i000: Setting string variable 'WixBundleRollbackLog_Main' to value 'C:\Users\admin\AppData\Local\Temp\OLD_20150716065545_1_Main_rollback.log'
[0D44:0D48][2015-07-16T06:55:47]i000: Setting string variable 'WixBundleLog_Main' to value 'C:\Users\admin\AppData\Local\Temp\OLD_20150716065545_1_Main.log'
[0D44:0D48][2015-07-16T06:55:47]i201: Planned package: Driver, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: None
[0D44:0D48][2015-07-16T06:55:47]i201: Planned package: Main, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0D44:0D48][2015-07-16T06:55:47]i299: Plan complete, result: 0x0
[0D44:0D48][2015-07-16T06:55:47]i300: Apply begin
[0E3C:0E40][2015-07-16T06:55:51]i360: Creating a system restore point.
[0E3C:0E40][2015-07-16T06:56:02]i361: Created a system restore point.
[0D44:0D48][2015-07-16T06:56:02]i000: Caching bundle from: 'C:\Users\admin\AppData\Local\Temp\{a8347316-8cc4-4c79-af14-abe18415227f}\.be\OLD.exe' to: 'C:\Users\admin\AppData\Local\Package Cache\{a8347316-8cc4-4c79-af14-abe18415227f}\OLD.exe'
[0D44:0D48][2015-07-16T06:56:02]i320: Registering bundle dependency provider: {a8347316-8cc4-4c79-af14-abe18415227f}, version: 1.0.0.0
[0E3C:0E50][2015-07-16T06:56:03]i305: Verified acquired payload: Driver at path: C:\ProgramData\Package Cache\.unverified\Driver, moving to: C:\ProgramData\Package Cache\{65E6DDFD-6DFE-47A3-9DE1-D7889AFEE8F4}v1.0.0.0\driver.msi.
[0D44:0FC8][2015-07-16T06:56:03]i305: Verified acquired payload: Main at path: C:\Users\admin\AppData\Local\Package Cache\.unverified\Main, moving to: C:\Users\admin\AppData\Local\Package Cache\{75743671-AC88-4369-8F9D-2EA7269BDDF1}v1.0.0.0\Main.msi.
[0E3C:0E40][2015-07-16T06:56:03]i301: Applying execute package: Driver, action: Install, path: C:\ProgramData\Package Cache\{65E6DDFD-6DFE-47A3-9DE1-D7889AFEE8F4}v1.0.0.0\driver.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0D44:0D48][2015-07-16T06:56:05]i319: Applied execute package: Driver, result: 0x0, restart: None
[0D44:0D48][2015-07-16T06:56:05]i323: Registering package dependency provider: {75743671-AC88-4369-8F9D-2EA7269BDDF1}, version: 1.0.0.0, package: Main
[0D44:0D48][2015-07-16T06:56:05]i301: Applying execute package: Main, action: Install, path: C:\Users\admin\AppData\Local\Package Cache\{75743671-AC88-4369-8F9D-2EA7269BDDF1}v1.0.0.0\Main.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0D44:0D48][2015-07-16T06:56:07]i319: Applied execute package: Main, result: 0x0, restart: None
[0D44:0D48][2015-07-16T06:56:07]i325: Registering dependency: {a8347316-8cc4-4c79-af14-abe18415227f} on package provider: {75743671-AC88-4369-8F9D-2EA7269BDDF1}, package: Main
[0D44:0D48][2015-07-16T06:56:07]i399: Apply complete, result: 0x0, restart: None, ba requested restart: No
[0D44:0D48][2015-07-16T06:56:08]i500: Shutting down, exit code: 0x0
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: EulaAcceptCheckbox = 1
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleAction = 4
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleElevated = 1
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleFileVersion = 1.0.0.0
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleInstalled = 0
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleLog = C:\Users\admin\AppData\Local\Temp\OLD_20150716065545.log
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleLog_Driver = C:\Users\admin\AppData\Local\Temp\OLD_20150716065545_0_Driver.log
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleLog_Main = C:\Users\admin\AppData\Local\Temp\OLD_20150716065545_1_Main.log
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleManufacturer = Ya
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleName = OLD
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleOriginalSource = C:\Users\admin\Desktop\OLD.exe
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleOriginalSourceFolder = C:\Users\admin\Desktop\
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleProviderKey = {a8347316-8cc4-4c79-af14-abe18415227f}
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleRollbackLog_Driver = C:\Users\admin\AppData\Local\Temp\OLD_20150716065545_0_Driver_rollback.log
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleRollbackLog_Main = C:\Users\admin\AppData\Local\Temp\OLD_20150716065545_1_Main_rollback.log
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleTag =
[0D44:0D48][2015-07-16T06:56:08]i410: Variable: WixBundleVersion = 1.0.0.0
[0D44:0D48][2015-07-16T06:56:08]i007: Exit code: 0x0, restarting: No
Update bundle
----------------------------------------
[09A0:09B0][2015-07-16T06:56:13]i001: Burn v3.9.1006.0, Windows v6.1 (Build 7600: Service Pack 0), path: C:\Users\admin\Desktop\NEW.exe, cmdline: ''
[09A0:09B0][2015-07-16T06:56:13]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\admin\AppData\Local\Temp\OLD_20150716065613.log'
[09A0:09B0][2015-07-16T06:56:13]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\admin\Desktop\NEW.exe'
[09A0:09B0][2015-07-16T06:56:13]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\admin\Desktop\'
[09A0:09B0][2015-07-16T06:56:13]i000: Setting string variable 'WixBundleName' to value 'OLD'
[09A0:09A8][2015-07-16T06:56:13]i000: Setting version variable 'WixBundleFileVersion' to value '1.2.0.0'
[09A0:09B0][2015-07-16T06:56:13]i100: Detect begin, 2 packages
[09A0:09B0][2015-07-16T06:56:13]i102: Detected related bundle: {a8347316-8cc4-4c79-af14-abe18415227f}, type: Upgrade, scope: PerUser, version: 1.0.0.0, operation: MajorUpgrade
[09A0:09B0][2015-07-16T06:56:13]i103: Detected related package: {75743671-AC88-4369-8F9D-2EA7269BDDF1}, scope: PerUser, version: 1.0.0.0, language: 0 operation: MajorUpgrade
[09A0:09B0][2015-07-16T06:56:13]i101: Detected package: Driver, state: Present, cached: Complete
[09A0:09B0][2015-07-16T06:56:13]i101: Detected package: Main, state: Absent, cached: None
[09A0:09B0][2015-07-16T06:56:13]i199: Detect complete, result: 0x0
[09A0:09A8][2015-07-16T06:56:15]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1
[09A0:09B0][2015-07-16T06:56:15]i200: Plan begin, 2 packages, action: Install
[09A0:09B0][2015-07-16T06:56:15]w322: Skipping cross-scope dependency registration on package: Driver, bundle scope: PerUser, package scope: PerMachine
[09A0:09B0][2015-07-16T06:56:15]i000: Setting string variable 'WixBundleRollbackLog_Main' to value 'C:\Users\admin\AppData\Local\Temp\OLD_20150716065613_0_Main_rollback.log'
[09A0:09B0][2015-07-16T06:56:15]i000: Setting string variable 'WixBundleLog_Main' to value 'C:\Users\admin\AppData\Local\Temp\OLD_20150716065613_0_Main.log'
[09A0:09B0][2015-07-16T06:56:15]i201: Planned package: Driver, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[09A0:09B0][2015-07-16T06:56:15]i201: Planned package: Main, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[09A0:09B0][2015-07-16T06:56:15]i207: Planned related bundle: {a8347316-8cc4-4c79-af14-abe18415227f}, type: Upgrade, default requested: Absent, ba requested: Absent, execute: Uninstall, rollback: Install, dependency: None
[09A0:09B0][2015-07-16T06:56:15]i299: Plan complete, result: 0x0
[09A0:09B0][2015-07-16T06:56:15]i300: Apply begin
[09A0:09B0][2015-07-16T06:56:15]i000: Caching bundle from: 'C:\Users\admin\AppData\Local\Temp\{2402d947-89fe-45e4-ab6f-822eab4bf04d}\.be\NEW.exe' to: 'C:\Users\admin\AppData\Local\Package Cache\{2402d947-89fe-45e4-ab6f-822eab4bf04d}\NEW.exe'
[09A0:09B0][2015-07-16T06:56:15]i320: Registering bundle dependency provider: {2402d947-89fe-45e4-ab6f-822eab4bf04d}, version: 1.2.0.0
[09A0:060C][2015-07-16T06:56:15]i305: Verified acquired payload: Main at path: C:\Users\admin\AppData\Local\Package Cache\.unverified\Main, moving to: C:\Users\admin\AppData\Local\Package Cache\{BFE6E992-B7D1-4989-90C5-607A14FD27ED}v1.2.0.0\Main.msi.
[09A0:09B0][2015-07-16T06:56:15]i323: Registering package dependency provider: {BFE6E992-B7D1-4989-90C5-607A14FD27ED}, version: 1.2.0.0, package: Main
[09A0:09B0][2015-07-16T06:56:15]i301: Applying execute package: Main, action: Install, path: C:\Users\admin\AppData\Local\Package Cache\{BFE6E992-B7D1-4989-90C5-607A14FD27ED}v1.2.0.0\Main.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[09A0:09B0][2015-07-16T06:56:16]i319: Applied execute package: Main, result: 0x0, restart: None
[09A0:09B0][2015-07-16T06:56:16]i325: Registering dependency: {2402d947-89fe-45e4-ab6f-822eab4bf04d} on package provider: {BFE6E992-B7D1-4989-90C5-607A14FD27ED}, package: Main
[09A0:09B0][2015-07-16T06:56:16]i301: Applying execute package: {a8347316-8cc4-4c79-af14-abe18415227f}, action: Uninstall, path: C:\Users\admin\AppData\Local\Package Cache\{a8347316-8cc4-4c79-af14-abe18415227f}\OLD.exe, arguments: '"C:\Users\admin\AppData\Local\Package Cache\{a8347316-8cc4-4c79-af14-abe18415227f}\OLD.exe" -uninstall -quiet -burn.related.upgrade -burn.ancestors={2402d947-89fe-45e4-ab6f-822eab4bf04d}'
[09A0:09B0][2015-07-16T06:56:20]i319: Applied execute package: {a8347316-8cc4-4c79-af14-abe18415227f}, result: 0x0, restart: None
[09A0:09B0][2015-07-16T06:56:20]i399: Apply complete, result: 0x0, restart: None, ba requested restart: No
[09A0:09B0][2015-07-16T06:56:21]i500: Shutting down, exit code: 0x0
[09A0:09B0][2015-07-16T06:56:21]i410: Variable: EulaAcceptCheckbox = 1
[09A0:09B0][2015-07-16T06:56:21]i410: Variable: WixBundleAction = 4
[09A0:09B0][2015-07-16T06:56:21]i410: Variable: WixBundleElevated = 0
[09A0:09B0][2015-07-16T06:56:21]i410: Variable: WixBundleFileVersion = 1.2.0.0
[09A0:09B0][2015-07-16T06:56:21]i410: Variable: WixBundleInstalled = 0
[09A0:09B0][2015-07-16T06:56:21]i410: Variable: WixBundleLog = C:\Users\admin\AppData\Local\Temp\OLD_20150716065613.log
[09A0:09B0][2015-07-16T06:56:21]i410: Variable: WixBundleLog_Main = C:\Users\admin\AppData\Local\Temp\OLD_20150716065613_0_Main.log
[09A0:09B0][2015-07-16T06:56:21]i410: Variable: WixBundleManufacturer = Ya
[09A0:09B0][2015-07-16T06:56:21]i410: Variable: WixBundleName = OLD
[09A0:09B0][2015-07-16T06:56:21]i410: Variable: WixBundleOriginalSource = C:\Users\admin\Desktop\NEW.exe
[09A0:09B0][2015-07-16T06:56:21]i410: Variable: WixBundleOriginalSourceFolder = C:\Users\admin\Desktop\
[09A0:09B0][2015-07-16T06:56:21]i410: Variable: WixBundleProviderKey = {2402d947-89fe-45e4-ab6f-822eab4bf04d}
[09A0:09B0][2015-07-16T06:56:21]i410: Variable: WixBundleRollbackLog_Main = C:\Users\admin\AppData\Local\Temp\OLD_20150716065613_0_Main_rollback.log
[09A0:09B0][2015-07-16T06:56:21]i410: Variable: WixBundleTag =
[09A0:09B0][2015-07-16T06:56:21]i410: Variable: WixBundleVersion = 1.2.0.0
[09A0:09B0][2015-07-16T06:56:21]i007: Exit code: 0x0, restarting: No
Uninstallation bundle version 1.0.0.0
------------------------------------------------------
[0724:0314][2015-07-16T06:56:16]i001: Burn v3.9.1006.0, Windows v6.1 (Build 7600: Service Pack 0), path: C:\Users\admin\AppData\Local\Package Cache\{a8347316-8cc4-4c79-af14-abe18415227f}\OLD.exe, cmdline: '-uninstall -quiet -burn.related.upgrade -burn.ancestors={2402d947-89fe-45e4-ab6f-822eab4bf04d} -burn.embedded BurnPipe.{18116179-F6EB-46D6-A465-8DC7C79758BE} {14F20C72-C821-4BD9-9B6B-CA9B20DBBF80} 2464'
[0724:0314][2015-07-16T06:56:16]i003: This bundle is being run by a related bundle as type 'Upgrade'.
[0724:0314][2015-07-16T06:56:16]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\admin\AppData\Local\Temp\OLD_20150716065616.log'
[0724:06FC][2015-07-16T06:56:16]i000: Setting version variable 'WixBundleFileVersion' to value '1.0.0.0'
[0724:0314][2015-07-16T06:56:16]i100: Detect begin, 2 packages
[0724:0314][2015-07-16T06:56:16]i102: Detected related bundle: {2402d947-89fe-45e4-ab6f-822eab4bf04d}, type: Upgrade, scope: PerUser, version: 1.2.0.0, operation: None
[0724:0314][2015-07-16T06:56:16]i103: Detected related package: {BFE6E992-B7D1-4989-90C5-607A14FD27ED}, scope: PerUser, version: 1.2.0.0, language: 0 operation: Downgrade
[0724:0314][2015-07-16T06:56:16]i101: Detected package: Driver, state: Present, cached: Complete
[0724:0314][2015-07-16T06:56:16]i101: Detected package: Main, state: Obsolete, cached: Complete
[0724:0314][2015-07-16T06:56:16]i199: Detect complete, result: 0x0
[0724:0314][2015-07-16T06:56:16]i200: Plan begin, 2 packages, action: Uninstall
[0724:0314][2015-07-16T06:56:16]i214: Plan skipped related bundle: {2402d947-89fe-45e4-ab6f-822eab4bf04d}, type: Upgrade, because it was previously scheduled.
[0724:0314][2015-07-16T06:56:16]w322: Skipping cross-scope dependency registration on package: Driver, bundle scope: PerUser, package scope: PerMachine
[0724:0314][2015-07-16T06:56:16]i000: Setting string variable 'WixBundleRollbackLog_Driver' to value 'C:\Users\admin\AppData\Local\Temp\OLD_20150716065616_0_Driver_rollback.log'
[0724:0314][2015-07-16T06:56:16]i000: Setting string variable 'WixBundleLog_Driver' to value 'C:\Users\admin\AppData\Local\Temp\OLD_20150716065616_0_Driver.log'
[0724:0314][2015-07-16T06:56:16]i207: Planned related bundle: {2402d947-89fe-45e4-ab6f-822eab4bf04d}, type: Upgrade, default requested: None, ba requested: None, execute: None, rollback: None, dependency: None
[0724:0314][2015-07-16T06:56:16]i201: Planned package: Main, state: Obsolete, default requested: None, ba requested: None, execute: None, rollback: None, cache: No, uncache: Yes, dependency: Unregister
[0724:0314][2015-07-16T06:56:16]i201: Planned package: Driver, state: Present, default requested: Absent, ba requested: Absent, execute: Uninstall, rollback: Install, cache: No, uncache: Yes, dependency: None
[0724:0314][2015-07-16T06:56:16]i299: Plan complete, result: 0x0
[0724:0314][2015-07-16T06:56:16]i300: Apply begin
[0724:0314][2015-07-16T06:56:19]i326: Removed dependency: {a8347316-8cc4-4c79-af14-abe18415227f} on package provider: {75743671-AC88-4369-8F9D-2EA7269BDDF1}, package Main
[0B70:0ACC][2015-07-16T06:56:19]i301: Applying execute package: Driver, action: Uninstall, path: (null), arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0724:0314][2015-07-16T06:56:20]i319: Applied execute package: Driver, result: 0x0, restart: None
[0724:0314][2015-07-16T06:56:20]i351: Removing cached package: Main, from path: C:\Users\admin\AppData\Local\Package Cache\{75743671-AC88-4369-8F9D-2EA7269BDDF1}v1.0.0.0\
[0B70:0ACC][2015-07-16T06:56:20]i351: Removing cached package: Driver, from path: C:\ProgramData\Package Cache\{65E6DDFD-6DFE-47A3-9DE1-D7889AFEE8F4}v1.0.0.0\
[0724:0314][2015-07-16T06:56:20]i330: Removed bundle dependency provider: {a8347316-8cc4-4c79-af14-abe18415227f}
[0724:0314][2015-07-16T06:56:20]i352: Removing cached bundle: {a8347316-8cc4-4c79-af14-abe18415227f}, from path: C:\Users\admin\AppData\Local\Package Cache\{a8347316-8cc4-4c79-af14-abe18415227f}\
[0724:0314][2015-07-16T06:56:20]i399: Apply complete, result: 0x0, restart: None, ba requested restart: No
[0724:0314][2015-07-16T06:56:20]i500: Shutting down, exit code: 0x0
[0724:0314][2015-07-16T06:56:20]i410: Variable: WixBundleAction = 3
[0724:0314][2015-07-16T06:56:20]i410: Variable: WixBundleElevated = 1
[0724:0314][2015-07-16T06:56:20]i410: Variable: WixBundleFileVersion = 1.0.0.0
[0724:0314][2015-07-16T06:56:20]i410: Variable: WixBundleInstalled = 1
[0724:0314][2015-07-16T06:56:20]i410: Variable: WixBundleLog = C:\Users\admin\AppData\Local\Temp\OLD_20150716065616.log
[0724:0314][2015-07-16T06:56:20]i410: Variable: WixBundleLog_Driver = C:\Users\admin\AppData\Local\Temp\OLD_20150716065616_0_Driver.log
[0724:0314][2015-07-16T06:56:20]i410: Variable: WixBundleManufacturer = Ya
[0724:0314][2015-07-16T06:56:20]i410: Variable: WixBundleName = OLD
[0724:0314][2015-07-16T06:56:20]i410: Variable: WixBundleOriginalSource = C:\Users\admin\Desktop\OLD.exe
[0724:0314][2015-07-16T06:56:20]i410: Variable: WixBundleOriginalSourceFolder = C:\Users\admin\Desktop\
[0724:0314][2015-07-16T06:56:20]i410: Variable: WixBundleProviderKey = {a8347316-8cc4-4c79-af14-abe18415227f}
[0724:0314][2015-07-16T06:56:20]i410: Variable: WixBundleRollbackLog_Driver = C:\Users\admin\AppData\Local\Temp\OLD_20150716065616_0_Driver_rollback.log
[0724:0314][2015-07-16T06:56:20]i410: Variable: WixBundleTag =
[0724:0314][2015-07-16T06:56:20]i410: Variable: WixBundleVersion = 1.0.0.0
[0724:0314][2015-07-16T06:56:20]i007: Exit code: 0x0, restarting: No
With regards,
Andrew.
>Четверг, 16 июля 2015, 8:54 -07:00 от "Rob Mensching-7 [via Windows Installer XML (WiX) toolset]" <ml-...@n2...>:
>
>What does the bundle log file show?
>
>_______________________________________________________________
> FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/
>
>-----Original Message-----
>From: boroda [mailto: [hidden email] ]
>Sent: Thursday, July 16, 2015 7:25 AM
>To: [hidden email]
>Subject: [WiX-users] «Bundle Uprgade issue: the same MSI in two bundles»
>
>Hello, guys.
>I have a problem. And the actions of bundle are not obvious.
>So, I have the follows packages:
>• MSI ‘MSI_A_v1’
>• MSI ‘MSI_B_v1’
>• Bundle Bv1, installs MSI_A_v1 and MSI_B_v1.
>• And MSI ‘MSI_A_v2’ (Major upgrade of ' MSI_A_v1', including changing
>Product Id)
>• Bundle Bv2 (the UpgradeCode is the same as the Bv1, but version is upper).
>Bundle Bv2 installs MSI_A_v2 and MSI_B_v1.
>
>My steps:
>1. Install Bundle Bv1
>2. Install Bundle Bv2.
>During the installation, MSI_A_v2 is updating MSI_A_v1 (it’s OK), MSI_B_v1 is doing nothing (it’s OK too), and Bv2 is deleting Bv1. It’s OK too, BUT the Bv1’s uninstallation also deletes MSI_B_v1! Why! Bv2 has link to MSI_B_v1, and the product MSI_B_v1 should remain on system. This is the main problem, after installation, the MSI_B_v1 is not on the system
>------------------------------------------------------------------------------
>Don't Limit Your Business. Reach for the Cloud.
>GigeNET's Cloud Solutions provide you with the tools and support that
>you need to offload your IT needs and focus on growing your business.
>Configured For All Businesses. Start Your Cloud Today.
>https://www.gigenetcloud.com/
>_______________________________________________
>WiX-users mailing list
>[hidden email]
>https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>----------------------------------------------------------------------
>If you reply to this email, your message will be added to the discussion below: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-Uprgade-issue-the-same-MSI-in-two-bundles-tp7600898p7600901.html
>To unsubscribe from «Bundle Uprgade issue: the same MSI in two bundles», click here .
>NAML
--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-Uprgade-issue-the-same-MSI-in-two-bundles-tp7600898p7600905.html
Sent from the wix-users mailing list archive at Nabble.com.
|
|
From: boroda <bo....@ma...> - 2015-07-16 16:02:29
|
oh, sorry, I completely forgot about the log files. logs are attached to the email. > > >What does the bundle log file show? > >_______________________________________________________________ > FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ > >-----Original Message----- >From: boroda [mailto: [hidden email] ] >Sent: Thursday, July 16, 2015 7:25 AM >To: [hidden email] >Subject: [WiX-users] «Bundle Uprgade issue: the same MSI in two bundles» > >Hello, guys. >I have a problem. And the actions of bundle are not obvious. >So, I have the follows packages: >• MSI ‘MSI_A_v1’ >• MSI ‘MSI_B_v1’ >• Bundle Bv1, installs MSI_A_v1 and MSI_B_v1. >• And MSI ‘MSI_A_v2’ (Major upgrade of ' MSI_A_v1', including changing >Product Id) >• Bundle Bv2 (the UpgradeCode is the same as the Bv1, but version is upper). >Bundle Bv2 installs MSI_A_v2 and MSI_B_v1. > >My steps: >1. Install Bundle Bv1 >2. Install Bundle Bv2. >During the installation, MSI_A_v2 is updating MSI_A_v1 (it’s OK), MSI_B_v1 is doing nothing (it’s OK too), and Bv2 is deleting Bv1. It’s OK too, BUT the Bv1’s uninstallation also deletes MSI_B_v1! Why! Bv2 has link to MSI_B_v1, and the product MSI_B_v1 should remain on system. This is the main problem, after installation, the MSI_B_v1 is not on the system >------------------------------------------------------------------------------ >Don't Limit Your Business. Reach for the Cloud. >GigeNET's Cloud Solutions provide you with the tools and support that >you need to offload your IT needs and focus on growing your business. >Configured For All Businesses. Start Your Cloud Today. >https://www.gigenetcloud.com/ >_______________________________________________ >WiX-users mailing list >[hidden email] >https://lists.sourceforge.net/lists/listinfo/wix-users > > >---------------------------------------------------------------------- >If you reply to this email, your message will be added to the discussion below: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-Uprgade-issue-the-same-MSI-in-two-bundles-tp7600898p7600901.html >To unsubscribe from «Bundle Uprgade issue: the same MSI in two bundles», click here . >NAML =?UTF-8?B?d2l4LnppcA==?= (63K) <http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/attachment/7600904/0/%3D%3FUTF-8%3FB%3Fd2l4LnppcA%3D%3D%3F%3D> -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-Uprgade-issue-the-same-MSI-in-two-bundles-tp7600898p7600904.html Sent from the wix-users mailing list archive at Nabble.com. |
|
From: Rob M. <ro...@fi...> - 2015-07-16 15:56:11
|
I think this only happens if you indicate to delete registry tree. You can definitely file the bug but this is probably one of those bugs where it won't get fixed until someone actually needs the fix. So don't file the bug expecting it to be fixed by itself. <smile/> _______________________________________________________________ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -----Original Message----- From: Edwin Castro [mailto:eg...@gm...] Sent: Thursday, July 16, 2015 8:18 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Possible Bug: RegDelete does not work properly with REG_KEY_32BIT on a 64-bit system I can't use semi-custom-actions for this particular piece of work because I need to call an API to get permission to create, delete, or modify these particular registry keys. I work at a security company where they have implemented additional security features through drivers that disallow normal interactions with certain resources. Otherwise, I would totally use the semi-custom-action approach. I use it right now to add rows to the RemoveFile table depending on whether we're uninstalling for an upgrade or not. In any case, RegDelete appears broken to me. At a minimum, the bitness should be incorporated into the RegOpen call. Should I file a bug to track? On Thu, Jul 16, 2015 at 7:01 AM, Phill Hogland <pho...@ri...> wrote: > FYI - I just implemented a semi-custom > <http://www.joyofsetup.com/2007/07/01/semi-custom-actions/> action > using a > similar implementation as I found in the WixGamingExtension which > calls WcaAddTempRecord on the Registry table, to allow MSI to manage > my registry change. The CA code (specifically the registry path) is > agnostic to WoW6432Node so that the CA can be built for either Win32 > or x64 and used in either a x86 or x64 MSI. I only needed to set > Component /@Win64="no" and MSI handles the redirection. > > The MSI packages are also built using the InstallerPlatform MSBuild > property to set the bitness of the MSI. For most of the Components I > never set Win64, but for this registry key setting Win64="no" was > needed to get MSI to redirect the the registry hive. > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Possible > -Bug-RegDelete-does-not-work-properly-with-REG-KEY-32BIT-on-a-64-bit-s > ystem-tp7600893p7600896.html Sent from the wix-users mailing list > archive at Nabble.com. > > > ---------------------------------------------------------------------- > -------- Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > _______________________________________________ > WiX-users mailing list > WiX...@li... > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Edwin G. Castro ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ WiX-users mailing list WiX...@li... https://lists.sourceforge.net/lists/listinfo/wix-users |
1985 messages has been excluded from this view by a project administrator.
