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...Upgrading DNN P...Upgrading DNN P...collation conflict logviewer 5.4.2 > 5.4.4collation conflict logviewer 5.4.2 > 5.4.4
Previous
 
Next
New Post
7/9/2010 10:13 AM
 
When i go to the logviewer, i see following error:
DotNetNuke.Services.Exceptions.ModuleLoadException: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation. ---> System.Data.SqlClient.SqlException: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.

please advise.
Thanks
 
New Post
7/11/2010 3:30 PM
 
Stephany;
Is your O/S set to use Latin as well or just SQL?
Have you installed Languages on you site? If so which Languages?

Ken Grierson
DotNetNuke Corporation
Test Lead
 
New Post
7/12/2010 3:14 AM
 
there are 5 languages installed. nl-BE / fr-FR/ de-DE/ en-US/ fr-BE.
I 'transported' my db using SQL Delta 4. My collation on development was Latin1_General_CI_AS, but the collation from my hosting provider is SQL_Latin1_General_CP1_CI_AS.

I hope this is the info you need.
Thanks in advance.
Stephany
 
New Post
7/12/2010 6:51 AM
 
This is typically a problem with SQL Server collation other than DNN database collation. If a stored procedure links two tables using a text column, both column needs to have the same collation. If the link is done to a temp table, this would use SQL Server collation by default, i.e. you need to use "collate database default" clause to avoid this error.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/19/2010 7:10 AM
 
but collate database default is already in the sql statement, but this didn't solve it. LogGUID varchar(36) collate database_default
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...collation conflict logviewer 5.4.2 > 5.4.4collation conflict logviewer 5.4.2 > 5.4.4


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