inRiver service does not start
inRiver has two windows services, one has display name "inRiver Server" and the other "inRiver Connect". (If you are using inRiver 6, the service names are "inRiver Server 6.0" and "inRiver Connect 6.0").
If these two services fail to start, or gets stuck in the middle, try following troubleshooting steps.
Read Log files
Usually a log file is created in the "C:\Program Files\inRiver AB\inRiver Server" if the server start fails, or in "C:\Program Files\inRiver AB\inRiver Connect\Log" if the inRiver connect service fails.
See whether you can resolve the issue listed in the log file. Usually these are database connection errors, file permission erros or errors relating to messege queing service.
How to kill a stuck service
If your inriver service is stuck, do the following to kill it (for Windows Server 2012 R2, may work in other versions as well).
- in the Local Services window, locate the service, and right click and go to properties, note its "Service name" (This can be different from the name displayed in the local services window)
- Open a command prompt with administrator permissions, and run following command.
sc queryex [service name you found above]
e.g. for inriver 6.0 service: > sc queryex InRiverServerWindowsService60
- Note the PID for the service. and run the task kill command as below.
taskkill /f /pid [PID you found above]
e.g. if the PID was 3652, > taskkill /f /pid 3652
Above will kill the stuck service, and you may try to resolve the issue found from log files and start service again.
Makesure RichClient and Model tool is working
Before you try the inRiver connector is working or not, makesure that the inRiver rich client and model tool is starting and working without crashes.