Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 137 Source: MSExchangeMTA
A fatal directory error occurred. Change to the maximum logging level for more details. [MTA MAIN BASE 1 15] (16).
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Exchange MTA Service?
How does one change the Exchange logging level?
As per Microsoft: "The value of the following registry key in the HKEY_LOCAL_MACHINE subtree does not match the corresponding directory entry: System\CurrentControlSet\Services\MSExchangeMTA\Parameters\X500 DN. The wrong Organization or Site name was used when Exchange Server was reinstalled on the server". See ME155027 to solve this problem.
See ME298954 and MSEX2K3DB for additional information on this event.
Check to make sure the Microsoft Exchange directory service is started. The MTA relies on the directory service to properly initialize. See ME170005, ME830828, ME840469, and ME840470 for more details.
MPSS had me run “c:\exchsrvr\dsadata>find /i "ou=" dir.edb |more” to query the DS for the OU info. Then checked this against the HKLM/system/currentcontrolset/services/MSExchangeMTA/Parameters X500 DN String. The /o= should equal the Dir.edb query from the above command. Changed the X500 DN string such that the /o is the same as the above find command.
|Private comment: Subscribers only. See example of private comment|
|Links: ME155027, ME170005, ME298954, ME830828, ME840469, ME840470, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated