Summary

Symptoms

When attempting to save a record in FlexNet Manager error "PRIMARY' filegroup is full" is displayed, this may also be present in the Compliance Import log file. This error will occur when any action that alters data in FlexNet Manager is attempted.

The full error message is outlined below:

"---Problem---

(s0m0): FlexNet Manager Platform is unable to save your changes. Please click More to see detailed error information.

---System exception---

System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> ManageSoft.Compliance.ComplianceException: Could not save asset 'Apple Mac mini'. ---> System.Data.SqlClient.SqlException: Could not allocate space for object 'dbo.ComplianceHistory_MT'.'IX_ComplianceHistoryByContractNote' in database 'Managesoft' because the 'PRIMARY' 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.

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)

at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)

at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)

at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)

at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

at ManageSoft.Database.DatabaseCommand.ExecuteNonQuery()

at ManageSoft.Database.Impl.DatabaseLayerBaseSql.Execute(CommandType p_CommandType, String p_CommandText, DatabaseParameter[] p_Parameters)

at ManageSoft.Database.Impl.DatabaseLayerBase.Execute(String p_StoredProcedure, DatabaseParameter[] p_Parameters)

at ManageSoft.Compliance.Database.Impl.AssetTable.UpdateObject(DatabaseObject p_Object, Boolean p_Resync)

at ManageSoft.Database.Impl.DatabaseTableBase.UpdateRecurse(DatabaseObject p_Object, Hashtable p_UniqueTables, Boolean p_Resync)

at ManageSoft.Database.Impl.DatabaseTableBase.Save(DatabaseObject p_Object)

at ManageSoft.Compliance.Database.Impl.AssetTable.Save(Asset p_Object)

at ManageSoft.Compliance.Logic.Core.Impl.AssetPersistence.SaveAssets(AssetPropertyAdapter p_PropertyAdapter, Int32[] p_AssetIDs, AssetCollection p_AssetCollection)

at ManageSoft.Compliance.Logic.Core.Impl.AssetPersistence.Save(AssetPropertyAdapter& p_PropertyAdapter, Int32[] p_AssetIDs)

--- End of inner exception stack trace ---

at ManageSoft.Compliance.Logic.Core.Impl.AssetPersistence.Save(AssetPropertyAdapter& p_PropertyAdapter, Int32[] p_AssetIDs)

at ManageSoft.Compliance.Logic.Core.Impl.ComplianceCoreServiceBase.AssetPropertyAdapterSave(AssetPropertyAdapter& p_AssetPropertyAdapter, Int32[] p_AssetIDs)

--- End of inner exception stack trace ---

---Source---

ManageSoft.Compliance.Common.Presentation.PropertiesDisplay"

Cause

This error message is caused by lack of space on the database machine, this prevents any new data being written into the FlexNet Manager database, you may also see similar errors with other applications that use the same database server. Consulting with your Database Administrator should help to verify if this is cause the issue.

Resolution

Additional Information