If the test succeeds

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

Steps

  1. Make sure that Policy Server is running and that Log Server can connect to Policy Server.
  2. 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.
  3. 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.
  4. Make sure the Log Server machine has not run out of disk space.
  5. Verify that the folders defined for ODBC cache and BCP files on the Web > Settings > Reporting > Log Server page in the Forcepoint Security Manager exist, and that Log Server has permission to write to them.
  6. If Log Server is defined to run as a domain administrator account, set the service to run as Local System:
    1. Open the Windows Services tool on the Log Server machine.
    2. Scroll down to find the Websense Log Server service, then right-click the service name and select Properties.
    3. Select the Log On tab to view and click Local System account, then click OK.
  7. Make sure Log Server is registered properly with the Windows operating system. See Log Server and Windows registration.