|
From: Leif M. <lei...@ta...> - 2014-06-06 06:19:59
|
Brian,
Just following up the list as the end of our conversation was off list.
The problem ended up being because the password used contained a '#'
character.
wrapper.ntservice.password=12345#7890
When the Wrapper reads in any property, it treats a '#' as a comment so all
the Wrapper was seeing was this:
wrapper.ntservice.password=12345
We have made a note in the documentation that will be in the next site
update.
If you need to use a password conaining a '#' then you will need to double
up the character so it escapes itself as follows:
wrapper.ntservice.password=12345##7890
Cheers,
Leif
On Mon, Jun 2, 2014 at 11:36 PM, <bri...@we...> wrote:
> Hi Alexandre,
>
>
>
> Sorry for the delay in response.
>
>
>
> Yes, AD-ENT\2CES-SERVICES-ID is an administrator on the machine with "Log
> on as a service" rights.
>
>
>
> I will set the debug statement in the .conf file and send you the results
> as requested.
>
>
>
> A few things to note:
>
> · I have removed the actual password value from the config file
> for security purposes
>
> · Although getting the “wrapper.ntservice.password={Password}”
> property to work would be good, my ultimate goal is to use the “#include
> ..\conf\password.conf” property. (Neither of these work for me currently)
>
> · I am including 2 log files that have been written to. (I left
> all entries in these files, including installations from 5/9/2014, just
> FYI):
>
> 1. wrapper.log
>
> § You can see from earlier wrapper.log entries from 5/9/2014 where I
> tried the include file method for entering the password during service
> installation. The log indicates that the include file is read in properly
>
> § Then there are the remaining entries from 2014/05/09, 2014/05/15, and
> 2014/06/02 where I tried installing the service using the
> “wrapper.ntservice.password={Password}” property.
>
> 2. CESCopyUtility_ServiceWrapper.log
>
> § You can see from the CESCopyUtility_ServiceWrapper.log – beginning
> with the first 2014/05/09 09:59:38 entry and ending with the 2014/05/09
> 10:34:52 entry – that the service ran successfully twice when I used the
> “wrapper.ntservice.account.prompt=true” property to install the service.
>
> § Then from 2014/05/09 12:08:01 on, there are multiple install/uninstall
> sequences where I tried installing the service using the
> “wrapper.ntservice.password={Password}” property, but afterwards, the
> service execution would fail with the error message I showed as a screen
> print in the original email.
>
>
>
> Please let me know if you need more info or data.
>
>
>
> Thanks.
>
>
>
> *~ Brian ~*
>
>
>
> *From:* Alexandre Klein [mailto:ale...@ta...]
> *Sent:* Wednesday, May 28, 2014 11:21 PM
>
> *To:* wra...@li...
> *Subject:* Re: [Wrapper-user] Issue with setting service account password
> when using Tanuki JSW
>
>
>
> Hi Brian,
>
> 1. Sorry for my mistake.
> wrapper.ntservice.* is the correct name.
>
> 2. Is “AD-ENT\2CES-SERVICES-ID” an admin?
>
> With which user are you installing and running the Wrapper? Is this user
> an admin?
>
> This user has the correct right in "log on as a service" in the "Local
> Security Settings" window?
>
>
>
> 3. You can place the property anywhere.
>
>
>
> Can you add in wrapper.conf:
>
> wrapper.debug=TRUE
>
>
>
> And try again, then send me your configuration file wrapper.conf and your
> log file wrapper.log.
>
> Please use our support email: su...@ta...
>
>
>
> I'm using Windows Server 2003 (32bit) for my test and everything look
> fine.
>
>
>
> Regards,
>
> Alexandre Klein
>
>
> On Wed, May 28, 2014 at 11:30 PM, <bri...@we...> wrote:
>
> Hi Alexandre,
>
>
>
> Thanks for the response!
>
>
>
> 1. I have actually tried this before, but I did notice a difference
> in what you have below and what I have tried:
>
>
>
> You have: wrapper.*net*service.account, wrapper.*net*
> service.password
>
> I have: wrapper.*nt*service.account, wrapper.*nt*
> service.password
>
>
>
> Should I be using *net*service instead of *nt*service? (BTW, this is
> being installed on a machine with Windows Server 2003 Enterprise x64 OS, if
> it matters).
>
>
>
> 2. Something else: I notice that the wrapper.ntservice.account=*{account
> ID}* property seems to work. (i.e., as you can see from the original 2nd
> screen print, “AD-ENT\2CES-SERVICES-ID” is what is stored in the Service
> Control Manager, which is correct). If I was to use the interactive option
> (i.e., “wrapper.ntservice.account.prompt=true”), and enter the password
> from the command line during installation, the correct password is stored
> and the service runs fine, but this is the only password-setting property I
> can get to work. L
>
>
>
> 3. Lastly, if I am going to use the “wrapper.ntservice.password”
> property, does the order/location in the wrapper.conf file where I place
> this property matter?
>
>
>
> Thanks.
>
>
>
> *~ Brian ~*
>
>
>
> *From:* Alexandre Klein [mailto:ale...@ta...]
> *Sent:* Wednesday, May 28, 2014 2:46 AM
> *To:* wra...@li...
> *Subject:* Re: [Wrapper-user] Issue with setting service account password
> when using Tanuki JSW
>
>
>
> Brian,
>
>
>
> Sorry for the delay.
>
>
>
> The property “wrapper.ntservice.password=*{Password}*” is used when the
> service is installed and it is stored in the Service Control Manager.
>
> When the Wrapper starts the service, it doesn't use
> “wrapper.ntservice.password"! So it is important to set this property
> correctly when you install the service.
>
>
>
> Maybe when you installed the service, the password was not correct?
>
>
>
> Can you do this test:
>
> - uninstall the service
>
> - set the login and password (wrapper.netservice.account,
> wrapper.netservice.password) in wrapper.conf
>
> - install the service
>
> - start the Wrapper
>
>
>
> Then it should work.
>
> Please try this and let me know the result.
>
>
>
> Regards,
>
> Alexandre Klein
>
>
>
> On Fri, May 16, 2014 at 2:20 AM, <bri...@we...> wrote:
>
> Hello,
>
>
>
> I am currently using “wrapper-windows-x86-32-3.5.24” to install a Java
> service on a Windows Server 2003 Enterprise x64 SP2 machine. I am having
> problem with the entering the password for the service account under which
> this service will run.
>
>
>
> For some reason, the only way I can get the password to store correctly
> and a subsequent successful service execution, is to require interaction
> from the user (i.e., have them manually enter the password) using the
> “wrapper.ntservice.account.prompt=true” option.
>
>
>
> If I try either the “wrapper.ntservice.password=*{Password}*” setting or
> the include file setting (i.e., “#include ..\conf\password.conf”), the
> service is installed and attempts to run under the proper account name, but
> fails due to a password violation.
>
>
>
>
|