When trying to create a new Translation Memory in the GS WebUI, the following error is thrown:

An internal server error occurred.
Failed to save TM resource data in database



In the TMService.log file the following error is captured:

2021-10-22 13:07:42.5804|SQLServerName|Error|THREAD_ID:125|TR_ID:db7cf3b0-b1ad-41ac-a76b-f8f42587cc4d|Error: System - The transaction log for database '_TMContainer' is full
 due to 'LOG_BACKUP'. (details: System.Data.SqlClient.SqlException (0x80131904): The transaction log for database '_TMContainer' is full due to 'LOG_BACKUP'.

Trying to open and/or add terms to the server-based Termbase is displaying the following error message

The transaction log for database 'MTMaster' is full due to 'LOG_BACKUP'.

 

Review Transaction/Backup Log size and/or disk space...

NOTE: The Transaction Log is not managed by SDL applications but rather by the Microsoft SQL Server.

To resolve this problem, contact your local/external (IT-) Database Administrator to handle/decide how and where to increase the limit or free up disk space.

This error occurs when the SQL Database Transaction Log reaches the limit of space available and therefore cannot ‘write’ data to the database anymore. Ask your database administrator to increase the limit or free up more space on the SQL Server.
It is also likely that the Recovery model for the database is set to Full instead of Simple. Change this to Simple to avoid again the issue.

If you are using SQL Server Express, this version is limited as to the size of databases.

Related articles

 

• Error message when opening a remote termbase: The transaction log for database 'tempdb' is full due to 'ACTIVE_TRANSACTION'
• Error message: The transaction log for database 'MTMaster_XX' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases