KB Article | Forcepoint Support
Support
  1. Home
  2. Knowledgebase

Log Server test connection failures

  • Article Number: 000015655
  • Products: Forcepoint URL Filtering, Forcepoint Web Security, TRITON AP-WEB, Web Filter & Security, Web Security Gateway, Web Security Gateway Anywhere
  • Version: 8.5, 8.4, 8.3, 8.2, 8.1, 8.0, 7.8, 7.7
  • Last Published Date: October 11, 2018

Problem Description

Logging appears to be working, however, the Log Server Test Connection button results in Forcepoint Security Manager (formerly Triton Manager) showing a "Failure: Network Exception" error or an "IO Exception" error.

Also, the BCP Test Location button is displaying a "Path is invalid" error.

For v8.3 and later:
 


For v8.2 and earlier:
 
 
For Hybrid Accounts, it will also generate the following alert:
 
Alert: Sync Service connection to hybrid service or Log Server timed out due to connection issues.
Description: Confirm your Sync Service proxy configuration is correct on the Settings>Hybrid Configuration>Scheduling page. If no proxy is configured on this page, check there are no network issues between Sync Service and the hybrid service or Log Server.
 
User-added image
 
Websense.log shows the following error:
03/25/2018 09:29:38,Error,WebsenseSyncService@10.239.125.6,SyncService,WsRESTRequest.java:261,0x15d0001,Communication failure detected on transmission to server.
 

Resolution

In order to resolve the issue, follow the steps below:

If on-premise logging is working and reports can be generated in Investigative Reports and Presentation Reports, this issue is most likely due to the configuration in the logserver.ini file.
  1. Navigate to the Websense\Web Security\bin directory.
  2. Open the logserver.ini file.
  3. Search for the Host token at the bottom to make sure it has the correct Log Server IP address. 
  4. Edit the file by commenting out the Host token by typing a ; before the word like the below example.
[RestService]
Active=true
Port=55885
;Host=0.0.0.0

Important Do not comment out the host token and replace Host=0.0.0.0 with Host=<LogServer_IP>.
  1. Navigate to Start > Administrative Tools > Services.
  2. Restart the Log Server service and test the connections again.
If the issue persists, raise a case with Technical Support for assistance. 

Article Feedback



Thank you for the feedback and comments.

Want 24/7 Tech Support?

Learn more