Manually creating or upgrading a catalog database
- Article Number: 000010561
- Products: Forcepoint URL Filtering, Forcepoint Web Security, TRITON AP-WEB, Web Filter & Security, Web Security Gateway, Web Security Gateway Anywhere, Web Security and Web Filter
- Version: 8.5, 8.4, 8.3, 8.2, 8.1, 8.0, 7.8, 7.7, 7.6
- Last Published Date: June 24, 2020
During the install, there was an error creating the Log Database. How can a Log Database be created manually?
In order to create a Log Database manually, follow the instructions below for the appropriate version:
Version 8.4 - 8.5 - Manually Creating the Log Database
Version 8.2 - 8.3 - Manually Creating the Log Database
Version 8.0 - 8.1 - Manually Creating the Log Database
Version 7.8 - 8.0 - Manually Creating the Web Security Log Database
Version 7.7 - Manually Creating the Web Security Log Database
Version 7.5 - 7.6 - See below for information
It is crucial to enter the exact path where the database will reside. For off-box (remote) SQL Servers, confirm the destination path exists prior to running the Log Server installation. The typical reason database creation fails is due to an incorrectly entered or unexpected directory path. SQL Server may not have local permission to create a new database outside its own directory structure. If you encounter this issue, try using the same directory where the SQL default system 'master' database resides. This failure occurs often with SQL 2008 Server.
By running the CreateDbU.exe utility, you can (1) manually create a new Websense reporting database, (2) upgrade tables in an existing database, or (3) automatically regenerate the ODBC and Log Server connections, and the Service Broker/SQL Agent jobs.
If SQL Server is running on a non standard port, then you need to embed the port number along with the SQL Server name. SQL Server has its own format, “ServerName,ServerPort”. For example:
When connecting to SQL Server listening on a non standard port, insert the server name and port number together in the above format and place it where you usually enter the SQL Server name. A CreateDbU example with SQL Server running on a non standard port follows:
The previous command contains the following parameters:
- CreateDbU is the executable
- SQL Server host name or SQLSERVER\INSTANCENAME
- user name or "" (The paired quotation marks indicate a trusted connection.)
- password or "" (The paired quotation marks indicate no password for trusted connection.)
- WSE (This option indicates Websense software type.)
- LogServer (This option indicates the component that will use the catalog database.)
- Database name (Do not start the name with a number or special character. If you do, database creation will fail.)
- Database Path (This is the full path to the location where the database will be created. For example: C:\Program Files\Websense\Web Security\SQL. If SQL Server is located off-box, then the path must already exist as the CreateDbU command cannot create it remotely.)
If the Websense installer shows that the Log Server is installed, yet the Log Server service does not appear in the Windows Services dialog box, then from the Websense bin directory, run the following DOS command to install the service:
For details, see article: Log Server Configuration States "Service Was Not Found"
If you are activity filtering, then within a few minutes new data should appear in Investigative Reports and the graphs on the Today Page.
To force the CreateDBU utility to use a trusted connection.
CreateDbU.exe; manual; create database; logging; setup; install; log server; wslogdb70; Manually Creating the Log Database; installation; error; linked kba; upgrade; SQL; dba