Recently, in an Exchange upgrade project, you need to update the existing environment's exchange SP1 to the Exchange Server SP3RU11 or the newer version before you deploy Exchange Server 2016. After the update sp3+ru11 found that logged on to OWA exception, at the beginning of the initial thought is the RU11 problem, but after unloading RU11 is still the same problem, so it took a relatively long time to exclude. The following is the phenomenon and the final solution for your reference.
After upgrading to SP3+RU11, it is sometimes possible to log in to OWA but when you click on "New" message, "You cannot complete your request." This can happen because of security reasons or a session timeout. "
650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M00/85/80/wKioL1el9HixUgDpAAAgmS6L7cU634.png "title=" 1.png " alt= "Wkiol1el9hixugdpaaagms6l7cu634.png"/>
650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M01/85/81/wKiom1el9ImD3IqtAAANdKWBajU393.png "title=" 2.png " alt= "Wkiom1el9imd3iqtaaandkwbaju393.png"/>
650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M01/85/80/wKioL1el9JfxBn62AACaKMoH9fY176.png "title=" 3.png " alt= "Wkiol1el9jfxbn62aacakmoh9fy176.png"/>
According to the following Microsoft KB by modifying the registry to change the default session 16 to 64, the application log still reported the maximum limit for MAPI sessions exceeding 64, and some sites mentioned modifying the server's TCP/IP session retention time, but I thought it was not the fundamental solution, so I did not modify this value.
https://support.microsoft.com/en-us/kb/980049
650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/85/81/wKiom1el9KXgmLj0AABjsJO1acw147.png "title=" 4.png " alt= "Wkiom1el9kxgmlj0aabjsjo1acw147.png"/>
https://technet.microsoft.com/en-us/library/dd349797 (v=ws.10). aspx
Hkey_local_machine\system\currentcontrolset\services\tcpip\parameters\
650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M02/85/80/wKioL1el9LLC1TSLAAA7pnBBs7I186.png "title=" 5.png " alt= "Wkiol1el9llc1tslaaa7pnbbs7i186.png"/>
http://problutions.com/2013/02/ exchange-2010-sp3-your-request-couldnt-be-completed-this-may-have-occurred-for-security-reasons/
650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M00/85/81/wKiom1el9Mbyg0pxAACLU-N29Mc849.png "title=" 6.png " alt= "Wkiom1el9mbyg0pxaaclu-n29mc849.png"/>
In addition, the Microsoft Web site found in Exchange SP2 explicitly mentions that if you do OWA redirection and cancel the "Require SSL" in IIS, you need to modify the parameters of the webconf file.
Https://technet.microsoft.com/en-us/library/hh529928.aspx#OWA
650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M01/85/81/wKiom1el9NjisiZ_AABJ-Jv_avA107.png "title=" 7.png " alt= "Wkiom1el9njisiz_aabj-jv_ava107.png"/>
650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M00/85/80/wKioL1el9OaBKOdvAACG64yos7w301.png "title=" 8.png " alt= "Wkiol1el9oabkodvaacg64yos7w301.png"/>
It's not going to happen in SP1 for this problem, After confirming that the web.conf file in SP1 does not have this requiressl parameter, and this problem only appears when using HTTP to access OWA, and most of the existing enterprise uses HTTPS access, so the initial analysis of the problem ignored this different scenario led to the analysis direction, the above share for large Home Reference.
This article is from the "Huang Jinhui column" blog, be sure to keep this source http://stephen1991.blog.51cto.com/8959108/1835155
Upgrade to Exchange Server SP3 mailbox exception occurred