- UNIFYBroker Forum
- UNIFYBroker/Aurion
-
Questions
Aurion Schedule Connector failed with reason Cannot resolve the collation conflict between ""SQL_Latin1_General_CP1_CI_AS"" and ""Latin1_General_CI_AS"" in the equal to operation
As per Dustin Page from ASC:
Hi Andre,
Looks like I found the issue, one of the guys made a change to the SQL server environment in Production a few weeks ago and forgot to set all the database collation types back properly. I did move it back to what it’s meant to be set to but it seems I’m still getting the following error in the logs;
20120914,05:25:47,Connector processing failed.,Connector Processor,Information,"Connector Processing page 1 for connector Aurion Schedule Connector failed with reason Cannot resolve the collation conflict between ""SQL_Latin1_General_CP1_CI_AS"" and ""Latin1_General_CI_AS"" in the equal to operation.. Duration: 00:00:01.5635366
SQL collation is set back to SQL_Latin1_General_CP1_CI_AS as per the test environment. Yet I’ve restarted the Broker Service and it keeps seeing the same error?
IdB upgrade issue.JPG
Customer support service by UserEcho
Hi André,
I had a quick look on Google, and the first hit suggests that there may be a mismatch with the collation for individual columns.
Have a look at http://stackoverflow.com/questions/1607560/cannot-resolve-the-collation-conflict-between-sql-latin1-general-cp1-ci-as-and.
If any changes were made to the database whilst the different setting was in place, then the collation could be mismatched for those changes. The collation should be changed so that they are in line with the database setting.
Thanks Adam, the client has done the following against every table in the database to identify all the incorrect columns with the wrong collation type, he has then set them all to the database default and rebooted the FIM server.
It is now successfully doing a full import without the red icon.
SQL script he used below to identify columns with incorrect collation.
______________________
SELECT
col.name, col.collation_name
FROM
sys.columns col
WHERE
object_id = OBJECT_ID('dbo.table_name')
Client stated all ok and we can close the the issue