none
Create Exchange DB problem? How to fix it? RRS feed

  • Question

  • Summary: 1 item(s). 0 succeeded, 1 failed.

    Elapsed time: 00:00:00

     

     

    MB Clearfield 6

    Failed

     

    Error:

    Active Directory operation failed on DC . This error is not retriable. Additional information: The attribute syntax specified to the directory service is invalid.

    Active directory response: 0000200B: AtrErr: DSID-031519C7, #1:

                    0: 0000200B: DSID-031519C7, problem 1002 (INVALID_ATT_SYNTAX), data 0, Att 200f4 (homeMDB):len 144

     

     

    The syntax is invalid.

    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.140).aspx?v=14.3.169.1&t=exchgf1&e=ms.exch.err.Ex6AE46B

     

    Exchange Management Shell command attempted:

    new-mailboxdatabase -Server 'PONY' -Name 'MB Clearfield 6' -EdbFilePath 'D:\Exchange\MB Clearfield 6\MB Clearfield 6.edb' -LogFolderPath 'L:\Exchange\MB Clearfield 6 Logs'

     

    Elapsed Time: 00:00:00

    Thursday, May 25, 2017 3:18 AM

Answers

  • Same problem here, Exchange 2016 Cu5 on win 2016 in a DAG.

    Fixed: I 'm in a child domian, i used a schema admin from parent domain (i used it for adprep) and it worked. I will check permission for other child domain user.

    Friday, May 26, 2017 3:04 PM
  • Hi Jacky,

    What is version of Exchange server? Exchange 2010 or Exchange 2013?
    Did you create database by EMC(EAC)? Or EMS?
    Did you have enough permission to create database?

    To this issue, we suggest you do the following steps to troubleshoot this issue:

    1. Make sure D volume and L volume are accessible
    2. Check the connection between DC and Exchange, include Ping and DNS resolve
    3. Make sure Exchange administrator is a member of “Organization Management” and “Server Management”
    4. Try to use the following command if you use EMC(EAC) in the former:New-Mailboxdatabase -Server 'PONY' -Name 'MB Clearfield 6' -EdbFilePath 'D:\Exchange\MB Clearfield 6\MB Clearfield 6.edb' -LogFolderPath 'L:\Exchange\MB Clearfield 6 Logs'  

    Best Regards,
    Jim Xu
    TechNet Community Support


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, May 29, 2017 8:13 AM
    Moderator

All replies

  • Hi

    Have you tried to force AD replication or check for replication errors?

    Thursday, May 25, 2017 4:00 AM
    Moderator
  • i export the replication result. it does not show any replication failures.
    Thursday, May 25, 2017 5:30 AM
  • Restart the Exchange Server and then try again.

    My Blog: www.ADExchangeAdmin.com

    Thursday, May 25, 2017 9:10 AM
  • Hello

    If remove space from name and db and other... wont work?


    sorry my english

    Thursday, May 25, 2017 12:34 PM
  • What do you mean about it? I don't understand it clearly.
    Friday, May 26, 2017 5:14 AM
  • I tried it before. The problem is still there.
    Friday, May 26, 2017 6:14 AM
  • Same problem here, Exchange 2016 Cu5 on win 2016 in a DAG.

    Fixed: I 'm in a child domian, i used a schema admin from parent domain (i used it for adprep) and it worked. I will check permission for other child domain user.

    Friday, May 26, 2017 3:04 PM
  • Hi Jacky,

    What is version of Exchange server? Exchange 2010 or Exchange 2013?
    Did you create database by EMC(EAC)? Or EMS?
    Did you have enough permission to create database?

    To this issue, we suggest you do the following steps to troubleshoot this issue:

    1. Make sure D volume and L volume are accessible
    2. Check the connection between DC and Exchange, include Ping and DNS resolve
    3. Make sure Exchange administrator is a member of “Organization Management” and “Server Management”
    4. Try to use the following command if you use EMC(EAC) in the former:New-Mailboxdatabase -Server 'PONY' -Name 'MB Clearfield 6' -EdbFilePath 'D:\Exchange\MB Clearfield 6\MB Clearfield 6.edb' -LogFolderPath 'L:\Exchange\MB Clearfield 6 Logs'  

    Best Regards,
    Jim Xu
    TechNet Community Support


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, May 29, 2017 8:13 AM
    Moderator
  • I saw this error with Exchange 2016 and found a fix in the article, "You cannot create a new Exchange Server 2010 Mailbox database in a multiple domain environment."  I used the following command to specify the domain controller my Exchange server should use.

    Set-ADServerSettings –PreferredServer DC1

    See: https://support.microsoft.com/en-us/help/977960/you-cannot-create-a-new-exchange-server-2010-mailbox-database-in-a-mul

    • Proposed as answer by doalwa Tuesday, September 3, 2019 9:44 AM
    Tuesday, February 27, 2018 7:26 PM
  • I just ran into this problem with Exchange 2016.   I was creating the database on a server that wasn't hosting the PAM role in the DAG.  Once I found the server hosting the PAM role, I was able to create the database from this server without issue.  Hopefully that helps.
    Thursday, April 4, 2019 8:12 PM
  • I still to this day get caught up with this - Make sure that if you are directly on the server in question that you have right clicked and start the Exchange Powershell instance as an Administrator. - It should work if you are remote-PS'ing by virtual of passing credentials. Ran into this and some other strange issues and realized that was my mistake. 
    Friday, July 12, 2019 12:19 AM
  • I saw this error with Exchange 2016 and found a fix in the article, "You cannot create a new Exchange Server 2010 Mailbox database in a multiple domain environment."  I used the following command to specify the domain controller my Exchange server should use.

    Set-ADServerSettings –PreferredServer DC1

    See: https://support.microsoft.com/en-us/help/977960/you-cannot-create-a-new-exchange-server-2010-mailbox-database-in-a-mul

    Had the same problem with our Exchange 2010 server running in a multi-domain environment and a total of 4 Exchange 2010 servers spread out across several sub-domain.

    Forcing a specific domain controller with the above command fixed the issue for me!

    Tuesday, September 3, 2019 9:45 AM
  • I did the following.

    Get-ADServerSettings, It displayed an empty line.

    I then added a dc-server with FQDN as preferredServer 

    Set-ADServerSettings -PreferredServer <DC-SERVER-NAME.DOMAIN.LOCAL>


    It worked for me, as i now can create a Recovery database.

    Thursday, October 24, 2019 7:36 PM