I think that exit code from SQL Server means that the RebootRequiredCheck
rule failed, so something further up the chain or something that was
installed previously is wanting a reboot. You can disable the reboot
required check with the /skiprules=RebootRequiredCheck parameter, or you
can force Burn to reboot if necessary before it gets to SQL Server, either
through your bootstrapper application (which is what we do) or using
ExitCode on earlier packages you know will need reboots.
Relatedly, it would be nice if Burn had something like a <RebootCheckPoint>
that could go in a Chain and force a reboot if one was pending from
previous packages...
Nicholas
On 6 June 2013 09:56, Pawel Fujcik <pfuj...@proximetry.pl> wrote:
> I am using WiX 3.7. I use a managed bootstrapper that is a parent process
> to install 3 packages in a chain. One of these packages ia another wix
> bootsrapper(stdba) called AVS_DB with two packages in a chain.
> During installation I get the following error in AVS_DB
>
> [0CA8:08E0][2013-06-06T08:29:47]i301: Applying execute package:
> SQL_Server_2012_x64, action: Install, path: C:\ProgramData\Package
> Cache\E15C2C539FA0506E677F623DD02DA287E0977FD2\SQLEXPR_x64_ENU.exe,
> arguments: '"C:\ProgramData\Package
> Cache\E15C2C539FA0506E677F623DD02DA287E0977FD2\SQLEXPR_x64_ENU.exe"
> /ACTION=INSTALL /Q /HIDECONSOLE /FEATURES=SQL /SECURITYMODE=SQL
> /SAPWD="*****" /TCPENABLED=1 /NPENABLED=0 /BROWSERSVCSTARTUPTYPE=Automatic
> /INSTANCENAME=AVSEXPRESS /IACCEPTSQLSERVERLICENSETERMS /UpdateEnabled=False'
> [0CA8:08E0][2013-06-06T08:31:02]e000: Error 0x84be0bc2: Process returned
> error: 0x84be0bc2
> [0CA8:08E0][2013-06-06T08:31:02]e000: Error 0x84be0bc2: Failed to execute
> EXE package.
> [06A4:0E04][2013-06-06T08:31:02]e000: Error 0x84be0bc2: Failed to
> configure per-machine EXE package.
> [06A4:0E04][2013-06-06T08:31:02]i319: Applied execute package:
> SQL_Server_2012_x64, result: 0x84be0bc2, restart: None
> [06A4:0E04][2013-06-06T08:31:02]e000: Error 0x84be0bc2: Failed to execute
> EXE package.
> [0CA8:08E0][2013-06-06T08:31:02]i329: Removed package dependency provider:
> SQLServer2012SP1_AVSEXPRESS, package: SQL_Server_2012_x64
> [0CA8:08E0][2013-06-06T08:31:02]i351: Removing cached package:
> SQL_Server_2012_x64, from path: C:\ProgramData\Package
> Cache\E15C2C539FA0506E677F623DD02DA287E0977FD2\
> [0CA8:08E0][2013-06-06T08:31:02]i330: Removed bundle dependency provider:
> {352459a6-1403-4fe8-b787-9626cfb74350}
> [0CA8:08E0][2013-06-06T08:31:02]i352: Removing cached bundle:
> {352459a6-1403-4fe8-b787-9626cfb74350}, from path: C:\ProgramData\Package
> Cache\{352459a6-1403-4fe8-b787-9626cfb74350}\
> [06A4:0E04][2013-06-06T08:31:02]i399: Apply complete, result: 0x84be0bc2,
> restart: None, ba requested restart: No
> [06A4:0E04][2013-06-06T08:31:02]i500: Shutting down, exit code: 0xbc2
>
> AVS_DB exits with code 0xbc2 which is different than 0x0 what means that
> an error occured.
>
> But in a parent bootstrapper i get the following information from the log:
>
> [073C:0A3C][2013-06-06T08:29:43]i301: Applying execute package: AVS_DB,
> action: Install, path: C:\ProgramData\Package
> Cache\0AD5463049E5A78AC1A53F4EA22A52D33FAD4A56\AVSDB.exe, arguments:
> '"C:\ProgramData\Package
> Cache\0AD5463049E5A78AC1A53F4EA22A52D33FAD4A56\AVSDB.exe" /install /quiet
> /norestart /log C:\Users\ADMINI~1\AppData\Local\Temp\2\AVS_DB.log
> SaPassword="*****" SSOOption=0 InstallFirewallRules=1'
> [0708:0F00][2013-06-06T08:31:02]i000: Package event AVS_DB status 0
> Restart RestartRequired
> [0708:0594][2013-06-06T08:31:02]i319: Applied execute package: AVS_DB,
> result: 0x0, restart: Required
>
> which means that the parent bootstrapper recognized somehow that no error
> ocured in a child bootstrapper(AVS_DB) and continues with installation
> instead of performing a rollback.
>
> Perhaps that has something to do with PackageGroup settings in AVS_DB
> beacuse exit code 0xbc2 is equal to 3010 and this value is configured to
> schedule restart in my code:
>
> <PackageGroup Id="SQLServer64">
> <ExePackage Id="SQL_Server_2012_x64"
> SourceFile="$(var.ResourcesPath)$(var.SQLServer64FileName)" Vital="yes"
> DisplayName="SQL Server 2012 x64"
>
> InstallCommand="/ACTION=INSTALL /Q /HIDECONSOLE /FEATURES=SQL
> /SECURITYMODE=SQL /SAPWD="[SaPassword]" /TCPENABLED=1
> /NPENABLED=0 /BROWSERSVCSTARTUPTYPE=Automatic /INSTANCENAME=AVSEXPRESS
> /IACCEPTSQLSERVERLICENSETERMS /UpdateEnabled=False"
>
> UninstallCommand="/ACTION=UNINSTALL /Q /HIDECONSOLE
> /INSTANCENAME=AVSEXPRESS /FEATURES=SQL"
>
> RepairCommand="/ACTION=REPAIR /Q /HIDECONSOLE /INSTANCENAME=AVSEXPRESS
> /FEATURES=SQL"
>
> DetectCondition="VersionNT64 AND SQLServerInstalled64"
>
> InstallCondition="VersionNT64"
> >
> <ExitCode Value="3010"
> Behavior="scheduleReboot"/>
> <dep:Provides
> Key="SQLServer2012SP1_AVSEXPRESS" Version="11.1.3000.0" />
> </ExePackage>
> </PackageGroup>
>
> Although I think that scheduling reboot should not prevent rollback when
> error occurs.
> Is there any way to perform a rollback when error occurs in this case?
>
>
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
