Migration Manager for Active Directory

2nd RUM console getting error 0x80090005 Bad Data

Hello all-
I've set up a 2nd RUM console so front-line support can move straggler workstations without our intervention. Items to note:
* 2nd console attaches to the ADLDS database and enumerates the collections
• 2nd console has its own local ADLDS instance but set up as a replica of the ADLDS instance on the first console
• Both consoles use the same domain service account
• Server Windows Firewall is disabled on both consoles
* QMMAD version is 8.14

As soon as I try to push an agent, process or move from the 2nd console, the status remains in "In progress" and nothing happens. Both systems are on the same subnet with no firewalls between them. Looking at the RUMController.log I see the agent push session and the error
5/20/2019 10:35:08 AM 7372 Successfully connected to console.
5/20/2019 10:45:50 AM 4236 Analyzing task with ID: 4D739DAB1437784CB1D5C4BD10A233C4.
5/20/2019 10:45:52 AM 4236 Task will be started immediately.
5/20/2019 10:45:52 AM 4236 Task type is Discovery.
5/20/2019 10:45:52 AM 4236 Task contains 2 computer(s).
5/20/2019 10:45:52 AM 4236 Modifying object <GUID=4D739DAB1437784CB1D5C4BD10A233C4>
5/20/2019 10:45:52 AM 4236 aelita-Amm-Status
5/20/2019 10:45:52 AM 4236 update 3
5/20/2019 10:45:52 AM 4236 modification successful
5/20/2019 10:45:52 AM 3864 Modifying object <GUID=BF74B001E84D1B47ADFDF425E6126ED5>
5/20/2019 10:45:52 AM 3864 aelita-Amm-CurrentTask
5/20/2019 10:45:52 AM 3376 Modifying object <GUID=97EA020F58F1E04F9B9CE786C64A1C38>
5/20/2019 10:45:52 AM 3376 aelita-Amm-CurrentTask
5/20/2019 10:45:52 AM 3864 update <GUID=4D739DAB1437784CB1D5C4BD10A233C4>
5/20/2019 10:45:52 AM 3376 update <GUID=4D739DAB1437784CB1D5C4BD10A233C4>
5/20/2019 10:45:52 AM 3864 aelita-Amm-Error
5/20/2019 10:45:52 AM 3864 erase attribute
5/20/2019 10:45:52 AM 3376 aelita-Amm-Error
5/20/2019 10:45:52 AM 3376 erase attribute
5/20/2019 10:45:52 AM 3864 aelita-Amm-LastOperation
5/20/2019 10:45:52 AM 3376 aelita-Amm-LastOperation
5/20/2019 10:45:52 AM 3864 update 2
5/20/2019 10:45:52 AM 3864 aelita-Amm-LastOperationTime
5/20/2019 10:45:52 AM 3376 update 2
5/20/2019 10:45:52 AM 3864 update 20190520144552.0Z
5/20/2019 10:45:52 AM 3376 aelita-Amm-LastOperationTime
5/20/2019 10:45:52 AM 3864 aelita-Amm-Status
5/20/2019 10:45:52 AM 3376 update 20190520144552.0Z
5/20/2019 10:45:52 AM 3376 aelita-Amm-Status
5/20/2019 10:45:52 AM 3864 update 2
5/20/2019 10:45:52 AM 3376 update 2
5/20/2019 10:45:52 AM 3864 modification successful
5/20/2019 10:45:52 AM 3376 modification successful
5/20/2019 10:45:52 AM 3864 Error 0x80090005. Bad Data.
5/20/2019 10:45:52 AM 3376 Error 0x80090005. Bad Data.

I could not find this on the Quest resources referring to this error but it may be a generic Windows error.
Any insight as to what is causing this is greatly appreciated.
Regards,
Eric

: