NM: MCC Stopped Processing Migrations (4300540)

Issue

MCC stopped processing migrations, in the Windows Event Viewer log, you see multiple

Autogrow of file 'NotesMigrator_CMT_log' in database 'NotesMigrator_CMT' was cancelled by user or timed out…. Use ALTER DATABASE to set a smaller FILEGROWTH value for this file or to explicitly set a new file size.

Solution

The "ALTER DATABASE statement failed" message indicates that you might have reached the capacity of your SQL database. Please follow the steps below:

Verify that there are no migrations running prior to checking the steps and shut down the migration workers (Exit Now on the system tray icon or shutdown Windows).

Open the SQL Management Studio on the controller (MCC).
Connect to the local SQL instance.
Expand the Databases.
Select the NotesMigrator_CMT database and right click that to select Tasks > Back Up.
In the dialog select to backup to Disk under the destination.
Click to add a disk location if one is not already present.
The default path can be retained and click (...) to add a file name (eg NotesMigratorBak191020)
Then click OK to run the backup.
Once complete right click the NotesMigrator_CMT database again and select Properties
Click on the Options and check the Recovery Model.
If the recovery Model is Full then change that to Simple.

Then expand the NotesMigrator_CMT tables, right click on the dbo.MigrationQueueTable and select to Edit Top 200.
If there are no migrations running (per the initial check) then there should not be anything in this table showing as status of "In Progress".
If there are any entries in this table then select and delete these (Pending migrations can be reset and re-submitted in Notes Migrator nsf after a restart).
Restart the Migration Controller.
Verify in IE the that cmt_xmlserver is available (http://controllerservername/cmt_xmlserver)
Start the Migration Workers (use Run As Administrator if that option is available on the desktop shortcut).
On the workers please confirm that the controller can be contacted through IE.
Verify the http://controllerservername/cmt_xmlserver and http://controllerservername/cmtmonitor pages.
Verify on the workers in the event log if there are errors reported.
Verify the controller event log and confirm if there are any errors (or Informational items regarding SQL).