Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Problem with site logsProblem with site logs
Previous
 
Next
New Post
8/11/2006 6:54 AM
 
Hello everyone! :)

I've just installed DNN 4.3.4 from source and have problems with enabling site logging system.

Can anyone give me some clues how to handle this?

Thanks very much!

Best regards!
Lukasz Czyzewski.

(Here's what I get:)

==================================================
A critical error has occurred.
Cannot insert duplicate key row in object 'dbo.EventLogConfig' with unique index 'IX_LogTypeKey_LogTypePortalID'. The statement has been terminated.
==================================================

and

==================================================
Error: Log Viewer is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Cannot resolve the collation conflict between "Polish_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation. ---> System.Data.SqlClient.SqlException: Cannot resolve the collation conflict between "Polish_CI_AS" 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() at DotNetNuke.Modules.Admin.Log.LogViewer.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---
==================================================


 
New Post
8/11/2006 8:06 AM
 

it looks like a problem with your sql server collation. AFAIR theres an issue when your tempdb collation is different from your database collation. you can fix this by specifying the COLLATE keyword in the stored procedure (I can't recall it at present, but think it's GetLog - see http://musingmarc.blogspot.com/2006/05/did-you-know-that-tempdbs-collation.html for a similar example)

An alternative is to use filebased logging i.e. in your web.config set logging defaultProvider="XMLLoggingProvider"

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/11/2006 2:02 PM
 
Hello! :)

Thank you for your answer!

Switching to filebased logging did the trick - however I will try to make database logging work for my site.

Cathal, perhaps you know, how big is the difference (in performance of a site) between database and file system logging?

Best Regards!
Lucas.
 
New Post
8/11/2006 3:04 PM
 

Theres little difference in writing individual records. Where there can be a problem is that when writing to the file, the xmlserializer is used. When using xmlserializer, asp.net loads the entire file into memory, so if you've let your logfile grow too large you can notice an overhead. If you keep your eventlog's small this isn't an issue (note: at one point on one of my site, the logfiles were 40MB, and I hadn't noticed an impact as it's very gradual)

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Problem with site logsProblem with site logs


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out