Dateiliste

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.10 MiB = 105.8 KiB = 108,365 bytes)