I'll start tracking my every step on here in hopes of getting this fixed. It's to the point where it has broken my site for all intents and purposes. Just editing a text module takes several tries.
Both sites I have are DNN3.2.2 on different servers with different domains. The site that has the problem gets much more traffic than the site that doesn't have the problem. I think it may be traffic related because I don't remember initially having this issue with my problem site initially. What became a minor nuissance has now become a major issue.
I have tried three different possible fixes to the situation. Some seem to partially fix the problem. I'll talk about implementing them and what the results have been once I reintroduce them. For now I've taken out all "fixes" and am starting from square one again to map what happens.
I'll explain what happens when I don't apply these suggestions first. First, I am only using my one trouble site. I am not doing anything with my second site. First, a little about my site:
A. DNN3.2.2 on WebSecureStores shared hosting
B. The web.config has this line in it but commented out:
<!
-- add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" / -->
C. The "enablewebfarmsupport" in the web.config is set to false (I don't think I'm on a web farm)
D. The "enablecachepersistance" is also set to false
E. The "customerrosmode" is set to Remote Only (I may need to change this)
The problems I am having:
1. Users get logged out in both IE and Firefox (not a time issue). This includes superusers. Log out occurs when viewing admin pages or updating changes to text modules and when generating a thid party report from a third party module only viewable by admin. While viewin the Log Viewer if I try to select more than the default 10 records I get logged out. If I try to view the second page of 10 errors I get logged out. I imagine it happens at other times but this is what comes to mind.
2. My error log shows MANY "invalid_viewstate" errors like mentioned previously in this post. This is from previous memory of the error log. At this time I can't verify past the first 10 log entries because if I try it logs me out. It also shows the "application started" frequently without any errors thrown in between. My log has shown application started at 1:17:53 and without error in between shows it started again at 1:22:16 and again at 1:32:44 and again at 1:38:52 and again at 1:40:54. I believe this is because I am getting logged out and something is causing my application to die. My host recently put my site on an isolated application pool for memory errors which have gone away after getting rid of the DNN Search Input and Results modules from my homepage. I certainly can't rule out Host configuration with my site as a possible cause of my issues but I don't know much about what they are doing to my site if anything (WebSecureStores).
Other errors I get less frequently which may be related:
DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest
Message: System.Exception: Unhandled Error: ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) at System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---
And:
Message: System.ArgumentException: Add failed. Duplicate key value supplied. at Microsoft.VisualBasic.Collection.Add(Object Item, String Key, Object Before, Object After) at DotNetNuke.Services.Scheduling.DNNScheduling.CoreScheduler.AddToScheduleQueue(ScheduleHistoryItem objScheduleHistoryItem) at DotNetNuke.Services.Scheduling.DNNScheduling.CoreScheduler.LoadQueueFromTimer() at DotNetNuke.Services.Scheduling.DNNScheduling.CoreScheduler.Start()
I am going to try a few things to see what they do. This will include renaming the cookies, renaming the forms authentication, taking the "IsoApps" out of the web.config, and trying a session variable again. I'll post what I come up with.