I have a problem with the event viewer on my DNN site which I hope someone can assist with. I have used it for the first time, the rest of the site and controls work fine. I can see the logs and data on the sql module on the site, I can backup the data and restore it on my pc and there seems to be no issue. The logs were not particularly large but in an attemptto resolve the matter I reduced them and then truncated them. I still get the error which from what I read seems to be due to incompatibilities that I dont really understand, particularly as they seem to affect just the one log? any Help eagerly awaited. Many thanks in anticipation. below the error message on the event log. . . Error: Event Viewer is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: Cannot resolve the collation conflict between "Latin1_General_CI_AI" 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_AI" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation. 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.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() in C:\Inetpub\vhosts\my url obscured\httpdocs\www\Admin\Logging\LogViewer.ascx.vb:line 110 at DotNetNuke.Modules.Admin.Log.LogViewer.Page_Load(Object sender, EventArgs e) in C:\Inetpub\vhosts\my url obscured\httpdocs\www\Admin\Logging\LogViewer.ascx.vb:line 411 --- End of inner exception stack trace ---

If you truncate the Event_Log table, does this persist? Not the IIS log files, but the Event_Log table in your DotNetNuke database.

hi JOe.

yes I have already truncated the event log and reduced the size of the few other logs that were running. same problem.

..hope that points to a solution but fearing not....
Rob

Did this "just start" or did it start after an upgrade?

Hello again thanks for the prompt reply!

I never looked ta the event viewer until now so I cannot say. I have not done any upgrade ( would love to upgrade but fear my inexperience with DN will make that a dangerous move just as the site goes live.

THe only changes recently apart from adding data to the database ( not DNN) is the failed install of some onyatek modules which I removed and ( as previously metioned on here in Modules section) the failed install of the latest revision ofthe documents module which failed with a similar error message.

REgards

Rob

Hmmmm ... if you are having trouble installing modules, and you have this error ... I would address those before going live. It's possible that there is something going on that might cause trouble when you are live. It would be best to deal with those problems now.

Some possible avenues for exploration:

"I think the problem is your web.config, change the "globalization culture" to the same as your SQL Server"

This looks helpful: http://www.dotnetnuke.com/Community...fault.aspx

" Found out the collate for the DB and the EventLog was diff. After I changed the EventLog collate to the same as DB I can see the EventLog again."

hello Joe,
thanks for the reply.

I checked the link you gave and the file for the event log has the amended text already.

I do not know how to check the DB culture but have dropped a message on the hosting Co. to see how to do this  or at least see how they have it set.
in my webconfig it is

 

not really sure how this relates to the CI etc in the fault listing. the web config is as the default for my version of DNN I have made no edits myself.

I think I understand the principle I just have no idea how to effect a resolution, nor how far the issue extends or if once I change the Cultures to match ( assuming they dont..) what will be the impact on the data I aready have in the Database and its use with the existing set up of DNN...

??

Rgds

Rob

not sure where the original paste   disappeared to but guessing it was seen as a command so have removed the carets this time!

the whole of the setting is this

globalization culture="en-US" uiCulture="en" requestEncoding="UTF-8" responseEncoding="UTF-8" fileEncoding="UTF-8"

rob

had feedback from host and only setting on globalization is that languge is Gb so changed webconfig to reflect this.
no change to error.. but guessing the collation conflict ( given what I have read) must be caused by something else?..Heeeeelp!

I would assume that you've fixed the problem.

Hi Joe..

O far from it. problem persists.
I have the following from the server Host
"We cant resolve the collation conflict as elements of the database rely on it being Latin1_General_CI_AI. The culture of our servers should all be en-GB"

set my webconfig to en-GB ( it was en-US).

it seems to me that the master database and the dnn database must have different collations, IF this is the case, how (practically) do I change my database to match? how can I Avoid the issue in future.

regards

Rob

Oops!

My recommendation is that you contact the DotNetNuke core team using the forums at DotNetNuke.com.  This is way outside of my experience/knowledge ...