Make sure that the Log Database machine is running, that Microsoft SQL Server is operating properly, and that network communication has not been interrupted between the Log Server and Log Database machines. Log Server stops unexpectedly or will not start. Topic | Web Protection Solutions, vx, vx | Updated Oct 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. Filtering Service may also appear to have stopped if you restarted multiple Websense services, and they were not started in the correct order. When you restart multiple services, remember to start the Policy Database, Policy Broker, and Policy Server before starting other Websense services. To troubleshoot these problems.
If you are running Microsoft SQL Server Standard or Enterprise (not Express), double-click the SQLSERVERAGENT service to open a Properties dialog box, and verify that the Startup type is set to Automatic. This ensures that SQL Server Agent restarts each time Microsoft SQL Server, or the database engine machine, . This alert is displayed when the Websense RTM Server service is stopped. Use the Windows Services tool to verify that all 3 Websense RTM Database If the service is running, but the alert continues to appear, this may indicate that Real- Time Monitor was unable to register with Policy Server. Verify that the Policy. 3. Go to the Settings > Reporting > Log Server page. 4. Under Log Database Connection, click Test Connection. If the test fails. Perform the following steps: 1. Make sure the Microsoft SQL Server machine is running and connected to the network. 2. Make sure the connection port entry is correct, and that there is no firewall.
The Websense Policy Database service fails to start. Administrator Help | TRITON AP-WEB and Web Filter & Security | Version x. The Policy Database runs as a special account: WebsenseDBUser. If this account experiences logon problems, the Policy Database is unable to start. To address this issue, change the. Note. If Filtering Service is in the process of downloading the Master Database, it does not stop running until the download is complete. When you start all Websense services, always start with the policy services, in the reverse of the shutdown order (starting with Policy Database and ending with Policy Server). When you. Filtering Service may also appear to have stopped if you restarted multiple web protection services, and they were not started in the correct order. When you restart multiple services, remember to start the Policy Database, Policy Broker, and Policy Server before starting other services. To troubleshoot these problems: .