Thank you!
After applaying scripts site works OK .
1) Does your script make the same, that scripts in this post?
http://staging301.dnnsoftware.com/community-blog/cid/135317/preparing-for-an-upgrade
2) I try upgrade 4.4.1 -> 4.6.2 and get strange log. It look like all is OK, but one error message after log:
-------------------------------------------------------------------------------------------
Current Assembly Version: 04.06.02
Current Database Version: 04.04.01
Upgrade Status Report
00:00:00.078 - Upgrading to Version: 4.6.2
00:00:00.140 - Executing Script: 04.05.00.SqlDataProvider Success
00:00:01.825 - Executing Script: 04.05.01.SqlDataProvider Success
00:00:02.168 - Executing Script: 04.05.02.SqlDataProvider Success
00:00:02.464 - Executing Script: 04.05.03.SqlDataProvider Success
00:00:02.496 - Executing Script: 04.05.04.SqlDataProvider Success
00:00:02.527 - Executing Script: 04.05.05.SqlDataProvider Success
00:00:02.527 - Executing Script: 04.06.00.SqlDataProvider Success
00:00:03.135 - Executing Script: 04.06.01.SqlDataProvider Success
00:00:03.135 - Executing Script: 04.06.02.SqlDataProvider Success
00:00:03.135 - Performing General Upgrades
--------------------------------------------------------------------------------
Server Error in '/Optolover' Application.
--------------------------------------------------------------------------------
Data at the root level is invalid. Line 1, position 1.
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.Xml.XmlException: Data at the root level is invalid. Line 1, position 1.
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:
[XmlException: Data at the root level is invalid. Line 1, position 1.]
System.Xml.XmlTextReaderImpl.Throw(Exception e) +95
System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() +5086762
System.Xml.XmlTextReaderImpl.ParseDocumentContent() +298
System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace) +165
System.Xml.XmlDocument.Load(XmlReader reader) +134
System.Xml.XmlDocument.Load(String filename) +95
DotNetNuke.Modules.Admin.ResourceInstaller.ResourceInstaller.InstallPortal(String strFile, Boolean writeFeedback, Int32 indent) +269
DotNetNuke.Modules.Admin.ResourceInstaller.ResourceInstaller.Install(Boolean writeFeedback, Int32 indent, String type) +890
DotNetNuke.Services.Install.Install.UpgradeApplication() +1130
DotNetNuke.Services.Install.Install.Page_Load(Object sender, EventArgs e) +320
System.Web.UI.Control. (EventArgs e) +132
System.Web.UI.Control.LoadRecursive() +66
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2428
--------------------------------------------------------------------------
Site works now on 4.6.2 , but when I try upgrade some module finished with the same message.
Is it critical error?