Product Documentation
Abstract
If one of the programs fails to start as a Windows service, it can be difficult to determine the cause. Typically the service fails to start but gives no indication of why. The Windows Event log has nothing useful and the process might not have got as far as creating its log file.
Content
The usual cause is that the listening port is already taken, or that the user who is associated with the service has insufficient permissions to write to files on the local system.
The Java services are started by using Apache Commons daemon. See this page for reference:
Procrun Documentation.
Ask for assistance from your local Windows administrator during this process.
This example looks at RIT-Agent, but also works for the HTTP Proxy and RTCP.
Run the service on the command line
Open the Windows Service and make a note of the name of it.
In this case, the name is IBMRITAgent.
Additionally, make a note of the user.
Open a command window in the RIT-Agent installation folder.
Run the service as a console application:
prunsrv //TS//IBMRITAgent
If this works, compare the permissions of the user who is logged in with the one configured in the service. You might be able to run the command as the other user:
runas /user:LOCALMACHINENAME\user "prunsrv //TS//IBMRITAgent"
Service Logging
It is possible to add low-level logging to the service itself.
Run the following:
prunmgr //ES//IBMRITAgent
Set the Level to Debug and configure the Log path folder name.
Restart the service and check the log files.
Three are produced:
commons-daemon.2017-09-22.log
ibmritagent-stderr.2017-09-22.log
ibmritagent-stdout.2017-09-22.log
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27050347