![]() Note the last few characters got truncated and removed. “ /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Faris Malaeb – (Corp System Engineerin“ The LegacyExchangeDN can hold up to 128 characters, so if the path is longer than what the attribute can hold, the path is truncated to be something like this. Note that the LegacyExchangeDN might hold other value, depend on the Exchange Server version and object history “ /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Faris Malaeb – (Corp System Engineering)“ The LegacyExchangeDN path should be something like So, lets assume that a user is named “ Faris Malaeb – (Corp System Engineering)“. ![]() The legacyExchangeDNholds the path for the user object in the exchange organization. ![]() One possible cause is a white space in the Active Directory user attribute and precisely in the legacyExchangeDN attribute. But in my case, none of these was the cause. Some of these fixes are related to starting Outlook in Safemode Outlook /safe or recreating the user profile… up to reinstalling Outlook itself. Multiple websites talk about the possible fix, but still no fix. How legacyExchangeDN can cause issues with outlook In this post, you will learn how to fix this outlook issue easily. The attempt to log on to Microsoft Exchange has failed“ Outlook users may face an issue when trying to connect to Exchange Server, where Outlook won’t start and instead shows the following error message “ Cannot Start Microsoft Outlook.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |