|
|
|
|
Joined: 9/21/2010
Posts: 34
|
|
|
When I upgraded to 5.6 the HTML Module did not install and will not install manually. I am recieving this error:
Package Installation Report
See below for the results of the package installation
|
Error loading files from temporary folder - see below
|
StartJob
|
Starting Installation
|
Info
|
Starting Installation - DNN_HTML
|
Info
|
Starting Installation - Script
|
Info
|
Begin Sql execution
|
Info
|
Creating backup of previous version - Providers\DataProviders\SqlDataProvider\03.00.00.SqlDataProvider
|
Info
|
Created - Providers\DataProviders\SqlDataProvider\03.00.00.SqlDataProvider
|
Info
|
Executing 03.00.00.SqlDataProvider
|
Info
|
Start Sql execution: 03.00.00.SqlDataProvider file
|
Failure
|
SQL Execution resulted in following Exceptions: System.Data.SqlClient.SqlException: Invalid column name 'DesktopHtml'. Invalid column name 'DesktopSummary'. Invalid column name 'CreatedByUser'. Invalid column name 'CreatedDate'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL) at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) /** Create Stored Procedures **/ create procedure dbo.AddHtmlText @ModuleId int, @DesktopHtml ntext, @DesktopSummary ntext, @UserID int as insert into HtmlText ( ModuleId, DesktopHtml, DesktopSummary, CreatedByUser, CreatedDate ) values ( @ModuleId, @DesktopHtml, @DesktopSummary, @UserID, getdate() ) System.Data.SqlClient.SqlException: Invalid column name 'DesktopHtml'. Invalid column name 'DesktopSummary'. Invalid column name 'CreatedByUser'. Invalid column name 'CreatedDate'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL) at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) create procedure dbo.UpdateHtmlText @ModuleId int, @DesktopHtml ntext, @DesktopSummary ntext, @UserID int as update HtmlText set DesktopHtml = @DesktopHtml, DesktopSummary = @DesktopSummary, CreatedByUser = @UserID, CreatedDate = getdate() where ModuleId = @ModuleId
|
Info
|
End Sql execution: 03.00.00.SqlDataProvider file
|
Info
|
Finished Sql execution
|
Failure
|
Installation Failed - Script
|
Info
|
Installation Failed - DNN_HTML
|
Info
|
Deleted temporary install folder
|
EndJob
|
Installation Failed
|
|
|
|
I am becoming increasingly frustrated.
Josh
|
|
|
|
| |
|
|
|
this sounds very odd - do you try to install HTML CE on DNN PE or vv?
|
|
|
|
| |
|
|
|
Joined: 9/21/2010
Posts: 34
|
|
|
Right now it is the CE. It was functioning on 5.5.01, but with the upgrade it does not work. Everything else on the site is functioning how it should.I grabbed the install zip from the Install bin in the root directory.
Josh
|
|
|
|
| |
|
|
|
www.wesnetdesigns.com Joined: 2/18/2005
Posts: 3253
|
|
|
It appears that when the HTML module failed to install during the upgrade to DotNetNuke 5.06.00, the installer attempted to roll back to the prior version and in so doing deleted the module's registration. Then when you manually tried to install the HTML module, the installation started with the 03.00.00.SqlDataProvider script thinking this was a new install of the module. However, the database still contained the tables of a later version of the module resulting in failure when creating stored procedures which refeferenced columns no longer used in later versions of the module. Please answer the following:
1. From what version of DotNetNuke were you upgrading?
2. Did you check the Admin --> Event Viewer to see if any errors were logged during the upgrade to 5.06.00 ?
3. Following the failure of the HTML module to install during the upgrade, did you make any manual changes to the database (such as cleaning up database objects related to the HTML module) or try to uninstall the HTML module using the Host --> Extensions page prior to trying to re-install the HTML module?
4. When you tried to reinstall the HTML module following the failure, did you use the HTML module package found in the 05.06.00 upgrade package at \Install\Module\HTML_Community_5.06.00_Install.zip ?
5. Do you have backups of both the filesystem and database taken prior to the upgrade to DotNetNuke 5.06.00 to which you can restore?
Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
|
|
|
|
| |
|
|
|
Joined: 9/21/2010
Posts: 34
|
|
|
William Severance wrote:
It appears that when the HTML module failed to install during the upgrade to DotNetNuke 5.06.00, the installer attempted to roll back to the prior version and in so doing deleted the module's registration. Then when you manually tried to install the HTML module, the installation started with the 03.00.00.SqlDataProvider script thinking this was a new install of the module. However, the database still contained the tables of a later version of the module resulting in failure when creating stored procedures which refeferenced columns no longer used in later versions of the module. Please answer the following:
1. From what version of DotNetNuke were you upgrading?
2. Did you check the Admin --> Event Viewer to see if any errors were logged during the upgrade to 5.06.00 ?
3. Following the failure of the HTML module to install during the upgrade, did you make any manual changes to the database (such as cleaning up database objects related to the HTML module) or try to uninstall the HTML module using the Host --> Extensions page prior to trying to re-install the HTML module?
4. When you tried to reinstall the HTML module following the failure, did you use the HTML module package found in the 05.06.00 upgrade package at \Install\Module\HTML_Community_5.06.00_Install.zip ?
5. Do you have backups of both the filesystem and database taken prior to the upgrade to DotNetNuke 5.06.00 to which you can restore?
Sorry for the delay in response, long weekend and some skin issues...
1. I upgraded from 5.5.1.
2. This is what I was able to find in the Event Viewer:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 25c26523-6d61-454b-9ac7-69573727c445
InnerException: Thread was being aborted.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Threading.Thread.AbortInternal
StackTrace:
Message: System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.Thread.AbortInternal() at System.Threading.Thread.Abort(Object stateInfo) at System.Web.HttpResponse.End() at DotNetNuke.UI.Utilities.ClientAPI.HandleClientAPICallbackEvent(Page objPage, CallBackTypeCode eType) at DotNetNuke.UI.Utilities.ClientAPI.HandleClientAPICallbackEvent(Page objPage) at Papayas.DnnModules.DnnAutoUpgrade.AutoUpgradeDefault.Page_Init(Object sender, EventArgs e) at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.UserControl.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at System.Web.UI.ControlCollection.Add(Control child) at DotNetNuke.UI.Modules.ModuleHost.InjectModuleContent(Control content) in C:\CCNet_Builds\CE_Development\WorkingDirectory\Library\UI\Modules\ModuleHost.vb:line 159 at DotNetNuke.UI.Modules.ModuleHost.CreateChildControls() in C:\CCNet_Builds\CE_Development\WorkingDirectory\Library\UI\Modules\ModuleHost.vb:line 386 at System.Web.UI.Control.EnsureChildControls() at DotNetNuke.UI.Modules.ModuleHost.get_ModuleControl() in C:\CCNet_Builds\CE_Development\WorkingDirectory\Library\UI\Modules\ModuleHost.vb:line 95 at DotNetNuke.UI.Containers.Container.get_ModuleControl() in C:\CCNet_Builds\CE_Development\WorkingDirectory\Library\UI\Containers\Container.vb:line 122 at DotNetNuke.UI.Containers.Container.ProcessModule() in C:\CCNet_Builds\CE_Development\WorkingDirectory\Library\UI\Containers\Container.vb:line 382 at DotNetNuke.UI.Skins.Pane.InjectModule(ModuleInfo objModule) in C:\CCNet_Builds\CE_Development\WorkingDirectory\Library\UI\Skins\Pane.vb:line 402
3. There were no manual changes made to the database.
4. Yes I used the HTML module package that was incuded in the install zip.
5. I do not have any backups, I am using this as a testing area for a new Intranet site. Very little content, would there be an issue with a clean install?
Josh
|
|
|
|
| |