Endpoint Encryption database creation fails

Products

• Endpoint Encryption
• Drive Encryption
• Desktop Email Encryption
• Encryption Management Server
• File Share Encryption
• Gateway Email Encryption
• PGP Command Line
• PGP Key Management Server
• PGP Key Mgmt Client Access and CLI API
• PGP SDK

Issue/Introduction

Installing Symantec Endpoint Encryption Server (SEEMS) fails, producing a SEEMSDb error.

SEEMS error window: Error executing database [SEEMSDb] creation script: database [SEEMSDb] creation failed The CREATE DATABASE statement failed.  The primary file must be at least 1024 MB to accommodate a copy of the model database.  Changed database context to 'master'.

You may also see the error MODIFY FILE failed. Specified size is less than or equal to current size:

Environment

Symantec Endpoint Encryption 11.3 and above.

Cause

When the Endpoint Encryption installer creates a new SEEMSDb database, it uses the Model database as a template.

The defaults of the model database vary depending on the version of SQL Server. For example, with SQL Server 2016, SQL Server 2017 and SQL Server 2019 the default initial size of both the model database  Primary data (model.mdf) and Log file (modellog.ldf) is 8 MB. The Primary data file is set to Autogrow by 64 MB until the disk is full. The Log file is set to Autogrow by 64 MB to a maximum of 2 TB.

If the file sizes of the model database are too large, there may not be sufficient disk space to create the initial SEEMSDb.

So too, if the model database has Autogrow disabled, it will not be possible to create the initial SEEMSDb.

Resolution

If the model database is too large, reduce it to its default size and use the default Autogrow settings. Restart the installation process and it should finish creating the SEEMSDb database successfully.

1. Open Microsoft SQL Server Management Studio.
2. Under Databases> System Databases, right-click on Model and open Properties.
3. Under 'Files', change the 'Initial Size (MB)' to, for example, 3. Click OK.