In version prior to Articles 4.2.5, you may see this error when you try to enter the Module settings for Articles under DNN 5.5+.

Error: is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Invalid column name ''ModuleTitle''.  -> System.Data.SqlClient.SqlException: 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.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Data.SqlDataProvider.ExecuteReader(String ProcedureName, Object[] commandParameters) at EfficionConsulting.Articles.ArticleController.GetExistingInstances(Int32 PortalId, Int32 ModuleId) at EfficionConsulting.Articles.Settings.BindExistingInstances() at EfficionConsulting.Articles.Settings.LoadSettings() at DotNetNuke.Modules.Admin.Modules.ModuleSettingsPage.Page_Load(Object sender, EventArgs e)  - End of inner exception stack trace  -

This error is due to a data model change that occurred in 5.5.0. We need to update the Aritlces_GetExistingInstances Stored Procedure to pull the Module Title from the ModuleDefinition table rather than the Module table. This fix will be in the next release of the Articles module. Please contact us if you are experiencing this issue now. It's a very easy fix.

Hi, i need to fix this problem, you can help me ? thank a lot
Marcello

Version 4.2.5 was released today and fixes this issue as well as a couple other minor issues introduced by DotNetNuke 5.5.x.

Hi David,

I am experiencing the exact same installation problem and error (invalid column name ModuleTitle), although I am trying to install version 4.2.6 under DNN 5.5.1. Any ideas?

Kevin

Hi I got the same installation error as Kevin under the same conditions.
And after the install when I try to access the settings of the article module I get an exception:

DotNetNuke.Services.Exceptions.ModuleLoadException: The stored procedure 'dbo.dnn_Articles_GetExistingInstances' doesn't exist. ---> System.InvalidOperationException: The stored procedure 'dbo.dnn_Articles_GetExistingInstances' doesn't exist. at System.Data.SqlClient.SqlCommand.DeriveParameters() at System.Data.SqlClient.SqlCommandBuilder.DeriveParameters(SqlCommand command) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.DiscoverSpParameterSet(SqlConnection connection, String spName, Boolean includeReturnValueParameter, Object[] parameterValues) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSetInternal(SqlConnection connection, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Data.SqlDataProvider.ExecuteReader(String ProcedureName, Object[] commandParameters) at EfficionConsulting.Articles.ArticleController.GetExistingInstances(Int32 PortalId, Int32 ModuleId) at EfficionConsulting.Articles.Settings.BindExistingInstances() at EfficionConsulting.Articles.Settings.LoadSettings() at DotNetNuke.Modules.Admin.Modules.ModuleSettingsPage.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

I apologize for not having a complete fix for this problem. The fix for this issue is complicated because there are three different scenarios for getting the ModuleTitle based on which version of DotNetNuke you are running. Version 4.2.6 should fix this issue for everyone except people who are running DNN 5.4.x.

If you are running DotNetNuke 5.4.x, please run the following script through your Host->SQL tab with the "Execute As Script" checkbox checked.

 IF EXISTS (SELECT * FROM sysobjects WHERE id = object_id(N'{databaseOwner}{objectQualifier}Articles_GetExistingInstances') and OBJECTPROPERTY(id, N'IsProcedure') = 1)
DROP PROCEDURE {databaseOwner}{objectQualifier}Articles_GetExistingInstances
GO

CREATE PROCEDURE {databaseOwner}{objectQualifier}Articles_GetExistingInstances
@PortalID int,
@ModuleID int
AS
Select t.TabID, tm.ModuleID, t.TabName, tm.ModuleTitle
    FROM {databaseOwner}{objectQualifier}DesktopModules dm
    INNER JOIN {databaseOwner}{objectQualifier}ModuleDefinitions md on dm.DesktopModuleID = md.DesktopModuleID
    INNER JOIN {databaseOwner}{objectQualifier}Modules m ON md.ModuleDefID = m.ModuleDefID
    INNER JOIN {databaseOwner}{objectQualifier}TabModules tm ON m.ModuleID = tm.ModuleID
        INNER JOIN {databaseOwner}{objectQualifier}Tabs t ON tm.TabID = t.TabID
    WHERE dm.ModuleName= 'Articles'
    AND m.PortalID = @PortalID
    AND m.ModuleID <> @ModuleID

GO

Hi David,
Thanks for your response, but like Kevin I am running DNN 05.05.1 with Articles 4.2.6 and got the exception error (see my previous post above).

I am kinda stuck, what to do?

- Daniel

Hi Daniel,

Hmm, the script David supplied worked perfectly for me (thanks David!). I was a little hesitant since David mentioned DNN 5.4.x instead of DNN 5.5.x, but I took a look at the script and compared it to the DB and determined it should work great. I would think it would work well for you since your error references the stored procedure that the script above re-creates. I assume you went to "Host" and then "SQL"? I pasted in the script but it had added a few ending line breaks which I removed (probably wouldn't have hurt anything, but just to be safe). Make sure to click the "run as script" checkbox before clicking Execute though. It only took a second to run and it solved my problem.

Give it a shot and I bet it will work for you.

Kevin

Hi Daniel,

Please try running the above script. It will work fine against 5.5.x.

David

:-)

Perfect!!!
Thanks Kevin & David!

Daniel