error not display database on ecp exchange 2016

Pham Tien Dung 105 Reputation points
2024-07-12T07:29:25.21+00:00

Our system has 2 faulty Exchange servers. I have removed these 2 servers from AD and reinstalled Exchange 2016 on 2 other servers. After installation is complete, we proceed to create a DB for the system. When creating, there is an error message Multiple databases match "MBDB02". Specify a unique value. When I checked, the database was not displayed on ECP. We used Exchange Management Shell (EMS) and the results were as shown. Can anyone help me regarding this case?

User's image

User's image

User's image

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,184 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,204 questions
Exchange Server Development
Exchange Server Development
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Development: The process of researching, productizing, and refining new or existing technologies.
528 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,486 questions
Microsoft Exchange
Microsoft Exchange
Microsoft messaging and collaboration software.
454 questions
0 comments No comments
{count} votes

Accepted answer
  1. Jake Zhang-MSFT 3,020 Reputation points Microsoft Vendor
    2024-07-15T09:08:46.0866667+00:00

    Hi @Pham Tien Dung,

    Welcome to the Microsoft Q&A platform!

    According to your description, the error message you encountered in the screenshot indicates that a database object in the Active Directory may be damaged or does not match the current Exchange server. You can try the following steps to solve this problem:

    1.You need to find and remove the damaged or orphaned database objects in Active Directory. First, you can use the following command to list all database objects, including those that may be damaged:

    Get-MailboxDatabase -IncludePreExchange2013 | Format-List Name,Guid,Server

    Identify the database objects that may be damaged.

    1. If you confirm that a database object is orphaned or damaged, you can use the following command to remove it from Active Directory:

    Remove-MailboxDatabase -Identity "Mailbox Database 0616638881"

    Please double-check the name of the database object you want to remove to ensure that it is accurate.

    1. Make sure the replication status of Active Directory is normal. Use the following command to check the AD replication status:

    repadmin /replsummary

    Make sure there are no replication errors.

    1. Make sure the records in DNS have been cleaned up and do not point to the old Exchange server that has been removed.
    2. Force update the Active Directory schema to ensure that the newly installed Exchange server is correctly registered:

    Setup.exe /IAcceptExchangeServerLicenseTerms /PrepareAD

    1. After completing the above operations, restart all related Exchange services or the entire server to ensure that all changes take effect.

    Please feel free to contact me if you have any queries.

    Best,

    Jake Zhang

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Amit Singh 4,871 Reputation points
    2024-07-15T11:32:14.6333333+00:00

    When you’re creating database with the name “MBDB02” its showing an error – multiple databases with similar name.

    To resolve this, you can do it with the help of EMS.

    1.       Check all the existing databases by running the command. Also verify there are no hidden and disconnected databases.

    2.       If you find any database named “MBDB02” remove it.

    3.       After that create the database “MBDB02” through EMS.

    Refer this link for the same.

    Please Note: Since the web sites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.

    0 comments No comments