I am getting this Error in owa 2010. the exchange servers are with 2010 sp2.  when i try to send a new message this will appear, Even i tried with different users as well. 

but all the other connectivities work fine like active sync and RPC. this happens only in OWA.

Request
Url: https://mail.domain.com:443/owa/forms/premium/EditMessage.aspx?ae=Item&a=New&t=IPM.Note&cc=MTQuMi4zMjguOSxlbi1VUyw0Mjk0OTY3Mjk1LEhUTUwsMCww&pspid=_1375363806798_283517181
User host address: 10.10.1.13
User: testuser
EX Address: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=testuser
SMTP Address: testuser@domain.net
OWA version: 14.2.328.9
Mailbox server: server1.domain.net

Exception
Exception type: System.Web.HttpException
Exception message: Request timed out.

Call stack

No callstack available

has anybody gone through this??

thanks.

does this issue hapeen only with one user or all users?

Do you see any errors in event logs?

this issue comes for all users. 

below is what i could find from even logWatson report about to be sent for process id: 5244, with parameters: E12, c-RTL-AMD64, 14.02.0328.009, OWA, unknown, unknown, System.InvalidOperationException, 0, unknown.
ErrorReportingEnabled: False

Watson report about to be sent for process id: 2536, with parameters: E12, c-RTL-AMD64, 14.02.0328.009, M.E.RpcClientAccess.Service, M.E.Data.Storage, M.E.D.S.ServerPerformanceObject.StopAndCollectPerformanceData, System.InvalidOperationException, 97fd, 14.02.0328.009.
ErrorReportingEnabled: False
Watson report about to be sent for process id: 684, with parameters: E12, c-RTL-AMD64, 14.02.0328.009, OWA, unknown, unknown, System.InvalidOperationException, 0, unknown.
ErrorReportingEnabled: False
Watson report about to be sent for process id: 2592, with parameters: E12, c-RTL-AMD64, 14.02.0328.009, M.E.RpcClientAccess.Service, M.E.Data.Storage, M.E.D.S.ServerPerformanceObject.StopAndCollectPerformanceData, System.InvalidOperationException, 97fd, 14.02.0328.009.
ErrorReportingEnabled: False
MSExchangeCommon 4999

have you attempted to access owa directly?

Https:\\serverfqdn\owa

hi lmurthy,

yes. it results the same.

thanks

I would recycling IIS on the servers. Was RU$ recently deployed, do you have CAS servers proxying OWA?

Hello,

I recommend you to run ExBPA against your exchange server health.

I recommend you check IIS logs.

And I recommend you install the latest RU to check the result.

If you have any feedback on our support, please click here