To resolve the issue:

1. Stop the following services:
   1. Trend Micro Control Manager service
   2. Trend Micro Management Infrastructure service.
2. Back up the TMCM database.
3. Shrink the TMCM database transaction log. Choose one of the following options:
   EXPAND ALL

   Option 1: Shrink a log file using Object Explorer in Microsoft SQL management Studio

   1. In Object Explorer, connect to an instance of the SQL Server Database Engine and then expand that instance.
   2. Expand Databases, and then right-click the database that you want to shrink.
   3. Point to Tasks, point to Shrink, and then click Files.
   4. Do the following:
      1. Select Log as the file type.
      2. Mark the Release unused space check box.
         Selecting this option causes any unused space in the file to be released to the operating system and shrinks the file to the last allocated extent. This reduces the file size without moving any data.
   5. Click OK.

   If you still need more help with shrinking the transaction log using this method, refer to theMicrosoft article: Shrinking the Transaction Log.

   Option 2: Shrink a log file using a Microsoft SQL Query

   Execute the following SQL query:

   BACKUP LOG <TMCM db Name>_Log WITH TRUNCATE_ONLY
   GO
   DBCC SHRINKFILE(<TMCM db Name>_Log , 10)
   GO

   The <TMCM DB name> is the name of the Control Manager database. For example, if the name of the Control Manager database is db_controlManager, the command would be the following:

   BACKUP LOG db_ControlManager_Log WITH TRUNCATE_ONLY
   GO
   DBCC SHRINKFILE(db_ControlManager_Log , 10)
   GO

   Since BACKUP LOG WITH TRUNCATE_ONLY is no longer a recognized BACKUP option in SQL Express 2008 you will encounter the following error after executing this query:

   Msg 155, Level 15, State 1, Line 1
   'TRUNCATE_ONLY' is not a recognized BACKUP option.

   Another way of shrinking the transaction logs in SQL server 2008 Express is to send Log Backups to “NUL:” using command:

   BACKUP LOG [db_name] TO DISK = N'Nul:

    

   This problem has been resolved in TMCM 6.0 Patch 4 and the fix is also included in TMCM 6.0 SP1.
4. Start the following services:
   • Trend Micro Management Infrastructure service
   • Trend Micro Control Manager service.