Troubleshooting Windows services

Check Services and ensure that the ReadSoft Production service is running:
Check Windows Task Manager's Processes tab to make sure that there is at least one instance of RSProcess.exe and one instance of RSProductionService.exe in the list. If RSProcess.exe is not immediately visible, it may appear every 20 seconds (the default wait time between restarts).

If RSProcess.exe starts but then exits immediately, the local path or command line may be incorrectly specified. Test them from the command prompt. (Details.)
1. Open the RSProductionService.exe.config.behaviour file. (Where can I find this file?)
  This file is usually found here: C:\Program Files\ReadSoft\DOCUMENTS\Bin
  
  If there are several Bin folders, or you are having trouble finding the file, Windows Registry can tell you where it is located:
  1. Click Start and then Run.
  2. Type Regedit and click OK.
  3. Locate the ImagePath attribute in the My Computer\HKEY_LOCAL_MACHINE\System\ControlSet001\Services\ReadSoft Production folder:
  4. In the Data column you can see the path to the behavior file.
2. Copy "localpath" value, including the quotation marks. Paste that into the command prompt, followed by the "commandline" value but without the single quotes. Example:
3. Press Enter and see if it works (that is, see if Production starts and processes the specified tasks and batches).
If that test passes, try starting the Production module and running the specified task manually. If the production task can be run manually, check the user credentials for the service, and ensure that the correct user and user details are specified.
If the two processes do not start, or if documents or batches are still not processed as expected, open Event Viewer and check under Windows Logs > Application for any errors related to the Readsoft Production Service. To do this, sort the events by Source and look at events whose source is ProductionServiceWinService:

There should be an Information-level message that the service started successfully. If there are Error-level messages from ProductionServiceWinService, click them to find out what is wrong, and fix the error if possible.
If Event Viewer is not showing any errors from ProductionServiceWinService, open Applications and Services Logs > ProductionServiceLog and make sure there is no errors listed there. If you see errors:

...then click them to see what is wrong. Correct the error yourself, or contact ReadSoft Support after checking the remaining points.

(To get more detail in this log, select Logging in the Service options dialog.)
If excessive memory usage is an issue, reduce the number of batches processed in the segment that has the memory problem. (See Configuring the ReadSoft Production service.)
Make sure that logging is enabled where tasks are running as services.
Check the Services log overview (ServicesLog.html) to see what actually took place in the service. (The Logging settings of the Logging policy dialog tells you the location of that log.)

There is an entry for each event in the service, including a link to each application log file from RSProcess.exe. Check the log files and act according to the information presented.
In the service log you may detect tasks that were started but not stopped. This means that either they are still running or they crashed. Most of the time, failed processes are restarted. However, if a process has "frozen," you may need to terminate it manually using Windows Task Manager. This may also include eiitrp.exe or efitrp.exe.

The Administration module also runs one instance ofeiitrp.exe. Therefore, close Administration before terminatingeiitrp.exe.
If you need to contact ReadSoft Support, use the Support Package and to provide log files, the registry, and your configuration.