Event ID/Source search
Keyword search
Example: Windows cannot unload your registry file
Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers
Sample report Custom views/filters Servers list, organized in groups Integration with EventID.Net Consolidated view for all logs Free for subscribersEvent ID: 2245 Source: MSExchangeMTA
| Source: MSExchangeMTA |
| Type: Warning |
| Description: Directory Operation failed with problem DS_E_NO_SUCH_OBJECT. Attribute. Directory Name [String]; \o=Organization\ou=Organizational_Unit\cn=Configuration\cn=Servers\cn=Server_Name\cn=Microsoft DSA. [RD server DISP; Router 11 114] [8] |
| English: Request a translation of the event description in plain English. |
| Concepts to understand: What is the role of the Exchange MTA Service? |
| Comments: EventID.Net 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. This problem may occur after the Exchange Server computer is converted from a dirsync requestor to a dirsync server. See ME181952 to find out why this event occurs and how to solve this problem.  x
1
EventID.Net If a site uses an MX wildcard record, the MX wildcard record directs all messages to that site. This can mean that the Internet Mail Service tries to send messages to its own IP address. See ME190711 to see how you can fix this. 
|
| Private comment: Subscribers only. See example of private comment |
| Links: ME155027, ME181952, ME190711 |
| Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... |
| Feedback:
Send comments or solutions
- Notify me when updated
|
| Printer friendly |
Subscribe to EventID.Net now!