- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
Watch NowOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Hello
I have 23500 appliance.
I am using Mobile Access Blade while reaching to Exchange 2019 for who is out site of my local.
Actually it is working fine but there is a annoying problem.
Some e-mail are not visible. There is an error on the page and it says
Your request cannot be completed at this time. Please try again later.Here is an example screen shot.
Users logons from mobile access web page, after that selects my owa link and than he can see owa page. He can login this page and send, read, forward all of mails.
But some of them giving this error. He can not read this mail or forward via mobile access. In my local without mobile access he can read this "broken" e-mail.
There is no drop or reject log in smart console.
Could yo help me?
Mobile Access Blade has to rewrite HTML and JavaScript so that it appears to be coming from the gateway.
As there are an infinite number of ways to write HTML/JavaScript, we only test (and support) specific applications.
OWA should be one of them.
That said, perhaps this doesn’t work on an older version of gateway code and a newer version of OWA.
What version/JHF are we talking about here?
Hello,
I am using R80.10 and Exchange Server 2019.
But I was having this issue while using Exchange Server 2016.
@sukruozdemir no problems with OWA since R80.40 (R81 and R81.10 works well)
Please check that caching on the endpoint is allowed for all content
with the layout value you can switch beetween the simple and advanced design of OWA. layout=light is not such a complex web-application like the standard OWA design.
https://yourOWAserver/owa/?layout=full
https://yourOWAserver/owa/?layout=light
If there is no connectivity problem between gateway and OWA opening a TAC case would be the best next step.
Hello
Actually, this option is default, so this is the setting for me.
I think it's best to open a support ticket.
Thank you.
We had have the same issue with OWA of Exchange 2019. The problem does not occur if using the older OWA design with minimal menues and less html code. Check Point provided some rewritten html pages for OWA integration in MOB blade but doesn‘t solve the problem. With R80.40 Jumbo take 43 and up everything is fine with OWA. Since the update none of our users are reporting the mentioned error.
Thank you, I am using R80.10 and will upgrade to 80.40 two weeks later. I will try after upgrade and write about issue.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
Fri 12 Dec 2025 @ 10:00 AM (CET)
Check Mates Live Netherlands: #41 AI & Multi Context ProtocolTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Fri 12 Dec 2025 @ 10:00 AM (CET)
Check Mates Live Netherlands: #41 AI & Multi Context ProtocolTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY