Another #550 5.1.1 RESOLVER.ADR.ExRecipNotFound problem

I am at my wits end with this problem and beg for your help.  Let me break it down for you:

We have a domain (we'll call it company.com) hosted on 3 DC's.  Mail is served up on a fresh new Exchange 2007 server.  About 4 months ago we transitioned from Exchange 2003 to 2007.  The 2003 server has since been completely decommissioned.  

When we create a distribution list (post-transition) and someone internally sends an e-mail to it (e-mails from external addresses seem to work fine), they get the following NDR:



Delivery has failed to these recipients or distribution lists:

apr28
The recipient's e-mail address was not found in the recipient's e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the e-mail address and try resending this message, or provide the following diagnostic text to your system administrator.

  _____  

Sent by Microsoft Exchange Server 2007







Diagnostic information for administrators:

Generating server: Mail.company.com

IMCEAEX-_O=NT5_ou=0294eba31c794b4faaab62a7669e5e71_cn=8a65b1506e9cff4daae931e15716ef1a@company.com
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

Original message headers:

Received: from Mail.company.com ([2002:8092:1a19::8092:1a19]) by
 Mail.company.com ([fe80::3453:3e8d:28a0:136e%12]) with mapi; Wed,
 31 Mar 2010 23:03:16 -0400
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Sender <sender@company.com>
To: apr28
      <IMCEAEX-_O=NT5_ou=0294eba31c794b4faaab62a7669e5e71_cn=8a65b1506e9cff4daae931e15716ef1a@company.com>
Date: Wed, 31 Mar 2010 23:03:16 -0400
Subject: test
Thread-Topic: test
Thread-Index: AcrRR9/6yMJ/whh6Td+7ET52mEqQOg==
Message-ID: <E8A0ABE2899EEB4C8A225977DB7086A34CC3981163@Mail.company.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <E8A0ABE2899EEB4C8A225977DB7086A34CC3981163@Mail.company.com>
MIME-Version: 1.0



I have checked the legacyExchangeDN value for the DL and it was <not set>, so I set it using one from another DL created prior to the transition that still works fine.  That didn't fix the problem.  

I've changed the purportedSearch values per the following links with no success:
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_24185173.html?sfQueryTermInfo=1+5.1.1+550+resolver.adr.exrecipnotfound
http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/813ec258-4de4-4f78-b249-b81a2c8363ce

I've added an X500 address with the ridiculous "IMCEAEX-_O=NT5_ou=0294eb...." nonsense with no success.

I've done all the basics like nuking the nk2 file, manually typing the address, re-downloading the OAB.

If I go into OWA and try to send to the DL, I get a message saying "You must choose a recipient before this message can be sent." when I hit Send.


Since I can't tell if this is all GAL-related, I'll mention that I'm also having some trouble getting new users to show up in the address lists and if I run Update-GlobalAddressList -identity "Default Global Address List" -vb I get the following:

VERBOSE: Update-GlobalAddressList : Beginning processing.
VERBOSE: Update-GlobalAddressList : Searching objects "Default Global Address List" of type "AddressBookBase" under the root $null".
VERBOSE: Update-GlobalAddressList : Previous operation run on domain controller 'dc1.company.com'.
VERBOSE: Update-GlobalAddressList : Processing object "\Default Global Address List".
VERBOSE: Updating all recipients matching the filter of global address list "Default Global Address List".
VERBOSE: Update-GlobalAddressList : The Address List Service on server "mail.company.com" will be used for the operation.
WARNING: The recipient "company.com/Microsoft Exchange System Objects/OAB Version 2" is invalid and could not be updated.
WARNING: The recipient "company.com/Microsoft Exchange System Objects/OAB Version 3a" is invalid and could not be updated.
WARNING: The recipient "company.com/Microsoft Exchange System Objects/Offline Address Book - \ /o=<our org>\ /cn=addrlists\ /cn=" is invalid and could not be updated.
WARNING: The recipient "company.com/Microsoft Exchange System Objects/Offline Address Book - First Administrative Group" is invalid and could not be updated.
WARNING: The recipient "company.com/Microsoft Exchange System Objects/Schedule+ Free Busy Information - First Administrative Group" is invalid and could not be updated.
VERBOSE: Update-GlobalAddressList : Saving object "\Default Global Address List" of type "AddressBookBase" and state "Unchanged".
VERBOSE: Update-GlobalAddressList : Previous operation run on domain controller 'dc1.company.com'.
VERBOSE: Update-GlobalAddressList : Ending processing.



Please help!
GlennSchoolAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MegaNuk3Commented:
Are you sure it is a distribution group and not a non-mail enabled security goup? Can you see it in the GAL or not?

All mail enabled objects should have a legacyExchangeDN
0
MegaNuk3Commented:
Can the apr28 DL/DG be seen under EMC\recipient Cofiguration\Distribution Group?

Can you run Get-DistributionGroup against it?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

GlennSchoolAuthor Commented:
Shreedhar:
I've previously read through both of those articles in my troubleshooting efforts and don't see anything that can help.

MegaNuk3:
It is a Mail-Enabled Universal Security Group.
I can see it in the GAL.
I manually set the legacyExchangeDN value to match a group created prior to the transition (/o=<our org>/ou=First Administrative Group/cn=Recipients/cn=apr28).  Should the legacyExchangeDN for new DL's point to First Administrative Group or Exchange Administrative Group?  Is there a way to make this auto-populate going forward?
I can see the apr28 DL under EMC\Recipient Configuration\Distribution Group.
When I run Get-DistributionGroup apr28 | fl I get the following:


GroupType                                             : Universal, SecurityEnabled
SamAccountName                                  : apr28
ExpansionServer                                    :
ReportToManagerEnabled                     : False
ReportToOriginatorEnabled                   : True
SendOofMessageToOriginatorEnabled  : False
ManagedBy                                            :
AcceptMessagesOnlyFrom                     : {}
AcceptMessagesOnlyFromDLMembers   : {}
AddressListMembership                         : {Default Global Address List, All Groups}
Alias                                                       : apr28
OrganizationalUnit                                 : company.com/our org/Groups
CustomAttribute1                                  :
CustomAttribute10                                :
CustomAttribute11                                :
CustomAttribute12                                :
CustomAttribute13                                :
CustomAttribute14                                :
CustomAttribute15                                :
CustomAttribute2                                  :
CustomAttribute3                                  :
CustomAttribute4                                  :
CustomAttribute5                                  :
CustomAttribute6                                  :
CustomAttribute7                                  :
CustomAttribute8                                  :
CustomAttribute9                                  :
DisplayName                                          : apr28
EmailAddresses                                     : {X500:IMCEAEX-_O=NT5_ou=0294eba31c794b4faaab62a7669e5e71_cn=8a65b1506e9cff4daae931e15716ef1a@company.com, SMTP:apr28
                                                                @company.com, X400:C=US;A= ;P=our org;O=Exchange;S=apr28;}
GrantSendOnBehalfTo                           : {}
HiddenFromAddressListsEnabled          : False
LegacyExchangeDN                               : /o=our org/ou=First Administrative Group/cn=Recipients/cn=apr28
MaxSendSize                                         : unlimited
MaxReceiveSize                                     : unlimited
PoliciesIncluded                                     : {}
PoliciesExcluded                                    : {{26491cfc-9e50-4857-861b-0cb8df22b5d7}}
EmailAddressPolicyEnabled                   : False
PrimarySmtpAddress                             : apr28@company.com
RecipientType                                        : MailUniversalSecurityGroup
RecipientTypeDetails                             : MailUniversalSecurityGroup
RejectMessagesFrom                            : {}
RejectMessagesFromDLMembers          : {}
RequireSenderAuthenticationEnabled   : False
SimpleDisplayName                               : apr28
UMDtmfMap                                           : {}
WindowsEmailAddress                          : apr28@company.com
IsValid                                                   : True
OriginatingServer                                  : dc1.company.com
ExchangeVersion                                   : 0.1 (8.0.535.0)
Name                                                     : apr28
DistinguishedName                                : CN=apr28,OU=Groups,OU=our org,DC=company,DC=com
Identity                                                  : company.com/our org/Groups/apr28
Guid                                                       : a68e22d2-5823-4ed9-a7e6-aa0a7803059e
ObjectCategory                                     : company.com/Configuration/Schema/Group
ObjectClass                                           : {top, group}
WhenChanged                                      : 4/1/2010 1:24:34 AM
WhenCreated                                        : 3/31/2010 7:02:46 PM
0
GlennSchoolAuthor Commented:
Also, I'm not sure which of the hundred changes I made yesterday might have made a difference, but now it allows me to send to the DL from OWA.  Another DL that I'm having the same problem with that I haven't touched still doesn't work in OWA.
0
GlennSchoolAuthor Commented:
Another update:

Within the last 20 minutes, something seems to have taken effect and the apr28 address now appears to work, but only after restarting Outlook and downloading the address book.  I've made the same changes to the apr15 address but it is still not working.

My followup questions are these:

1) Why could it be that this is the first time I've done a manual address book download in months where it actually showed some sort of progress?  In other words, instead of having the window open and close 4 seconds later, the progress bar moved and it appeared to actually be doing something.  If I do it again now, I get no such progress.  If I run the update-globaladdresslist cmdlet, I get the same results as in the original post.

