In your Exchange 2013, you have setup everything and now you want to start administering your new environment, upon launching the Exchange Admin Center you enter your credentials and click login, you are then presented with the following error:

Exchange 2013 - ecp login error 400
Exchange 2013 - ECP Login Error 400 1

As a start you reboot the server, after a reboot, same problem still applies.

To start troubleshooting, we first need to look at IIS (Internet Information Services)

Open up IIS and then expand your server name and then expand sites and click on Default Web Site.

On the right hand side click bindings. We need to ensure that we have no strange IP addresses in the site bindings as shown below:

Exchange 2013 - ecp login error 400
Exchange 2013 - ECP Login Error 400 2

Now double click https and make sure that your SSL cert is set.

Exchange 2013 - ecp login error 400
Exchange 2013 - ECP Login Error 400 3

Next, click on Exchange Back End under sites and then click bindings on the right hand side.

Exchange 2013 - ecp login error 400
Exchange 2013 - ECP Login Error 400 4

Ensure that the port 444 has not changed and click Edit on the right hand side or double click it.

As mentioned above, ensure your SSL certificate is selected.

So in this case the bindings are correct.

The next thing we need to look at is redirection. This can give you the error listed above.

Exchange 2013 - ecp login error 400
Exchange 2013 - ECP Login Error 400 5

Expand your Default Web Site and click on ECP, you will see HTTP Redirect on the right hand side as shown above, double click on it.

Exchange 2013 - ecp login error 400
Exchange 2013 - ECP Login Error 400 6

As shown above, you will most likely have the checkbox ticked with a value in the field, un-tick the box and then click apply in the top right hand corner.

Lastly, reboot your server and then launch the EAC again, this time you should be able to login without a problem.

Hope it helps.

Discover more from COLLABORATION PRO

Subscribe now to keep reading and get access to the full archive.

Continue reading