That procedure that I have at the moment in the base of portal that shows the error:

USE [xxx]

GO

/****** Object: StoredProcedure [dbo].[AddModule] Script Date: 08/22/2010 09:43:16 ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

ALTER PROCEDURE [dbo].[AddModule]

@ContentItemID int,

@PortalID int,

@ModuleDefId int,

@AllTabs bit,

@StartDate datetime,

@EndDate datetime,

@InheritViewPermissions bit,

@IsDeleted bit,

@CreatedByUserID int

 

AS

INSERT INTO Modules (

ContentItemID,

PortalId,

ModuleDefId,

AllTabs,

StartDate,

EndDate,

InheritViewPermissions,

IsDeleted,

CreatedByUserID,

CreatedOnDate,

LastModifiedByUserID,

LastModifiedOnDate

)

VALUES (

@ContentItemID,

@PortalID,

@ModuleDefId,

@AllTabs,

@StartDate,

@EndDate,

@InheritViewPermissions,

@IsDeleted,

@CreatedByUserID,

getdate(),

@CreatedByUserID,

getdate()

)

SELECT SCOPE_IDENTITY()

Yael - That is the correct version of the AddModule stored procedure for DNN 5.5.0. It does not reference the Modules.ModuleTitle, Header, or Footer columns as did the most recent previous version of that same stored procedure which did. That is consistent with no errors being logged during the 5.05.00.SqlDataProvider script's execution. It also appears from the stack trace that was posted earlier, the parameters passed to the ModuleControlle.AddModule also appear to be correct for v 5.5.0. But . . . something is very strange here and seems to be happening to several other users.

Can anyone having the ModuleTitle issue happen when adding a module to the page and who has NOT added the ModuleTitle colum back into the Modules table perform a restart of the SQL Server then see if the issue reoccurs when adding a module after the SQL Server has been restarted?

---

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

I want to add that I am very interested in a fix of that issue since I can not run localization due to this error since the page and module population for sublanguages does not work due to this issue and I need it badly. So I can provide you any access to the site incl. remote desktop access to th server.