When installing janet.RandomImages the SQLProvider Script throws an error of not being able to resolve a collation conflict.
System.Data.SqlClient.SqlException: Cannot resolve collation conflict for column 2 in SELECT statement. 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 Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText) at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) create procedure dbo.JanetRandomimage_Getimage @ModuleID int, @PortalID int, @ID int AS SELECT Name, 'imageName' = case when Files.FileName is null then JanetRandomimage_Images.ImageName else Files.Folder + Files.FileName end, AltText, StrapLine, Live, Category FROM JanetRandomimage_Images LEFT OUTER JOIN Files ON JanetRandomimage_Images.ImageName = 'fileid=' + convert(varchar,Files.FileID) WHERE JanetRandomimage_Images.PortalID = @PortalID AND JanetRandomimage_Images.ID = @ID .
The DNN database, running on an english Windows 2K3 und an SQL 2K5 Server has a SQL_Latin1_General_CP1_CI_AS collation by default. The SQL collation is the best to use.
The SQL Provider script tries to create the tables using the Latin1_General_CI_AS collation, which is a OS specific collation.
Maybe you should change the the collation in your script or just do not set the collation explicitly.
Thomas