00:00:00.039 - Upgrading to Version: 05.06.00
00:00:00.068 -   Executing Script: 05.05.01.SqlDataProvider Success
00:00:00.184 -   Executing Script: 05.06.00.SqlDataProvider Success
00:00:02.111 -   Executing Application Upgrades: 05.05.01 Success
00:00:02.111 -   Executing Application Upgrades: 05.06.00 Error!
00:00:03.677 -   Cleaning Up Files: 05.05.01 Success
00:00:03.678 -   Cleaning Up Files: 05.06.00 Success
--- all else is Success

So far, everything seems to be working correctly though that error was encountered - is it imperative that I roll back and get resolve the issue or could a future update resolve the issue?

05.06.00_Application.log.resources:

Error: Invalid column name 'ModuleTitle'.   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.SqlDataReader.ConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteScalar()
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(String connectionString, String spName, Object[] parameterValues)
   at DotNetNuke.Data.SqlDataProvider.AddModuleDefinition(Int32 DesktopModuleId, String FriendlyName, Int32 DefaultCacheTime, Int32 createdByUserID)
   at DotNetNuke.En ies.Modules.Definitions.ModuleDefinitionController.SaveModuleDefinition(ModuleDefinitionInfo moduleDefinition, Boolean saveChildren, Boolean clearCache)
   at DotNetNuke.Services.Upgrade.Upgrade.AddModuleDefinition(String DesktopModuleName, String Description, String ModuleDefinitionName, String BusinessControllerClass, Boolean IsPortable, Boolean Premium, Boolean Admin)
   at DotNetNuke.Services.Upgrade.Upgrade.AddModuleDefinition(String DesktopModuleName, String Description, String ModuleDefinitionName, Boolean Premium, Boolean Admin)
   at DotNetNuke.Services.Upgrade.Upgrade.UpgradeToVersion_560()
   at DotNetNuke.Services.Upgrade.Upgrade.UpgradeApplication(String strProviderPath, Version version, Boolean writeFeedback)

Is there any chance that you are using the DotNetNuke Events Module? If so, the solution seems to be to upgrade the module. See: http://www.dotnetnuke.com/Community...N-5-5.aspx

Thanks Joe. I do have the events module installed but I'm upgrading from DNN 5.5.0 so I already have v5.1.4 of the Events Module installed. Just to be certain I checked the list of installed module definitions. Any other suggestions? Most important: should I roll back update (restore backup db and files) and try again after correcting issue or would this Application Upgrade issue not be a critical error and could be dealt with as you mentioned by possibly updating an installed module?

If you started at 5.5.0 AND you already had the Events 5.1.4 module installed, I'd guess that this isn't the issue.  You could revert back and verify that this really is the case.

Then, there could be another module with the same sort of problem.

Basically, the blog entry says that the Event Module team used a direct access to the database for performance reasons.  This is also known as dangerous programming as it opens the module up to changes in the underlying database structure.  This is what happened.  So, if there is another module that bypasses the API for direct calls, it could be the problem.

Unfortunately, I don't think that the error message is sufficiently detailed to identify which module is the offender.