1a. If a single Failure Alert is received followed by a Success Alert then no action is required.
1b. If a second Failure Alert is received within the threshold (default 10 minutes) followed again by a Success Alert this indicates there is an error causing the Service to stop each time it is started. However the Service Monitor will restart the service again.
1c. If a third Failure Alert is received within the threshold then the Service Monitor will not attempt to restart the service again and the service with the error will remain stopped. This will now require an investigation into the log file to determine the reason for the stoppage.
2. The log file can be accessed on the server hosting versaSRS and the default path to the log file is C:\Temp. You will need to access the log file for the stopped service and scroll to the end where the error that caused the service to stop will be displayed. This will indicate what action should be taken.
Example: A service cannot process a particular problematic email. The error in the log file will need to be addressed, then the service restarted to get it operating as expected. Setting an Error Folder for the email account will prevent this scenario.
3. To start a stopped service manually, access the server hosting versaSRS and go to Control Panel > Administrative Tools > Services > Locate the stopped service (prefixed with versa) and click Start. You can then check the log file again and see if it is processing correctly (please allow a few minutes for the log file to update).