Hello,
When I try to upgrade from 05.03.01 to 05.04.04 I got this error, do you have any idea why ?? I need to upgrade to the newer version of DNN and I try to follow the right upgrade path.
Tanks :)
This is the error I got :
Upgrading DotNetNuke
Current Assembly Version: 05.04.04
Current Database Version: 05.03.01
Upgrade Status Report
00:00:00.078 - Upgrading to Version: 05.04.04
00:00:00.327 - Executing Script: 05.04.00.SqlDataProvider Success
00:00:01.731 - Executing Script: 05.04.01.SqlDataProvider Success
00:00:01.778 - Executing Script: 05.04.02.SqlDataProvider Success
00:00:01.903 - Executing Script: 05.04.03.SqlDataProvider Success
00:00:01.981 - Executing Script: 05.04.04.SqlDataProvider Success
00:00:02.012 - Executing Application Upgrades: 05.04.00 Success
00:00:03.525 - Executing Application Upgrades: 05.04.01 Success
00:00:03.525 - Executing Application Upgrades: 05.04.02 Success
00:00:03.525 - Executing Application Upgrades: 05.04.03 Error!
00:00:03.603 - Executing Application Upgrades: 05.04.04 Success
00:00:03.603 - Cleaning Up Files: 05.04.00 Success
00:00:03.603 - Cleaning Up Files: 05.04.01 Success
00:00:03.603 - Cleaning Up Files: 05.04.02 Success
00:00:03.603 - Cleaning Up Files: 05.04.03 Success
00:00:03.603 - Cleaning Up Files: 05.04.04 Success
00:00:03.603 - Updating Config Files: 05.04.00 Success
00:00:03.603 - Updating Config Files: 05.04.01 Success
00:00:03.603 - Updating Config Files: 05.04.02 Success
00:00:03.603 - Updating Config Files: 05.04.03 Success
00:00:03.603 - Updating Config Files: 05.04.04 Success
00:00:03.603 - Performing General Upgrades
body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon } pre {font-family:"Lucida Console";font-size: .9em} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }
Server Error in '/' Application.
Access to the path 'C:\dnn\Install\Cleanup\03.00.08.txt' is denied.
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.UnauthorizedAccessException: Access to the path 'C:\dnn\Install\Cleanup\03.00.08.txt' is denied.
ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.
To grant ASP.NET access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
|
Stack Trace:
[UnauthorizedAccessException: Access to the path 'C:\dnn\Install\Cleanup\03.00.08.txt' is denied.] System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +10546755 System.IO.File.SetAttributes(String path, FileAttributes fileAttributes) +190 DotNetNuke.Services.Upgrade.Upgrade.UpgradeApplication() +3821 DotNetNuke.Services.Upgrade.Upgrade.UpgradeDNN(String strProviderPath, Version dataBaseVersion) +1060 DotNetNuke.Services.Install.Install.UpgradeApplication() +1208 DotNetNuke.Services.Install.Install.Page_Load(Object sender, EventArgs e) +335 System.Web.UI.Control.OnLoad(EventArgs e) +132 System.Web.UI.Control.LoadRecursive() +66 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2428
|
Version Information:
Microsoft .NET Framework Version:2.0.50727.4961; ASP.NET Version:2.0.50727.4955