Metabase Update failed replication %1 times with error %2.Please change the diagnostic logging level of MSExchangeMU to ‘minimum’ or greater to find the source of the problem.

Metabase Update Agent failed repeatedly.

This is probably not a sporadic failure. Obtain detailed event logs to find

the problem.

Set the following key in the registry to obtain more detailed event logs.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMU\Diagnostics]

“1 General”=dword:00000000

Here are some known causes of this event:

• Cause 1 – Internet Information Server (IIS) has been uninstalled and

  reinstalled, but Exchange server was not reinstalled.

• Cause 2 – The IIS Lockdown was not configured correctly to work with

  Exchange.

• Cause 3 – The metabase is not being updated with changes made to the

  Default SMTP Virtual Server due to unknown reasons — when checking the metabase with medaedit.exe,

  the changes are not being replicated.

• Cause 4 – Active Directory replication is not working properly or DSaccess

  problems are preventing directory replication. Changes to Active Directory are not being

  propagated to the metabase.

problem.

Set the following key in the registry to obtain more detailed event logs.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMU\Diagnostics]

“1 General”=dword:00000000

Resolutions for known causes as listed above:

• Resolution 1 – After reinstalling IIS and hotfixes, reinstall Exchange server (do not perform an uninstall of Exchange — only use the /reinstall). Then

  reinstall the same Exchange server service pack and hotfixes.

• Resolution 2 – Configure the IIS Lockdown Tool to work correctly with

  Exchange server.

• Resoluion 3 – This depends on the error. Search the Knowledge Base, and contact PSS if there is no resolution for the error indicated.
• Resolution 4 – Fix the root cause of active directory replication problems

  or add another DC as a replication partner or fix the root cause of the DSAccess problems.