Thursday, January 2, 2014

The name cannot be resolved. The Name cannot be matched to a name in the address list.

I have worked on Mailbox Profile connection issue which is Unknown Issue on the regular practice, which makes me more curious to understand to resolve the issue and finally I have resolved it J. So I alleged to share with you for future reference. 

Issue: - Unable to configure Outlook Profile on Windows Desktop/Laptop. 

Error Message: - The name cannot be resolved. The Name cannot be matched to a name in the address list. 

Problem Statement: -
The default solution is navigate to the user’s account on the Exchange Server and make sure that the checkbox is not checked “Hide name from address list”.
This solution could work for some, but as Exchange administrators we found this too basic. But in our scenario it’s not hidden from GAL and user able to access the mailbox via Webmail.
Let’s take a deeper look at the error message “Name cannot be matched to a name in the address list”, usually Microsoft errors are generic error codes, such as object cannot be found0X000, error 1253 etc.
However, there is no numbered error. In our experience, this error message is stating that the user cannot be matched in an address list. Now here comes the strange part:
How can a user not match an address list when Outlook hasn’t even made a connection to an Exchange server to check if that user exists or not?
The reason why the error message is generated is that – there are address list traces Exchange Legacy DN in AD which get mismatch with Exchange DN,
Therefore failing with the error “Name cannot be matched to a name in the address list”.
Troubleshooting Steps: -
1.    Checked the user mailbox MAPI Connectivity through Exchange Management Shell which get passed without any error message.
Test-MAPIConnectivity -Identity ""
MailboxServer      Database           Result    Error
-------------      --------           ------    -----
EXCH007           DB07               Success 
2.    Checked user mail flow inbound/Outbound it give the impression be to working fine,
Test-Mailflow -TargetEmailAddress
TestMailflowResult : Success
MessageLatencyTime : 00:00:03.3680852
IsRemoteTest       : True
Identity           :
IsValid            : True
3. Verified mailbox Active Directory Properties settings and found LegacyExchangeDN mismatched with user name.
4.   Checked user mailbox Autodiscover connectivity over the Internet using and got the error stating “ The email address could not matched with mailbox”.
Resolution: - 
To resolve this issue, I have modified LegacyExchangeDN value, 
a.       Start the ADSIEDIT.msc and navigate to user organizational unit, Select the user account properties and change the LegacyExchangeDN value as descripted below,
Note: - Doing attributes modification through ADSIEDIT incorrectly could damage the User account. Please be cautious while doing the change.
After Active Directory replication the LegacyExchangeDN look like below, 
LegacyExchangeDN                       : /o=ORG/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Bolden, LaRhonda
b.       Start the Active Directory Users and Computers snap-in, click View, and then make sure that Advanced Features is checked. 
Right-click Users, click the Security tab, and then click the Authenticated Users group. 
Verify that Read permissions are assigned to either the Users container or to the organizational unit where the accounts are located.
Keep Visit.