Posted By Mark Buelsing on 22 Jun 2020 09:00 AM
1. Is it possible that there are DNNGo modules on those pages, and that they are actually the problem after the theme is changed?.... I suggest testing by adding a new page with only the standard DNN HTML module. ....

2.....Additionally, you can run a query to see which pages have a particular theme applied to it. That way you can go right to the ones that need attention and skip the rest. Try this non-destructive SQL script for that.

SELECT [TabID],[PortalID],[TabName],[SkinSrc],[ContainerSrc] FROM [Tabs]
 

i do not, nor have i ever, use dnngo modules other than the theme per se. i can't add a page using dnn default theme. the page is unnavigable unless i use the dnngo theme. depending upon how extensively i deviate from dnngo themes, the site becomes blank - ie no page renders. i had to restore my site more than once this past weekend trying to recover from these types of experiments.

thanks for the sql query.

the next step is to 1. change the site default theme 2. using the query for reference, change every page theme to dnn default 3. pray to god that i can still reach the extensions page to unistall the theme 4. go to the server to delete the folders 5. assume that i will have to restore my site because i can't navigate any more. the website will probably fail to come up. i have experienced this numerous times this past weekend mucking around with this theme. it is outrageous.

 

 

i may have been too rash and uncritical in my aspersions cast upon dnngo. the issue may be more complicated than themes. after removing dnngo - in a rather unorthodox way i might add - as there was no other - i studied the output of the browser window and noticed in small fine print - 6pt or so - ERR_CONNECTION_RESET. would that have anything to do with skin removal or missing? there is more to the story than meets the eye but i have not uncovered it. as far as i have been able to discern, there have been no errors logged by dnn. i am not even certain that i am reaching the application successfully but may try fiddler to see if it detects anything

Here is some direction on that error: https://www.ionos.ca/digi...rr-connection-reset/
Also, It occurred to me to mention that in addition to the themes on the pages, you should make sure you have no modules with DNNGo containers on them. Use that same query to determine if there are any and also change the default container in site settings or themes to not be DNNGo.

Posted By Mark Buelsing on 23 Jun 2020 12:40 AM
Here is some direction on that error: https://www.ionos.ca/digi...ection-reset/.......

i went through that article - and a few others - last night with no success. i tested the site from 4 different browsers including phone and from work. i don't think that the issue is client side. i am looking at server side remediation and am almost all out of tricks for iis. i had planned to upgrade the server os soon, so this may be the push i needed.

 

 

i finally could reproduce on demand an error which appears in the server event logs. this is running dnn 9.6. whenever i navigate to the website, after a few seconds this error is generated. is it possible to repair a dnn site? i do have the ddrmenu dll.

Log Name: Application
Source: .NET Runtime
Date: 6/23/2020 11:59:38 AM
Event ID: 1025
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxxxxxxxxxxxxx.local
Description:
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.RuntimeType.CreateInstanceDefaultCtor(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.ProcessRequestWithNoAssert(System.Web.HttpContext)
at System.Web.UI.Page.ProcessRequest(System.Web.HttpContext)
at ASP.default_aspx.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.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.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.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.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, Int32)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr, IntPtr, IntPtr, Int32)

Event Xml:



1025
2
0
0x80000000000000

57234005
Application
xxxxxxxxxxxxxxxxxxxxxxxxxxxxx.local



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.RuntimeType.CreateInstanceDefaultCtor(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.ProcessRequestWithNoAssert(System.Web.HttpContext)
at System.Web.UI.Page.ProcessRequest(System.Web.HttpContext)
at ASP.default_aspx.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.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.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.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.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, Int32)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr, IntPtr, IntPtr, Int32)

 

Not being a developer myself, this is stepping out of my skill set. I would still try the following. Reapply the correct access permissions to all the folders in the httpdocs folder and below, and restarting the App Pool.

If possible, can you restore and switch the theme? Then, as Mark suggested, check for pages that may have DNNGo modules.

Delete the modules.
Delete the skin and container folders for the DNNGo theme.
Do not delete dlls.

Posted By Joe Craig on 23 Jun 2020 12:25 PM
If possible, can you restore and switch the theme? Then, as Mark suggested, check for pages that may have DNNGo modules....
 

been there and done that repeatedly. it does not work. it may not even be an issue with the dnngo themes per se - their removals may simply be unmasking a deeper problem. in other words, isn't ddrmenu a native dnn artifact? if so, what is it complaining about in the stack trace i posted? why would ddrmenu care about any dnngo elements? if it does, then it goes back to my comment about a hard dependency between dnn and dnngo. i have purged all dnngo code - as far as i know - from the website folder as well as from the database - including dlls. i am sure that i have missed a few items, but i don't think that it explains the ddrmenu error - except for that curious chinese method which is second to last called. i am stepping back from the dnngo aspect a bit to consider what is amiss in the dnn installation or configuration proper.

ps - in any event, i have proven to my satisfaction that the event represented by the stack trace is the cause of the err_connect_reset. i watched the page attempt to load on the server. at the point where the popup occurs, the browser waiter stops spinning. to me they seem quite related. so until the ddrmenu issue - and maybe that is not even the root - is resolved, then the website simply will not serve pages.

i have concluded that there is no solution but to start anew with a fresh install. my current hypothesis is that the chinese or korean method reported in the stack trace above is malware from dnngo. i would love to be proven wrong. there may be a simple cure or explanation, but i don't have it. I do know for certain that the error prevents my site from loading when not using the dnngo theme, and is the cause of the err_connection_reset error seen on some browsers' failure pages.

the only silver lining is that this creates an opportune moment to upgrade the operating system and dbms.

Have you reported this to DNNGo? Especially the part about malware. They need to know of your conclusion.

Also, if you really think that this is malware, you should report to [email protected]. That will help everyone.