I "successfully" upgrading my Exchange 2013 server on Windows 2012 to CU1. After the installation I am noticing that OWA is very flaky, to the point that it isn't useful. So this is what I get. Click on a folder in my mailbox, or People, or Tasks: Your Request Can't be completed right now. Please try again later" When I can see messags and I click on one I may get: "Error: Your request can't be completed right now. Please try again later." The same message occurs when I create a new message and try to send it. This is a huge pain since OWA is not reliable to use whatsoever. Is there anything that can be done to make this work? Waiting another 3 months or more for CU2 is really not an option. Any help or suggestions from Microsoft would be helpful. thanks Rob

Hi RobMD, Is the user experiencing this proble a user who was having no issues with OWA previously? I am not aware of any OWA destabalization issues in CU1, it would be helpful if you can spot-check your application logs for us and copy/paste anything of interest that appears to relate to OWA.Senior Program Manager, Exchange Customer Advisory Team NOTICE: My posts are provided AS IS without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Hi Brian. Yes, this is a new problem as OWA was working perfectly prior to installing CU1. I checked the application and system logs and there is nothing out of the ordinary being logged. One important note is OWA is being proxy'd by TMG. All that TMG is doing is the normal reverse proxy setup that is commonly used for OWA. When I access ECP that all works without issue as all items can be accessed on the first attempt and there are no errors. The weird thing is something won't display, like your Inbox messages or it can list the messages but not render a message body. If you navigate to around to other parts of your mailbox, People, Calendar, Tasks, etc. and then come back to the Inbox it might show you the message list or render a message body. It's quite strange. Rob

Hi Guys, I can confirm what Rob is seeing as I too am experiencing the same issue. If I click on any folders in the mailbox, an error is returned "Your Request Can't be completed right now. Please try again later" I have to click another folder and then click back to the folder I was trying to access...sometimes multiple times until the emails re-appear. This has only happened since I upgraded to Exchange 2013 CU1. Cheers, Hardeep

Out of curiosity, what happens if you bypass TMG and go directly to the CAS? This is a single multi-role server, correct?Senior Program Manager, Exchange Customer Advisory Team NOTICE: My posts are provided AS IS without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Hi Brian. Bypassing TMG does not make a difference. I have the problem on the LAN going directly to the CAS. Yes, this is a multi-role server. Thanks Rob

Hi Brian. One last observation on this issue with OWA. When it isn't functioning, if you press Refresh, then it will fix things up at least temporarily so that you can read a message, delete a message, or reply to a message. This works everytime. Rob

Same problem here. No proxy. It happens on IE10, IE9 on Windows 7/8 as well as the mobile version of OWA on iOS 6.1.3.

Hi Everyone, While looking around for more info about this problem for one of my clients I came across this thread. I managed to fix this problem for my client by selecting in the OWA Virtual Directory (IIS) the "Ignore certificates" under SSL settings. My customer was having "Accept certificate" instead of "Ignore certificate". The symptoms that my customer had are exactly the same as yours. Hope this will help you to fix it. Cheers, Andrei

Hi Andrei. Thanks for the info. Yes, I had "Accept Certificates" selected on the OWA Virtual Directory. This is on purpose, but setting to "Ignore certificate" does fix the problem, however, it causes another. Thanks Rob

Any updates Rob? OWA was working great but suddenly I am seeing this error on all 3 client access servers...very odd. Brandon

In addition, I checked the mailbox servers and I am seeing the following in the event logs: WebHost failed to process a request. Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/35320229 Exception: System.ServiceModel.ServiceActivationException: The service '/owa/service.svc' cannot be activated due to an exception during compilation. The exception message is: The authentication schemes configured on the host ('IntegratedWindowsAuthentication') do not allow those configured on the binding 'WebHttpBinding' ('Anonymous'). Please ensure that the SecurityMode is set to Transport or TransportCredentialOnly. Additionally, this may be resolved by changing the authentication schemes for this application through the IIS management tool, through the ServiceHost.Authentication.AuthenticationSchemes property, in the application configuration file at the <serviceAuthenticationManager> element, by updating the ClientCredentialType property on the binding, or by adjusting the AuthenticationScheme property on the HttpTransportBindingElement.. ---> System.NotSupportedException: The authentication schemes configured on the host ('IntegratedWindowsAuthentication') do not allow those configured on the binding 'WebHttpBinding' ('Anonymous'). Please ensure that the SecurityMode is set to Transport or TransportCredentialOnly. Additionally, this may be resolved by changing the authentication schemes for this application through the IIS management tool, through the ServiceHost.Authentication.AuthenticationSchemes property, in the application configuration file at the <serviceAuthenticationManager> element, by updating the ClientCredentialType property on the binding, or by adjusting the AuthenticationScheme property on the HttpTransportBindingElement. at System.ServiceModel.Channels.HttpTransportBindingElement.UpdateAuthenticationSchemes(BindingContext context) at System.ServiceModel.Channels.HttpsTransportBindingElement.BuildChannelListener[TChannel](BindingContext context) at System.ServiceModel.Channels.Binding.BuildChannelListener[TChannel](Uri listenUriBaseAddress, String listenUriRelativeAddress, ListenUriMode listenUriMode, BindingParameterCollection parameters) at System.ServiceModel.Description.DispatcherBuilder.MaybeCreateListener(Boolean actuallyCreate, Type[] supportedChannels, Binding binding, BindingParameterCollection parameters, Uri listenUriBaseAddress, String listenUriRelativeAddress, ListenUriMode listenUriMode, ServiceThrottle throttle, IChannelListener& result, Boolean supportContextSession) at System.ServiceModel.Description.DispatcherBuilder.BuildChannelListener(StuffPerListenUriInfo stuff, ServiceHostBase serviceHost, Uri listenUri, ListenUriMode listenUriMode, Boolean supportContextSession, IChannelListener& result) at System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost) at System.ServiceModel.ServiceHostBase.InitializeRuntime() at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(ServiceActivationInfo serviceActivationInfo, EventTraceActivity eventTraceActivity) at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity) --- End of inner exception stack trace --- at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity) at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath, EventTraceActivity eventTraceActivity) Process Name: w3wp Process ID: 15616