All I'm trying to do is export terminated users' mailboxes to a pst file and then archiving the pst files somewhere. I get the error indicated in the subject line when attempting to run Exmerge in batch mode in an Exchange 2003 environment. I have been able to get this to run successfully on 3 of my Exchange 2003 servers, however, it has failed when ran against the other 3 exchange servers. When I encountered the errors, I then decided to create a brand new service account and a brand new security group and I then added the service account to the security group. I then added the new Security group to the Security tab of the mailbox store, granting full control permissions and I also went into Advanced Security Settings and granted Send As and Receive As permissions to the new security group. The service account is only a member of this new security group and nothing else(it is not a member of any Administrative group that has implicit deny permissions.) I then log into the server that I run my Exmerge from (logging in with the new service account) but I still get errors for each legacyExchangeDN value(specified as a list in a text file) Here is a sample of the error, the error is repeated for each legacyExchangeDN in my text file: Error creating EntryID for '/o=ABCcompany/ou=Chicago/cn=Recipients/cn=JSmith' (GetMailboxInfoFromAB) [16:14:50] Error accessing directory object for '/o=ABCcompany/ou=Chicago/cn=Recipients/cn=JSmith'. Ignoring this mailbox Any help with this would be appreciated, thank you. Steve

Hi, What is the account that you used to run ExMerge? Please verify if this account has List Object and Open Address List rights on GALsXiu Zhang TechNet Community Support

Any uodate?Xiu Zhang TechNet Community Support

Hello Xiu, sorry for the late reply. The Exmerge is working now. Unfortunately, I am unable to provide a definitive resolution but it is working. A coworker of mine thinks that he corrected the issue by modifying the network gateway on the server that I run the exmerge from as he informed me that the gateway information was outdated. Exmerge was working perfectly fine(just prior to the start of this problem) for physical sites outside of the site that the Exmerge server is located, so I do not believe that it was a gateway issue(unless someone mysteriously changed it without me knowing but I don't think that is the case.) Prior to my coworker updating the gateway on the exmerge server, I suspected that the point of failure was the server (as it got to the point where it was failing on every single site that I was running it against) so I installed exmerge on my local PC and ran it against an exchange server at one of our remote sites and it completed successfully so my suspicion was correct that the Exmerge server was the point of failure. I have a feeling that maybe this issue was caused by an installed patch but again, that is only a guess. Unfortunately, there was nothing in either of the application or system logs that suggested anything pertinent to the issue. My coworker updated the gateway afterwards and the server was also rebooted a couple of times too so it is unclear as to whether the gateway update or the reboot resolved the issue. Thank you again for responding so promptly to my issue, I wish I could have provided you with a definitive resolution to my problem however what I DO know is that the problem was definitely local to the Exmerge server and NOT some sort of rights or priviledges issue. Cheers, Steve Steven A. Smith

Hi, I will close the thread and mark your finally reply as answer. Thannks.Xiu Zhang TechNet Community Support