I too have been getting this error
2 Tiered System
Web server on 1 end, Database on the other, connection through Private IP TCP/IP
I am hosted with "the planet" (Server 2008 RC 2 [IIS 7.5]) and we have been going over the TCP/IP connection to SQL for days to no Avail, all the scanners report that SQL 2008 is there, you can ping, telnet, connect via 1433, dynamic (4915x) and so on...
But the DNN installer fails every time, I uploaded it to a GoDaddy Account and it worked, very slowly but it works.
So as another mentioned I have tried AUTO and here is what I get:
Current Assembly Version: 05.01.04
Current Database Version: 05.00.00
Upgrade Status Report
00:00:00.015 - Upgrading to Version: 05.01.04
00:00:21.060 - Executing Script: 05.00.01.SqlDataProvider
Success
00:00:21.434 - Executing Script: 05.01.00.SqlDataProvider
Success
00:00:22.744 - Executing Script: 05.01.01.SqlDataProvider
Success
00:00:22.978 - Executing Script: 05.01.02.SqlDataProvider
Success
00:00:22.994 - Executing Script: 05.01.03.SqlDataProvider
Success
00:00:23.041 - Executing Script: 05.01.04.SqlDataProvider
Success
00:00:23.103 - Executing Application Upgrades: 05.00.01
Error!
00:00:23.119 - Executing Application Upgrades: 05.01.00
Error!
00:00:23.150 - Executing Application Upgrades: 05.01.01
Error!
00:00:23.150 - Executing Application Upgrades: 05.01.02
Success
00:00:23.150 - Executing Application Upgrades: 05.01.03
Error!
00:00:23.166 - Executing Application Upgrades: 05.01.04
Success
00:00:23.166 - Cleaning Up Files: 05.00.01
Success
00:00:23.166 - Cleaning Up Files: 05.01.00
Success
00:00:23.166 - Cleaning Up Files: 05.01.01
Success
00:00:23.166 - Cleaning Up Files: 05.01.02
Success
00:00:23.166 - Cleaning Up Files: 05.01.03
Success
00:00:23.166 - Cleaning Up Files: 05.01.04
Success
00:00:23.166 - Updating Config Files: 05.00.01
Success
00:00:23.166 - Updating Config Files: 05.01.00
Success
00:00:23.197 - Updating Config Files: 05.01.01
Success
00:00:23.197 - Updating Config Files: 05.01.02
Success
00:00:23.197 - Updating Config Files: 05.01.03
Success
00:00:23.197 - Updating Config Files: 05.01.04
Success
00:00:23.197 - Performing General Upgrades
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>
|
It doesn't matter if I use DNN 5.1 or 5.2, same errors same issues.