Re: [Wrapper-user] wrapper Service Start Error 1053 - failed to initialize properly (0xc0000142)

[Leif M. <le...@ta...>]

Edith,

Edith Schmahljohann wrote:
> Hallo Leif,
> thanks for your quick response,
> but i don't understand the instruction
>   ... to reinstall the sevice
>    after changing the configured account ...
>
> I installed the TestWrapper out of the BOX.
> the Service StartUser is .LocalSystem (default)
> then i change the StartUser ... 
> i don't configure the account in file wrapper.conf -
> is that the problem ?
>   
Ok. That should be fine.  The Wrapper only looks at the value of the
wrapper.ntservice.account property when it installing a service.  Once it
is installed, that is hard coded into the service manager configuration.
That is why I require that the service be uninstalled and then reinstalled.
If you are changing the service account manually, then that should not be
a problem.

When the service is running, please confirm in the Task Manager that
the wrapper and it's java process are running as the adamue61 account.
> But Note:
> I make several tests on other Workstations.
> I am able to change the StartUser without
> reinstalling the service and it works.
>
> Attched you will find the settings you asked for ...
> I want to make User "adamue61" able to start the wrapper service
> this is a  local User  belonging to group Administrator  with Log on as 
> Servie rights
>   
Were you able to verify that the wrapper.log file does not exist in any 
of the locations
specified?

As an alternative to the wrapper.log, lets try sending output to the 
event log.
Set the following property and see if you are getting any output in the log.
wrapper.syslog.loglevel=INFO

If you ARE getting output, but the problem is not obvious, try setting 
the following:
wrapper.syslog.loglevel=DEBUG

This will fill up your event log fairly quickly.  But if you are not 
able to see the wrapper.log,
this may be the only way to see what is going on.

I still think this is most likely a permission problem.  Try setting the 
wrapper.log location
to an absolute directory where you are sure the user will have the 
ability to write to.
wrapper.logfile=C:/tmp/wrapper.log

Where is your wrapper/application installed?   Is it a local drive or a 
network drive?
I ask because some users have had problems running from a network drive 
if things
are not set up correctly.

Cheers,
Leif

> regards,
> Edith
>
> #############
> policy Local Settings
> #############
> Policy  Local Setting   Effective Setting
> Access this computer from the network   Everyone,Users,Power 
> Users,Backup Operators,Administrators      Everyone,Users,Power 
> Users,Backup Operators,Administrators
>
> Act as part of the operating system            
> Add workstations to domain             
> Back up files and directories   Backup Operators,Administrators Backup 
> Operators,Administrators
> Bypass traverse checking        Everyone,Users,Power Users,Backup 
> Operators,Administrators      Everyone,Users,Power Users,Backup 
> Operators,Administrators
>
> Change the system time  Power Users,Administrators      Power 
> Users,Administrators
> Create a pagefile       Administrators  Administrators
> Create a token object          
> Create global objects   Administrators,SERVICE  Administrators,SERVICE
> Create permanent shared objects        
> Debug programs  Administrators  Administrators
> Deny access to this computer from the network          
> Deny logon as a batch job              
> Deny logon as a service        
> Deny logon locally             
> Enable computer and user accounts to be trusted for delegation         
> Force shutdown from a remote system     Administrators  Administrators
> Generate security audits               
> Impersonate a client after authentication       Administrators,SERVICE  
> Administrators,SERVICE
> Increase quotas Administrators  Administrators
> Increase scheduling priority    Administrators  Administrators
> Load and unload device drivers  Administrators  Administrators
> Lock pages in memory           
> Log on as a batch job   SIRONA\felmei,BHMF061A\adamue61 
> SIRONA\felmei,BHMF061A\adamue61
> Log on as a service     
> SIRONA\edbserv,SIRONA\axalantrt,BHMF061A\axalantrt,BHMF061A\adamue61,SIRONA\de400178    
> SIRONA\edbserv,SIRONA\axalantrt,BHMF061A\axalantrt,BHMF061A\adamue61,SIRONA\de400178
>
> Log on locally  Administrators,Backup Operators,Power 
> Users,Users,BHMF061A\Guest,BHMF061A\TsInternetUser        
> Administrators,Backup Operators,Power 
> Users,Users,BHMF061A\Guest,BHMF061A\TsInternetUser
>
> Manage auditing and security log        Administrators  Administrators
> Modify firmware environment values      Administrators  Administrators
> Profile single process  Power Users,Administrators      Power 
> Users,Administrators
> Profile system performance      Administrators  Administrators
> Remove computer from docking station    Users,Power 
> Users,Administrators        Users,Power Users,Administrators
> Replace a process level token          
> Restore files and directories   Backup Operators,Administrators Backup 
> Operators,Administrators
> Shut down the system    Power Users,Backup Operators,Administrators     
> Power Users,Backup Operators,Administrators
> Synchronize directory service data             
> Take ownership of files or other objects        Administrators  
> Administrators
> #######################
>