I have very frequent incidence of the following error on windows 2012r2, in the event log, which seems related to dnn. i am running dnn 9.6. i believe that this causes an application crash.in which the client becomes unresponsive. In numerous cases i encounter service unavailable (http 503) because the apppool is disabled! so i have to start the apppool. this is more of a booby trap than windows 3.1.
is ddr a 9.6 artifact, or is it something i have lingering from legacy dnn installations? if it is obsolete, how can i track down the page(s) using it. my entire website is using, to the best of my knowledge a dnngo theme allegedly compatible with 9.6.
is it possible to configure apppool to ignore requests for termination?
any help resolving would appreciated.
Application: w3wp.exe Framework Version: v4.0.30319 Description: The application requested process termination through System.Environment.FailFast(string message). Message: Stack: at System.Environment.FailFast(System.String) at ➥돖驴熎걝덛掌ϳ.ᆵ鷊�䝂饞혡ፖ() at ..cctor() at System.RuntimeTypeHandle.CreateInstance(System.RuntimeType, Boolean, Boolean, Boolean ByRef, System.RuntimeMethodHandleInternal ByRef, Boolean ByRef) at System.RuntimeType.CreateInstanceSlow(Boolean, Boolean, Boolean, System.Threading.StackCrawlMark ByRef) at System.Activator.CreateInstance(System.Type, Boolean) at System.Activator.CreateInstance(System.Type) at DotNetNuke.Web.DDRMenu.Localisation.Generic.HaveApi() at DotNetNuke.Web.DDRMenu.Localisation.Localiser.get_LocalisationApi() at DotNetNuke.Web.DDRMenu.Localisation.Localiser.LocaliseDNNNodeCollection(DotNetNuke.UI.WebControls.DNNNodeCollection) at DotNetNuke.Web.DDRMenu.SkinObject.OnPreRender(System.EventArgs) at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Page.ProcessRequestMain(Boolean, Boolean) at System.Web.UI.Page.ProcessRequest(Boolean, Boolean) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(System.Web.HttpContext) at System.Web.HttpApplication+CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep) at System.Web.HttpApplication.ExecuteStep(IExecutionStep, Boolean ByRef) at System.Web.HttpApplication+PipelineStepManager.ResumeSteps(System.Exception) at System.Web.HttpApplication.BeginProcessRequestNotification(System.Web.HttpContext, System.AsyncCallback) at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(System.Web.Hosting.IIS7WorkerRequest, System.Web.HttpContext) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, Int32) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr, IntPtr, IntPtr, Int32) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr, System.Web.RequestNotificationStatus ByRef) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr, System.Web.RequestNotificationStatus ByRef) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, Int32) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr, IntPtr, IntPtr, Int32)
after further research, i have determined that the dnngo theme is the culprit. i cannot change the site default theme to, let's say, xcillion as it causes site navigation to fail. i cannot use another theme on a new or existing page because it results in navigation failure as noted in my previous post - comlete with server side faults which eventually stop the apppool. when i add a module to a dnngo themed page, page elements are corrupted. in fact, i got an email from google telling me that i had bread crumb issues and that if they weren't resolved my page would be boycotted.
maybe there is a simple fix. i asked the vendor to resolve. i gave them 1-2 days or i would demand back my money. it will be a big job removing its theme from my site, but i will do it and blast away every byte of their software from my server. the only reason that i am giving it (dnngo) the benefit of the doubt is because i have used its themes for several years with general satisfaction.
as to my question about regulating the behavior of the apppool, the answer is yes - there are options in advanced settings of the apppool which govern how, when, and if the apppool should shut down
Linda has proven to be very responsive and i have liked the theme in the past. the one i just installed is basically an upgrade to a prior edition. the new one is UnZip_DNNGo20047_Unlimited033_AllModules_7.7.0.
it turns out that i am part of the problem. there were a couple of pages using the old revolution slider. however, i thought that making them hidden and inactive would eliminate them as a cause of problems.
over all this upgrade has been my worst. i am restoring back to 8.3 and starting again. my frustration was that i thought i could make progress on website rennovations this weekend but those plans went up in smoke. dnngo has been very attentive but i have to weed my own garden first. i will make this work, but it is requiring a substantial amount of work.
are you saying that i should remove radeditor from my 8.3 installation before upgrading to 9.6? where do i get the correct ckeditor? which version is correct for 9.6?
ps - actually i recall it being a configuration setting. neeeever mind.
i have upgraded successfully. removing old software and updating core existing software prior to upgrading dnn was key to overcoming the server errors i encountered in round one. the server errors have decreased substantially. there is still more weed pulling to do from the 8.3 days.
the biggest lesson which i had learned long ago from upgrades served me well this time around. BACKUP UP YOUR IIS SITE AND YOUR DATABASE BEFORE UPGRADING DNN
These Forums are dedicated to the discussion of DNN Platform.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.