asked on

554 5.6.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn't found.

I'm having problems with a public folder in E2010 .. it's a public folder that was migrated from E2003 .. I already decommisioned the E2003 server a whil ago and everything worked fine.. i think this problem started when I deleted the old E2003 server with ADSIedit , i've serached and ran exBPA to test .. but can't find a good post or solution

has anybody ever seen this issue?

When I try to mail to the public colder e-mail address this is what i get :

Delivery has failed to these recipients or groups:

Aanbesteding-EBP (Aanbesteding-EBP@mobius.eu)
The e-mail system had a problem processing this message. Exchange will not try to redeliver this message for you.

Diagnostic information for administrators:

Generating server: MOBE-MAIL-01.mobius.be

Aanbesteding-EBP@mobius.eu
#554 5.6.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn't found. ##

Coast-IT

Found this tip on another page, any good?

“Practical End User Friendly Detection” of this issue can be done using exfolders.exe. You can read more about this tool here: “Exchange, meet ExFolders” (http://msexchangeteam.com/archive/2009/12/04/453399.aspx).The error only occurs when you create a public folder on Exchange 2010 and can be very annoying for the users so I’ll share this tip with you. Download the tool here http://msexchangeteam.com/files/12/attachments/entry453398.aspx and install it on an Exchange 2010 server in the bin directory (follow the readme.txt and don’t forget to merge the .reg file or the tool will crash). Running exfolders.exe and connect against any Exchange 2007 public folder. When you get this error …

—————————

ExFolders

—————————

An error occurred while trying to establish a connection to the Exchange server. Exception: The Active Directory user wasn’t found.

—————————

OK

—————————

… you know you are affected. Deleting the empty Servers containers from ALL legacy Administrative Groups fixes the error. You then can connect successfully to a Exchange 2007 public folder with exfolder.exe. Which is a cool way to test for this issue and if the fix works as you don’t need to create a public folder and possibly hinder you users.

ASKER CERTIFIED SOLUTION

VincentDefour

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial