Re: [WiX-users] Burn SQL Express Install Fails 0x84b40000

2012-03-22 Thread David Watson
There are several sql express packages  (we used 'Microsoft SQL Server 2008
Express R2 With Tools' in the last release) and its quite customizable from
the command line. For example we specify instance name, features, service
accounts and accounts that can administer the DB.

Each user's needs may vary on what features they want - we used
SQLEngine,Tools,SSMS,ADV_SSMS.

I wonder if just specifying ="/ACTION=INSTALL /IAcceptSQLServerLicenseTerms
/QS" will work and get sensible defaults.

Dave

-Original Message-
From: Daniel Sniderman [mailto:dani...@magenic.com] 
Sent: 21 March 2012 21:46
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn SQL Express Install Fails 0x84b4

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...


http://schemas.microsoft.com/wix/2006/wi";>
  




  
  
  


  
  




-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  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...
>
>   xmlns="http://schemas.microsoft.com/wix/2006/wi";>
>   Manufacturer="Abbott Laboratories"
> UpgradeCode="b89ca7ba-9287-4041-b466-5f3ebb12647d">
> Id="WixStandardBootstrapperApplication.RtfLicense" />
>
>
>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">
>  
>   SourceFile="$(va

Re: [WiX-users] Burn SQL Express Install Fails 0x84b40000

2012-03-21 Thread Daniel Sniderman
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...


http://schemas.microsoft.com/wix/2006/wi";>
  



  
  
  


  
  




-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  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...
>
>   xmlns="http://schemas.microsoft.com/wix/2006/wi";>
>   Manufacturer="Abbott Laboratories"
> UpgradeCode="b89ca7ba-9287-4041-b466-5f3ebb12647d">
> Id="WixStandardBootstrapperApplication.RtfLicense" />
>
>
>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">
>  
>   SourceFile="$(var.SetupCMSNextWIX.TargetDir)SetupCMSNext.msi"
> Name="$(var.Name)">
>  
>
>  
> 
>
>
> [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-

Re: [WiX-users] Burn SQL Express Install Fails 0x84b40000

2012-03-21 Thread Daniel Sniderman
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...


http://schemas.microsoft.com/wix/2006/wi";>
  



  
  
  


  
  




-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  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...
>
>   xmlns="http://schemas.microsoft.com/wix/2006/wi";>
>   Manufacturer="Abbott Laboratories"
> UpgradeCode="b89ca7ba-9287-4041-b466-5f3ebb12647d">
> Id="WixStandardBootstrapperApplication.RtfLicense" />
>
>
>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">
>  
>   SourceFile="$(var.SetupCMSNextWIX.TargetDir)SetupCMSNext.msi"
> Name="$(var.Name)">
>  
>
>  
> 
>
>
> [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,
> st

Re: [WiX-users] Burn SQL Express Install Fails 0x84b40000

2012-03-21 Thread Rob Mensching
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  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...
>
> 
> http://schemas.microsoft.com/wix/2006/wi";>
>   Manufacturer="Abbott Laboratories"
> UpgradeCode="b89ca7ba-9287-4041-b466-5f3ebb12647d">
> Id="WixStandardBootstrapperApplication.RtfLicense" />
>
>
>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">
>  
>   SourceFile="$(var.SetupCMSNextWIX.TargetDir)SetupCMSNext.msi"
> Name="$(var.Name)">
>  
>
>  
> 
>
>
> [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:3

Re: [WiX-users] Burn SQL Express Install Fails 0x84b40000

2012-03-21 Thread David Watson
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...


http://schemas.microsoft.com/wix/2006/wi";>
  



  
  
  
  

  



[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
Cache\ACF5494D18EDF117A2683D66A96FB8954F98D86D\SQLServerExpress'
[2E14:2E34][2012-03-20T21:15:09]: Moving payload from working path
'C:\Users\daniels\AppData\Local\Temp\{4dac6a09-c35c-403f-854b-0af65f3c61e5}\C
MSNext' to path 'C:\ProgramData\Package
Cache\{C5CE00F2-5C35-42FA-91DD-551DFE87C6ED}v1.0.0.0\CMSNext-Dev'
[0624:3F24][2012-03-20T21:15:09]: Applying package: SQLServerExpress, action:
Install, path: C:\Users\daniels\AppData\Local\Package
Cache\ACF5494D18EDF117A2683D66A96FB8954F98D86D\SQLServerExpress, arguments:
'"C:\Users\daniels\AppData\Local\Package
Cache\ACF5494D18EDF117A2683D66A96FB8954F98D86D\SQLServerExpress"
/Action=Install /INSTANCENAME=GSSSQLEXPRS_DEV /FEATURES=SQLEngine,
Replication'
[0624:3F24][2012-03-20T21:25:26]: Error 0x84b4: Process returned error:
0x84b4
[0624:3F24][2012-03-20T21:25:26]: Error 0x84b4: Failed to configure
per-user EXE package.
[0624:3F24][2012-03-20T21:25:26]: Error 0x84b4: Failed to execute EXE
package.
[0624:3F24][

Re: [WiX-users] Burn SQL Express Install Fails 0x84b40000

2012-03-20 Thread Rob Mensching
I used Bing and found a couple things:

http://social.microsoft.com/Forums/en/Offtopic/thread/2ef8013a-4d1e-450a-b237-14717a1c5424
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/fe38259a-11bf-4d1b-a198-62e63e7e995b

After that this suggestion seems appropriate:

http://social.microsoft.com/Forums/en/Offtopic/thread/2ef8013a-4d1e-450a-b237-14717a1c5424

On Tue, Mar 20, 2012 at 7:47 PM, Daniel Sniderman wrote:

> 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...
>
> 
> http://schemas.microsoft.com/wix/2006/wi";>
>   Manufacturer="Abbott Laboratories"
> UpgradeCode="b89ca7ba-9287-4041-b466-5f3ebb12647d">
> Id="WixStandardBootstrapperApplication.RtfLicense" />
>
>
>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">
>  
>   SourceFile="$(var.SetupCMSNextWIX.TargetDir)SetupCMSNext.msi"
> Name="$(var.Name)">
>  
>
>  
> 
>
>
> [0624:3F24][2012-03-20T21:15:00]: Burn v3.6.2221.0, path:
> C:\TFS2010\CMSNext\CMS
> Next\Branches\BuildAutomation\BootstrapCMSNextAndSQLExpress\bin\Debug\SetupCMSNext.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_20120320211500.log'
> [0624:3F24][2012-03-20T21:15:00]: Setting string variable
> 'WixBundleOriginalSource' to value 'C:\TFS2010\CMSNext\CMS
> Next\Branches\BuildAutomation\BootstrapCMSNextAndSQLExpress\bin\Debug\SetupCMSNext.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_20120320211500_0_SQLServerExpress.log'
> [0624:3F24][2012-03-20T21:15:05]: Setting string variable
> 'WixBundleRollbackLog_SQLServerExpress' to value
> 'C:\Users\daniels\AppData\Local\Temp\BootstrapCMSNextAndSQLExpress_20120320211500_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_20120320211500_1_CMSNext.log'
> [0624:3F24][2012-03-20T21:15:05]: Setting string variable
> 'WixBundleRollbackLog_CMSNext' to value
> 'C:\Users\daniels\AppData\Local\Temp\BootstrapCMSNextAndSQLExpress_20120320211500_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\SetupCMSNext.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}\SQLServerExpress'
> to path 'C:\Users\daniels\AppData\Local\Package
> Cache\ACF5494D18EDF117A2683D66A96FB8954F98D86D\SQLServerExpress'
> [2E14:2E34][2012-03-20T21:15:09]: Moving payload from working path
> 'C:\Users\daniels\AppData\Local\Temp\{4dac6a09-c35c-403f-854b-0