OK I copied your exampled of manually removing the DB version 6.1.3 from the version table using SQL Svr Manager Studio, then I reset permissions on file properties as I understand they get reset when attach/detaching

I then loaded the link:

as specified in your last respone. I now get the following error

Upgrading DotNetNuke
Current Assembly Version: 06.01.03
Current Database Version: 06.01.02


Upgrade Status Report
00:00:00.093 - Upgrading to Version: 06.01.03
00:00:00.687 - Executing Script: 06.01.03.SqlDataProvider Success
00:00:01.359 - Executing Application Upgrades: 06.01.03 Success
00:00:01.796 - Cleaning Up Files: 06.01.03 Success
00:00:01.796 - Updating Config Files: 06.01.03 Success
00:00:01.796 - Performing General Upgrades


Server Error in '/' Application.
Access to the path 'C:\inetpub\wwwroot\PassionateAboutIT\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:\inetpub\wwwroot\PassionateAboutIT\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 and IIS 7, and the configured application pool identity on IIS 7.5) that is used if the application is not impersonating. If the application is impersonating via , 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:







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:\inetpub\wwwroot\PassionateAboutIT\Install\Cleanup\03.00.08.txt' is denied.]
System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +9717694
System.IO.File.Delete(String path) +9555620
DotNetNuke.Common.Utilities.FileSystemUtils.DeleteFile(String fileName) +43
DotNetNuke.Services.Upgrade.Upgrade.UpgradeApplication() +311
DotNetNuke.Services.Upgrade.Upgrade.UpgradeDNN(String providerPath, Version dataBaseVersion) +724
DotNetNuke.Services.Install.Install.UpgradeApplication() +905
DotNetNuke.Services.Install.Install.OnLoad(EventArgs e) +375
System.Web.UI.Control.LoadRecursive() +74
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2207


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.27

Yeah - on mine too it's called that - it had read write access - changed it to full access and going through the motions once more