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

Upgrading DotNetNuke Current Assembly Version: 04.08.02 Current Database Version: 04.04.01   Upgrade Status Report 00:00:00.031 - Upgrading to Version: 4.8.2 00:00:00.390 -   Executing Script: 04.05.00.SqlDataProvider Success 00:00:04.328 -   Executing Script: 04.05.01.SqlDataProvider Success 00:00:05.812 -   Executing Script: 04.05.02.SqlDataProvider Success 00:00:07.828 -   Executing Script: 04.05.03.SqlDataProvider Success 00:00:09.031 -   Executing Script: 04.05.04.SqlDataProvider Success 00:00:10.296 -   Executing Script: 04.05.05.SqlDataProvider Success 00:00:11.484 -   Executing Script: 04.06.00.SqlDataProvider Success 00:00:14.062 -   Executing Script: 04.06.01.SqlDataProvider Success 00:00:15.171 -   Executing Script: 04.06.02.SqlDataProvider Success 00:00:16.281 -   Executing Script: 04.07.00.SqlDataProvider Success 00:00:19.468 -   Executing Script: 04.08.00.SqlDataProvider Success 00:00:21.484 -   Executing Script: 04.08.01.SqlDataProvider Success 00:00:22.718 -   Executing Script: 04.08.02.SqlDataProvider Success 00:00:23.859 - Performing General Upgrades 00:01:29.609 - Installing Module File Adsense_01.00.01_Install:   Server Error in '/' Application. 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. 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) +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   Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832

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.