We recently reskinned a site because after upgrading versions the skin that the site was using was no longer compatible with the new DNN version that we are using. Everything works great. We get the site looking good, everything organized and working well. Then in the middle of the night the site dies, and throws a 500 Error. Looking through logs we receive a number of Page Load Exception Errors. If I roll the database back to the day that we installed the skin then everything works fine, then at a random time these errors occur again bringing the whole site down. Is it something as simple as switching out the skin or do we have greater issues here? At a loss as to how we should proceed with this one. Multiple other sites that are working well on this portal.
Site Info: Dnn Version: 09.06.01 (0 )
4.7 DotNet Framework
Errors present in logs:
This is the latest error:
AbsoluteURL:/Default.aspx
DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke
ExceptionGUID:3fb90655-4e96-462b-9b24-ad780b2c19fb
AssemblyVersion:9.6.1
PortalId:1053
UserId:-1
TabId:6597
RawUrl:/Default.aspx?tabid=6597&error=An%20unexpected%20error%20has%20occurred&content=0
Referrer:
UserAgent:Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm)
ExceptionHash:IaBqzZrxQgUZIzTJp8RRWG09dQM=
Message:Value cannot be null. Parameter name: file
StackTrace:
InnerMessage:Value cannot be null. Parameter name: file
InnerStackTrace:
at DotNetNuke.Services.FileSystem.FileManager.GetUrl(IFileInfo file) at DotNetNuke.Framework.DefaultPage.InitializePage() at DotNetNuke.Framework.DefaultPage.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Source:
FileName:
FileLineNumber:0
FileColumnNumber:0
Method:
Server Name: ^$%#$#$&^$#
This is the first instance of it in logs:
02/09/2021 18:59:26
Page Load Exception
Anonymous Township
AbsoluteURL /Default.aspx DefaultDataProvider DotNetNuke.Data.SqlDataProvi
ExceptionGUID:51a63ab0-4a87-443a-9362-913c8d1040b7
TabId:6724
RawUrl:/Township-Office/Inspection-Permits
Referrer:http://www.anonymous.com/...e/Inspection-Permits
UserAgent:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.150 Safari/537.36
Server Name: *&^(*&^*&)
I honestly dont even know where to start with this one so your advice is welcome. I have close to 25 hours into reskinning, restoring, and resurrecting the site. Just to have it die on me again. Never faced this issue before.
Unfortunately there was nothing in those logs either. Literally the site is working one minute, and then its not the next. Rolling back the database brings the site back up. Some times it's stable for 24-48hrs. Sometimes it's satble for a half hour. Thought it was working well, and then after confirming that the site was functional with the client it died again the moment I hung up the phone. Sadly unless someone here comes up with an answer from these logs we are likely recreating the site in a different environement.
This can have multiple causes. Did you check if the Database was not flooded by errors? Compare the databae size of a restored site and the one that fails.
If there's an issue in the database with a file which causes an error I have seen sites that crashed on the number of errors caused by crawlers that kept asking for that file again and again.
Also, what is the actual 500 error when the site is down? (delete the log file, open the site and look at the last error)
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.