Contents
English (United Kingdom)French (Fr)Deutsch (DE-CH-AT)
Search
Login
Who Is Online?
We have 108 guests online
Navigation
Home Free Software Command line utilities ServiceExe - Install and run applications as Windows services - Common pitfalls
Most Recent
Featured Articles
Joomla 1.5 Featured Articles
Navigation
Home Free Software Command line utilities ServiceExe - Install and run applications as Windows services - Common pitfalls
English (United Kingdom)French (Fr)Deutsch (DE-CH-AT)
ServiceExe - Install and run applications as Windows services - Common pitfalls E-mail
User Rating: / 42
PoorBest 
Free Software - Command line utilities
Written by Thomas   
Thursday, 05 February 2009 17:22
Article Index
ServiceExe - Install and run applications as Windows services
License
Installation
The configuration file
Example configuration file
Configuration: The [General] section
Configuration: Process task sections
Embedded environment variables
Command line parameters
User credentials
Process logging
Common pitfalls
All Pages

 

One common pitfall with ServiceExe is when the application has been tested with -console or -debug, but then does not work as intended when installed as a service. For example, if no logging information is stored in the intended log path (configuration file, section [General], key 'LogPath'), this is an indication for that issue. The user account that runs the service is most likely responsible for this misbehaviour.

ServiceExe -console ServiceExeTest.ini

Runs the application specified in the key 'ApplicationName' of the configuration file ServiceExeTest.ini with the credentials of the user currently logged on (-console). The application is started immediately.

ServiceExe -install ServiceExeTest.ini

Installs the application specified in the key 'ApplicationName' of the configuration file ServiceExeTest.ini as a Windows service. When started, the service runs with the user credentials of the account LocalSystem.

If LocalSystem does not have appropriate permissions to access all required resources, the service seems not to work properly, which includes:

- Registry keys/values cannot be accessed.
- The file system cannot be accessed, for instance log files cannot be written.
- Network access is denied.

The solution is to either provide appropriate permissions for LocalSystem or run ServiceExe under an account that has the required permissions. The parameters /U: and /P: or the Windows Services Panel can assist here.

 

Download ServiceExe.zip (0.11 MiB = 108.4 KiB = 111,041 bytes)

 



Last Updated on Thursday, 05 July 2012 13:25
 
You need to login or register to post comments.
Discuss this item on the forums. (0 posts)
Discuss (0 posts)