Skip to main content
cromerofustes
Staff
Staff
July 6, 2026

Technical Tip: Resolving an upgrade failed error during FortiClient EMS update caused by the Microsoft SQL Server Express database reaching size limit

  • July 6, 2026
  • 0 replies
  • 15 views

Description

This article describes how to resolve the Setup Failed error 0x80070643 during a FortiClient EMS v7.2 upgrade.

Scope

FortiClient EMS v7.2 On-Premises using Microsoft SQL.

Solution

During the upgrade from FortiClient EMS v7.2.12 to v7.2.13 or v7.2.14, the installer may fail with the error Setup Failed and code 0x80070643.

In the installer logs, the following SQL error may be observed:

Could not allocate a new page for database 'FCM_default' because the 'PRIMARY' filegroup is full due to lack of storage space or database files reaching the maximum allowed size.


This behavior is consistent with the Microsoft SQL Server Express database reaching its 10 GB size limit.

To validate the database size, check the .mdf files in the following path:

C:\Program Files\Microsoft SQL Server\MSSQL12.FCEMS\MSSQL\DATA\


Before applying any change, create an EMS backup from EMS -> Dashboard -> Backup.


If EMS is running on a virtual machine, create a VM snapshot as well.


Stop all FortiClient EMS services from the Windows Services console. These services are usually listed as 'FCEMS_xxxx'.

Open cmd.exe as Administrator and connect to the EMS database:

sqlcmd -E -S.\fcems -d fcm_Default


Delete historical EMS events:

1> truncate table events
2> go
1> exit


Execute the database shrink operation:

sqlcmd -E -S.\fcems -d fcm_Default
1> DBCC SHRINKDATABASE(fcm_Default,10)
2> go
1> exit


The database name may vary between deployments. Validate whether the database is named fcm_Default, fcm_default, or fcm_root, and adjust the command accordingly.


Restart the FortiClient EMS services and run the upgrade again.


The EMS log retention setting removes records older than the configured retention period, but it does not necessarily reduce the physical size of the SQL Server .mdf file. For this reason, the database file may remain close to the SQL Server Express 10 GB limit even after old records are removed.


As a preventive measure, monitor the EMS database size periodically, keep regular EMS backups, and consider migrating to Microsoft SQL Server Standard or Enterprise if the EMS database continues growing near the SQL Server Express limit.