Committing changes to a Legacy Mail or Calendar sync collection fails, with the following error:
"Cannot update the agents database"
The following lines will also be present in the Migration Manager Console log (EMWMigration.log):
MMECluster::Factory::GetOSVersion Error: (Cannot connect to 'hostname' using WMI.)
MMECluster::Factory::Create Error: (Cannot get OS version on hostname)
Px1980 Tx1 A- C- M- Trace Connect using WMI. Server: 'hostname'. Namespace: 'root\cimv2'. Username: 'DOMAIN\Service_Account'.
MMExConsoleCore|Quest.MigrationManager.Exchange.Core.AdvancedServerInfo.IsAvailable Warning: hostname: Not found
aeEMWCommit::JobBase::BeforeUpdate Error: (hostname: Cannot connect to the server where the agent's database is located.)
The Migration Manager Console host uses the WMI protocol to connect to the remote Mail or Calendar agent hosts, to update their Config.mdb file when committing changes. If there is anything malfunctioning with WMI on the agent host, the console will not be able to successfully push out changes.
These errors can been seen if the WMI Repository on the agent host becomes corrupted.
Using the hostname information in the EMWMigration.log file, log into the affected agent host and perform the following steps to confirm the issue, as well as correct it if validated.
*NOTE* - If attempting to repair the WMI repository fails, please contact the Operating System vendor (Microsoft) for further support.
The following external article also contains further information on rebuilding the WMI Repository: