migration mailbox fails

When we do a migration on a user,  the migration fails because there's a migration batch in the past for certain users, even though the batch was deleted in the past.  Exchange still thinks there's a migration batch even tough it has been deleted.  It keeps failing every time

ran this command:
get-migrationuser

tried to delete, but failed
PS C:\Users\exec> Get-MigrationUser | Remove-MigrationUser -force
Remove-MigrationUser : The user "00000000-0000-0000-0000-000000000000" was already removed.
At line:1 char:21
+ Get-MigrationUser | Remove-MigrationUser -force
+                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Remove-MigrationUser], MigrationUserAlreadyRemovedException
    + FullyQualifiedErrorId : [Server=ELISHA,RequestId=fc2f5d22-0113-430b-a589-9e086e46913e,TimeStamp=12/29/2017 4:2
   1:01 AM] [FailureCategory=Cmdlet-MigrationUserAlreadyRemovedException] 62A4F749,Microsoft.Exchange.Management.Mi  
  gration.MigrationService.User.RemoveMigrationUser

Any idea's how to fix this issue?

exchange error
DanNetwork EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jason CrawfordTransport NinjaCommented:
You might have a disabled mailbox in the source.  Try this:

Get-MailboxDatabase | Clean-MailboxDatabase
Get-MailboxDatabase | Get-MailboxStatistics | Where-Object {$_.disconnectdate -ne $null} | fl DisplayName,MailboxGuid,Database,LegacyDN

Open in new window

0
DanNetwork EngineerAuthor Commented:
I ran the command:
Get-MailboxDatabase | Get-MailboxStatistics | Where-Object {$_.disconnectdate -ne $null} | fl DisplayName,MailboxGuid,Database,LegacyDN

and nothing came up.
0
DanNetwork EngineerAuthor Commented:
If use the Get-MailboxDatabase | Clean-MailboxDatabase comamnd, do I need to add each DB name after the command?
Never used this command before
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

8046586Commented:
Are you migrating to O365 or internally from one to another server?
0
DanNetwork EngineerAuthor Commented:
I have ex 2013, and migrating to ex 2016, on premise.  I've pretty much have done everything else, DNS, certs, connectors, virtual directories, etc...  Everything seemed to be fine.  I can confirm that now mail is flowing through my new exchange, and it's delivering the mail to my old server because the mailboxes still reside there.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DanNetwork EngineerAuthor Commented:
Not that article specifically, but I've done most of the steps, I had my datacenter provide support, and they ran into this problem, so I'm stuck.

I've already done the following:
Updated internal dns
Updated my firewall
Updated exchange virtual directories/certs/receive/send connectors
Renamed the default DB
Created the new DBs on new server

That's where I'm at now, I can't move a mailbox because of this error
0
8046586Commented:
In the document, I sent you there is a command for migrating the database, then public folders and et the end user mailboxes. Why don't you compare the two documents and try using the one I gave you. You might be missing a step in the one you are following.
0
Jason CrawfordTransport NinjaCommented:
Did you run the commands I gave you on the source server?  Sorry I should have been more clear there.
0
DanNetwork EngineerAuthor Commented:
Thanks guys for your help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Powershell

From novice to tech pro — start learning today.