Unable to migrate mailbox in Exchange 2019 - Prompt error Couldn't find database

Question

Unable to migrate mailbox in Exchange 2019 - Prompt error Couldn't find database

KAI SENG 30

I encounter error when trying to move mailbox from Exchange 2013 to 2019. It prompt the error Couldn't find database and pointing to a non existing database. Kindly refer to screenshot.

Can any expert guide me on how to fix this? Exch19error

Accepted answer

2 additional answers

Your answer

Answer 1

Yuki Sun-MSFT 41,376 Moderator

Hi @KAI SENG ,

Regarding the error message in the screenshot you shared, do you have any impression on the database mentioned in the error? Based on my research, "first storage group" appears to be related to some outdated version of Exchange server, so I am wondering if there was an earlier version of Exchange in your environment.

Besides, could you run the command below to check the arbitration mailboxes in the environment? Make sure the databases returned in the output are all mounted properly.

Set-ADServerSettings -ViewEntireForest $true; Get-Mailbox -Arbitration | Format-Table Name, ServerName, Database, AdminDisplayVersion

Furthermore, in order to narrow down if it's an issue with the administrator account, please try testing with a different admin account and see how it goes.

You can also try migrating mailboxes using the New-MoveRequest cmdlet and check the result:

New-MoveRequest -Identity '******@contoso.com' -TargetDatabase "DB01"

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

KAI SENG 30 Reputation points

2023-03-03T11:18:45.0633333+00:00

Hi Yuki,

Using the powershell to check arbitration mailbox, I don't see the mailbox as specified in the error pop up. Refer to below screenshot. Do this mean I need to use ADSI edit to manual remove that DB? Can guide me how to do that?

I use the New-MoveRequest and able to move the mailbox.

Thank you.
Yuki Sun-MSFT 41,376 Reputation points Moderator

2023-03-07T08:09:04.4666667+00:00

Hi @KAI SENG ,

Using the powershell to check arbitration mailbox, I don't see the mailbox as specified in the error pop up.

It's expected that the mailbox database in the error is not in the output. Actually, I was just intended to suggest checking the status of the arbitration mailboxes in your environment.

Noticed from the output that there are still several system mailboxes on Exchange 2013. Could you try moving all arbitration mailboxes to Exchange 2019 and then check the result?
KAI SENG 30 Reputation points

2023-03-13T08:45:06.71+00:00

Hi Yuki,

I moved all the mailbox to Exchange 2019 and result same. Still prompt same error.

Any idea how I can remove this legacy database?

Thank you.
Yuki Sun-MSFT 41,376 Reputation points Moderator

2023-03-15T01:38:41.3066667+00:00
Hi @KAI SENG ,

As aforementioned, do you perhaps have any idea about this legacy database? Was it created in Exchange 2013 or there has been an older version of Exchange server in the environment?

I tried searching hard in terms of this kind of error but can hardly find anything applicable. Below is the only thread I found that appears to be relevant, but it was for Exchange 2003 to Exchange 2010:
Mailbox database "EXCHANGE\First Storage Group\Mailbox Store (EXCHANGE)" doesn't exist.
The solution in the case above is to add the server that holds Exchange 2010 to the security tab of the original 2003 server vis ESM and give it full permissions. While there's no more ESM in either Exchange 2013 or Exchange 2019, personally I suppose it's still worth trying to add the server that holds Exchange 2019 to Exchange 2013 with full control and check if it can help (Revert the change back if it doesn't work.):

Open ADSI Edit, connect to Configuration.

Expand "CN=Configuration,DC=contoso,DC=com" -> "CN=Services" -> "CN=Microsoft Exchange" -> "CN=Administrative Groups" -> "CN=Exchange Administrative Group (FYDIBOHF23SPDLT)" -> "CN=Servers".

Right click on the Exchange 2013 server, choose Properties, click the Security tab.

Click Add, click Object Types and tick the checkbox of Computers, seach for and add the server that holds Exchange 2019, give it Full control permissions.
Yuki Sun-MSFT 41,376 Reputation points Moderator

2023-03-22T07:41:10.6633333+00:00

Hi @KAI SENG ,

Just wondering how things are going on with this issue. Have you managed to sort things out?
KAI SENG 30 Reputation points

2023-03-22T10:20:54.0933333+00:00

Hi @Yuki Sun-MSFT ,

I've tried adding the EX19 server with full permission, but result is the same. Still prompt the same error message.

Thank you.
Yuki Sun-MSFT 41,376 Reputation points Moderator

2023-03-27T01:20:32.59+00:00

Hi @KAI SENG ,

Can you see any instance of legacy Exchange server in the ADSI edit?
KAI SENG 30 Reputation points

2023-06-26T09:13:54.47+00:00

Hi @Yuki Sun-MSFT ,

I've resetup the whole testing environment and the results still same. The same error pop up. If I type the command below, the error appears. Does this mean it has something to do with ArchiveDatabase?

Can guide where can I find this database and remove it?

Thank you.
KAI SENG 30 Reputation points

2023-07-20T06:51:33.4166667+00:00
Finally, found the solution.

Open powershell, run this command:
dsquery * forestroot -attr * -limit 0 >c:\temp\result.txt

From the result.txt, search for the offending database.

Open Active Directory and locate the object where the key is located. In my case, it's a SystemMailbox{.....}

Go to Attribute Editor tab and go to attribute homeMDB

Click Clear button then OK button.

Go to attribute homeMTA

Click Clear button then OK button.

Click OK button to close the window.

Done.

Answer 2

KAI SENG 30

Found the solution:

Open powershell
Run this command: dsquery * forestroot -attr * -limit 0 >c:\temp\result.txt
Open results.txt and look for the offending database where it's located in Active Directory and in which object.
Open Active Directory and open the object.
Go to Attribute Editor tab and edit the attribute homeMDB and homeMTA. Click Clear button and OK to accept changes.
Click OK to close the window.

That's it.

Answer 3

Amit Singh 5,306

Check the value for msExchOwningPFTree for your Public Folder Database (path above) and make sure it's set to CN=Public Folders,CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Deppmann,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com

KAI SENG 30 Reputation points

2023-03-07T01:22:59.9266667+00:00

Hi Amit. I'm not using any public folder.

Share via

Unable to migrate mailbox in Exchange 2019 - Prompt error Couldn't find database

2 additional answers

Your answer