Documentation | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Troubleshooting > Log Server and Log Database issues > Log Server is not recording data in the Log Database
Log Server is not recording data in the Log Database
Administrator Help | Forcepoint Web Security and Forcepoint URL Filtering | v8.5.x
Usually, when Log Server is unable to write data to the Log Database, the database has run out of allocated disk space. This can occur either when the disk drive is full, or in the case of Microsoft SQL Server, if there is a maximum size set for how large the database can grow.
If the disk drive that houses the Log Database is full, you must add disk space to the machine to restore logging.
If your SQL Server Database Administrator has set a maximum size for how large an individual database within Microsoft SQL Server can grow, do one of the following:
*
Contact your SQL Server Database Administrator to increase the maximum.
*
Find out the maximum size, and go to the Settings > Reporting > Log Database page to configure the Log Database to roll over when it reaches approximate 90% of the maximum size. See Configuring database partition options.
If your IT department has established a maximum amount of disk space for SQL Server operations, contact them for assistance.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Troubleshooting > Log Server and Log Database issues > Log Server is not recording data in the Log Database
Copyright 2023 Forcepoint. All rights reserved.