Starting the HSE event notification server as a service

 

 

Notes - This topic is primarily intended for IT systems administrators -

 

Installing HSE Notifier as a service on the same server  

This is straight forward because the service will have access to the folder where the database resides. The service will be set up to run in "Local" mode, meaning it will have access to local folders on the server. It will be an "automatic" service meaning it will be restarted when the server is rebooted and will not require anyone to login.

 

 

The service will be "automatic" meaning it will be started or restarted when the server is rebooted.

 

Installing HSE Notifier as a service on different server

The event notifier service starts automatically when the computer boots. If it is installed on a server other than the one containing the H&S Compliance Manager database, the service needs the access rights of a user account to access the SafetyLink Risk Manager database folder. This is achieved by following the guidelines below:

 

 

Starting HSE event notifier service

The event notifier server service is installed as "Automatic", meaning it will start automatically each time the server starts.

 

To start or restart the service manually, use any of these methods:

 

 

Stopping an event notifier process or service

To stop an event notifier (process or service) manually from outside of the SafetyLink Risk Manager use any of these methods:

 

To stop a single event notifier (process or service) manually from the SafetyLink Risk Manager

 

To stop ALL event notifier (processes or services) manually from the SafetyLink Risk Manager

 

To enable ANY event notifier to be restarted again (after ALL event notifiers were stopped as above):

 

Checking Event notifier service

The event notifier looks at the database to determine when emails should be sent and to whom. These are set in the rules for each event type. When the event notifier determines an email should be sent it tries to determine from the rules the person or people to send the email to then looks in their staff records to get their work email address. If it can not find a valid address the email will be sent to the System Administrator (defined in the Company Data).

 

The first place to check to determine that the email notification service is running is by going to Company Data, selecting the Email Notifier tab, pressing the button to see email notifiers and then check the date and time of the entry. If there is no entry in the list the email notifier is not running. If there is an entry you can see the computer it is running on. By pressing the refresh button with 5 second intervals you can determine if the time is changing. If it is changing the email event notifier is running. If it is not changing, either the email event notifier is not running or it has stopped or hung. If it has stopped, delete the notifier record, wait 5 or 10 seconds then press refresh. If the notifier record reappears, it is running. If not it has either stopped or is hung up for some reason.

 

If the email notifier is running then it is time to check the emails being sent. At the time the email notifier attempts to send the email, it updates the email address of the recipient and this may be verified by checking the email events in the calendar for the event. If the email is sent successfully to the smtp email server the date and time the email was sent is updated in the calendar in the particular email notification. If an error occurs the date and time is not updated and the error is placed in the calendar for the email notification.

 

Checks:

 

Turn on error Logging

Note: Logging will significantly degrade performance so ensure it is tuned off after testing.

[Notifier]

COMPUTERNAME-Version=8.040

COMPUTERNAME-Started=NO

COMPUTERNAME-Service=YES

 

Notes

1. COMPUTERNAME is the computer the email notifier process or service was started on.

2. The case should be exactly as above.

ADMINISTRATOR-LogFile=c:\mylogfile.log

 

 

After starting the event notifier log file will contain the latest error.

 

Turn off error logging