Forum Discussion

Anthony_Ventimi's avatar
Anthony_Ventimi
Icon for Nimbostratus rankNimbostratus
Jun 20, 2012

OWA 2010 Freezes when trying to access a shared mailbox

Hello,

 

 

Currently we have two F5 BIG IP 3900's deployed for our Exchange 2010 environment. We are noticing when users are using the VIP address to access another shared mailbox OWA freezes right after login, the only way to get out is to close the browser (This does NOT happen when they user OWA-Lite)

 

 

For instance users put in the following link:

 

 

https://VIPCASArray/owa/sharedmailbox@company.local/

 

 

The OWA login pages displays normally once after the user logs in the page freezes and they're stuck.

 

 

If they access the shared mailbox directly via a single CAS server in the array, the page loads fine, which is pushing me in the direction of a configuration issue with the F5 device.

 

 

https://CASSERVER1/owa/sharedmailbox@company.local/

 

 

This works just fine.. I did some searching around on the forums and found this article:

 

 

https://devcentral.f5.com/community/GroupDetails/tabid/1082223/asg/62/aft/1179031/showtab/groupforums/default.aspx

 

 

I removed "Keep Accept-Encoding" from the HTTP profile but the issue still occurs, if anyone has some thoughts on this issue it would be greatly appreciated.

 

 

 

 

-Anthony

 

microsoft
partner
  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Jun 20, 2012
    Hi Anthony, this only happens when opening a shared mailbox, not the user's own mailbox? I just tried to replicate this but was unable to. Does it still happen if you remove all but one CAS server from the LTM pool?

     

     

    Which version of BIG-IP are you running? Did you deploy using an iApp template?

     

     

    Is it possible to monitor the traffic with a utility such as HTTPWatch or Fiddler, to see which request it is getting hung up on?

     

    thanks

     

    Mike
  • Anthony_Ventimi's avatar
    Anthony_Ventimi
    Icon for Nimbostratus rankNimbostratus
    Jun 20, 2012
    Hey Mike,

     

     

    So far it's mainly with a shared mailbox; I didn't try removing any CAS servers from the LTM pool.. I can try and let you know.

     

     

    Were running the follow build: BIG-IP 10.2.4 Build 577.0 Final

     

     

    Were using the following profile: microsoft_exchange_2010_https_http-lan-optimized-caching_shared_http

     

     

    And yes we used a iApp template for Exchange

     

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Jun 20, 2012
    OK. Also, make sure that you are using the latest version of the deployment guide, located here:

     

     

    http://www.f5.com/pdf/deployment-guides/f5-exchange-2010-dg.pdf

     

     

    The version you want is 4.0, dated 5-22-2012.
  • Bjarne_10209's avatar
    Bjarne_10209
    Icon for Nimbostratus rankNimbostratus
    Sep 25, 2012

    I have done serveral F5 LTM and Exchange 2010 configurations. Same problem everywhere with OWA freeze. Solved the problem by removing the Web Acceleration Profile that iApp creates on the VS with OWA.

     

  • Perry_70844's avatar
    Perry_70844
    Icon for Nimbostratus rankNimbostratus
    Mar 22, 2013
    Bjarne is correct, try disabling Web Acceleration. I'm running a pair of 3900s on 11.1 with iApp template "f5.microsoft_exchange_2010_cas.2012_06_08". Here's what I had to do with the assistance of support:

     

     

    First, disable the Strict Updates option under (iApp >> Application Services >> Properties >> Advanced).

     

     

    Then, when you try to go into the individual virtual servers and click "none" on the web acceleration profile you will receive the following error:

     

     

    "01070394:3: CACHE::disable in rule (/Common/iApp_Exchange_2010.app/iApp_Exchange_2010_combined_vs_persist_iRule) requires an associated WEBACCELERATION profile on the virtual server (/Common/iApp_Exchange_2010.app/iApp_Exchange_2010_combined_https)."

     

     

    The resolve this error, do the following:

     

     

    Navigate to Local Traffic >> iRules and click on the rule named "iApp_Exchange_2010_combined_vs_persist_iRule" and comment out the three lines that have CACHE::disable listed. Just put a sign in front of them, and then click Update at the bottom.

     

     

    I hope this helps someone.