Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade 4.7 to 4.9 Thread was being abortedUpgrade 4.7 to 4.9 Thread was being aborted
Previous
 
Next
New Post
2/10/2009 4:37 PM
 

Hello Everyone,
I have tried to upgrade my DNN 4.7 to 4.9 using the merge method I am having some issues. I have my production server, test server, and a local copy. This is the way I have my setup.

Local machine, WinXP, MSSQL 2005, copy of my production DNN site at 4.7.

Test server, ASP.NET 2.0, Window 2003, MSSQL 2005, copy of production DNN site at 4.7.

Production Server .NET 2.0, Window 2003, copy of production DNN site at 4.7 (MSSQL is located on another server)

OK here is the issue when I upgrade on the Local machine everything goes as planned no errors or thread issues. But when I go to the Test server I get the Thread was being aborted issue. I am not sure how to correct this and I don’t feel confident moving forward with the upgrade on production. I have done some reading but I have not found a solution that has worked. I have tried the following.

1.       Checked permissions

2.  Change the webconfig settings <httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="10240" requestLengthDiskThreshold="10240" executionTimeout="1200" />

3.       Restarted the web services.

4.       Started from scratch. I have looked all over the place but can not find a solution. Below is what I get any ideas?

B

Upgrading DotNetNuke

Current Assembly Version: 04.09.01

Current Database Version: 04.07.00

 

Upgrade Status Report

00:00:00.015 - Upgrading to Version: 4.9.1
00:00:00.281 -   Executing Script: 04.08.00.SqlDataProvider 
Success
00:00:02.859 -   Executing Script: 04.08.01.SqlDataProvider 
Success
00:00:03.062 -   Executing Script: 04.08.02.SqlDataProvider 
Success
00:00:03.078 -   Executing Script: 04.08.03.SqlDataProvider 
Success
00:00:03.078 -   Executing Script: 04.08.04.SqlDataProvider 
Success
00:00:03.078 -   Executing Script: 04.09.00.SqlDataProvider 
Success
00:00:03.499 -   Executing Script: 04.09.01.SqlDataProvider 
Success
00:00:03.671 - Performing General Upgrades

 


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.


Stack Trace:

 

[ThreadAbortException: Thread was being aborted.]

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

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

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

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

 

 
New Post
2/10/2009 5:46 PM
 

Just a quick note after I get the error I go to the home page and login and I check the DNN version and it is listed as 4.09. I wonder is there is a way to find out what did not get upgraded.

 
New Post
1/26/2010 6:00 PM
 

Can anyone help or has had this issue. I have tried to upgrade to 4.9.5 and I still have the same problem.

 
New Post
1/27/2010 5:08 AM
 

I suggest to streamline the database first, usually the timeout is caused by lengthly running queries.

truncate tables eventlog, sitelog and schedulehistory and clear the search tables. make sure, database transaction log has been truncated on backup as well.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/3/2010 12:53 PM
 

Hello Sebastian
After intense testing truncated all the tables suggested to get a leaner DB I even shrunk the DB which broght the size way smaller. I am still getting the same results, But I did notice that when upgrading from 4.7 to 4.8.00 upgraded fine and then to 4.8.01 upgraded fine but when I upgrade from 4.8.01 to 4.8.02 or above this version I get the error.  I have tried it with the manual method and the merge method same thing. Any other ideas?

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade 4.7 to 4.9 Thread was being abortedUpgrade 4.7 to 4.9 Thread was being aborted


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:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. 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.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out