2) If the problem is with the missing legacyExchangeDN value, why doesn't the apr15 address work after setting the value and forcing DC replication through ADS&S?

3) How can I make sure that the legacyExchangeDN  populates in the future?  I would hate to have to manually set this every time I set up a mailbox or DL.
0
GlennSchoolAuthor Commented:
Anyone?
0
MegaNuk3Commented:
How are you creating these DLs? Through EMC or EMS? If you create a new one through the console (EMC) does it become visible in the GAL and does it get a legacyExchangeDN or not?
0
GlennSchoolAuthor Commented:
I've created all of the new DL's through EMC.  The ones I've created recently seem to be showing up in the GAL, but for some reason they do not get a legacyExchangeDN value assigned to them.
0
MegaNuk3Commented:
Hmmm, remind me. are you on SBS 2008?

I have just tried creating a new DL on SBS 2008 SP1 and can veify that it gets a legacyExchangeDN value automatically.
0
MegaNuk3Commented:
If you did an intra Org upgrade (exchange 2003 was in the same Org as you new Exchange 2007 server) then you need to have a look at this article: http://msexchangeteam.com/archive/2007/01/11/432158.aspx

Which talks about updating your e-mail address policies from Exchange 2003 to Exchange 2007 so that they apply properly.

Run
Get-EmailAddressPolicy | where { $_.RecipientFilterType -eq "Legacy" }
and it should list any e-mail address policies that you have that need to be updated to work
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
GlennSchoolAuthor Commented:
Sorry for the delay, just got back from a much-needed vacation.  

