I've recently upgraded a site to 4.0.3, when my ISP decided to shut the site down due to it overloading the CPU. I have it on a dedicated server now for testing. I deleted all DLL's except for just the default DNN DLL's and I still get very high CPU usage, and many times this error shows up (see below). I also upgraded sql 2000 to sql 2005 express. Same problem, and now I can't use the profiler. Any ideas how to troubleshoot this?

-------------------------------------
Thread was being aborted.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Threading.ThreadAbortException: Thread was being aborted.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[ThreadAbortException: Thread was being aborted.]
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +483
System.Web.HttpApplication.ResumeSteps(Exception error) +539
System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) +144
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +300


Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

---

Jason Honingford - Web & Software Developer
www.PortVista.com

Update: I looked at the profiler, and on each page load, 1000's of stored procedures are running, like: updatefolder, getfolders, getfolderpermissions, etc. It seems like the file synch is running, but I turned off all schedules. I believe this is the problem!

Does anyone know why this happens? It seems to want to run the file synch on each load! How do I stop this??



exec dbo.UpdateScheduleHistory @ScheduleHistoryID = 2, @EndDate = 'Jul 17 2006 9:18:38:890PM', @Succeeded = 1, @LogNotes = N'File System Synchronized.
', @NextStart = 'Dec 9 2005 12:36:08:620PM'

Where is it getting this Dec 9, 2005? This has got to be why this DNN install is slow!! lol! Help!

---

Jason Honingford - Web & Software Developer
www.PortVista.com

Hey PortVista,
Try truncating your schedulehistory table.  We've found that sites with a lot of entries in this table have dead slow speed.

---

Tony Valenti
Tony.Valenti@PowerDNN.com
+001-402-650-6072

PowerDNN.com - World Leader in DotNetNuke Hosting and DNN Hosting
DNN Hosting Australia - DNN Hosting Europe - DNN Hosting US