We are a large organization running DNN 4.9 with 50 portals. Random portals appear to have a problem where, when they add a page, it technically does not exist - in other words, it gets added to the DB, but navigating to it is impossible unless the cache is cleared or the application pool is recycled. We've had this issue since 4.0 and keep hoping with each successive upgrade that it will be solved, but alas, it keeps popping up. By popping up, sometimes it will go away - after an upgrade, one portal will be free and clear, then two months down the line, a different portal will begin to report the problem that did not experience it previously. we've done extensive troubleshooting, and have tracked it down to the cache that's being stored in the webserver memory. Whatever mechanism that is supposed to mark the cache as dirty is failing, though we cannot discover what this mechanism is or how it is failing. we've been working on this for months now, and the executives now have the ultimatum - solve it, or find another framework.

Anyone have any ideas that can help us solve this? I do not want to leave the DNN arena.

Thank you

D

In going to answer your questions, I think you might have lead us to the answer, or at least in the direction the answer lies in.

 We haven't yet upgraded - for us, upgrading is a mounmental task, as we have made some custom changes to the library itself (and that's also one of the reasons we haven't purchased the pro license, not sure that the dnn team could help with all of the customization we have done). While the goal is to abstract these customizations away from the customizations, I'm wondering if these customizations are interrupting the normal process of clearing the cache when pages are created. What I am curious is... has anyone else experienced this sort of issue? Doing an internet search doesn't show a lot of hits with this problem. Thank you for the questions!

D.

I would go here and search the web page and itself for all issues after 4.9.0 that have the word "cache" in them...

http://support.dotnetnuke.com/project/ChangeLog.aspx?PROJID=2

Thanks