Log Database was not created
If the installer cannot create the Log Database, make sure that:
- The account used to log on for installation has inadequate SQL Server permissions to create a database. The required permissions depend on the version of Microsoft SQL Server:
- SQL Server Standard or Enterprise requires dbcreator server role membership, db_datareader role membership, and membership in one of the following roles:
- SSQLAgentUserRole
- SQLAgentReader Role
- SQLAgentOperator Role
- SQL Server Express: sysadmin permissions required
Update the logon account or log on with an account that already has the required permissions, then run the installer again.
- SQL Server Standard or Enterprise requires dbcreator server role membership, db_datareader role membership, and membership in one of the following roles:
- A file or files exist with the default Log Database names (wslogdb70 and wslogdb70_1), but the files are not properly connected to the database engine and cannot be used by the Forcepoint Web
Security installer.
To address this issue:
- If you don’t want to upgrade the existing database files, remove or rename them, and then run the installer again.
- If the existing database files are from a version that can be upgraded, and you want to continue using them, use the SQL Server Management Studio to attach the files to the database engine, then run the installer again.
- The account used to run the installer has inadequate permissions on the drive where the database is being installed.
Update the logon account to have read and write permissions for the installation location, or log on with a different account that already has these permissions. Then, run the installer again.
- There is insufficient disk space available to create and maintain the Log Database at the specified location.
Clear enough space on the selected disk to install and maintain the Log Database. Then, run the installer again. Alternatively, choose another location.