Hello DNN pros,

I've semi-successfully upgraded a live DNN 3.2.2 site to 4.8.2. I've upgraded via the following versions:

3.2.2 --> 3.3.7 --> 4.4.1(.NET 2) --> 4.8.2(always using the Install.zip files)

The reason I say "semi-successfully" is because I've notive considerable performance issues in version 4.8.2 (I've also tried 4.6.2 and 4.7.0 with the same results).

The first indication is during the installation phase. I noticed the upgrade from 4.4.1 to 4.8.2 (as well as 4.6.2 and 4.7.0) takes very long, particularly (but not exclusively) at the "Performing General Upgrades" phase, at which point I would get a "Thread was aborted" error after ~2.25 minutes into the process. (see trace below).

I ran the 4.8.2 install as-is several times, and kept getting the same error. Sometimes it would get past the "Performing General Upgrades" and crash on the "Intalling Module xyz" phase.

My database and web server are running on different machines which I have unrestricted access to. I monitored the CPU and RAM usage during the installation:

1. The DB machine's CPU usage seems normal during the execution of the *.SqlDataProvider scripts.
2. At the "Performoing General Upgrades" phase, the WebServer CPU hits 100% and stays there until the process crashes.\
3. RAM usage is always constant at a safe level.

I then renamed all the *Install.zip files in the Install/Module folder to *.resources so they would not be installed during the upgrade. I finally managed to complete the upgrade in ~ 2.2 minutes.

The second observation is that after I've successfully upgraded my app, every page request sends the Web server's CPU usage through the roof. I have all DNN versions (3.2.2, 3.3.7, 4.4.1, 4.6.2, 4.7.0, and 4.8.2) running side by side (I created a different App Pool for .NET2 apps), but I only notice this behaviour in 4.6.2+.

Does anyone esle experience similar issues? Has anyone found a solution?

Many thanks

 [ThreadAbortException: Thread was being aborted.]

   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +495

   System.Web.ApplicationStepManager.ResumeSteps(Exception error) +590

   System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) +140

   System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +426

Rad,

I have helped many people through these types of issues on their sites, it is a main service of my support offerings.

There are many potential causes for this type of error, including module errors, scheduler errros, event queue errors, and more.  If you would like drop me an e-mail and we might be able to talk specifics, as truly resolving this via the forums is almost impossible.