When you are installing Exchange Server 2016 on Windows Server 2016 with PowerShell, you may get the following error.

[ERROR] Cannot bind parameter ‘EdbFilePath’ to the target. Exception setting “EdbFilePath”: “File path “C:\ExchangeDB” does not match the expected file extension “.edb”.”
[11/02/2017 12:19:36.0912] [1] [ERROR] Exception setting “EdbFilePath”: “File path “C:\ExchangeDB” does not match the expected file extension “.edb”.”
[11/02/2017 12:19:36.0912] [1] [ERROR] File path “C:\ExchangeDB” does not match the expected file extension “.edb”.
[11/02/2017 12:19:36.0927] [1] [ERROR-REFERENCE] Id=MailboxComponent___61cf7fc80dac4973a39d3a0c960fe7c3 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[11/02/2017 12:19:36.0927] [1] Setup is stopping now because of one or more critical errors.

Solution:

The error is generated because of the following wrong command you executed:

./Setup.exe /Mode:Install /IAcceptExchangeServerLicenseTerms /Role:Mailbox /CustomerFeedbackEnabled:False /TargetDir:”C:\\Exchange\\” /DbFilePath:”C:\\ExchangeDB\\” /LogFolderPath:”C:\\Logs\\”

Use the following command instead and it should work,

./Setup.exe /Mode:Install /IAcceptExchangeServerLicenseTerms /Role:Mailbox /CustomerFeedbackEnabled:False

 

[SOLVED] Cannot bind parameter ‘EdbFilePath’ to the target.
Avatar

Karim Buzdar

About the Author: Karim Buzdar holds a degree in telecommunication engineering and holds several sysadmin certifications. As an IT engineer and technical author, he writes for various web sites. You can reach Karim on LinkedIn

One thought on “[SOLVED] Cannot bind parameter ‘EdbFilePath’ to the target.

  • Avatar
    March 13, 2020 at 9:23 pm
    Permalink

    What if you are wanted to put the database, log and binaries on a different drive? Your command will make those files default to the C drive which is not a good practice.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

*