So these errors happen about 50% of the time (only to the custom modules) and its been happening for a few days now out of nowhere, and it makes working on the site extremly difficult. On top of that i have to deal with a very old version of DNN (For some reason i was told updating breaks things which is why we been stuck on version 3 of DNN for so long)
I'll take any advice anyone can throw at me, I'm at a loss for where to even begin.
Here are the error logs:
AssemblyVersion: 03.02.00 Method: CCC.DNN.Modules.CM_Application_Centre_View.CM_Application_Centre_View.Page_Load FileName: FileLineNumber: 0 FileColumnNumber: 0 PortalID: 0 PortalName: The CCC UserID: 19766 UserName: 1064799 ActiveTabID: 116 ActiveTabName: Application Centre AbsoluteURL: /en/Default.aspx AbsoluteURLReferrer: https://test.ca/en/Defaul...id=116&Type=OpenApps ExceptionGUID: 6f3529b3-77a8-4d2d-83c2-e09c182d7dc9 DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider InnerException: Internal Server Error Message: DotNetNuke.Services.Exceptions.PageLoadException: Internal Server Error ---> System.Web.HttpException: Internal Server Error at CCC.DNN.Modules.CM_Application_Centre_View.CM_Application_Centre_View.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain() --- End of inner exception stack trace --- StackTrace: Source: Server Name: CCC
Ugh... You're in a pickle! (As "they" say in certain places.) :)
The most obvious thing that would normally need to be done is to upgrade to the latest release. With this being a version 3.xx instance, upgrading would be just as time-consuming as rebuilding the website. Unfortunately, no matter the software, if it just sits there without regular maintenance (e.g., upgrades and updates), it will indeed break over time. Seemingly (and sadly), it will indeed come out of nowhere as well.
What's most likely in your case is that a Windows Update is causing the code to break. This is not something that would allow you to apply a quick fix.
If you have the expertise to rebuild the website in a current release of DNN, this would be your best and cheapest option to fix this now, as well and protect your website investment over the long term. This is because much of the DNN work is already done. It's a matter of finding feature parity with today's features and extension options.
If you don't have the resources to do this yourself, you can find an agency to help you as well. :)
Did you check if the database or db logs aren't very large? That often causes issues like this.
Posted By Timo Breumelhof on 10 Jul 2019 04:37 AM Did you check if the database or db logs aren't very large? That often causes issues like this.
No large database logs and windows updates are deactivated.
Posted By jeff2 on 10 Jul 2019 02:23 PM No large database logs and windows updates are deactivated.
Eh.. really? Completely? In that case, are you sure the site has not been hacked?
Another thing you can do is create a new website with a new app pool identity and move the whole site to that new website. Next thing I would do is move the site to your local machine and see if you get the same error.
Do you have the source of these modules?
Posted By Timo Breumelhof on 10 Jul 2019 02:53 PM Posted By jeff2 on 10 Jul 2019 02:23 PM No large database logs and windows updates are deactivated. Eh.. really? Completely? In that case, are you sure the site has not been hacked?
It dosent look like any signs of that.
Posted By Timo Breumelhof on 10 Jul 2019 02:56 PM Another thing you can do is create a new website with a new app pool identity and move the whole site to that new website. Next thing I would do is move the site to your local machine and see if you get the same error. Do you have the source of these modules?
The source of the modules have been long lost. Where only a few months away from migrating to a new website.
These Forums are for the discussion of the open source CMS DNN platform and ecosystem.
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.