Technical Library | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Web Security Log Server Troubleshooting Guide
Web Security Log Server Troubleshooting Guide
Topic 50300 | Web Security Solutions | Updated 19-Sept-2013
Applies To:
Websense Web Filter, Web Security, Web Security Gateway, and Web Security Gateway Anywhere, v7.7 and 7.8
If you are using Websense Web Security solutions, the Websense Log Server service (Log Server) must be installed to enable creation of Internet activity reports. Log Server:
*
Receives browsing data from:
*
(All Web Security products) Filtering Service
*
(Websense Web Security Gateway and Gateway Anywhere) Content Gateway
*
(Web Security Gateway Anywhere) Sync Service
*
Stores the data in temporary files on its local hard drive
*
Forwards the data to the Log Database, where it is moved into database tables for use in generating reports
Log Server also requests and receives:
*
User and group information from User Service
*
Category, risk class, and protocol information from Policy Server
When a user generates browsing data for the first time, Log Server requests information about that user from User Service, which pulls the needed data from the directory server. From that point on, Log Server regularly requests user information for employee names, network login names and group membership, updating its stored data accordingly as changes are found in the directory.
Custom categories and protocols, as well as changes to risk class mappings are forwarded to Log Server and maintained in the Log Database.
When there is a problem with Log Server, none of this data is sent to the Log Database. Reports do not include the most recent browsing data, user information, or customized filtering information.
This collection contains the following articles to help you identify and resolve the underlying cause of reporting problems. Click a link to jump to an article, or use the arrows at the top of the content pane to browse through the articles in this collection.
*
Web Security Log Server installation: Error connecting to SQL Server
*
Error creating the Log Database
*
Web Security Log Server stops unexpectedly or will not start
*
Web Security Log Server and Windows registration
*
Incorrect or missing data in Web Security reports
*
Web Security Log Database permissions
Additional troubleshooting and reference articles are also available:
*
Manually Creating the Web Security Log Database
*
Using TestLogServer for Web Security Troubleshooting
*
Web Security Log Server Error Reference

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Web Security Log Server Troubleshooting Guide
Copyright 2016 Forcepoint LLC. All rights reserved.