After modifying the mail or calendar synchronization job on the console and clicking Commit Changes the message is displayed:
"Cannot commit changes for the selected job. If you are sure it's not connectivity or an access error, Project Manager can try to fix project database inconsistencies. Do you want to check database consistency now?"
In addition to this when you click Yes to check database consistency another error may open displaying that there were not inconsistencies with the database and please check if network problems are preventing connections to the servers.
There may be three causes of this issue:
1. Project Database inconsistencies.
2. Communication failure between the console and one of the source or target Exchange servers.
3. Local agent database corruption on one of the mail servers.
Take the following steps to fix the issue:
Project Database inconsistencies.
Click "Yes" to the message and see if any inconsistencies were fixed in the project database. Try to Commit Changes again.
Communication failure between the console and one of the source or target Exchange servers.
- Ping source and target Exchange servers from the console.
- Try to access C$ and QMMEX$SERVER_NAME$ shares on the source and target exchange servers from the console.
Local agent database corruption on one of the mail servers.
Depending on if it's calendar or mail synchronization job that is experiencing the problem please:
The agents can be uninstalledinstalled by right-clicking on the Exchange Migration Project within the EMW console, and choosing install/uninstall agents. This will launch the Agents Installation Wizard.
You can determine which agents is having the problem with a corrupt database by performing the following:
Pick an agent to start with, for example the MTA. Go to the Mail Target Agent folder on the target server and find the file, EMWMTA.mdb. Open the file in Microsoft Access and try to run Database Utilities under Tools | Database Utilities | Compact and Repair Database. If you can, then the database may have been repaired.
Try to commit the changes again to see if you still get the error. If so, go to the Mail Source Agent folder on the Source server, find the EMWMSA.mdb file and do the same as for the EMWMTA.mdb file. If successful the try to commit the changes.
One error you may get when opening the database is, "AOIndex is not an index in this table". The only way to repair this is to uninstalled and re-installed the appropriate Agent.