Alberto,

Have you tried installing a module other than Feedback to see if you get a similar error?

I had also looked at the FriendlyURL extension and as Bruce indicated, that cannot be the source of the error as it does not create any custom SQL scripts. I have also done several installs or upgrade of the Feedback module v 5.00.02 on DNN 5.05.01 and 5.06.00 without encountering this error.

---

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

Bad news:

Upgrading DotNetNuke
Current Assembly Version: 05.06.00
Current Database Version: 05.05.01


Upgrade Status Report
00:02:01.109 - Upgrading to Version: 05.06.00
00:02:01.125 -   Executing Script: 05.06.00.SqlDataProvider Error! (see 05.06.00.log.resources for more information)
00:02:02.718 -   Executing Application Upgrades: 05.06.00 Error!

after these errors all is good, but now if I try to install the feedback module I get a new sql error (below).
I will try to investigate this problem tomorrow - I have a coupld of modules on this host to be checked (Multi Portals Users Sharing and iWeb).




Nell'esecuzione SQL risultano le seguenti eccezioni: System.Data.SqlClient.SqlException: Invalid column name 'Category'. Invalid column name 'CreatedByEmail'. Invalid column name 'DateCreated'. Invalid column name 'FeedBackGUID'. 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.CreateFeedback @Category int, @CreatedByEmail nvarchar(200), @FeedBackGUID nvarchar(50), @ModuleID int, @Status int, @Message nvarchar(1000), @Subject nvarchar(200) as insert into Feedback ( Category, CreatedByEmail, DateCreated, FeedBackGUID, ModuleID, Status, Message, Subject ) values ( @Category, @CreatedByEmail, getdate(), @FeedBackGUID, @ModuleID, @Status, @Message, @Subject ) System.Data.SqlClient.SqlException: Invalid column name 'Category'. Invalid column name 'CreatedByEmail'. Invalid column name 'DateCreated'. Invalid column name 'FeedBackGUID'. Invalid column name 'Category'. Invalid column name 'Category'. Invalid column name 'CreatedByEmail'. Invalid column name 'DateCreated'. Invalid column name 'FeedBackGUID'. 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.GetCategoryFeedback @Category int, @Status int, @CurrentPage int, @PageSize int AS --Create a temp table to hold the current page of data --Add and ID column to count the records CREATE TABLE #TempTable ( ID int IDENTITY PRIMARY KEY, FeedbackID int, Category int, CreatedByEmail nvarchar(200), ApprovedBy int, DateCreated datetime, FeedBackGUID nvarchar(50), ModuleID int, Status int, Message nvarchar(1000), Subject nvarchar(200) ) --Fill the temp table with the Customers data IF @Category = 0 BEGIN INSERT INTO #TempTable ( FeedbackID, Category, CreatedByEmail, ApprovedBy, DateCreated, FeedBackGUID, ModuleID, Status, Message, Subject ) SELECT FeedbackID, Category, CreatedByEmail, ApprovedBy, DateCreated, FeedBackGUID, ModuleID, Status, Message, Subject FROM Feedback WHERE Status = @Status ORDER BY DateCreated Desc END IF @Category > 0 BEGIN INSERT INTO #TempTable ( FeedbackID, Category, CreatedByEmail, ApprovedBy, DateCreated, FeedBackGUID, ModuleID, Status, Message, Subject ) SELECT FeedbackID, Category, CreatedByEmail, ApprovedBy, DateCreated, FeedBackGUID, ModuleID, Status, Message, Subject FROM Feedback WHERE Category = @Category and Status = @Status ORDER BY DateCreated Desc END --Return the total number of records available DECLARE @TotalRecords int SELECT @TotalRecords = COUNT(FeedbackID) FROM #TempTable --Create variable to identify the first and last record that should be selected DECLARE @FirstRec int, @LastRec int SELECT @FirstRec = (@CurrentPage - 1) * @PageSize SELECT @LastRec = (@CurrentPage * @PageSize + 1) --Select one page of data based on the record numbers above SELECT FeedbackID, Category, CreatedByEmail, ApprovedBy, DateCreated, FeedBackGUID, ModuleID, Status, Message, Subject, TotalRecords = @TotalRecords FROM #TempTable WHERE ID > @FirstRec AND ID < @LastRec System.Data.SqlClient.SqlException: Invalid column name 'FeedbackGUID'. 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.GetFeedbackByGUID @FeedbackGUID nvarchar(50) as select * from Feedback where FeedbackGUID = @FeedbackGUID System.Data.SqlClient.SqlException: Invalid column name 'FeedbackGUID'. 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.UpdateFeedbackStatus @FeedBackGUID nvarchar(50), @Status int as update Feedback set Status = @Status where FeedbackGUID = @FeedbackGUID

Since you received the following errors during the upgrade to DotNetNuke 5.06.00:

00:02:01.125 -   Executing Script: 05.06.00.SqlDataProvider Error! (see 05.06.00.log.resources for more information)
00:02:02.718 -   Executing Application Upgrades: 05.06.00 Error!

I would not be so sure that all is good with the upgrade.

Did you look in the file /Providers/DataProviders/SqlDataProvider/05.06.00.log.resources to check what errors were logged while executing script 05.06.00.? There were many changes made to database objects in the 05.06.00 script.

The Appiication Upgrades errors often do not get logged but I would check the Admin --> Event Log when logged in as host user just in case there is some information there.

If the 'ModuleTitle' errors you received when trying to install any module are caused by a trigger that an earlier version of the  iFinity URL Master placed on the Modules (and possibly the ModuleControls table) but did not get removed or disabled when the extension was uninstalled, this issue would not have been corrected by the upgrade. In looking quickly at the 05.06.00.SqlDataProvider script which errored, I did not see any portion of that script that would be affected by the 'ModuleTitle' issue.

The Application Upgrade 05.06.00 does include a module installation that could have been affected. Check your Host menu and Host --> Extensions to see if the new Configuration Manager (XmlMerge) installed correctly.

Regarding the errors you hit when trying to install the feedback module, those are being caused by "remains" of the prior failed installation still being in the database. Unfortunately, that can happen if a module installation fails after its SqlDataProvider scripts have been run. Some changes to files are rolled back if the installation fails. Changes to the module's database objects are not rolled back. In the case of Feedback, it's version 5.00.02 tables (Feedback and FeedbackList) remained in the database as did all of the version 5.00.02 stored procedures. When the install of Feedback was re-attempted, the script for the earliest version 3.02.01 saw that the tables already existed and did not  try to replace them. However, since these tables did not contain several columns that had been used in version 3.02.01, the installation of the stored procedures for that version failed with the errors you noted.

The fix that will have to be done before reattempting the install of the Feedback module will require manual editing of the database to remove all traces of the failed Feedback module installation - at least to delete the Feedback and FeedbackLists tables. I would, however, hold off on trying another module install until you are sure the original 'ModuleTitle' issue has been corrected.

---

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