How to avoid "Access policy evaluation is already in progress"

Please help. I'm using APM BIG-IP 12.1.2 Build 1.0.271 Hotfix HF1 and iAPP (tried as well)

I login once everything is fine then if I try again I get "Access policy evaluation is already in progress for your current session." Everytime. doesn't matter if I close the browser. The only way around it is in private mode. I have tried everything in this thread and nothing seems to work. I seem to have the rule for "Creating the iRule to terminate inactive APM sessions" on from the iAPP but I still get the error. Anyone know what I am missing?

Thanks,

Misty

Ok actaully I think matt's rule worked for me

when HTTP_REQUEST { 
if { [HTTP::cookie exists "IsClientAppCacheEnabled"] } { 
HTTP::cookie "IsClientAppCacheEnabled" False } }

You just really have to clean out the browser. Clearing cache and cookies from HTTP watch wasn't enough.

The irule you used disable App cache

This irule prevent new session when app cache is enabled

when ACCESS_SESSION_STARTED {
    set landinguri [ACCESS::session data get session.server.landinguri]
    switch -glob $landinguri {
        "/owa/plt1.ashx?*" -
        "/owa/sessiondata.ashx?appcacheclient=1" -
        "/owa/userspecificresourceinjector.ashx?*&appcacheclient=1*" -
        "/owa/manifests/appCacheManifestHandler.ashx?owamanifest=1" {
            ACCESS::respond 403 -version "1.1" noserver "Connection" "Close"
            ACCESS::session remove
            return
        }
    }
}

Thank you Stanislas Piron

I tried that on a clean system but it doesn't seem to work on Outlook 2016. Do you know for a fact that it does? Is it a replacement for the other iRule?

Thanks for you time

I didn't work a lot with exchange 2016, but the customer I wrote this irule for was migrated from Exch 2013 to 2016 and didn't say me it's not working.

 

You can try with this irule and if the "Access policy evaluation is already in progress for your current session." message appears, look at session variable session.server.landinguri and add a comment on the codeshare article.

 

the 4 URLs in this code were discovered like that and may be we can add more URLs.