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 ... Error: Thread was being aborted.!!!! URGENT Error: Thread was being aborted.!!!! URGENT
Previous
 
Next
New Post
10/24/2008 3:11 AM
 

Hi I am getting this below error. Please let me know the exact steps  how to get rid from this error.

By badly need a quick solution as my website is sleeping due to this .

Thanks a lot to all in advance.

 

 

Installing DotNetNuke

Version: 04.09.00

 

Installation Status Report

00:00:00.093 - Installing Version: 4.4.0

 

00:00:00.093 -   Executing Script: DotNetNuke.SetUp.SqlDataProvider 

Success

00:00:00.468 -   Executing Script: DotNetNuke.Schema.SqlDataProvider 

Success

00:02:10.093 -   Executing Script: DotNetNuke.Data.SqlDataProvider 

Success

00:02:12.203 - Installing MemberRole Provider:

 

00:02:12.203 -   Executing Script: InstallCommon

 

00:02:15.015 -   Executing Script: InstallMembership

 

00:02:17.875 -   Executing Script: InstallProfile

 

00:02:19.453 -   Executing Script: InstallRoles

 

00:02:21.609 - Upgrading to Version: 4.9.0

 

00:02:21.734 -   Executing Script: 04.04.01.SqlDataProvider 

Success

00:02:22.703 -   Executing Script: 04.05.00.SqlDataProvider 

Success

00:02:32.515 -   Executing Script: 04.05.01.SqlDataProvider 

Success

00:02:33.203 -   Executing Script: 04.05.02.SqlDataProvider 

Success

00: -   Executing Script: 04.05.03.SqlDataProvider 

Success

00:02:36.078 -   Executing Script: 04.05.04.SqlDataProvider 

Success

00:02:36.859 -   Executing Script: 04.05.05.SqlDataProvider 

Success

00:02:37.203 -   Executing Script: 04.06.00.SqlDataProvider 

Success

00:02:44.968 -   Executing Script: 04.06.01.SqlDataProvider 

Success

00:02:45.171 -   Executing Script: 04.06.02.SqlDataProvider 

Success

00:02:45.359 -   Executing Script: 04.07.00.SqlDataProvider 

Success

00:02:47.078 -   Executing Script: 04.08.00.SqlDataProvider 

Success

00:02:48.359 -   Executing Script: 04.08.01.SqlDataProvider 

Success

00:02:49.625 -   Executing Script: 04.08.02.SqlDataProvider 

Success

00:02:49.890 -   Executing Script: 04.08.03.SqlDataProvider 

Success

00:02:50.078 -   Executing Script: 04.08.04.SqlDataProvider 

Success

00:02:50.265 -   Executing Script: 04.09.00.SqlDataProvider 

Success

00:02:50.828 - Performing General Upgrades

 

00:02:57.031 - Loading Host Settings:

 

00:03:03.375 - Configuring SuperUser:

 

00:03:05.375 - Synchronizing Host Files:

 

00:03:12.281 - Installing Modules:

 

00:03:12.296 -   Installing Module File HTML_04.08.01_Install:  

Success

00:03:15.812 -   Installing Module File Links_04.00.01_Install:  

Success

00:03:19.593 - Executing Additional Scripts:

 

00:03:19.609 -   Creating Portal: My Website

 

00:04:46.046 -   

Error: Thread was being aborted.

 


Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

 
New Post
10/24/2008 3:44 AM
 

there happened a timeout, when creating default web site, though I don't see the reason for it. I prefer to use custom install.

Please delete and recreate your datebase, reunzip files, check file system permissions and restart installation.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/24/2008 6:07 AM
 

Thanks a Lot !!! Sebstain Leuplod for the quick response.

I did. but the problem stll happens. Now I changed the customError mode from RemoteOnly to Off.

I found the bellow error.

 

CAn you please solve this problem. Or is there any easy steps to install DNN.

Thanks,

Jajati

 

00:03:36.187 -   Creating Portal: My Website
00:05:16.625 -   Error: Thread was being aborted.

 


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


Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433
 
New Post
10/24/2008 6:46 AM
 

unfortunately the error message does not point to details of the issue. Please make sure, that the database use a case insensitive collation, this is the only idea I have atm.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/27/2008 2:17 AM
 

I hosted DNN in my local system and Sql database was in the hosted server. There was no problem it worked fine. But while installing DNN in the hosted server I am getting the error.

Please let me know where is the exact issue?

Thanks,

Jajati

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ... Error: Thread was being aborted.!!!! URGENT Error: Thread was being aborted.!!!! URGENT


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