User move stalls or fails at administrative level

Move user status stuck at "destination domain updated - DB2A"
The destination domain shows "ADM: Error" [DB2A] Update replica User"

This error may repeat frequently in the destination domain log file.

 

The primary domain and all other domains except for the destination domain shows the user has been moved to the destination domain.

The destination domain shows the user as not having been moved.

This error occurs when there is a discrepancy between the primary domain and the destination domain. To fix this error you need to rebuild the secondary domain database of the destination domain. This will get the information in both domains on the same page and allow the move admin messages to complete properly. After the admin message that was causing the error should now process successfully and the move should continue.