Symptoms

FlexNet Manager Suite processes may fail with an error similar to the following if the storage space for a SQL Server database file runs out:

Could not allocate space for object 'dbo.ComplianceHistory_MT'.'IX_ComplianceHistoryByContractNote' in database 'FNMSCompliance' because the 'PRIMARY' filegroup is full.

Error details like this will most commonly appear in log files associated with the affected processes. They may also appear in console output when running processes interactively on a command line on the application server.

Cause

Error messages like this are generally reported by SQL Server when storage space for a SQL Server database file runs out.

Resolution

Some items to check to resolve an out-of-space condition for a database file are:

1. Ensure the disk drive the file is stored on is not full.
2. Ensure the file is not configured in SQL Server with a fixed maximum size that has not been reached.
3. If the database file that has run out of space is a transaction log file, ensure backups are being taken of the transaction log with an appropriate frequency so it does not grow too large or grow indefinitely.

If you suspect the database file may be larger than expected, it may be helpful to review which database tables are consuming the most space. This can be done in SQL Server Management Studio as follows:

1. Right-click on the database in question.
2. Select the Reports > Standard Reports > Disk Usage by Top Tables menu option.