Exchange in OWA Login exception

Today, you receive a script alert message that an Exchange Server OWA cannot log on!

A manual test, found that there is a problem, the error message is as follows:

Check the log of the server, found the following information

1. The request to access OWA received an error of $ internal Server error at HTTP level (error pointing to OWA backend problem)

　　

2018-10-19 02:34:37 127.0.0.1 Post/owa/auth.owa &clientid=d743aeedadf24394b3932a43fd81a704&correlationid= <empty>;&cafeReqId=4d419796-dfb2-4242-bfc3-33558bd9c81c;&encoding=; 443 test0001 127.0.0.1 mozilla/5.0+ (windows+nt+6.3;+wow64;+trident/7.0;+rv:11.0) +like+gecko https://localhost/owa/ Auth/logon.aspx?replacecurrent=1&ureason=5&reason=0 302 0 0 0

2018-10-19 02:34:37 127.0.0.1 Get/owa &clientid=d743aeedadf24394b3932a43fd81a704&correlationid=<empty >;&clientrequestid=636755132782181904&cafereqid=62c96cbe-fa86-42dd-afde-30ba14ededb5;&encoding= ; 443 test0001 127.0.0.1 mozilla/5.0+ (windows+nt+6.3;+wow64;+trident/7.0;+rv:11.0) +like+gecko https://localhost/owa/ Auth/logon.aspx?replacecurrent=1&ureason=5&reason=0 500 0 0 31

2, then get the OWA side of the display error

Negotiatesecuritycontext failed with a for host ' bjmail6.sohu-inc.com ' with status ' logondenied '

3. Check the event log

Event ID 1309来 from the Web event of the ASP. NET 4.0.30319.0, the details are as follows (I select the problem section to show)

Through the analysis of the log, I found that the thread account name is actually my domain accounts, which is obviously wrong, the correct should be the SYSTEM account

Judging by the above three points, the problem should be the Exchange back-end IIS virtual directory OWA

Check my IIS Configuration

Found the problem, OWA physical path credential is actually my account, here the correct configuration is as follows

Reconfigure the restart of IIS or OWA application pool can be restarted after re-testing, found that users can access, observe a period of time, the above problem log no longer appear, so that the problem is solved successfully.

Exchange in OWA Login exception