Hello all,

Over the past few days, I've been bringing a 3.2.2 up to date to version 4.8.2. My setup:

• Windows Server 2003 Standard PS1
• SQL Server 2005 Enterprise
• ASP.NET 2.0

I've upgraded using the following DNN versions:

• 3.2.2 (Initial version)
• 3.7.7
• 4.4.1
• 4.8.2
• Upgrading using Install.zip packages (I've also tried using the Upgrade.zip file, which rendered the same result)

Upgrades ran surprisingly smooth up to 4.4.1 to 4.8.2 where I get the following error:

[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

I've read several posts about this error, mainly curly brakets issue fixed in 4.4.0, none of which seem to apply to my setup.

A few notes:

• The error does not always occure at the same place. Above the error occured at Installing Module File Adsense_01.00.01_Install but it doesn't always occure at that step, but always after Performing General Upgrades which seem to take an awful long time to complete (> 1min.).
• The w3wp.exe is taking up a lot of CPU time.

Any insight about this issue will be greatly appreciated

Thanks Drew, I'll give it a show.

Noticed that having the EnableCachePersistence="True" puts a significant load on the CPU. I managed to successfully complete my installation after setting this value to false.

Ah, this is helping me. with my DNN install. Changing to this:

<httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="18192" requestLengthDiskThreshold="18192" shutdownTimeout="900" />

GREATLY, helped prevent errors on install and install resources. OUr DNN has 150 child portals and many thousands of pages. The upgrades have been fialing and failing due to what I think are timeout issues. The line change above in web.config HELPED. Just fyi to everyone searching. I've spent two weeks trying to get an upgrade to take and this finally seems to have done the trick. My god why isn't there a better DNN upgrade help/faq type of document that would tell us these things to try?