troubleshooting Question

Exchange 2016 Phantom Public Folder Mailbox Migration Requests

Avatar of Jim Stiveson
Jim StivesonFlag for United States of America asked on
Exchange* Exchange Database
5 Comments2 Solutions335 ViewsLast Modified:
Good day all

So we have run into a somewhat interesting but annoying situation. We have a 3 node DAG that we have started to migrate from to a new DAG in the same organization. After migrating all mailboxes from a particular database, yes, ALL mailboxes of every type, we removed all copies and then attempted to delete the last copy. When we attempted to remove the last copy we received the following error:

This mailbox database is associated with one or more active PublicFolderMailboxMigration requests. To get a list of all PublicFolderMailboxMigration requests associated with this database, run
Get-PublicFolderMailboxMigrationRequest | ?{ $_.RequestQueue -eq "<Database ID>" }. To remove a PublicFolderMailboxMigration request, run Remove-PublicFolderMailboxMigrationRequest <Recipient I ... etc etc



Well, here is the funny thing. When we run Get-PublicFolderMailboxMigrationRequest | ?{ $_.RequestQueue -eq "<Database ID>" } it returns absolutely nothing. So, that is a problem since one cannot remove a request that does not exist. So after some web research we were able to find a few posts on this situation along with a potential solution. The following links are what we found: https://social.technet.microsoft.com/Forums/office/en-US/54fd0db4-11d3-421c-92e8-d4050338a907/trouble-removing-2016-mailbox-database?forum=Exch2016Adm and http://terenceluk.blogspot.com/2017/01/attempting-to-delete-exchange-server.html

After reading these we opened ADSI edit and navigated to: CN=Configuration,DC=DomainName,DC=local ==> Services ==> Microsoft Exchange ==> Organization Name ==> Mailbox Replication ==> PublicFolderMailboxMigrationRequests

Here we found four PublicFolderMailboxMigration Request from two years ago. This matches pretty much exactly what was contained in the two articles we found. Our questions are: Does anyone else out there have experience with this? Both articles state that they were able to resolve the issue and delete the database by using ADSIedit to manually delete these orphaned migration requests. What are your thoughts on the safety of doing this? In the past I have personally deleted orphaned mailbox databases themselves in AD but I also consider that the "Nuclear Option" and I like to avoid doing so. Does anyone know of another way to resolve this issue?



Any and all input will be greatly appreciated.
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 2 Answers and 5 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 5 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros