Hi,

From Commerce Server Manager global resources I have these problems:
I can't change ProfileService_SQLSource connection string  - I get "Catalog
Update Error Cannot resolve collation conflict for SQL operation"
Can't refresh the profile either - I get "Get Profile Error Cannot resolve
collation conflict for SQL operation".

SQL Server 2000 is installed with default collation of
SQL_Latin1_General_CP1_CI_AS.

My CS2002 databases are have a collation of Latin1_General_CI_AS.

I could re-install SQL 2000, but that seems like a sledge hammer to crack a
nut.

Is there a quicker way to resolve this conflict?

Thanks
Martin

[ Post a follow-up to this message ]

Is the master database on the SQL Server set to Case Sensitive?

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team
--------------------
From: "Martin" <x@y.z>
Subject: Collation conflict with profile management
Date: Wed, 14 Jul 2004 09:40:38 +0100
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <#tvJ94XaEHA.2056@TK2MSFTNGP12.phx.gbl>
Newsgroups: microsoft.public.commerceserver.userprofilemgt
NNTP-Posting-Host: cpc3-cmbg6-5-0-cust233.cmbg.cable.ntl.com 81.104.212.233
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
Xref: cpmsftngxa06.phx.gbl
microsoft.public.commerceserver.userprofilemgt:3051
X-Tomcat-NG: microsoft.public.commerceserver.userprofilemgt

Hi,

From Commerce Server Manager global resources I have these problems:
I can't change ProfileService_SQLSource connection string  - I get "Catalog
Update Error Cannot resolve collation conflict for SQL operation"
Can't refresh the profile either - I get "Get Profile Error Cannot resolve
collation conflict for SQL operation".

SQL Server 2000 is installed with default collation of
SQL_Latin1_General_CP1_CI_AS.

My CS2002 databases are have a collation of Latin1_General_CI_AS.

I could re-install SQL 2000, but that seems like a sledge hammer to crack a
nut.

Is there a quicker way to resolve this conflict?

Thanks
Martin

[ Post a follow-up to this message ]