Quantcast
Channel: Exchange Server 2013 - Administration, Monitoring, and Performance 论坛
Viewing all articles
Browse latest Browse all 8719

The Exchange 2013 problems just continue.. :-( HTTP 500 error when accessing ECP on the server using https://localhost using FQDN is ok

$
0
0

So here is the next Exchange 2013 problem.. really starting to hate Exchange 2013..

If I'm logged directly on the server, and I try to access ECP, owa by using the icon created by exchange usinghttp://localhost  I get an http 500 error after I try to authenticate why? Exchange 2013 SP1 CU5 on windows 2008 R2.  If I usehttps://127.0.0.1/ecp all is good, if I use https://fqdn/ecp or owa all is good,  but not https://localhost.  Has to do something with the IIS binding right? When I try the  *.443 binding using IIS manager bingo same issue so has something to do I think with the *:443 binding.  I check my other lab 2013 server and check bindings they look the same, so what gives?   I take the IIS logs into log parser to analyze but nothing sticks out at me.. I see http 500 errors like these.  Any suggestions?

 

cs-uri-query

 

&CorrelationID=<empty>;&cafeReqId=bf948ca5-8d67-4772-85cd-02c5e51e5e02;

FQDN of SERVER:6001&CorrelationID=<empty>;&RequestId=191bad18-4a70-4af5-93dd-4fe85968997c&cafeReqId=191bad18-4a70-4af5-93dd-4fe85968997c;

Http 503 errors.

/rpc/rpcproxy.dll    SERVERNAME:6001&CorrelationID=<empty>;&RequestId=b5cfde55-5552-415a-9dac-239c025aef73&cafeReqId=b5cfde55-5552-415a-9dac-239c025aef73;


Viewing all articles
Browse latest Browse all 8719

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>