You’re offline. This is a read only version of the page.
We are running v7.0.0023 Portals in production on a 2 instance Azure WebApp application. We are occasionally running into a 'Failed to retrieve current HTTP context.' portal error that causes the entire portal to crash. A restart of the WebApp application resolves the problem. We are unable to reproduce the error and the problem appears to occur randomly. We have plenty of unused room on CPU and memory server resources. This is happening for us a couple times per week.
Has anyone else run into this problem or know a solution?
Thanks,
Greg
*This post is locked for comments
Hi,
Please plan to upgrade your Adxstudio Portal to the latest one to get this issue resolved.
I am not sure what exactly line of code and changes I made at that time. Since, now I have been moved to the Adxstudio latest version so unfortunately, it's not possible for me to find.
Thanks
I think this is supposed to be fixed in version 7.0.0026 that was released on February 2, 2018 (download page). This is the relevant item from the release notes:
@Arpit I checked our Web Pages and we did not have any pages with 'Enable Tracking' set to 'Yes'. Do you have and could you share the web.config lines provided by MS support?
Thx for all the responses(Arpit,Goodwin).
@Arpit -
For us they suggested some changes in our Global.asax as explained in below post
www.adoxio.com/.../2017-04-03-workaround-fix-for-validation-of-viewstate-mac-failed
but this this didn't worked for us :(
were you suggested any other changes ?
will you able to share what code changes Microsoft suggested in your Web.Config.
Hello Everyone,
I had also faced the same problem in my Production instance with Adxstudio 7.23 version. It was a showstopper issue so I raised a ticket with Microsoft and got to know It's a bug in Adxstudio code. They suggested me to upgrade it to the latest version but doing the upgrade was not the solution for me as this process may take time.
Another solution was:
Microsoft suggested avoiding the 'Page Tracking' feature in Adxstudio, especially when you're portal is being used by the large audience. This is the root cause of this issue.
After doing this my issue got resolved completely.
First, I would recommend you to try the second step and observe whether the issue gets resolved or not. If not, then get in touch with Microsoft to perform the first step also.
If you find the answer as useful, please mark it as verified
Cheers
Arpit
https://arpitmscrmhunt.blogspot.in
We still randomly run into this problem. We haven't found a pattern to the problem. Our portal usage is pretty consistent, and sometimes we run into the error multiple times per week, at other times we can go a month or two before running into the error again.
Any luck with this error we are seeing same issue. after heavy load portal goes down for us. we are also using same ADX version.
Thanks,
Mahesh
Is anyone found out a confirmed cause and solution? I'm experiencing the same
We use Always On without any problems, all that does is prevent the application pool from shutting down during periods of inactivity.
The only other change I can think of that we made which may have stopped the error from occuring is reducing to 1 instance. If you could try that and the error stops then I think the error is probably related to the portal bus cache invalidation.
Alan Mervitz We do not have application initialization enabled in web.config, but we do have 'Always On' configured on the Web App instance running our Portals application. Any experience with this setting causing problems?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (