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
8/8/2006 2:47 PM
 
Juan Pablo Schmiede


jschmiede.wordpress.com/
Joined: 8/20/2004
Posts: 1

This is a SQL Server problem not DNN, so i dont get why upgrading to 4.3 os superior will fix this problem.

What you need to do is configure your tables (EventLog in this case) to use a collation equal to your server (server, tempdb and DNN database), you do this by changing collation propertie of the column you are comparing (LogGuid).

If you use MS SQL Server Management Studio, you do this by right clicking over your table name and selecting "modify" and changing the "Collation" to the database default (or the one ou are using in all server tables).

Greetings,

JP.
 
New Post
8/31/2006 5:03 PM
 
Lorenzo

Joined: 8/24/2006
Posts: 1

Hello!

Of course I run into the same problem. The solution of changing the collation for the EventLog tables woked fine. However I found more coherent another solution, namely insert a collation on the LogGUI field on the temp table as follows:

CREATE TABLE #PageIndex
   (
      IndexID int IDENTITY (1, 1) NOT NULL,
      LogGUID varchar(36) COLLATE SQL_Latin1_General_CP1_CI_AS
   )

and all works perfectly!

I was wondering if, in fact, that was a SQL problem or a DNN problem. Let's put the matter in this way:

DNN "forces" collation on the database. However when using a temp table, the stored proc doesn't "force" any collate on the text (varchar, nvarchar etc.) fields.

For the sake of coherence I would suggest that either the db shouldn't be forced with a collation or that on creation of a temp table should be forced with the correct collation.

Lorenzo
 
New Post
10/7/2006 4:49 PM
 
Frank Corrao

www.raiseepilepsy.org
Joined: 4/7/2005
Posts: 122
I totally agree.  Not good to assume anything in the db creation scripts.  Get rid of the collation in the create table(s).!!
Version: DNN 4.4.1
Hosting Provider: 1and1
RAISE
 
New Post
7/23/2007 7:04 AM
 
Simon Holman

expeed.com.au
Joined: 1/6/2006
Posts: 50

Nevermind, had a blonde moment
 
New Post
12/10/2008 6:53 AM
 
Michael Dohr

Joined: 3/23/2006
Posts: 70

I have the same problem:

acutall Collations:

DNN_DB: Latin1_General_CI_AS
TempDB: SQL_Latin1_General_CP1_CI_AS
Server-default: SQL_Latin1_General_CP1_CI_AS

I allready tried to change the collation of the EventLog-table-columns (as far as possible)
Next to this, i tried to add the table as described above to the tempdb:

CREATE TABLE #PageIndex
   (
      IndexID int IDENTITY (1, 1) NOT NULL,
      LogGUID varchar(36) COLLATE Latin1_General_CI_AS
   )

Unfortunately none of the provided solutions worked out. Or maybe I've done something wrong. Wahts does the #PageIndex stand for in the tempdb?
 
 Page 3 of 12
Previous1234...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