This topic is resolved

Share

This topic contains 6 replies, has 2 voices, and was last updated by  Karim Buzdar 4 weeks, 1 day ago.

  • Author
    Posts
  • #308844
     Karim Buzdar 
    Moderator
    • Topics: 24
    • Replies: 80
    Post count: 251
    Member Points: 6,145
    Rank: Level 1

    Hi all,

    I was installing Exchange Server 2016 on Windows Server 2016 with PowerShell and I got the following error at the end. The log files has following errors.

    [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.

    It looks like there is an error in command syntax.

    Thank you,

    0
  • #308846
     Michael Pietroforte 
    Keymaster
    • Topics: 138
    • Replies: 337
    Post count: 1046
    Member Points: 7,244
    Rank: Level 1

    What command did you use?

    0
  • #308849
     Karim Buzdar 
    Moderator
    • Topics: 24
    • Replies: 80
    Post count: 251
    Member Points: 6,145
    Rank: Level 1

    This is an entire command.

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

    0
  • #308852
     Michael Pietroforte 
    Keymaster
    • Topics: 138
    • Replies: 337
    Post count: 1046
    Member Points: 7,244
    Rank: Level 1

    Why are you doing this from a PowerShell console? Did you try it from an elevated command prompt? And why are you using two backslashes for the file paths?

    0
    • #308855
       Karim Buzdar 
      Moderator
      • Topics: 24
      • Replies: 80
      Post count: 251
      Member Points: 6,145
      Rank: Level 1

      Does this matter? I mean the command we run on command prompt can also be run on PowerShell too. Yes, I elevated the PowerShell.

      As far as // are concerned, I copy pasted from a blog site.

      Thank you,

      0
  • #308860
     Michael Pietroforte 
    Keymaster
    • Topics: 138
    • Replies: 337
    Post count: 1046
    Member Points: 7,244
    Rank: Level 1

    The official way is to do use a command prompt. Everything that is not official can cause problems. Try it from a command prompt with just one \.

    0
  • #318882
     Karim Buzdar 
    Moderator
    • Topics: 24
    • Replies: 80
    Post count: 251
    Member Points: 6,145
    Rank: Level 1

    Thank you,

    0

You must be logged in to reply to this topic.

CONTACT US

Please ask IT administration questions in the forum. Any other messages are welcome.

Sending
© 4sysops 2006 - 2017

Log in with your credentials

or    

Forgot your details?

Create Account