I'm installing DNN 5.2.3 on IIS 6 windows server 2003. It has the latest .Net 3.5 sp1. I've already checked permissions on the app pool user doens't seem to be the problem. More importantly doing a "TYPICAL" install it will install fine. However, I have a script that will set up the web.config and DotNetNuke.install.config with values to create DNN sites quickly. When doing the Typical install this works, however when doing the AUTO install it fails in the same place every time. Below is the output from the install screen.

It takes a good while to get to the error, could it just be that something is timing out. I checked Database and everything seems fine. I don't know what its actually doing when it says "Installing Pacakge FckHtmlEditorProvider_02.00.04_Install", but it errors every time at that point.

Thanks for any help in advance.

Andres

Installing DotNetNuke

Version: 05.02.03

Installation Status Report

00:00:00.015 - Installing Version: 05.00.00

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

00:00:26.969 -   Executing Script: DotNetNuke.Data.SqlDataProvider 

00:00:35.594 - Installing MemberRole Provider:

00:00:35.594 -   Executing Script: InstallCommon

00:00:43.970 -   Executing Script: InstallMembership

00:00:52.626 -   Executing Script: InstallProfile

00:00:58.251 -   Executing Script: InstallRoles

00:01:06.220 - Upgrading to Version: 05.02.03

00:01:06.392 -   Executing Script: 05.00.01.SqlDataProvider 

00:01:15.768 -   Executing Script: 05.01.00.SqlDataProvider 

00:01:27.971 -   Executing Script: 05.01.01.SqlDataProvider 

00:01:34.596 -   Executing Script: 05.01.02.SqlDataProvider 

00:01:41.393 -   Executing Script: 05.01.03.SqlDataProvider 

00:01:50.675 -   Executing Script: 05.01.04.SqlDataProvider 

00:01:57.113 -   Executing Script: 05.02.00.SqlDataProvider 

00:02:10.754 -   Executing Script: 05.02.01.SqlDataProvider 

00:02:18.613 -   Executing Script: 05.02.02.SqlDataProvider 

00:02:26.004 -   Executing Script: 05.02.03.SqlDataProvider 

00:02:34.458 -   Executing Application Upgrades: 05.00.01 

00:02:34.739 -   Executing Application Upgrades: 05.01.00 

00:02:39.005 -   Executing Application Upgrades: 05.01.01 

00:02:39.005 -   Executing Application Upgrades: 05.01.02 

00:02:39.005 -   Executing Application Upgrades: 05.01.03 

00:02:39.833 -   Executing Application Upgrades: 05.01.04 

00:02:39.833 -   Executing Application Upgrades: 05.02.00 

00:02:40.067 -   Executing Application Upgrades: 05.02.01 

00:02:40.083 -   Executing Application Upgrades: 05.02.02 

00:02:40.083 -   Executing Application Upgrades: 05.02.03 

00:02:40.083 -   Cleaning Up Files: 05.00.01 

00:02:40.083 -   Cleaning Up Files: 05.01.00 

00:02:40.083 -   Cleaning Up Files: 05.01.01 

00:02:40.083 -   Cleaning Up Files: 05.01.02 

00:02:40.083 -   Cleaning Up Files: 05.01.03 

00:02:40.083 -   Cleaning Up Files: 05.01.04 

00:02:40.083 -   Cleaning Up Files: 05.02.00 

00:02:40.083 -   Cleaning Up Files: 05.02.01 

00:02:40.083 -   Cleaning Up Files: 05.02.02 

00:02:40.083 -   Cleaning Up Files: 05.02.03 

00:02:40.083 -   Updating Config Files: 05.00.01 

00:02:40.083 -   Updating Config Files: 05.01.00 

00:02:40.114 -   Updating Config Files: 05.01.01 

00:02:40.114 -   Updating Config Files: 05.01.02 

00:02:40.114 -   Updating Config Files: 05.01.03 

00:02:40.114 -   Updating Config Files: 05.01.04 

00:02:40.114 -   Updating Config Files: 05.02.00 

00:02:40.114 -   Updating Config Files: 05.02.01 

00:02:40.130 -   Updating Config Files: 05.02.02 

00:02:40.130 -   Updating Config Files: 05.02.03 

00:02:40.130 - Performing General Upgrades

00:02:40.270 - Loading Host Settings:

00:02:41.333 - Configuring SuperUser:

00:02:42.395 - Synchronizing Host Files:

00:02:43.286 - Executing Additional Scripts:

00:02:43.286 - Installing Optional Modules:

00:02:43.286 -   Installing Package File HTML_Community_05.02.00_Install:  

00:04:34.727 - Installing Optional Skins:

00:04:34.727 -   Installing Package File DNN-MinimalExtropySkin_01.00.05_Install:  

00:04:37.336 - Installing Optional Containers:

00:04:37.336 -   Installing Package File DNN-MinimalExtropyContainer_01.00.05_Install:  

00:04:38.024 - Installing Optional Languages:

00:04:38.024 - Installing Optional Providers:

00:04:38.024 -   Installing Package File AspNetMembershipProvider_05.02.00_Install:  

00:04:38.415 -   Installing Package File CorePermissionProvider_05.01.01_Install:  

00:04:38.602 -   Installing Package File DatabaseLoggingProvider_05.01.01_Install:  

00:04:38.790 -   Installing Package File DNNMembershipProvider_05.01.03_Install:  

00:04:38.977 -   Installing Package File DNNMenuNavigationProvider_05.01.00_Install:  

00:04:39.118 -   Installing Package File DNNTreeNavigationProvider_05.01.00_Install:  

00:04:39.290 -   Installing Package File FckHtmlEditorProvider_02.00.04_Install:

Server Error in '/dnntest3' Application.

---

Thread was being aborted.

[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

1. When you get the failure do you have any tables built in SQL? I'm specfically looking for dbo.EventLog entries.

2. Recycle the AppPool as you are about to kick of an installation. This should kill all the worker processes so you start with a clean slate.

3. You should also consider running SQL Profiler against the installation. If you're using SQL Server SQL Profiler is included. If you are using SQL Express SQL Profiler is not included but there is an Open Source alternative here: http://sqlprofiler.googlepages.com/

By profiling I would expect you would catch exactly what is going wrong when the HTTP request fails and throws the YSOD you originally posted.

If this is a clean install then recycling should work.

If you're upgrading then it could very well be an issue with the HTML editor upgrade and the eventlog data would be most helpful