When the AddressBookPolicyRoutingEnabled attribute is enabled by running Set-TransportConfig -AddressBookPolicyRoutingEnabled $True, I am having an issue with delivery failures for mailboxes that are hidden from the address book. I receive the following undeliverable message:

'532 5.3.2 STOREDRV.Deliver; Missing or bad StoreDriver MDB properties'

If I disable the AddressBookPolicyRoutingEnabled attribute by running Set-TransportConfig -AddressBookPolicyRoutingEnabled $False then emails are successfully delivered to the mailbox that is hidden from the address list.

I followed the installation instructions here: http://technet.microsoft.com/en-us/library/jj907308(v=exchg.150).aspx

Below is the status of the ABP Routing Agent on my Hub Transport/Mailbox server:

Enabled: True
Priority: 5
TransportAgentFactory: Microsoft.Exchange.Transport.Agent.AddressBookPolicyRoutingAgent.AddressBookPolicyRoutingAgentFactory
AssemblyPath: C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\AddressBookPolicyRoutingAgent\Microsoft.Exchange.Transport.Agent.AddressBookPolicyRoutingAgent.dll
Identity: ABP Routing Agent
IsValid: True
ObjectState: New

Has anyone else run into this issue yet?

In the multi-tenant document Microsoft says that one should not use the "hide from addresslist" attribute on the users. I guess this is because of the Routing Agent.

Reference:

http://www.microsoft.com/en-us/download/details.aspx?id=36790

No, that's not quite the same issue. I know, as I wrote the guidance. The issue with users hidden from the GAL and the ABP agent is a bug. I am working on getting it fixed. For now there's only one workaround, don't hide users from the GAL, or don't use the agent. :-(

• Proposed as answer by Rufuso_12 Saturday, April 27, 2013 9:39 AM
• Marked as answer by Simon_WuMicrosoft contingent staff, Moderator Wednesday, May 01, 2013 3:28 AM

Thank you Greg! Hopefully it will be fixed in CU2!

@Greg

Do you know if this was resolved in CU2? I read the release notes and it doesn't appear to be included in CU2.

Can you please confirm?

Thank You,

ExchangeKiller

Not yet resolved in code, sorry. So no fix in CU2. We are still working on the fix.

No sweat! Thanks for the update!

ExchangeKiller

Greg:

Is there a version of Exchange in which this bug is fixed?

Not yet, sorry.

Could you please raise the priority of this? More than a year without a fix is a long time. Do you need us to report this via the official support channel to get a higher prio?

Is there a workaround (like hiding the address book completely for specific basic users in OWA) which would allow us to migrate individual mailboxes to Exchange 2013?

If you open a support case that will help bump the priority, and as it's a known bug you shouldn't be charged.

The only workaround is not to hide users from the GAL.

MS Partners organize, let's open multiple tickets, if it will help.

I've run into this problem too.  Submitted a ticket. 

Fix is coming. It'll appear first in Exchange Online, then come to on-prem in the next available CU.

Any time frame yet?  I spoke with a tech on the Office 365 side about this issue and he said soon (that was a couple of weeks ago.)  We are waiting on migrating staff and faculty to Exchange Online until this fix is in place.

Thanks.

 

Very soon. It should be in the service already, did you test?

I hadn't tried this in a couple of weeks - probably just before I sent my last post.

Did a quick test and it worked on Office 365!  Will put it through more testing today.

Looks good.

Thanks!

Is anyone else still having this issue? I have a ticket open with support and I'm not getting anywhere. This problem is delaying other projects for me right now.

Greg - Anything you can do to assist?

The issue is fixed in CU6, which is coming soon. Very soon.

CU6 is out now is this issue now 100% fixed?

We believe so yes.

I applied CU6 and it fixed my problem.  Last month I applied windows updates to my Exchanges Servers and now I'm having the same issue again.  Is their a known problem with one or more windows updates or would applying CU7 re-fix my issue?