|
From: Leif M. <le...@ta...> - 2005-10-19 23:40:27
|
Leif Mortenson wrote: > Jani, > Figured it out... I added the following to the documentation for the > next release: > > Note that under Windows XP and Windows 2000 SP3 and > above, by default, > the system will not allow services to be run for > accounts which do not > have a password set. > > To make it possible to run as an account without a > password, you need to > disable the "Accounts: Limit local account use of blank > password to > console logon only." setting. Go to the Administrative > Tools folder in > your control panel. Open the Local Security Policy > applet. Expand Local > Policy and then click on Security Options. On the right > side you will > find the above setting. Right click to access its > properties dialog > and then disable it. > > Cheers, > Leif > > jan...@pe... wrote: > >> Hello! >> >> I have a question about wrapper. We try to use it for running java >> application on Windows 2000 Workstation as windows service. >> We want to run this service as user xxxx which has no password. >> >> In our .conf file we set option: >> wrapper.ntservice.account=.\xxxx >> This option is processed OK by wrapper. >> >> What should we do to tell wrapper that this user has no password? We >> tryed >> option: >> wrapper.ntservice.password= >> We also tryed without this option (default should be no password). >> >> When we ty to start this service it doesn't start and we get a response: >> The service did not start due to a logon failure. >> >> If we manually change logon properties of our service on windows >> services >> (GUI), it starts OK after we delete all * characters in password fields. >> >> Since our plan is to install our service on many machines, it is wery >> hard >> job to manually update passwords of service. >> If you can suggest me any solution of this problem, please let me know! >> >> >> Thanks in advance! >> >> Best regards, >> Jani Kavcic >> >> > > |