Controller behaves erratically

Cause: You can run the reporting controller as a Windows service or through the desktop shortcut. Either method runs the same code, however, you can configure the Windows service to start automatically at boot up.

If a request is made to end the Windows service, the end controller process runs automatically.

The end-controller process works by writing a special entry to the reporting controller outbox. The reporting controller ends when this entry is seen. If you run the end-controller process when the reporting controller is inactive, then, when the reporting controller starts, the controller will see the special entry and terminates.

Symptom: Erratic behavior of the reporting controller

Solution: Restart the controller to resolve this problem. If the problem persists, you must review the log files to see if there is another underlying problem that causes this issue.