Cannot Access Exchange contorl Panel ‘ECP’ in Exchange Server 2013

Ok here we go,

I received a couple of messages on Twitter from Engineers saying they cannot access the ECP page after they finished configuring the Virtual Directories.


When trying to access the ECP , it takes you to the OWA page and after providing your username and password it gives you a blank “HTTP 400 Error” page.


You missed up your authentications methods my friend


make sure that the authentication methods used by OWA and ECP are matching this is done by running the following

> Get-owavirtualdirectory | fl

make sure that you using “Form based Authentication” and “Basic Authentication”


do the same with ECP using the following command line

> Get-ECPVirtualDirectory | fl


If not then you just need to reconfigure the Authentications on both Virtual Directories, DONNOT use IIS use Exchange Management Shell.

For owa use the following

>Set-owavirtualdirectory -identity “owa <Default Web site>” -FormsAuthentication:$true

use the same also for ECP

>Set-ecpvirtualdirectory -identity “ecp <Default Web site>” -FormsAuthentication:$true

then restart your iis services using the following


once finished try to access your ECP page again and it should work now

if it didn’t make sure to run the same command lines but using “owa <Exchange Back End>” to make sure that both Default web site and Exchange back end website authentication methods are matching.

Cheers :)

About these ads

Mostafa Tohamey is a Senior Unified Communications & Messaging Engineer specialized in working with Microsoft Exchange and Microsoft Lync Server”, lives and works in Germany by 1&1 Internet AG taking care of the Microsoft Lync & Exchange Infrastructures. Worked Closely with Microsoft Dubai for 3 years designing , building and supporting Exchange and Lync Infrastructures. A Microsoft Certified ITP in Lync, Exchange and also attended Microsoft Partner Primer Filed Support Engineer T1 Training for Microsoft Lync 2010.

Tagged with: ,
Posted in Exchange 2013
8 comments on “Cannot Access Exchange contorl Panel ‘ECP’ in Exchange Server 2013
  1. SNMP says:

    Thank you saved me a huge amount of work after stuffing up my OWA setttings..

  2. normantech says:

    Hi Mostafa,
    I have serious Exchange issue, hope you can give an helping hand.
    Beisde the error HTTP 400 Bad Request for OWA and ECP, my Exchange Management Shell also not working.
    When I run Exchange Management Shell, I have error message:

    VERBOSE: Connecting to exchange.domain.local.
    New-PSSession : [exchange.domain.local] Connecting to remote server exchange.domain.local failed with the following error
    message :
    Bad Request

    Bad Request – Invalid Hostname
    HTTP Error 400. The request hostname is invalid.

    [Server=EXCH-SVR01,RequestId=4bde48ea-bb4e-4fc3-bafd-fa1b5ee5e862,TimeStamp=9/14/2013 12:09:04 AM] For more
    information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    + FullyQualifiedErrorId : -2144108477,PSSessionOpenFailed
    Failed to connect to an Exchange server in the current site.
    Enter the server FQDN where you want to connect.:

    Please help me. Thanks


    • Lyncdude says:

      Hi mate,

      Did you try to test connect to the owa or ecp from the IIS?

      Also regarding the EMS problem, try to check that in the IIS under the default website binding is configured correctly.
      If binding exist then delete the hostname from it, if there is no binding create one using HTTP and all unassigned for the IP-option.

      I think that there is a problem with your IIS.

  3. Ibrahim says:

    use the following URL to access the Exchange ECP


    Ibrahim Mahmoud

  4. Andy says:

    Issued the Set-owavirtualdirectory -identity “owa ” -FormAuthentication:$true, and received error: The operation couldn’t be performed because object ‘\owa ‘ couldn’t be found on

    What am I doing wrong? Your suggestions will be appreciated.

    Thank you,

  5. John says:

    typo should be formsAuthentication:$true

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow me on Twitter
Contact me

Notes to Myself Shared For Everyone


The World of Lync 2010 & Lync 2013

Julian Frank's Blog

Some Random Thoughts You May Like

TechOnTip Weblog

Run book for Technocrats

JC's Blog-O-Gibberish

Microsoft Lync and Exchange info, and things I can't remember

Just a Lync Guy

Guy Bachar's IT blog


UC and beyond

Mastering Lync

Yet another Lync blog but this one by Masters & MVP's

UC Ninjas

By the UC Community, for the UC Community!


Random collection of thoughts that are more than 140 characters

EighTwOne (821)

If you can't explain it simply, you don't understand it well enough.

All about Lync and soon Skype 4 Business

All about Lync and soon Skype 4 Business

VoIPNorm's Unified Communications Blog

All about Lync and soon Skype 4 Business

Site Home

All about Lync and soon Skype 4 Business

All about Lync and soon Skype 4 Business


Get every new post delivered to your Inbox.

%d bloggers like this: