When trying to run a migration session in Quest Migration Manager (QMM) an error is displayed similar to the following:
Migration session failed.
Cannot send to message queue DIRECT=OS:.private$ACD03D2126A93D43A7C487E48D199752_Request.
Error 0xc00e0027. There are insufficient resources to perform this operation. (source=MSMQMessage).
If synchronization is running, dsa.log may contain error messages like:
02/07/12 14:23:30 (GMT+01:00) Common AcAdTaskHandler Error 0xc00e0027. There are insufficient resources to perform this operation. (source=MSMQMessage).
or
09/12/11 16:37:28 (GMT+01:00) Common JobID:0 -> Error 0xe1000045. Cannot send to message queue DIRECT=OS:.\private$\[queue name]
Error 0xc00e0027. There are insufficient resources to perform this operation. (source=MSMQMessage).
Most common reason for this error is running into the MSMQ limits or lack of disk space on the system drive of the DSA machine.
Alternatively, similar error may be generated when Domain Controller was removed or replaced without stopping Synchronization first
Perform the following steps to resolve the problem:
1) Make sure there's enough disk space for the system to work.
2) Restart the DSA server. Before the restart, check that there is sufficient disk space on the system driver and the drive where DSA is installed. If not, please free up disk space.
3) Increase the MSMQ quota size on DSA machine to twice that of the current setting under "Computer Management | Services and Applications | Message Queuing | Properties | General Tab | Limit Message Storage to KB" setting.
After increasing the storage size of the message queuing on the DSA server it will be able to handle larger number of transactions.
If above methods do not help, there is an option to purge the existing queue contents, which requires technical support overview. Please raise a support case if increasing MSMQ limit does not resolve the problem.
In the separate case, when DC was removed in the middle of migration, MSMQ may still contain messages, pointing to the original machine. To resolve the issue, it's possible to temporarily create a HOSTS entry, pointing to the working DC instead of removed one on DSA machine. Please check Event Viewer to find entries like:
Event ID: 69
Cannot send to message queue DIRECT=OS:.\private$\62503FB14BBEAF4AAEF53CD821C8B514_Request.
Event ID: 78
Cannot connect to host "<removed_DC_name>"
Event ID: 4
The network name cannot be found.
Event ID: 129
Task Handler, cannot connect to directory
Event ID: 44
Cannot make the LDAP connection with host: <removed_DC_name> port: 389.
