Exchange 2010 - Export request queued

webox_suuport
webox_suuport used Ask the Experts™
on
Hi,
I am trying to export some mailboxes to pst from the shell but all the requests are held in queue forever. Restart to MRS and CAS servers is not helping here.
From the CAS server I've found out the following warning:

Process MSExchangeMailboxReplication.exe () (PID=1344). Object [CN=xxx,OU=xxx,OU=xxx,OU=xxx,DC=xxx,DC=xxx]. Property [HomeMTA] is set to value [domain.local/Configuration/Deleted Objects/Microsoft MTA
DEL:e1a556ef-107e-4590-831b-9120debcc966], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.

Found on the web several articles with similar error but everything is pointing to Edge Transport and I didn't installed this role on my system.
Also tried out "get-mailbox user |update-recipient" but still got the warning and the export did not processed at all.

Using Exchange 2010SP3

Thanks.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
confirm if you have any orphaned exchange server references in active directory to which the homeMTA value is point to.

Author

Commented:
How can I check it?
Did you checked the HomeMTA value for the user you are trying to move ? is it point to correct server or any other old server or showing any orphaned value.

If you have moved any other mailbox earlier then find out it's HomeMTA value using adsiedit and compare it with the mailbox failed to move it it doesn't match then set the value for the failed mailbox to similar as the successful mailbox

additionally you can check homeMTA value for your current server from below location in adisiedit

CN=Configuration
   CN=Services
      CN=Microsoft Exchange
          CN=Administrative Groups
               CN=Servers
                    CN=[name of your transport server]
                         CN=Microsoft MTA
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
Ok, to my surprise, all the mailboxes have similar setting:
CN=Microsoft MTA\0ADEL:e1a556ef-107e-4590-831b-9120debcc966,CN=Deleted Objects,CN=Configuration,DC=domain,DC=local
Did you checked the MTA value of the server as I suggested earlier ?
you can also try below things.

1) Open adsiedit
2) Go to one of the user's properties
3) Note down the homeMTA value and then delete them from the properties.
4) try exporting again.

Exchange 2010 does not really needs homeMTA so we can give it a try.

Author

Commented:
Since I have 2 hubs, each have a different MTA.
I will try your solution.
Any update?

Author

Commented:
Since the problem was with only one mailbox, We left it that way

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial