Hello Experts,
Does anyone know how to fix metabase errors/sync erros and/or what is the path that is not being found? By the way, the reporting level is set as per the article but it does not provide more info.
SBS 2003 SP1/Exchange SP2
Thanks in advanced.
Pedro
Event Type: Warning
Event Source: MSExchangeMU
Event Category: General
Event ID: 1040
Date: 9/20/2006
Time: 8:36:56 AM
User: N/A
Computer: KPI
Description:
Metabase Update failed replication 5 times with error 80070003 (The system cannot find the path specified.). Please change the diagnostic logging level of MSExchangeMU to 'minimum' or greater to find the source of the problem.
For more information, click
http://www.microsoft.com/contentredirect.asp.
--------------------------
----------
----------
----------
----------
----------
----------
----------
----
Details (from above link)
Product: Exchange
Event ID: 1040
Source: MSExchangeMU
Version: 6.5.0000.0
Message: 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.
Explanation
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
\CurrentCo
ntrolSet\S
ervices\MS
ExchangeMU
\Diagnosti
cs]
"1 General"=dword:00000000
(this is done already)
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.
User Action
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
\CurrentCo
ntrolSet\S
ervices\MS
ExchangeMU
\Diagnosti
cs]
"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.
Version: 6.5.6940.0
Component: Microsoft Exchange Metabase Update
Message: Metabase Update failed replication <number> times with error <error code>.Please change the diagnostic logging level of MSExchangeMU to 'minimum' or greater to find the source of the problem.
Explanation
Metabase Update Agent failed repeatedly.
This is probably not a sporadic failure. Obtain detailed event logs to find the problem.
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.
User Action
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
\CurrentCo
ntrolSet\S
ervices\MS
ExchangeMU
\Diagnosti
cs]
"1 General"=dword:00000000
The following are resolutions for the known causes listed above:
Resolution 1 - After reinstalling IIS and hotfixes, reinstall Exchange server (do not perform an UNINSTALL of Exchange - only use the REINSTALL from the SETUP menu). Then apply the same Exchange server service pack and hotfixes that were present before.
Resolution 2 - Configure the IIS Lockdown Tool to work correctly with Exchange server.
Resolution 3 - This depends on the error. Search the Microsoft Knowledge Base, and contact Microsoft Product Support Services 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.
--------------------------
----------
----------
----------
----------
----------
----
Currently there are no Microsoft Knowledge Base articles available for this specific error or event message. For information about other support options you can use to find answers online, see
http://support.microsoft.com/default.aspx.
Related Sites
Exchange Server TechCenter
Connect to Exchange Server-related technical articles and other resources developed by Microsoft and the broader Exchange Server community.
Downloads for Exchange Server 2003
Use this site to download the latest product updates and tools.
Exchange Server 2003 Support Center
Visit the Exchange Server 2003 Support Center for links to common questions and answers, instructions, most popular downloads, and more. From the Support Center, you can also search the Microsoft Product Support Knowledge Base and contact Microsoft Product Support Services.
Start Free Trial
