Backup transaction log
When the transaction logs are full, you must immediately back up your transaction log file. While the backup of your transaction log files is created, SQL Server automatically truncates the inactive part of the transaction log. The inactive part of the transaction log file contains the completed transactions, and therefore, the transaction log file is no longer used by SQL Server during the recovery process. SQL Server reuses this truncated, inactive space in the transaction log instead of permitting the transaction log to continue to grow and to use more space.
To Backup a transaction log
1. In SQL Server Management Studio, Expand Databases
2. Right-click GEMSDb database, point to Tasks, and then click Back Up. The Back Up Database dialog box appears.
3. In the Database list box, verify the database name.
4. Verify that the recovery model is either FULL or BULK_LOGGED.
5. In the Backup type list box, select Transaction Log.
Set Autogrowth to "Unrestricted"
1. In SQL Server Management Studio, right click on GEMSDb the database.
2. Go to Properties.
3. Then go to the Files section.
4. Click on both the data and log autogrowth column (Click the ...)
5. Select “ Unrestricted File Growth”
Note : This also applies for the error : "Transaction log for database SEEMDb is full"
Running GuardianEdge or Symantec Endpoint Encryption