We have 10 workers registered. Migrations were working on all 10 workers. Had a break from migrations and now migrations only seem to be picked up and processing on 2 out of the 10 workers. I've rebooted all the workers and they all show "online" in the monitor. What am I missing?
This could happen if there are bad entries in the 'MigrationQueueTable" back-end table .
If you currently have migrations running, go to that worker and for the migration job click 'Pause' button on each worker.
For 3.8 and newer versions:
Open SQL Management Studio
Open the CMT for Exchange SQL database.
Open the MigrationQueuetable table and remove any and all entries not currently migrating.
Check if any user has a -1 in there record. If Yes, delete that record and or records, close the access database
Close SQL management studio
For 3.7 and older versions:
Open cmt.exe and go to the User queue
Locate the user(s) that are in a pending and right click them and choose Reset user.
The user should change to "Ready for migration" status.
Open the cmt_universal.mdb from C:\Program Files (x86)\BinaryTree\CMT for Exchange\CMT_XMLServer\App_Data
Run an IISreset from the start/run menu or cmd
Resume any migrations you paused.
Send the problem user(s) to migrate again.
If this does not resolve the issue, then open the back-end database again, and check the FarmHands table.
What value is in the 'Status_Text' and 'Online' columns for the workers not picking up jobs?
Send this information to email@example.com