Portal Error: Failed to retrieve current HTTP context

(0) Share

Report

Posted on by Community Member

Hello,

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

I have the same question (0)

All responses (15)

Answers (0)

Suggested answer

Nick.Doelman 1,947 Most Valuable Professional on at

Like (0)

Report

I have seen this when the registration key is no longer valid. It is supposed to show you a "nag" message every so often but I have seen it instead the "failed to retrieve current HTTP context"

It might not be your issue but that would be one thing to check.

Cheers

Nick

Was this reply helpful? Yes No
G. E. Goodwin on at

Like (0)

Report

We've verified the registration key is valid. We continue to experience this error from time to time. We have verified that this only occurs when the site is under heavy load, especially when cache.axd is getting hit heavily due to CRM activity. We've limited cache notifications to only the entities we need Portals to invalidate cache for, but some of the required entities are the ones which see a lot of activity in our system.

Was this reply helpful? Yes No
Suggested answer

Nick.Doelman 1,947 Most Valuable Professional on at

Like (0)

Report

Are you using CRM Online or Onprem? If online is your portal located in the same data center as your CRM online? If onprem, have you selected a portal azure location as geographically close as possible to your CRM server? There are massive latency issues if the portal and CRM and located far apart. Might be worth investigating and potentially moving your portal location. Just a few thoughts.

Cheers

Nick

Was this reply helpful? Yes No
G. E. Goodwin on at

Like (0)

Report

We are online and our app is running in the same data center as our CRM instance.

Was this reply helpful? Yes No
Alan Mervitz 295 on at

Like (0)

Report

G. E. Goodwin, are you using IIS application initialization functionality? We have also had this error and suspect it might be related. If so, try removing the initialization configuration from your web.config file and see if the error stops occuring.

Was this reply helpful? Yes No
G. E. Goodwin on at

Like (0)

Report

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?

Was this reply helpful? Yes No
Alan Mervitz 295 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Tanguy TOUZARD 687 Most Valuable Professional on at

Like (0)

Report

Is anyone found out a confirmed cause and solution? I'm experiencing the same

Was this reply helpful? Yes No
Mahesh Wankhade 90 on at

Like (0)

Report

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

Was this reply helpful? Yes No
G. E. Goodwin on at

Like (1)

Report

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.

Was this reply helpful? Yes No