Re: [WiX-users] Burn SQL Express Install Fails 0x84b40000
SQL Express can be a pain to install silently, the trick is to run it from
the command line without the silent switch on until you are sure you have the
right parameters.
I suspect you will at least need to add the /IACCEPTSQLSERVERLICENSETERMS
parameter.
-Original Message-
From: Daniel Sniderman [mailto:dani...@magenic.com]
Sent: 21 March 2012 02:48
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Burn SQL Express Install Fails 0x84b4
I'm trying to use Burn to Chain a SQL Express Install with my application and
I'm getting what appears to be a generic error code - I can't find anything
specific as to what the actual failure is. If I run the install from the
command line with the same parameters it's failing...
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Bundle Name=BootstrapCMSNextAndSQLExpress Version=1.0.0.0
Manufacturer=Abbott Laboratories
UpgradeCode=b89ca7ba-9287-4041-b466-5f3ebb12647d
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense /
!--WixVariable Id=WixStdbaLicenseRtf Value=License.rtf /--
Chain
ExePackage Id=SQLServerExpress
Compressed=no
Name=SQLServerExpress
SourceFile=Binaries\SQLEXPR32_x86_ENU.exe
InstallCommand=/Action=Install
/INSTANCENAME=$(var.Instance) /FEATURES=SQLEngine, Replication /QS
RepairCommand=/ACTION=Repair
/INSTANCENAME=$(var.Instance)
UninstallCommand=/Action=Uninstall
/INSTANCENAME=$(var.Instance)
Vital=yes
/ExePackage
MsiPackage Id=CMSNext
SourceFile=$(var.SetupCMSNextWIX.TargetDir)SetupCMSNext.msi
Name=$(var.Name)
/MsiPackage
/Chain
/Bundle
/Wix
[0624:3F24][2012-03-20T21:15:00]: Burn v3.6.2221.0, path:
C:\TFS2010\CMSNext\CMS
Next\Branches\BuildAutomation\BootstrapCMSNextAndSQLExpress\bin\Debug\SetupCM
SNext.exe, cmdline: ''
[0624:3F24][2012-03-20T21:15:00]: Setting string variable 'WixBundleName' to
value 'BootstrapCMSNextAndSQLExpress'
[0624:3F24][2012-03-20T21:15:00]: Setting string variable 'WixBundleLog' to
value
'C:\Users\daniels\AppData\Local\Temp\BootstrapCMSNextAndSQLExpress_2012032021
1500.log'
[0624:3F24][2012-03-20T21:15:00]: Setting string variable
'WixBundleOriginalSource' to value 'C:\TFS2010\CMSNext\CMS
Next\Branches\BuildAutomation\BootstrapCMSNextAndSQLExpress\bin\Debug\SetupCM
SNext.exe'
[0624:3F24][2012-03-20T21:15:00]: Detect 2 packages
[0624:3F24][2012-03-20T21:15:00]: Detected related bundle:
{a6290142-ee0c-47b2-9a25-67b60fd4be2d}, scope: PerMachine, version: 1.0.0.0,
operation: None
[0624:3F24][2012-03-20T21:15:00]: Detected package: SQLServerExpress, state:
Absent, cached: No
[0624:3F24][2012-03-20T21:15:00]: Detected package: CMSNext, state: Absent,
cached: No
[0624:3F24][2012-03-20T21:15:00]: Detect complete, result: 0x0
[0624:3F24][2012-03-20T21:15:05]: Plan 2 packages, action: Install
[0624:3F24][2012-03-20T21:15:05]: Setting string variable
'WixBundleLog_SQLServerExpress' to value
'C:\Users\daniels\AppData\Local\Temp\BootstrapCMSNextAndSQLExpress_2012032021
1500_0_SQLServerExpress.log'
[0624:3F24][2012-03-20T21:15:05]: Setting string variable
'WixBundleRollbackLog_SQLServerExpress' to value
'C:\Users\daniels\AppData\Local\Temp\BootstrapCMSNextAndSQLExpress_2012032021
1500_0_SQLServerExpress_rollback.log'
[0624:3F24][2012-03-20T21:15:05]: Planned package: SQLServerExpress, state:
Absent, default requested: Present, ux requested: Present, execute: Install,
rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0624:3F24][2012-03-20T21:15:05]: Setting string variable
'WixBundleLog_CMSNext' to value
'C:\Users\daniels\AppData\Local\Temp\BootstrapCMSNextAndSQLExpress_2012032021
1500_1_CMSNext.log'
[0624:3F24][2012-03-20T21:15:05]: Setting string variable
'WixBundleRollbackLog_CMSNext' to value
'C:\Users\daniels\AppData\Local\Temp\BootstrapCMSNextAndSQLExpress_2012032021
1500_1_CMSNext_rollback.log'
[0624:3F24][2012-03-20T21:15:05]: Planned package: CMSNext, state: Absent,
default requested: Present, ux requested: Present, execute: Install,
rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0624:3F24][2012-03-20T21:15:05]: Plan complete, result: 0x0
[0624:3F24][2012-03-20T21:15:05]: Apply begin
[0624:3F24][2012-03-20T21:15:08]: Caching executable from:
'C:\TFS2010\CMSNext\CMS
Next\Branches\BuildAutomation\BootstrapCMSNextAndSQLExpress\bin\Debug\SetupCM
SNext.exe' to: 'C:\Users\daniels\AppData\Local\Package
Cache\{4dac6a09-c35c-403f-854b-0af65f3c61e5}\SetupCMSNext.exe'
[0624:3F24][2012-03-20T21:15:08]: Registering bundle dependency key:
{4dac6a09-c35c-403f-854b-0af65f3c61e5}, version 1.0.0.0
[0624:36A8][2012-03-20T21:15:09]: Moving payload from working path
'C:\Users\daniels\AppData\Local\Temp\{4dac6a09-c35c-403f-854b-0af65f3c61e5}\S
QLServerExpress' to path 'C:\Users\daniels\AppData\Local\Package
Re: [WiX-users] Burn blows up when upgrading a bundle with mixed privilege packages
Done. Thanks! What are your thoughts on using Burn like this to be both an installer and autoupdate? Good idea, bad idea...? Chris On Tue, Mar 20, 2012 at 9:51 PM, Rob Mensching r...@robmensching.com wrote: Please open a bug (with all this information) to track the issue. On Tue, Mar 20, 2012 at 7:38 AM, Chris Hynes ch...@foundry57.com wrote: I'm trying to put together a burn bundle with two msi packages. One is per user and one is per machine (there are actually 4 because the two msi's have 1 each for x32 and x64). Initial installation works fine. When I try to run a new burn .exe that would upgrade only the per user .msi but not the per machine msi, I get a error: 0x80070006 - The handle is invalid. The new .exe contains an upgrade version of the per user .msi and the old version of the per machine .msi. I would think that burn would install the upgrade of the per user msi and leave the per machine msi alone (since it is already the correct version). Based on the log, it seems to realize that it only needs to install the per user upgrade .msi, and starts installing. But then it thinks it should be elevated and blows up. See projects/log below. If more details about what I'm trying to do are useful -- this is for an installer/autoupdate package for a shell extension I'm developing. My idea right now is to use a single burn .exe for both installation and updating. It would contain (or download) all 4 msi's (one per machine for the actual extension, one per user for the client tools, multiply by 2 for x32 and x64 support). Since its a shell extension, the actual extension .dll must be installed per-machine. However, that part won't be updated frequently, and I'd like to be able to do a silent update when not updating the shell extension .dll (hence the per user installation of everything else). Initial installation would be easy -- the user would download the burn .exe and run it. Silent updates would be just as easy -- the app would check for an update, download the latest burn.exe and run it with silent command line args. Updating the shell extension would be a bit more tricky, as the app would need to know that and not pass the silent args so that the user would get a UAC prompt. I'm not sure if this is the best way to go about this -- if anyone has a better idea for the install/autoupdate, I'd love to hear it. I realize I'm on the bleeding edge with Burn here, but any help tracking down the issue would be very much appreciated. Having a simple silent auto update would be so cool and I'm close enough I can taste it. Thanks! Chris Hynes Foundry 57 --- PER USER PROJECT --- Product Id=* Name=$(var.ProductName) Language=1033 Version=$(var.ProductFullVersion) Manufacturer=$(var.ProductManufacturer) UpgradeCode=$(var.UpgradeId) Package InstallerVersion=200 Compressed=yes InstallPrivileges=limited InstallScope=perUser Manufacturer=$(var.ProductManufacturer) / --- PER MACHINE PROJECT --- Product Id=$(var.ProductId) Name=$(var.ProductName) Shell Extension Language=1033 Version=!(bind.FileVersion.ClickScanShellExtension) Manufacturer=$(var.ProductManufacturer) UpgradeCode=$(var.UpgradeId) Package InstallerVersion=200 Compressed=yes InstallPrivileges=elevated InstallScope=perMachine Manufacturer=$(var.ProductManufacturer) / --- BURN PROJECT --- Bundle Version=$(var.ProductFullVersion) DisableModify=yes Name=$(var.ProductName) Manufacturer=$(var.ProductManufacturer) UpgradeCode=33788ba7-5d04-4e29-b9b0-13f88ab8b81e BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense / Chain PackageGroupRef Id=Netfx4Client / !-- NOTE: .NET 4 installer requires MSI 3.1, but that is auto installed in XP SP3 and 2003 SP2, which are required -- MsiPackage SourceFile=..\MyAppSetup\bin\Release\MyApp-x86.msi InstallCondition=NOT VersionNT64 / MsiPackage SourceFile=..\MyAppSetup\bin\x64\Release\MyApp-x64.msi InstallCondition=VersionNT64 / MsiPackage SourceFile=..\MyAppShellExtensionSetup\bin\Release\MyAppShellExtension-x86.msi InstallCondition=NOT VersionNT64 / MsiPackage SourceFile=..\MyAppShellExtensionSetup\bin\x64\Release\MyAppShellExtension-x64.msi InstallCondition=VersionNT64 / /Chain /Bundle --- LOG OUTPUT --- [14EC:0B88][2012-03-20T07:16:55]: Burn v3.6.2719.0, path: C:\Dev\Foundry\MyApp\Build\Dist\MyAppSetup_0.9.0.exe, cmdline: '' [14EC:0B88][2012-03-20T07:16:55]: Setting string variable 'WixBundleLog' to value 'C:\Users\Chris\AppData\Local\Temp\MyApp_20120320071655.log' [14EC:0B88][2012-03-20T07:16:55]: Setting string variable 'WixBundleOriginalSource' to value 'C:\Dev\Foundry\MyApp\Build\Dist\MyAppSetup_0.9.0.exe' [14EC:0B88][2012-03-20T07:16:55]: Setting string variable 'WixBundleName' to value 'MyApp' [14EC:0B88][2012-03-20T07:16:55]: Detect 5
Re: [WiX-users] Burn SQL Express Install Fails 0x84b40000
PS: When you discover the correct set of parameters, let us know here.
There is a plan afoot to pre-bake the silent install of a bunch of well
known redists so you can use them by just doing PackageGroupRef Id=x at
the correct place in your Chain.
On Wed, Mar 21, 2012 at 3:33 AM, David Watson dwat...@sdl.com wrote:
SQL Express can be a pain to install silently, the trick is to run it from
the command line without the silent switch on until you are sure you have
the
right parameters.
I suspect you will at least need to add the /IACCEPTSQLSERVERLICENSETERMS
parameter.
-Original Message-
From: Daniel Sniderman [mailto:dani...@magenic.com]
Sent: 21 March 2012 02:48
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Burn SQL Express Install Fails 0x84b4
I'm trying to use Burn to Chain a SQL Express Install with my application
and
I'm getting what appears to be a generic error code - I can't find anything
specific as to what the actual failure is. If I run the install from the
command line with the same parameters it's failing...
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Bundle Name=BootstrapCMSNextAndSQLExpress Version=1.0.0.0
Manufacturer=Abbott Laboratories
UpgradeCode=b89ca7ba-9287-4041-b466-5f3ebb12647d
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense /
!--WixVariable Id=WixStdbaLicenseRtf Value=License.rtf /--
Chain
ExePackage Id=SQLServerExpress
Compressed=no
Name=SQLServerExpress
SourceFile=Binaries\SQLEXPR32_x86_ENU.exe
InstallCommand=/Action=Install
/INSTANCENAME=$(var.Instance) /FEATURES=SQLEngine, Replication /QS
RepairCommand=/ACTION=Repair
/INSTANCENAME=$(var.Instance)
UninstallCommand=/Action=Uninstall
/INSTANCENAME=$(var.Instance)
Vital=yes
/ExePackage
MsiPackage Id=CMSNext
SourceFile=$(var.SetupCMSNextWIX.TargetDir)SetupCMSNext.msi
Name=$(var.Name)
/MsiPackage
/Chain
/Bundle
/Wix
[0624:3F24][2012-03-20T21:15:00]: Burn v3.6.2221.0, path:
C:\TFS2010\CMSNext\CMS
Next\Branches\BuildAutomation\BootstrapCMSNextAndSQLExpress\bin\Debug\SetupCM
SNext.exe, cmdline: ''
[0624:3F24][2012-03-20T21:15:00]: Setting string variable 'WixBundleName'
to
value 'BootstrapCMSNextAndSQLExpress'
[0624:3F24][2012-03-20T21:15:00]: Setting string variable 'WixBundleLog' to
value
'C:\Users\daniels\AppData\Local\Temp\BootstrapCMSNextAndSQLExpress_
2012032021
1500.log'
[0624:3F24][2012-03-20T21:15:00]: Setting string variable
'WixBundleOriginalSource' to value 'C:\TFS2010\CMSNext\CMS
Next\Branches\BuildAutomation\BootstrapCMSNextAndSQLExpress\bin\Debug\SetupCM
SNext.exe'
[0624:3F24][2012-03-20T21:15:00]: Detect 2 packages
[0624:3F24][2012-03-20T21:15:00]: Detected related bundle:
{a6290142-ee0c-47b2-9a25-67b60fd4be2d}, scope: PerMachine, version:
1.0.0.0,
operation: None
[0624:3F24][2012-03-20T21:15:00]: Detected package: SQLServerExpress,
state:
Absent, cached: No
[0624:3F24][2012-03-20T21:15:00]: Detected package: CMSNext, state: Absent,
cached: No
[0624:3F24][2012-03-20T21:15:00]: Detect complete, result: 0x0
[0624:3F24][2012-03-20T21:15:05]: Plan 2 packages, action: Install
[0624:3F24][2012-03-20T21:15:05]: Setting string variable
'WixBundleLog_SQLServerExpress' to value
'C:\Users\daniels\AppData\Local\Temp\BootstrapCMSNextAndSQLExpress_
2012032021
1500_0_SQLServerExpress.log'
[0624:3F24][2012-03-20T21:15:05]: Setting string variable
'WixBundleRollbackLog_SQLServerExpress' to value
'C:\Users\daniels\AppData\Local\Temp\BootstrapCMSNextAndSQLExpress_
2012032021
1500_0_SQLServerExpress_rollback.log'
[0624:3F24][2012-03-20T21:15:05]: Planned package: SQLServerExpress, state:
Absent, default requested: Present, ux requested: Present, execute:
Install,
rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0624:3F24][2012-03-20T21:15:05]: Setting string variable
'WixBundleLog_CMSNext' to value
'C:\Users\daniels\AppData\Local\Temp\BootstrapCMSNextAndSQLExpress_2012032021
1500_1_CMSNext.log'
[0624:3F24][2012-03-20T21:15:05]: Setting string variable
'WixBundleRollbackLog_CMSNext' to value
'C:\Users\daniels\AppData\Local\Temp\BootstrapCMSNextAndSQLExpress_2012032021
1500_1_CMSNext_rollback.log'
[0624:3F24][2012-03-20T21:15:05]: Planned package: CMSNext, state: Absent,
default requested: Present, ux requested: Present, execute: Install,
rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0624:3F24][2012-03-20T21:15:05]: Plan complete, result: 0x0
[0624:3F24][2012-03-20T21:15:05]: Apply begin
[0624:3F24][2012-03-20T21:15:08]: Caching executable from:
'C:\TFS2010\CMSNext\CMS
Next\Branches\BuildAutomation\BootstrapCMSNextAndSQLExpress\bin\Debug\SetupCM
SNext.exe' to: 'C:\Users\daniels\AppData\Local\Package
[WiX-users] Burn: cache only Burn engine?
Hello. Recently we have some problem with bundle maintaining. Here is use case: 1. Customer gets cd-layout and renames bundle from OldName to NewName. 2. Then he installs some 2 products from bundle. 3. Then he deletes one and tries to install it again. Boom! Bundle failed with Failed to find payload error, where it refers to original bundle location with OldName. It uses to cache entire bundle and uses it for source prompts, but then I found this in wix history: WixBuild: Version 3.6.2109.0 - RobMen: SFBUG:3197472 - cache only Burn engine, fix up signatures when using attached containers. So I wonder what should my bundle do now, if some mad customer decides to rename or even delete original bundle (to free some disk space for instance)? I see wix installer itself solved this problem by downloading cab from internet, but I don't think this is the option in my case, because we have packages attached to bundle default container (inside bundle in other words). As usual, you are the best and I will appreciate any help here). Maybe make some feature request to allow entire bundle to be cached by setting some attribute? Or it is just by design and we have to tell customer to do not remove or rename cd-layout? BR, Vadym. /pre font face=arial size=1 color=#736F6E bSDL PLC confidential, all rights reserved./b If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us.BR SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207.BR Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. /font -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn SQL Express Install Fails 0x84b40000
Those links were for different errors - that hex code must be generic I'm getting my friendly neighborhood DBA to help. He pointed me to folder C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log (Since this is SQL Server 2008 R2 Express). Which creates a folder for each install attempt. So - one thing I learned is to validate the command line outside WiX before putting it in (d'uh!) David Watson was correct about the parm below. Also - you CAN'T run the 32-bit installer on a 64-bit machine (my DBA thought you could - but would get a 32-bit engine)... That was my next error. The target machines will all be 32-bit - but one of my Dev laptops is 64. I then started testing on a 32-bit machine. So - I got it tweaked from command line - and this did install successfully! (See below) The bad news - I did an uninstall (through control panel) of the bootstrapper and it did not uninstall either SQL Express or CMSNext. Note that if you do make a standard package I'm guessing most people will just want the SQLEngine feature and not necessarily Replication. I would expect needing to set an instance name would be a popular need... ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=BootstrapCMSNextAndSQLExpress Version=1.0.0.0 Manufacturer=Abbott Laboratories UpgradeCode=b89ca7ba-9287-4041-b466-5f3ebb12647d BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense / !--WixVariable Id=WixStdbaLicenseRtf Value=License.rtf /-- Chain ExePackage Id=SQLServerExpress Compressed=no Name=SQLServerExpress SourceFile=Binaries\SQLEXPR32_x86_ENU.exe InstallCommand=/ACTION=INSTALL /INSTANCENAME=GSSSQLEXPRS_DEV /FEATURES=SQLEngine Replication /IAcceptSQLServerLicenseTerms /QS RepairCommand=/ACTION=REPAIR /INSTANCENAME=GSSSQLEXPRS_DEV /FEATURES=SQLEngine Replication /IAcceptSQLServerLicenseTerms /QS UninstallCommand=/ACTION=UNINSTALL /INSTANCENAME=GSSSQLEXPRS_DEV /FEATURES=SQLEngine Replication /IAcceptSQLServerLicenseTerms /QS Vital=yes /ExePackage MsiPackage Id=CMSNext SourceFile=$(var.SetupCMSNextWIX.TargetDir)SetupCMSNext.msi Name=$(var.Name) /MsiPackage /Chain /Bundle !--/INSTANCENAME=($var.Instance)-- /Wix -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, March 21, 2012 8:56 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn SQL Express Install Fails 0x84b4 PS: When you discover the correct set of parameters, let us know here. There is a plan afoot to pre-bake the silent install of a bunch of well known redists so you can use them by just doing PackageGroupRef Id=x at the correct place in your Chain. On Wed, Mar 21, 2012 at 3:33 AM, David Watson dwat...@sdl.com wrote: SQL Express can be a pain to install silently, the trick is to run it from the command line without the silent switch on until you are sure you have the right parameters. I suspect you will at least need to add the /IACCEPTSQLSERVERLICENSETERMS parameter. -Original Message- From: Daniel Sniderman [mailto:dani...@magenic.com] Sent: 21 March 2012 02:48 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Burn SQL Express Install Fails 0x84b4 I'm trying to use Burn to Chain a SQL Express Install with my application and I'm getting what appears to be a generic error code - I can't find anything specific as to what the actual failure is. If I run the install from the command line with the same parameters it's failing... ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=BootstrapCMSNextAndSQLExpress Version=1.0.0.0 Manufacturer=Abbott Laboratories UpgradeCode=b89ca7ba-9287-4041-b466-5f3ebb12647d BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense / !--WixVariable Id=WixStdbaLicenseRtf Value=License.rtf /-- Chain ExePackage Id=SQLServerExpress Compressed=no Name=SQLServerExpress SourceFile=Binaries\SQLEXPR32_x86_ENU.exe InstallCommand=/Action=Install /INSTANCENAME=$(var.Instance) /FEATURES=SQLEngine, Replication /QS RepairCommand=/ACTION=Repair /INSTANCENAME=$(var.Instance) UninstallCommand=/Action=Uninstall /INSTANCENAME=$(var.Instance) Vital=yes /ExePackage MsiPackage Id=CMSNext SourceFile=$(var.SetupCMSNextWIX.TargetDir)SetupCMSNext.msi Name=$(var.Name) /MsiPackage /Chain /Bundle /Wix [0624:3F24][2012-03-20T21:15:00]: Burn v3.6.2221.0, path: C:\TFS2010\CMSNext\CMS
Re: [WiX-users] Burn SQL Express Install Fails 0x84b40000
My comment below wasn't entirely correct - the MSI Package WAS uninstalled - but the SQL Express instance wasn't. I have verified that the command line in the UninstallCommand does work when run manually - it seems it wasn't called when I did the uninstall... -Original Message- From: Daniel Sniderman [mailto:dani...@magenic.com] Sent: Wednesday, March 21, 2012 1:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn SQL Express Install Fails 0x84b4 Those links were for different errors - that hex code must be generic I'm getting my friendly neighborhood DBA to help. He pointed me to folder C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log (Since this is SQL Server 2008 R2 Express). Which creates a folder for each install attempt. So - one thing I learned is to validate the command line outside WiX before putting it in (d'uh!) David Watson was correct about the parm below. Also - you CAN'T run the 32-bit installer on a 64-bit machine (my DBA thought you could - but would get a 32-bit engine)... That was my next error. The target machines will all be 32-bit - but one of my Dev laptops is 64. I then started testing on a 32-bit machine. So - I got it tweaked from command line - and this did install successfully! (See below) The bad news - I did an uninstall (through control panel) of the bootstrapper and it did not uninstall either SQL Express or CMSNext. Note that if you do make a standard package I'm guessing most people will just want the SQLEngine feature and not necessarily Replication. I would expect needing to set an instance name would be a popular need... ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=BootstrapCMSNextAndSQLExpress Version=1.0.0.0 Manufacturer=Abbott Laboratories UpgradeCode=b89ca7ba-9287-4041-b466-5f3ebb12647d BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense / !--WixVariable Id=WixStdbaLicenseRtf Value=License.rtf /-- Chain ExePackage Id=SQLServerExpress Compressed=no Name=SQLServerExpress SourceFile=Binaries\SQLEXPR32_x86_ENU.exe InstallCommand=/ACTION=INSTALL /INSTANCENAME=GSSSQLEXPRS_DEV /FEATURES=SQLEngine Replication /IAcceptSQLServerLicenseTerms /QS RepairCommand=/ACTION=REPAIR /INSTANCENAME=GSSSQLEXPRS_DEV /FEATURES=SQLEngine Replication /IAcceptSQLServerLicenseTerms /QS UninstallCommand=/ACTION=UNINSTALL /INSTANCENAME=GSSSQLEXPRS_DEV /FEATURES=SQLEngine Replication /IAcceptSQLServerLicenseTerms /QS Vital=yes /ExePackage MsiPackage Id=CMSNext SourceFile=$(var.SetupCMSNextWIX.TargetDir)SetupCMSNext.msi Name=$(var.Name) /MsiPackage /Chain /Bundle !--/INSTANCENAME=($var.Instance)-- /Wix -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, March 21, 2012 8:56 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn SQL Express Install Fails 0x84b4 PS: When you discover the correct set of parameters, let us know here. There is a plan afoot to pre-bake the silent install of a bunch of well known redists so you can use them by just doing PackageGroupRef Id=x at the correct place in your Chain. On Wed, Mar 21, 2012 at 3:33 AM, David Watson dwat...@sdl.com wrote: SQL Express can be a pain to install silently, the trick is to run it from the command line without the silent switch on until you are sure you have the right parameters. I suspect you will at least need to add the /IACCEPTSQLSERVERLICENSETERMS parameter. -Original Message- From: Daniel Sniderman [mailto:dani...@magenic.com] Sent: 21 March 2012 02:48 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Burn SQL Express Install Fails 0x84b4 I'm trying to use Burn to Chain a SQL Express Install with my application and I'm getting what appears to be a generic error code - I can't find anything specific as to what the actual failure is. If I run the install from the command line with the same parameters it's failing... ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=BootstrapCMSNextAndSQLExpress Version=1.0.0.0 Manufacturer=Abbott Laboratories UpgradeCode=b89ca7ba-9287-4041-b466-5f3ebb12647d BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense / !--WixVariable Id=WixStdbaLicenseRtf Value=License.rtf /-- Chain ExePackage Id=SQLServerExpress Compressed=no Name=SQLServerExpress SourceFile=Binaries\SQLEXPR32_x86_ENU.exe InstallCommand=/Action=Install /INSTANCENAME=$(var.Instance) /FEATURES=SQLEngine, Replication
Re: [WiX-users] exit code for msu packages
As of WiX 3.6.2719.0, the standard MSU exit codes are not being handled properly by MsuPackage. In particular, the burn bootstrapper does not notice when an MSU indicates a reboot is required and instead just moves on to the next package. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/exit-code-for-msu-packages-tp7268087p7393848.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
