Problem installing modules

Hmmm. That is strange. Maybe it didn't run all the DB scripts when you installed. That proc was updated in DNN 4.5

You can run this in the SQL window after selecting to execute as script:

/* Update AddDesktopModule */
/***************************/

IF EXISTS (SELECT * FROM dbo.sysobjects WHERE id = object_id(N'{databaseOwner}[{objectQualifier}AddDesktopModule]') AND OBJECTPROPERTY(id, N'IsPROCEDURE') = 1)
DROP PROCEDURE {databaseOwner}{objectQualifier}AddDesktopModule
GO


CREATE PROCEDURE {databaseOwner}{objectQualifier}AddDesktopModule

@ModuleName nvarchar(128),
@FolderName nvarchar(128),
@FriendlyName nvarchar(128),
@Description nvarchar(2000),
@Version nvarchar(8),
@IsPremium bit,
@IsAdmin bit,
@BusinessController nvarchar(200),
@SupportedFeatures int,
@CompatibleVersions nvarchar(500),
@Dependencies nvarchar(400),
@Permissions nvarchar(400)

AS

INSERT INTO {objectQualifier}DesktopModules (
ModuleName,
FolderName,
FriendlyName,
Description,
Version,
IsPremium,
IsAdmin,
BusinessControllerClass,
SupportedFeatures,
CompatibleVersions,
Dependencies,
Permissions
)
VALUES (
@ModuleName,
@FolderName,
@FriendlyName,
@Description,
@Version,
@IsPremium,
@IsAdmin,
@BusinessController,
@SupportedFeatures,
@CompatibleVersions,
@Dependencies,
@Permissions
)

SELECT SCOPE_IDENTITY()

GO

There's a couple ways you can do it. The fastest and easiest way for me is to create a new Install and then script out all the stored procedures and run the script against the DB that is not up to date.

The other way is to look at the actual scripts that get ran on a DNN install.  These are located in the /providers/DataProviders/SqlDataProvider folder.

I tried creating a script for you, but my default website on my laptop is acting funny and i can't test it. 

After I reboot I'll get it working and attach the script.

Ok, attached is a file.

Yes, make a backup of your DB first!  We are all human.  I tested this on my dnn 451 dev version but you never know.

Upload it to your sql window, or open it and paste it in.  Check the execute as script checkbox, and hold your breath while clicking on execute.

Running it multiple times won't hurt.  I should have looked at your error closer, it does say you are running the ExecuteScript routine.

It must be a SQL 2005 thing, let me check that out.