Endpoint Protection Manager using a Microsoft SQL database no longer hosts the latest definitions and install packages

Products

• Endpoint Protection

Issue/Introduction

A Symantec Endpoint Protection Manager (SEPM) that uses a Microsoft SQL database no longer applies new content updates or client installation packages.

Manual or scheduled LiveUpdate sessions shows Liveupdate successfully updated the content however no updates are downloaded.

Applying Intelligent Updater or importing client packages into the SEPM fails to update the SEPM database.

 

scm-server.log shows below error :

 

2023-11-22 13:53:18.243 THREAD 19 SEVERE: Unexpected server error. in: com.sygate.scm.server.consolemanager.requesthandler.ConfigServerHandler

com.sygate.scm.server.metadata.MetadataException: Could not allocate space for object 'dbo.BINARY_FILE' in database 'sepm' because the 'FG_CONTENT' 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 SEPM installation sets a default maximum size for the FG_CONTENT filegroup to 20,000 MB in size.

This space is used by content (virus definitions, IPS signatures, etc) as well as client packages that can be exported by the SEPM.  This amount of space can handle all existing client packages (current version and all historical packages) and the default enterprise content retention of 30 revisions. Storing more content revisions may require a SQL administrator to increase the maximum autogrowth size of the FG_CONTENT filegroup.

The default size may no longer be large enough for 30 revisions.  You can monitor the size in case the maximum size needs to be increased.

Resolution

If you require more than 30 revisions of content, work with your database administrator to increase the maximum Autogrowth size for the database file(s) in the FG_CONTENT file group. If you do not require a large number of content revisions, this problem can be worked around by lowering the number of content revisions stored in your SEPM database to the default of 30.

Increasing the maximum Autogrowth size

You will need to increase the maximum Autogrowth setting for the file(s) in the FG_CONTENT Filegroup for each revision of content above the default maximum of 30 you wish to keep. This will ensure the database allows for enough expansion to prevent this problem in the future.

Note: A single revision of content will use approximately 765 MB of space. This number grows each day.

Reducing the number of content revisions

• Log in to the SEPM console
• Click Admin > Servers > Local Site.
• Click Edit Site Properties > LiveUpdate.
• Change the value of "Number of content revisions to keep:" to 30 or less.
• Click OK.