System Event Log

CommServer uses a standard Windows mechanism – EventLog to provide information about activity - warnings or errors.

When CommServer starts for the first time it registers itself as an EventLog source.

The table below shows main eventlogs entries.

Type	Source	Category	Event	Description	Explanation
information	Communication Server	---	10	A new SBUS channel protocol created with COM2,4800,0,0	CommServer has just started and uses the SBUS protocol over serial line on the port COM 2; serial settings are COM2,4800,0,0
warning	Communication Server	92	11000	sbus[ProtocolID=2] channel protocol failed to start - port: COM3,4800,0,0 cannot be opened.	CommServer has tried to start communication over SBUS and COM3, but the port could not be opened. Possible solution: - mistake in the configuration – the COM3 does not exist - COM3 was occupied by another application
information	Communication Server	---	0	Communication server started: product name: Communication Server; product version: 2.5.1714.30221	CommServer is successfully started; OPC server is running. The built version of the software is 2.5.1714.30221.
error	Communication Server	---	0	Communication server finished with Assert error	This error forces CommServer to stop the service; it can be caused by an improper configuration; please verify the configuration. If the problem occurs and changes in the configuration do not overcome it, please contact the tech-support
error	Communication Server	130	240	Timeout error: Segment main scanner thread had to be timed out after 60s and caused a system reboot	CommServer finds a serious problem (maybe deadlock occurs). The operating system will be restarted. It may be caused by an improper configuration; please verify the configuration. If the problem occurs and changes in the configuration do not overcome it, please contact the tech-support and send the log.
warning	Communication Server	248	30000	Cannot disconnect all clients (3 still connected )	CommServer is going to be stopped, but 3 OPC clients are still connected in spite shutdown requests sent at least 3 times.