locked
Error 500 when logging into EAC after Exch 2016 Installation RRS feed

  • Question

  • I am getting an Error 500 when attempting to log in to EAC after installation of Exchange Server 2016. I have verified all services are running and following the troubleshooting steps found in previous questions. 
    Tuesday, March 20, 2018 5:26 PM

Answers

  • I ended up uninstalling and reinstalling Exchange and that resolved the problem. 
    • Marked as answer by jmrs123 Thursday, March 29, 2018 1:01 PM
    Thursday, March 29, 2018 1:01 PM

All replies

  • 2018-03-20 17:20:44 192.168.1.60 GET /owa/auth/logon.aspx replaceCurrent=1&url=https%3a%2f%2fdev-exch2016%2fecp%2f%3fexchclientver%3d15&CorrelationID=<empty>;&ClientId=83A4A215196741FCAE5CE01C1B55BD1D&cafeReqId=da06e487-213a-49d2-b0d3-09fb47b60695;&encoding=; 443 - 192.168.1.60 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 200 0 0 15
    2018-03-20 17:20:44 ::1 GET /OAB/ &CorrelationID=<empty>;&ClientId=F61C98E608D04F53AF1856BE11DB2A20&cafeReqId=e921958b-570a-4c3d-b8bc-896facb44ec4; 443 DEVELOP\HealthMailboxd665174 ::1 AMProbe/Local/ClientAccess - 200 0 0 0
    2018-03-20 17:20:46 127.0.0.1 GET /ecp/ReportingWebService/ &CorrelationID=<empty>;&ClientId=6F50749E88744C9EA5F3BFAC7D849E58&cafeReqId=c6f5550d-8bb1-4e87-b828-60d98f5cfda0;&LogoffReason=NoCookiesGetOrE14AuthPost 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 302 0 0 0
    2018-03-20 17:20:51 192.168.1.60 POST /mapi/emsmdb/ mailboxId=4eef1018-6e43-4b31-86b4-2a3bdfeb9862@develop.ds.amrdec.army.mil&CorrelationID=<empty>;&ClientId=E212513D958748CFA19099781825A9F2&ClientRequestInfo=R:c9aeb4f1-f614-4c15-9477-2b73c2b85df1:1;CI:3a4c1148-6b46-4776-83ac-baca8c124689:1;CID:<null>;RT:Connect&cafeReqId=2d64eabf-882b-4a79-9cbe-f58735c7f2b6; 443 DEVELOP\HealthMailboxd665174 192.168.1.60 MapiHttpClient - 500 0 0 281
    2018-03-20 17:20:51 192.168.1.60 POST /owa/auth.owa &CorrelationID=<empty>;&ClientId=83A4A215196741FCAE5CE01C1B55BD1D&cafeReqId=6b3dc65b-38b1-43a7-9eb5-8e15855de3d4;&encoding=; 443 develop\sturgesjm 192.168.1.60 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko https://dev-exch2016/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2fdev-exch2016%2fecp%2f%3fexchclientver%3d15 302 0 0 46
    2018-03-20 17:20:51 192.168.1.60 GET /ecp/ exchclientver=15&CorrelationID=<empty>;&ClientId=83A4A215196741FCAE5CE01C1B55BD1D&cafeReqId=9ad535cf-f7c5-4cda-9bc7-9c0a895b7f2f; 443 develop\sturgesjm 192.168.1.60 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko https://dev-exch2016/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2fdev-exch2016%2fecp%2f%3fexchclientver%3d15 500 0 0 46

    Tuesday, March 20, 2018 5:28 PM
  • Hi Jmrs123,

    Please also check if the following articles provide any helps, these articles apply to Exchange 2016 also:

     HTTP 500 Internal Server Error when logging into Exchange 2013 Exchange Control Panel (ECP)

    Exchange 2013 Troubleshooting: Error 500 when login ECP and OWA

    Exchange 2016 – HTTP Error 500 after logging into ECP/OWA


    Best Regards,
    Niko Cheng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Niko.Cheng Friday, March 23, 2018 2:19 AM
    Wednesday, March 21, 2018 8:54 AM
  • Hi Jmrs123,

    I'm just writing to check how's everything going? If you have any questions or needed further help on this issue, please feel free to post back. If the issue has been resolved, please mark the helpful replies as answers, this will make answer searching in the forum easier and be beneficial to other community members as well.

     

    Thanks for your understanding.


    Best Regards,
    Niko Cheng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Niko.Cheng Thursday, March 29, 2018 1:28 AM
    Monday, March 26, 2018 9:49 AM
  • I ended up uninstalling and reinstalling Exchange and that resolved the problem. 
    • Marked as answer by jmrs123 Thursday, March 29, 2018 1:01 PM
    Thursday, March 29, 2018 1:01 PM