<Component Id="cSessionService" DiskId="1" KeyPath="yes" Guid="DE2D99DF-93B9-4423-AD73-60D9343E85A5">
<File Id="fwfile82" Name="WSSESS_1.EXE" LongName="WSSession.exe" src="d:\FWRedist\WSSession.exe" />
<ServiceInstall Id='fwfile82' DisplayName='WS Session Manager' Name='WSS'
ErrorControl='normal' Start='auto' Type='ownProcess' Vital='yes' /><ServiceControl Id='fwfile82' Name='WSS'
Start='install' Stop='uninstall' Remove='uninstall' /></Component>
from the log file:
...
MSI (s) (08:34)
[13:48:46:546]: Doing action: InstallServices
Action 13:48:46:
InstallServices. Installing new services
Action start 13:48:46:
InstallServices.
Action ended 13:48:46: InstallServices. Return value
1.
MSI (s) (08:34) [13:48:46:561]: Doing action: StartServices
Action
13:48:46: StartServices. Starting services
Action start 13:48:46:
StartServices.
StartServices: Service: Starting services
Action ended
13:48:46: StartServices. Return value 1.
...
MSI (s)
(08:34) [13:49:28:405]: Executing op:
ActionStart(Name=StartServices,Description=Starting services,Template=Service:
[1])
Action 13:49:28: StartServices. Starting services
MSI (s) (08:34)
[13:49:28:405]: Executing op:
ProgressTotal(Total=4,Type=1,ByteEquivalent=1300000)
MSI (s) (08:34)
[13:49:28:405]: Executing op:
ServiceControl(,Name=WSQ,Action="">StartServices: Service: WSQ
Error
1920. Service 'WSQ' (WSQ) failed to start. Verify that you have sufficient
privileges to start system services.
By: - ![]() 2005-06-06 08:55 |
I wonder if anyone else experienced that recently.I have a project
that installs a service and everything worked fine until a couple of
daysago. The only thing that changed is MSI 3.0 runtime got
installed.Running install with all logging on indicates that during script
preparation msiexec seesthat InstallServices should be run. But later on
there is no ActionStarted (InstallServices ...) anywhere. Obviously, when
it gets to ActionStarted (StartServices ...) thatfails miserably. Trying
to schedule InstallServices in InstallExecuteSequence does nothelp.I
beleieve it"s either MSI 3.0 bug or there were some changes to services
related tablesthat WiX does not know about. If anyone has any idea of
what"s going on, please chime in.Beware, MSI 3.0 may break your setup. The
problem is that MSI 3.0 is now a Windows XPupdate, so your customers may
get it automatically.-- Best regards, Alexei Boukirev mailto:[EMAIL PROTECTED]
|
The information contained in this e-mail is likely to be confidential and may be legally privileged. It is intended only for the addressee. If you have received this message in error please notify the sender immediately at the above address. The disclosure, copying or distribution of this message or its contents without the prior approval of Wallingford Software Ltd. is strictly prohibited. Wallingford Software Ltd. is not liable for unauthorised disclosures nor for subsequent actions or omissions in reliance upon them.
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users