In Exchange 2013, the user reported a failure while logging on to OWA,
An unexpected error occurred and your request could not be processed.
x-owa-error:system.nullreferenceexceptionx-owa-version:15.0.775.32x-feserver:cas01x-beserver:mbx02date:2016/9/ 21 9:57:05
Open ADSI Edit, connect to configuration, and then find "cn=services"-"Cn=microsoft Exchange"-"cn=< your Exchange organization name >"-"cn= Client Access, then right-click to select Properties, open the Property Editor window, find the property value for the word "msexchcanarydata" in the Property Editor tab, and then clear (there may be 0-n multiple items)
Here we will copy the contents of these values again to Notepad to save, so you can play a backup double insurance, careful operation, after all, is the production environment.
650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/89/a3/wkiom1gyophssyslaafrv7j-tlg492.png "width=" 469 "height=" 364 "/>
Open the IIS Manager for the CAS server, click on "Application Pool", locate "Msexchangeowaapppool", and then click "Recycle" in the right window.
650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/89/a1/wkiol1gyoplie-eeaae8mhewdyu543.png "width=" 832 "height=" 177 "/>
After the Exchange server restart is complete, the user OWA and ECP are back to normal, and other Outlook features are normal.
This article is from the "old British Microsoft Blog" blog, please be sure to keep this source http://zyliday.blog.51cto.com/760700/1868258
Exchange 2013 Failure X-owa-error:system.nullreferenceexception