Log Server stops unexpectedly or will not start

Web Protection Solutions, v8.2.x, v8.3.x | 10-Dec-2016

If you have installed Log Server, but the service will not start or continues to stop, first verify that Log Server is connected to the Log Database:

Log on to the TRITON Manager with Global Security Administrator or unconditional Super Administrator permissions.

Select the Web module.

Go to the Settings > Reporting > Log Server page.

Under Log Database Connection, click Test Connection.

If the test fails

Perform the following steps:

Make sure the Microsoft SQL Server machine is running and connected to the network.

Make sure the connection port entry is correct, and that there is no firewall blocking the port.

The default port is 1433, but other ports can be used.

Use the Windows Services tool (Start > Administrative Tools > Services or Server Manager > Tools > Services) to verify that the following services are running:

SQL Server

If you are using the default instance, the full service name is SQL Server (MSSQLSERVER).

SQL Server Browser

(SQL Server Standard or Enterprise) SQL Server Agent

For the default instance, the full service name is SQL Server Agent (MSSQLSERVER).

SQL Server Express does not require the SQL Server Agent service.

Make sure that your authentication settings are correct.

If you are using SQL Authentication, make sure that the password in the Log Database Connection section of the Settings > Reporting > Log Server page is correct.

If the password has been changed within SQL Server, it also needs to be changed here.

If you are using Windows Authentication, make sure that Log Server is set up to run as a trusted account:

Open the Windows Services tool on the Log Server machine.

Scroll down to find the Websense Log Server service.

Right-click the service name, then select Properties.

Select the Log On tab to view and change account information.

To recreate the database connection, re-enter the database information on the Settings > Reporting > Log Server page.

If you are using a SQL instance, make sure the instance name is included as part of the SQL Server location (for example, IP_address\instance_name).

Double-check the port entry.

Make sure that the network connection between the Log Server and Log Database machines has not been interrupted.

Make sure Log Server can connect to the DSN server.

An error indicating that Log Server cannot connect to the DSN server may occur:

If Windows User Account Control (UAC) is enabled. Disable UAC.

If a hostname, rather than IP address, is specified for the SQL Server location. Use the IP address so that access to the DSN server is not required.

If the test succeeds

If the connection test passes but Log Server does not start, or continues to stop:

Make sure that Policy Server is running and that Log Server can connect to Policy Server.

Navigate to the bin directory on the Log Server machine (C:\Program Files\Websense\Web Security\bin, by default) and verify the Policy Server IP address and UID in the websense.ini file.

The Policy Server UID in websense.ini should match the one in the config.xml file on the Policy Server machine.

Still in the bin directory, make sure the logserver.ini file exists and has not been corrupted.

If an error occurs when you try to open the file in a text editor, replace the corrupted file with a good file from backup.

Make sure the Log Server machine has not run out of disk space.

Verify that the folders defined for ODBC cache and BCP files on the Settings > Reporting > Log Server page in the Web module of the TRITON Manager exist, and that Log Server has permission to write to them.

If Log Server is defined to run as a domain administrator account, set the service to run as Local System:

Open the Windows Services tool (Start > Administrative Tools > Services or Server Manager > Tools > Services) on the Log Server machine.

Scroll down to find the Websense Log Server service, then right-click the service name and select Properties.

Select the Log On tab to view and click Local System account, then click OK.

Make sure Log Server is registered properly with the Windows operating system. See Log Server and Windows registration.