The Error log displays information about serious errors that affect the functionality of the entire firewall. WinRoute administrator should check this log regularly and fix detected problems as soon as possible. Otherwise, users might have problems with some services or/and serious security problems might arise.
A typical error message in the Error log could be: a problem when starting a service (usually a collision at a particular port number), problems when writing to the disk or when initializing anti-virus, etc.
Each record in the Error log contains error code and sub-code as two numbers in parentheses (x y)
. The error code (x
) may fall into one of the following categories:
1-999
— system resources problem (insufficient memory, memory allocation error, etc.)
1000-1999
— internal errors (unable to read routing table or interface IP addresses, etc.)
2000-2999
— license problems (license expired, the number of users would break license limit, unable to find license file, etc.)
3000-3999
— configuration errors (unable to read configuration file, detected a loop in the configuration of the DNS module or the Proxy server, etc.)
4000-4999
— network (socket) errors
5000-5999
— errors while starting or stopping the WinRoute Firewall Engine (problems with low-level driver, problems when initializing system libraries, services, configuration databases, etc.)
6000-6999
— filesystem errors (cannot open /save /delete file)
7000-7999
— SSL errors (problems with keys and certificates, etc.)
8000-8099
— HTTP cache errors (errors when reading / writing cache files, not enough space for cache, etc.)
8100-8199
— errors of the Kerio Web Filter module
8200-8299
— authentication subsystem errors
8300-8399
— anti-virus module errors (anti-virus test not successful, problems when storing temporary files, etc.)
8400-8499
— dial-up error (unable to read defined dial-up connections, line configuration error, etc.)
8500-8599
— LDAP errors (server not found, login failed, etc.)
Note: If you are not able to correct an error (or figure out what it is caused by) which is repeatedly reported in the Error log, do not hesitate to contact our technical support. For detailed information, refer to chapter 26 Technical support or to http://www.kerio.com/.