Error: Cannot update the agent's database - when attempting to commit changes on a legacy mail or calendar sync collection (4314507)

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.

1. Click on Start, then Run and type - wmimgmt.msc
2. Once the Windows Management Instrumentation (WMI) console opens, right click on WMI Control (Local) and select Properties
3. The Properties page should display Processor and Operating System information about the local computer if WMI is functioning correctly.  However, if you see the following error continue to step 4  "Failed to initialize all WMI classes"
4. Click on Start, then Run and type - WBEMTEST.EXE  (This will open up the WMI Tester)
5. Click on Connect, leave ALL pre-filled default options as is and then click Connect again and validate if you are returned error "0x80041002 - WMI Not found"
6. Open a command prompt as "Administrator" and type - winmgmt /verifyrepository   If the repository is "INCONSISTENT" then run the next command
7. Type winmgmt /salvagerepository
8. Attempt the tests in steps 2 -> 4 again to ensure these now pass.

The following external article also contains further information on rebuilding the WMI Repository:
http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.aspx