Technical Library | Support

Go to the table of contents Go to the previous page Go to the next page
Log Server Troubleshooting Guide : Log Server installation: Error creating the Log Database
Log Server installation: Error creating the Log Database
Topic 51252 | Web Protection Solutions, v8.0.x, v8.1.x | Updated 12-Oct-2015
If the installer encounters problems creating the Log Database, you can either:
*
Exit the installer, correct the problem, and re-run the installer.
*
Complete the installation, then correct the problem and manually create the Log Database (see Manually Creating the Log Database).
If you choose this option, note that Log Server cannot start until the Log Database has been created.
To address the problem:
1.
Make sure the database location that you specified currently exists on the SQL Server machine.
2.
Verify that the account used to run the installer has read and write permissions to the database location.
If a custom path has been selected, the SQL Server process must have adequate file system permissions for database file creation in the specified location.
3.
Make sure there is sufficient disk space on the SQL machine to create the Log Database files.
This may mean creating the Log Database on a drive other than C.
4.
Check to see if a file or files with the default Log Database names (wslogdb70 and wslogdb70_1) already exist.
*
In order for existing database files to be used by the installer, they must be properly connected to the database engine.
*
If the files exist but are not connected, either connect the files to the database engine, or remove them before continuing.
5.
Use SQL Server Management Studio to make sure the Initial Size defined for the model database does not exceed 10MB.

Go to the table of contents Go to the previous page Go to the next page
Log Server Troubleshooting Guide : Log Server installation: Error creating the Log Database
Copyright 2016 Forcepoint LLC. All rights reserved.