| Event Id | 2245 |
| Source | MSExchangeMTA |
| 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" |
| Event Information | According to Microsoft: CAUSE 1 : 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. RESOLUTION : Check the value of the registry key and edit it, if necessary, so that it matches the corresponding directory entry, or reinstall Exchange Server using the correct Organization and Site names. WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. 1. Start Registry Editor (Regedt32.exe). 2. Under the HKEY_LOCAL_MACHINE subtree, go to the following subkey: System\CurrentControlSet\Services\MSExchangeMTA\Parameters\X500 DN 3. Check the value for this key. The Organization [o=], Site [ou=], and Server Directory names [cn=] must exactly match the properties of the Organization, Site, and Server objects as they are displayed in the Exchange Server Administrator program. To see whether these objects match the value of the registry key: a. In the left pane of the Exchange Server Administrator program, click to expand the Organization object, click to expand the Site object, and then click to expand the Server object. b. On the File menu, click Properties. The Directory Name of each of these objects must exactly match the corresponding attributes in the registry setting described in step 3. CAUSE 2: This problem may occur after the Exchange Server computer is converted from a dirsync requestor to a dirsync server. When the first dirsync process was run, all MS Mail custom recipients participating in it were given a Distinguished Name (DN). This |
| Reference Links | Unable to Start Microsoft Exchange Server MTA
XFOR: DS_E_NO_SUCH_OBJECT Error During DirRep over IMC PAB Addresses Invalid After Converting to DirSync Server |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.