Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 2245 Source: MSExchangeMTA

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]
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.
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.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.