Symantec Endpoint Protection Manager (SEPM) SQL Database size (autogrowth)

book

Article ID: 156126

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

The Symantec Endpoint Protection Manager (SEPM) is unable to update to the latest definitions, update policies, add new clients, connect to the manager, or perform other duties because its database is full.

Could not allocate space for object
'dbo.AGENT_TRAFFIC_LOG_2' in database 'SEP_DATA' because the 'FG_LOGINFO'
filegroup is full. Create disk space by deleting unneeded files dropping
objects in the filegroup adding additional files to the filegroup or
setting autogrowth on for existing files in the filegroup.

Cause

The SQL Server database cannot grow further and is full.

Resolution

Adjust the size limit in SQL for Symantec Database using the following steps:

  1. Open SQL Server Management Studio.
  2. Connect to database instance containing the SEPM database
  3. Expand Databases. Find the database used by SEPM
  4. Right click on the database and select properties
  5. Click on Files
  6. Select the Autogrowth option for each of the entries and select the option "Unrestricted file growth"
  7. Close the windows and restart the SQL Database service
  8. If necessary, run Management Server Configuration Wizard to reconfigure the Symantec Endpoint Protection Manager

This problem could also appear when the MS SQL Server Express database is used in a production environment. SQL Express is not a supported version for Symantec Endpoint Protection database.