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

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: March 27, 2019

Problem Description

During the install, there was an error creating the Log Database. How can a Log Database be created manually?
 

Resolution

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.
  • A new reporting database will be create if the database name passed in the CreateDbU command is not found on the SQL server.
  • An existing database will be upgraded if the database name passed in the CreateDbU command matches a database hosted on the SQL server.
  • The ODBC/Log Server connections and Service Broker/SQL Agent jobs will be regenerated if the database name passed in the CreateDbU command matches a database hosted on the SQL server.
Creating a new database with the CreateDbU utility using the SQL 'sa' account:
  1. Open a command prompt and navigate to the SQL directory.
    • v7.5 and prior: \Program Files\Websense\SQL
    • v7.6-8.5.x and higher: \Program Files\Websense\Web Security\SQL
  2. Use the appropriate parameters and be sure to include a space between each parameter. A sample command might be: 
    • CreateDbU "SQL_server" "sa" "password" "WSE" "LogServer" "wslogdb70" "C:\Program Files\Websense"
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:
  • 127.0.0.1,1433 
  • If the wslogdb70 database already exists, using that name in the command will upgrade that database.
  • If the wslogdb70 database does not already exist, it will create a new database with that name.

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:
  • CreateDbU "SQL_Server,port" "sa" "password" "WSE" "LogServer" "newlogdb70" "C:\Program Files\Websense"
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.)
  1. When the CreateDbU command finishes, open Microsoft SQL Server Management Studio and verify the databases were created. From the prior example in step 3, the following two databases should exist:
    • wslogdb70
    • wslogdb70_1
  2. If you ran the CreateDbU command because the database creation failed during installation, then open Windows Services and start the Websense Log Server service.  
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:

LogServer.exe -i
 
  1. From the TRITON Manager, click Settings > Reporting > Log Database. If necessary, update your Log Database path settings. Ensure the database paths shown are correct.
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.

  1. Using your Windows trusted account, log onto the server where Websense Log Server is installed.
  2. Open a DOS window, navigate to the SQL directory.
    • v7.5 and earlier: \Program Files\Websense\SQL
    • v7.6: \Program Files\Websense\Web Security\SQL
       
      Run the following command:
       
      CreateDbU "SQL_Server" "" "" "WSE" "LogServer" "wslogdb7x" "C:\Program Files\Websense"
  • If the database creation fails, then add the trusted account with Full security permissions on the folder where the database will be generated. 
  • The typical reason database creation fails when using a trusted connection is due to account permissions.
  • For a trusted connection to be successful, SQL Server must allow using mixed authentication as shown:
 User-added image
 

Article Feedback



Thank you for the feedback and comments.

Want 24/7 Tech Support?

Learn more