[Troubleshooting]-exchange OWA & ECP Error 500 unexpected error

"Summary"     

You have recently encountered an issue with OWA/ECP unreachable in the Exchange Microsoft environment ; send and receive mail, only after accessing the OWA/ECP page, after entering the account verification information, prompted "An unexpected error occurred, unable to process your request"; more magical, the current environment is the headquarters of 7 Exchange front-end servers, Exchange back-end servers, Division 2 full-Role deployment, dozens of mail servers, the beginning of the database on a back-end server, the user, in the process of troubleshooting another back-end server on the user does not work properly OWA/ECP This article will share the entire process of troubleshooting, so that you have a similar problem to facilitate troubleshooting.

"Phenomenon Symptoms"

Access OWA The following error occurred:

650) this.width=650; "src=" Http://stastudio.net/wp-content/uploads/2016/02/020116_0909_Troubleshoo1.png "/>

Access ECP The following error occurred:

650) this.width=650; "src=" Http://stastudio.net/wp-content/uploads/2016/02/020116_0909_Troubleshoo2.png "/>

The following error is logged in the Mailbox server event log:

journal name : Application

Source : MSExchange Control Panel

Events Id:4

650) this.width=650; "class=" AlignCenter "src=" http://stastudio.net/wp-content/uploads/2016/02/020116_0909_ Troubleshoo3.png "/>

journal name : Application

Source : MSExchange Common

Events id:4999

650) this.width=650; "class=" AlignCenter "src=" http://stastudio.net/wp-content/uploads/2016/02/020116_0909_ Troubleshoo4.png "/>

journal name : Application

Source : ASP. 4.0.30319.0

Events id:1309

650) this.width=650; "class=" AlignCenter "src=" http://stastudio.net/wp-content/uploads/2016/02/020116_0909_ Troubleshoo5.png "/>

"Troubleshooting Process"     

when the first time a fault is found, the first checks the user's database status is normal, Exchange cas\mbx service is normal, and through the command check the status of the unit is normal.     

Get-servercomponentstate ServerName

650) this.width=650; "src=" Http://stastudio.net/wp-content/uploads/2016/02/020116_0909_Troubleshoo6.png "/>

The above check server is in a normal state, then go to view the user's active database Exchange Server log, the discovery server logged the following error:

journal name :	Application	Application	Application
Source :	MSExchange Control Panel	MSExchange Common	ASP. 4.0.30319.0
Events ID:	4	4999	1309

the error message basically can be determined that the problem is caused by IIS failure, the most recent changes have not been network tuning, the only change is to all mailbox server \clientaccess\ecp\web.config files add parameters, so that the ECP can display the list of all OUs;     

Check that the server Web. config modification is not a problem, and through Google query the above log information in the Microsoft Forum to find similar problems, the general argument is that the cause of the problem is the ad configuration-services--Microsoft Exchange,cn=,cn=configuration,--The Msexchcanarydatax property value of Client Access is wrong;

650) this.width=650; "src=" Http://stastudio.net/wp-content/uploads/2016/02/020116_0909_Troubleshoo7.png "/>

at that time, because there is no way to determine the environment of the Msexchcanarydata property value is normal, this value is a global setting, the problem of the server only one; there is no attempt to empty this property value in the build environment to resolve the problem Because the mailbox server mounted several production databases at the same time, taking into account the impact on users, the DAG active copy of the switch, switch database hosting server, user access OWA\ECP normal. But the cause of this problem has not been found out;

After checking the server IIS security settings, redirection settings, SSL settings, and so on, there is still no exception, by restarting the Iis,exchange service, restarting the server, fallback \clientaccess\ecp\ The attempt to modify the Web. config file still exists, but in the process of restarting, it is found that the OWA\ECP access test immediately after the reboot is able to log in normally, but the same problem still occurs after a few seconds.

The failure of the user, although solved, but the root cause of the failure has not been found, the next day to Microsoft opened a case to investigate the problem, waiting for Microsoft's reply process, there is a mailbox server OWA/ECP access error, the same phenomenon and logging; Realize that it might really be due to an Msexchcanarydata property value exception, an operation that empties the property is simulated in the test environment, and the normal use of existing users is not affected, and the server does not need to be restarted after emptying the value. Simply restart the Msexchangeowaapppool application pool; Microsoft's reply is also recommended to empty the Msexchcanarydata property value to resolve the issue

"Resolution Process"

1. Open ADSI Edit, connect to configuration, and find "cn=services"--"Cn=microsoft Exchange"--"cn=<exchange organization Name >"--"cn=client Access"

2. Right-click on select "Properties" to open the Property Editor window and find the "Msexchcanarydata" attribute value in the "Property Editor" tab (there may be more than one 0-n)

3. Copy and record the value of the Msexchcanarydatax attribute to Notepad for backup, and you can also back up the ad for backup

650) this.width=650; "class=" AlignCenter "src=" http://stastudio.net/wp-content/uploads/2016/02/020116_0909_ Troubleshoo8.png "/>

4. Then empty the Msexchcanarydatax property value (there may be more than one 0-n), note here is empty, not delete the attribute, is emptied;

650) this.width=650; "class=" AlignCenter "src=" http://stastudio.net/wp-content/uploads/2016/02/020116_0909_ Troubleshoo9.png "/>650) this.width=650; class=" AlignCenter "src=" http://stastudio.net/wp-content/ Uploads/2016/02/020116_0909_troubleshoo10.png "/>

5. Open the IIS Manager of the CAS server, click on "Application Pool", locate "Msexchangeowaapppool", then click "Recycle" in the right window. 650) this.width=650; "class=" AlignCenter "src=" http://stastudio.net/wp-content/uploads/2016/02/020116_0909_ Troubleshoo11.png "/>

6. Re-view the value of the Msexchcanarydata property to see that the Msexchcanarydata property value has been regenerated

650) this.width=650; "class=" AlignCenter "src=" http://stastudio.net/wp-content/uploads/2016/02/020116_0909_ Troubleshoo12.png "/>

7. Verify that you can log in normally OWA/ECP

"Problem Resolution"

MsexchcanarydataMsexchcanarydatais aExchangeproperties that are created during schema expansion,MsexchcanarydataThe value is an encrypted token, typically on the client and server sideOWA,ECPor otherWebservice is used650) this.width=650; "class=" AlignCenter "src=" http://stastudio.net/wp-content/uploads/2016/02/020116_0909_ Troubleshoo13.png "/>

Normal Access process:

650) this.width=650; "class=" AlignCenter size-full wp-image-1077 "src=" http://stastudio.net/wp-content/uploads/2016 /02/msexchcanarydata01.jpg "alt=" MsExchCanaryData01 "width=" "height=" 218 "/>"

Non-normal access process:

650) this.width=650; "class=" AlignCenter size-full wp-image-1078 "src=" http://stastudio.net/wp-content/uploads/ 2016/02/msexchcanarydata02.jpg "alt=" msExchCanaryData02 "width=" and "height="/> detailed analysis can refer to this article: https://ucbite.wordpress.com/2014/01/13/exchange-2013-owa-ecp-failure-after-deploying-cu3/ http://social.technet.microsoft.com/wiki/contents/articles/29433. Exchange-2013-troubleshooting-something-went-wrong-in-both-owa-and-ecp.aspx

This article starts with: http://stastudio.net/@STA Studio

This article is from the "Gi Haixin It Records" blog, so be sure to keep this source http://jihaixin.blog.51cto.com/11174607/1740947

[Troubleshooting]-exchange OWA & ECP Error 500 unexpected error