Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Cannot resolve the collation conflict between "Latin1_General_CI_AS"Cannot resolve the collation conflict between "Latin1_General_CI_AS"
Previous
 
Next
New Post
6/12/2006 4:56 PM
 
Dale Burrell

www.creative-dreaming.com
Joined: 4/2/2006
Posts: 232

I am getting the following error when I try to access the log viewer... Any ideas? I haven't touched the database myself... could a module have installed itself with the wrong collation?

Error: Log Viewer is currently unavailable.
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.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 ---

www.creative-dreaming.com
 
New Post
6/15/2006 6:08 AM
 
Laurence Neville


Joined: 11/2/2003
Posts: 383
This is a problem with the Log Viewer which is a built in part of DNN, not an installed module.
One possibility is you might have a collation conflict between your database server's "TempDB" (a SQL Server maintained DB for temporary storage) database and your DotNetNuke database.

Assuming you have access to running SQL scripts against your SQL Server, try this:

SELECT
    DATABASEPROPERTYEX( 'DotNetNuke or whatever your DNN database is called' , 'Collation' ) AS DotNetNukeDB_Collation,
    DATABASEPROPERTYEX( 'tempdb' , 'Collation' ) AS TempDB_Collation,
    SERVERPROPERTY( 'Collation' ) AS Server_Default_Collation

If all three are the same, then tempdb collation is not your problem. If the DotNetNukeDB_Collation is different from the
TempDB_Collation then you have a problem - it may or may not be the source of the error you described, but if not you may get collation conflict errors in other areas of DNN. To resolve it is another conversation ..!

PS - this is Dale Burrell, right? Long time no see ... we used to be on the CS program together, remember? Funny how we have both wound up in the world of DNN (for more personal chit chat lets swap email addresses - laurenceneville at hotmail dot com).
 
New Post
6/22/2006 1:18 PM
 
Sérgio Almeida

Joined: 4/4/2006
Posts: 16
I have this same problem. I have two machines with SQL Server 2005 and DNN4 running. On machine 1 I have these settings:
DotNetNukeDB_Collation = Latin1_General_CI_AS   
TempDB_Collation = SQL_Latin1_General_CP1_CI_AS    Server_Default_Collation = SQL_Latin1_General_CP1_CI_AS

and Log Viewer does not work

on the other machine, machine 2, Log Viewer woks and have these settings:

DotNetNukeDB_Collation = Latin1_General_CI_AS   
TempDB_Collation = Latin1_General_CI_AS   
Server_Default_Collation = Latin1_General_CI_AS

So the two machines have different settings. What should I do? Should I change the settings on SQL Server of the machine 1 to Latin1_General_CI_AS? Or to SQL_Latin1_General_CP1_CI_AS? And how do I do that on SQL Server 2005? On SQL Server properties I see the SQL_Latin1_General_CP1_CI_AS on Server Collation, but i don't know how to change it.

Help is needed!

Thanks in advance
 
New Post
6/22/2006 2:08 PM
 
yannick kiekens

www.purplebox.be
Joined: 9/13/2004
Posts: 192

If I had to guess I'd say you are running English SQL server on a non english windows.

I have the collation problem myself on my development machine. And this looks like the only plausible reason to me

I am running english SQL server on a dutch Windows XP

 

 

my production machine (english windows 2003 ) does not have these problems and it is running the same version of SQL server and visual studio

Edit your Skin.xml and Container.xml files with:
Yannick's SXE
 
New Post
6/22/2006 4:36 PM
 
Sérgio Almeida

Joined: 4/4/2006
Posts: 16
Hi

well, no, I use english SO and english SQL and VS.NET, but I am a portuguese in Portugal, so the only thing that are not english is my regional settings... I'm not able to see the log viewer ! HELP! :)
 
 Page 1 of 12
123...12Next 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Cannot resolve the collation conflict between "Latin1_General_CI_AS"Cannot resolve the collation conflict between "Latin1_General_CI_AS"


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