I am using Wix 3.5 and Visual Studio 2010 to install a Windows Service
on a Windows Server 2003 SP 2 box. After a system reboot if an
exception is thrown in the Startup method of the service it causes the
machine to reboot. If the exception continues to be thrown in the
service startup it can cause the machine to go into a reboot loop
where a console session has to be initiated to take the system back to
the last known good configuration in order to recover. The recovery
options are set to 'Take No Action' but because the error is thrown
not after the service has already started but during startup this
setting does not appear to make any difference. Is there a setting in
the Wix XML file that can guard against this problem? Below is the
ServiceInstall portion of the Wix XML file. If anyone has seen this
error any help will be greatly appreciated.
<ServiceInstall
Id="ServiceInstaller"
Type="ownProcess"
Vital="yes"
Name="$(var.ServiceName)"
DisplayName="$(var.ServiceName)"
Description="My service description"
ErrorControl="critical"
Interactive="no"
Start="auto">
</ServiceInstall>
<ServiceControl
Id="StartService"
Stop="both"
Remove="uninstall"
Name="$(var.ServiceName)"
Wait="yes" />
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
