We are seeing this error when connecting to OWA (Exchange 2013 SP1 with Claims Based Auth enabled) through Windows Server 2012 WAP configured for ADFS (v3.) Now I have seen this discussion on WAP (Here) articles and they seem to lay the blame the OWA server, which is why I am posting here.
The user sees this error: "This method or property is not supported after HttpRequest.Form, Files, InputStream, or BinaryRead has been invoked." which goes away after the browser is refreshed. This is an intermittent issue.
WAP reports this error:
Connection to the backend server failed. Error: (0x80072ef1).
Details:
Transaction ID: {---}
Session ID: {---}
Published Application Name: OWA
Published Application ID: 9ABCB3E7-AF7F-CCEE-F282-7528AF9E0306
Published Application External URL: https://webmail.westminster.org.uk/owa/
Published Backend URL: https://webmail.westminster.org.uk/owa/
User: [UserName]@westminster.org.uk
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0
Device ID: <Not Applicable>
Token State: NotFound
Cookie State: OK
Client Request URL: https://webmail.westminster.org.uk/owa/ev.owa2?ns=PendingRequest&ev=PendingNotificationRequest&UA=0&cid=af31207c-4fff-423c-a102-9da7b9b7c54e&X-OWA-CANARY=JTEnu1OJJUG0fnzYGACHOxFCMyb0MNEIbLGjM1u9TDu6BhbBje3M-3NPBSQ5VT7RROofPbYlBk8.&n=gf
Backend Request URL: https://webmail.westminster.org.uk/owa/ev.owa2?ns=PendingRequest&ev=PendingNotificationRequest&UA=0&cid=af31207c-4fff-423c-a102-9da7b9b7c54e&X-OWA-CANARY=JTEnu1OJJUG0fnzYGACHOxFCMyb0MNEIbLGjM1u9TDu6BhbBje3M-3NPBSQ5VT7RROofPbYlBk8.&n=gf
Preauthentication Flow: PreAuthBrowser
Backend Server Authentication Mode: PassThrough
State Machine State: FEBodyWriting
Response Code to Client: 200
Response Message to Client: OK
Client Certificate Issuer: <Not Found>
Anthony Sheehy - MCP, MCITP