Hi there

I moved my DNN Portal to a new Server and upgraded SQL Server 2000 to 2005. After that, everything was working fine except the Log. When I try to access the log, I get the following exception:

Fehler: Log-Anzeige ist zur Zeit nicht verfügbar.
DotNetNuke.Services.Exceptions.ModuleLoadException: Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation. ---> System.Data.SqlClient.SqlException: Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation. at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream) 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.Services.Log.EventLog.DBLoggingProvider.Data.SqlDataProvider.GetLog(Int32 PageSize, Int32 PageIndex) at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.DBLoggingProvider.GetLog(Int32 PageSize, Int32 PageIndex, Int32& TotalRecords) at DotNetNuke.Services.Log.EventLog.LogController.GetLog(Int32 PageSize, Int32 PageIndex, Int32& TotalRecords) at DotNetNuke.Modules.Admin.Log.LogViewer.BindData() at DotNetNuke.Modules.Admin.Log.LogViewer.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

Any Ideas how to resolve this?

Thanks, Rene

I had this problem after restoring a production database to my local machine using sql express.

The problem was that 3 tables have all character columns with explicit collation settings.

After I changed the database settings and tempdb settings to be the same, I also had to manual change the column settings for the following tables to the database default (or explicit setting that matched the DB and tempdb).

The tables affecting my system were EventLog, EventLogConfig, and EventlogTypes.

The log viewer is now working.

I would expect that these explicit settings could be removed from the column to avoid this extra work.

I am using the brute force method of chaning the eventlog tables collation to the database default.
1) open the database with sql server management studio
2) expand, drilldown to the columns for the table in question
3) right click modify the columns that are are characters
4) go to extended properties and ensure the collation is set to database_default

This could be done with a T_SQL script, but brute force works for now...

- Jim

Here is a screen print for the modify screen.
http://walkspoiled.com/Home/tabid/36/EntryID/57/Default.aspx