We're running Server 2k8 Enterprise.  I had already done the policy updates, but when I ran a Get-EmailAddressPolicy | Format-List Name,*RecipientFilter*,ExchangeVersion, I noticed that the policy was not being applied.  I went through the gui wizard and applied the policy, created a new test DL, and found that it was given a legacyExchangeDN value!!!  YAY!!!!  


So that's one major problem down and I think I'm almost entirely out of the woods.  I'm still getting the following when I run Update-GlobalAddressList -identity "Default Global Address List" -vb:

VERBOSE: Update-GlobalAddressList : Beginning processing.
VERBOSE: Update-GlobalAddressList : Searching objects "Default Global Address List" of type "AddressBookBase" under the root $null".
VERBOSE: Update-GlobalAddressList : Previous operation run on domain controller 'dc1.company.com'.
VERBOSE: Update-GlobalAddressList : Processing object "\Default Global Address List".
VERBOSE: Updating all recipients matching the filter of global address list "Default Global Address List".
VERBOSE: Update-GlobalAddressList : The Address List Service on server "mail.company.com" will be used for the operation.
WARNING: The recipient "company.com/Microsoft Exchange System Objects/OAB Version 2" is invalid and could not be updated.
WARNING: The recipient "company.com/Microsoft Exchange System Objects/OAB Version 3a" is invalid and could not be updated.
WARNING: The recipient "company.com/Microsoft Exchange System Objects/Offline Address Book - \ /o=<our org>\ /cn=addrlists\ /cn=" is invalid and could not be updated.
WARNING: The recipient "company.com/Microsoft Exchange System Objects/Offline Address Book - First Administrative Group" is invalid and could not be updated.
WARNING: The recipient "company.com/Microsoft Exchange System Objects/Schedule+ Free Busy Information - First Administrative Group" is invalid and could not be updated.
VERBOSE: Update-GlobalAddressList : Saving object "\Default Global Address List" of type "AddressBookBase" and state "Unchanged".
VERBOSE: Update-GlobalAddressList : Previous operation run on domain controller 'dc1.company.com'.
VERBOSE: Update-GlobalAddressList : Ending processing.

Are these warnings normal or did I miss something else in the transition?
0
GlennSchoolAuthor Commented:
I think I just answered my own question with some more digging.  In case anyone in the future has the same problem, you need to go into adsiedit, look up the objects EMS is complaining about, check the mailnickname value, and replace all spaces with underscores.  More info here: http://social.technet.microsoft.com/Forums/en/exchangesvradmin/thread/1a819714-3f35-4109-a1a4-665e788d98dd

I believe most, if not all of my problems are now resolved!  Thanks to MegaNuk3 for pointing me toward the e-mail address policy.
0
MegaNuk3Commented:
Thanks for the update and that other information in your last post.

Glad we got there in the end.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.