Correcting Errors - Installing DNN Platform

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

Home All Forums

4/26/2007 4:43 PM

John Kirkman

Joined: 2/4/2003

Posts: 13

Correcting Errors

We have been using DNN for our church site for two years. None of us who are trying to keep the site updated are highly technical, but we have been able to keep the site updated, add new modules, upgrade DNN, etc. Or at least we thought. Two weeks ago I tried to upgrade DNN from 4.4 to 4.5.1 and ran into many, many problems…lost skin, none of the modules would load, and none of the panels would load. We are back to 4.4…I did have a good backup.

Today, for the first time, I looked at the log file and it is full of red error messages. Just this morning there are over 25 errors. The errors include page load exceptions, module load exceptions, scheduler exceptions and general exceptions plus more. The question that I have is where we go from here. None of us have the experience or talent to resolve the errors that appear in the log files. Example, AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Thread was being aborted.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.Threading.ThreadAbortException: Thread was being aborted. at DotNetNuke.Services.Scheduling.DNNScheduling.ProcessGroup.Run(ScheduleHistoryItem objScheduleHistoryItem)
Source:
Server Name: DEDI372
The web site has around 100 pages and receives 30 to 40 hits a day. Would we be better off just dumping the site and starting with a new install of DNN 4.5.1? If so what do I need to do to be sure this does not happen again? Is there another portal software that would be appropriate for our organization?

I apologize for the length of this post, but we really do need some knowledgeable input. Thank you for your insight and guidance.

John Kirkman

4/26/2007 5:51 PM

Sanjay Mehrotra

www.acuitisolutions.com
Joined: 5/30/2003

Posts: 591

Re: Correcting Errors

John - check whether your schedule process has gone rogue. You can check this very simply by going to the schedule page under the host menu and looking at the next start. Refresh the page and see if your next start keeps changing every time you refresh the page.

You can restart IIS and see if your error goes away. If you are in a shared host environment, see if your provider is also cycling your connections very often....

Sanjay

AcuitiDP - Oracle Data Provider for DotNetNuke

4/26/2007 6:54 PM

ROB AX

Joined: 9/3/2004

Posts: 2185

Re: Correcting Errors

I've never been able to fully rid a site of those. Check the times the errors happen.. sometimes you might a dozen in a row but they're all within the same minute. I've increased the time between some of my schedules, such as the search scheduler.. there's no need for me to run it more than once a day.

DNN4.5 and 4.51 and a VPS account have also reduced the overall amount of red in my event logs... and it's also worth learning what some of the errors are.. check the referrign URL if it has one.. that's most often a search spider or someone looking for an expired page. You can also clear out some of the tables.. search the forum for truncate shedulehistory. I've learned to live with a certain level of errors and only get fussed if it changed from that.

Not sure what happened with your upgrade, but it will work.. so maybe try again. Take extra care with what's in your web.config and also set permissions on your site folders beforehand. It's my feeling that a lot of errors creep in because permissions get reset. Iv'e not had a broken upgrade since I've been strict about re-doing permissions beforehand.

Rob

4/26/2007 10:02 PM

John Kirkman

Joined: 2/4/2003

Posts: 13

Re: Correcting Errors

Thanks for the responses. I am really not too concerned with the error logs unless they are indicating a problem that is causing the upgrade to fail. I am really looking at anything that would cause the upgrade to fail.

I tried the upgrade last week which failed then used my backup I went back to DNN 4.4. Retried the upgrade this week and it also failed. This is third attempt to upgrade the site. I know it must be me, but I am running out of ideas.

Here is a copy of the install message:

Upgrading DotNetNuke

Current Assembly Version: 04.05.01

Current Database Version: 04.04.00

Upgrade Status Report

00:00:00.080 - Upgrading to Version: 4.5.1

00:00:00.180 - Executing Script: 04.04.01.SqlDataProvider Success

00:00:00.791 - Executing Script: 04.05.00.SqlDataProvider Error! (see 04.05.00.log for more information)

00:00:03.264 - Executing Script: 04.05.01.SqlDataProvider Success

00:00:04.015 - Performing General Upgrades

Upgrade Complete

Then when I go to the site, I have lost my skins. All of the modules do not have any content and are showing error messages about not being able to load. I can log on as Host or Administrator and then I get to see lots and lots of red error messages.

We would appreciate any input or places to look for errors.

Thanks for any help.

John

4/26/2007 10:49 PM

Chris Hammond

www.christoc.com
Joined: 1/14/2003

Posts: 7319

Re: Correcting Errors

Have you checked this file 04.05.00.log for errors as the line that states there is an error tells you to? Should be in providers, dataprovider, sqldataprovider folder I believe.

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions

Page 1 of 2

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
No Flaming or Trolling.
No Profanity, Racism, or Prejudice.
Site Moderators have the final word on approving / removing a thread or post or comment.
English language posting only, please.

Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

DNN Corp. (DotNetNuke)