I've done this upgrade a dozen times with very little problems, but this time is different. When I run install.aspx I get an error that the file <portal>\Install\Module\Links_3.3_Install.zip is not found. I've checked, and when the update starts that file IS there! Even stranger is that, according to the log, the file Links_04.00.01_Install is installed FIRST (and successfully) and then it tries to install Links_3.3_Install! I've tried everything I can think of, including:
- Reinstall the Links module prior to upgrading
- Delete and reinstall the Links module prior to upgrading
- Unzip a complete copy of the 3.3.7 install into the site folder
Nothing I've tried works. Why is DNN trying to install Links_3.3_Install AFTER it installs Links_04.00.04_Install and why does it delete the file and then complain that it can't find it?
Install log (don't even mention the SqlDataProvider error, I get that every time I do the upgrade and it doesn't seem to matter):
Upgrading DotNetNuke
Current Assembly Version: 04.09.05
Current Database Version: 03.03.07
Upgrade Status Report
00:00:00.015 - Upgrading to Version: 4.9.5
00:00:00.093 - Executing Script: 04.00.00.SqlDataProvider Success
00:00:00.515 - Executing Script: 04.00.01.SqlDataProvider Success
00:00:00.640 - Executing Script: 04.00.02.SqlDataProvider Success
00:00:00.687 - Executing Script: 04.00.03.SqlDataProvider Success
00:00:00.718 - Executing Script: 04.00.04.SqlDataProvider Success
00:00:02.921 - Executing Script: 04.00.05.SqlDataProvider Success
00:00:02.937 - Executing Script: 04.00.06.SqlDataProvider Success
00:00:02.953 - Executing Script: 04.00.07.SqlDataProvider Success
00:00:02.968 - Executing Script: 04.03.00.SqlDataProvider Success
00:00:03.015 - Executing Script: 04.03.01.SqlDataProvider Success
00:00:03.062 - Executing Script: 04.03.02.SqlDataProvider Success
00:00:03.156 - Executing Script: 04.03.03.SqlDataProvider Success
00:00:03.515 - Executing Script: 04.03.04.SqlDataProvider Success
00:00:03.546 - Executing Script: 04.03.05.SqlDataProvider Success
00:00:03.781 - Executing Script: 04.03.06.SqlDataProvider Success
00:00:04.156 - Executing Script: 04.03.07.SqlDataProvider Success
00:00:04.265 - Executing Script: 04.04.00.SqlDataProvider Error! (see 04.04.00.log for more information)
00:00:05.031 - Executing Script: 04.04.01.SqlDataProvider Success
00:00:05.281 - Executing Script: 04.05.00.SqlDataProvider Success
00:00:06.843 - Executing Script: 04.05.01.SqlDataProvider Success
00:00:07.015 - Executing Script: 04.05.02.SqlDataProvider Success
00:00:07.656 - Executing Script: 04.05.03.SqlDataProvider Success
00:00:07.812 - Executing Script: 04.05.04.SqlDataProvider Success
00:00:07.906 - Executing Script: 04.05.05.SqlDataProvider Success
00:00:07.937 - Executing Script: 04.06.00.SqlDataProvider Success
00:00:09.125 - Executing Script: 04.06.01.SqlDataProvider Success
00:00:09.140 - Executing Script: 04.06.02.SqlDataProvider Success
00:00:09.156 - Executing Script: 04.07.00.SqlDataProvider Success
00:00:09.718 - Executing Script: 04.08.00.SqlDataProvider Success
00:00:10.187 - Executing Script: 04.08.01.SqlDataProvider Success
00:00:10.328 - Executing Script: 04.08.02.SqlDataProvider Success
00:00:10.390 - Executing Script: 04.08.03.SqlDataProvider Success
00:00:10.406 - Executing Script: 04.08.04.SqlDataProvider Success
00:00:10.406 - Executing Script: 04.09.00.SqlDataProvider Success
00:00:10.500 - Executing Script: 04.09.01.SqlDataProvider Success
00:00:10.640 - Executing Script: 04.09.02.SqlDataProvider Success
00:00:10.921 - Executing Script: 04.09.03.SqlDataProvider Success
00:00:10.984 - Executing Script: 04.09.04.SqlDataProvider Success
00: - Executing Script: 04.09.05.SqlDataProvider Success
00: - Performing General Upgrades
00:00:12.250 - Installing Module File Announcements_03.03.05_Install: Success
00:00:12.859 - Installing Module File Blog_3.02.00_Install: Success
00:00:12.968 - Installing Module File Contacts_3.1_Install: Success
00:00:13.390 - Installing Module File Documents_03.01.05_Install: Success
00:00:13.515 - Installing Module File Events_3.2_Install: Success
00:00:13.656 - Installing Module File FAQs_3.1_Install: Success
00:00:13.968 - Installing Module File Feedback_03.02.01_Install: Success
00:00:14.468 - Installing Module File Forum_3.20.08_Install: Success
00:00:20.500 - Installing Module File Gallery_3.0.12_Install: Success
00:00:33.031 - Installing Module File Help_2.0.4_Install: Success
00:00:33.109 - Installing Module File HTML_04.09.05_Install: Success
00:00:35.656 - Installing Module File HTML_3.3.0_Install: Success
00:00:35.734 - Installing Module File IFrame_3.2_Install: Success
00:00:35.812 - Installing Module File Links_04.00.01_Install: Success
00:00:37.500 - Installing Module File Links_3.3_Install:
--------------------------------------------------------------------------------
Server Error in '/' Application.
--------------------------------------------------------------------------------
Could not find file 'd:\3lqhwsxez6urrw\cust\DNNLawnBeautician\Install\Module\Links_3.3_Install.zip'.
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.IO.FileNotFoundException: Could not find file 'd:\3lqhwsxez6urrw\cust\DNNLawnBeautician\Install\Module\Links_3.3_Install.zip'.
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:
[FileNotFoundException: Could not find file 'd:\3lqhwsxez6urrw\cust\DNNLawnBeautician\Install\Module\Links_3.3_Install.zip'.]
System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +305
System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy) +1162
System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access) +67
DotNetNuke.Modules.Admin.ResourceInstaller.PaInstaller..ctor(String Path, String SitePath) +90
DotNetNuke.Modules.Admin.ResourceInstaller.ResourceInstaller.InstallModule(String strFile, Boolean allowResources, Boolean writeFeedback, Int32 indent) +255
DotNetNuke.Modules.Admin.ResourceInstaller.ResourceInstaller.Install(Boolean writeFeedback, Int32 indent, String type) +475
DotNetNuke.Modules.Admin.ResourceInstaller.ResourceInstaller.Install(Boolean writeFeedback, Int32 indent) +17
DotNetNuke.Services.Install.Install.UpgradeApplication() +886
DotNetNuke.Services.Install.Install.Page_Load(Object sender, EventArgs e) +272
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +50
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3082