web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Dynamics CRM V9 On-Pre...
Microsoft Dynamics CRM (Archived)

Dynamics CRM V9 On-Premise | Collation Failure using Latin1_General_CI_AS

(0) ShareShare
ReportReport
Posted on by Steve Le Monnier 959

Having waited so long to get my hands on CRM V9 On-Premise, I was frustrated to encounter problems doing a clean install.
I don't know if this is bad luck on my part or a repeatable problem, but this is what I encountered during my install attempts.

Coming from the UK we normally use the SQL Collation Latin1_General_CI_AS (similar to DOCI). This isn't the default as far as CRM is concerned, the product ships with the default collation Latin1_General_CI_AI. And if you install V9 without changing this... it installs just fine.

However, if you change the default collation (to match your SQL Server) the installation crashes with a Collation Change failure on scripts creating foreign keys etc.

Has anybody else encountered this problem?
I was using the EXE install rather than an ISO image

Cheers
Steve

*This post is locked for comments

I have the same question (0)
  • David Girard Profile Picture
    David Girard 50 on at

    Do you already find any solution ? We have the same issue... :(

    Thanks

  • Steve Le Monnier Profile Picture
    Steve Le Monnier 959 on at

    Hi David

    Many thanks for confirming the same behaviours that I encountered. At least I know its not my setup, or me doing something wrong.

    Looks like the installation scripts themselves are at fault, which is disappointing given this is V9 and not V1.

    As for a remedy, I don't want to waste valuable time trying to fix the install package itself, but I am going to trying something to see how deep rooted the problem is.

    The initial install of V9 was for my test tenant called "Sandbox". I'm going to install another tenant over the weekend using the deployment manager to see if that root has the same issues, and I'll post my feedback here.

    Before we can role this out to our customer base MS are going to need to resolve these issues, hopefully in a timely manor.

    Cheers

    Steve

  • riaandelange Profile Picture
    riaandelange 20 on at

    Yes, same issue here, I also normally set it to CI_AS (for South Africa) ordering etc. and the setup failed. I rolled-back and did a fresh "Install" instance with Setup defaults (not my defaults) and it worked.

    The error from before was also the size of the entire screen (higher than 1440px) so I could not even click on Cancel / Ignore / Exit...

    I think this is rushed job from Microsoft as they were running out of time to publish this and keep their on-premise customers happy.

    I have not tried to do the upgrade from 8.2.2 org yet... Good luck

  • Steve Le Monnier Profile Picture
    Steve Le Monnier 959 on at

    Thanks everyone for the feedback.

    I did use the Deployment Manager over the weekend to add a second instance, and I can confirm the collation bug exists via that method also.

    To add insult to injury the MSCRM_CONFIG database does get created with the correct collation, it's just the organisational tenant that errors with a huge script error.

    I'm always amazed how this wasn't picked up during testing, unless it wasn't!

    I hope this gets fixed quickly as we now have V9 and lots of work pilling up and we can't use it. I would rather it was late and worked, than being on-time and useless.

    Steve

  • Community Member Profile Picture
    Community Member on at

    Hello Steve,

    We encoured the same problem during the creation of a new organization. For this particular issue we've contacted Microsoft (premier support). At the moment they are evaluating the issue. When they provide the solution, I'll get back.

    Cheers Arjan

  • Steve Le Monnier Profile Picture
    Steve Le Monnier 959 on at

    Hi Arjan

    Many thanks for the heads up on this. We've decided to install with the CRM default collation rather than the SQL default collation, as we had work stacking up. Hopefully when the installer is fixed we can re-install and return everything back to normal.

    Talking of broken installers, we've also detected a problem with adding users to a V9 on-premise install. Apparently the installer forgets to add inheritance to folder permissions in the CRMweb which causes an error when adding new users. There is a post with a solution that's easy to find and fixes the problem (after a reboot).

    Cheers Steve

  • Community Member Profile Picture
    Community Member on at

    Hi Steve,

    Let me clarify. The issue is not the installer but the tooling which creates an organization. A default organization will be created automatically when installing Dynamics 365 with a full server configuration. That's why you are getting the error.

    You can install Dynamics 365 v9 without a default organization and create one afterwards. However the Latin1_General_CI_AI collation is the only one without errors.

    Keep you posted.

    Arjan

  • crw Profile Picture
    crw 10 on at

    Same here:

    17:30:47|   Info| OrganizationCollation Latin1_General_CI_AS selected from UI page
    ...
    17:30:50|   Info| OrganizationInfo.OrganizationCollation: Latin1_General_CI_AS
    ...
    17:30:50|Verbose| The supported collation 'Latin1_General_CI_AI' matches the language of the database's collation 'Latin1_General_CI_AS'
    17:30:50|   Info| The case sensitivity of the database collation is correct.
    17:30:50|   Info| The database collation is correct.
    ...
    17:31:07|  Error| System.Exception: Error.ActionFailed Microsoft.Crm.Tools.Admin.SetDatabaseCollationAction ---> System.Data.SqlClient.SqlException: The statistics 'Attribute.ndx_Attribute_EntityId_ColumnNumber' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
    The object 'fn_CollectForCascadeShare' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
    The object 'fn_CollectForCascadeUnShare' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
    ALTER DATABASE failed. The default collation of database '#####' cannot be set to Latin1_General_CI_AS. 

  • Community Member Profile Picture
    Community Member on at

    Microsoft did indeed clarify, that it is a bug an that they are currently working on the fix. When this will be released is unknown

  • Steve Le Monnier Profile Picture
    Steve Le Monnier 959 on at

    Thanks for the confirmation, since the initial on-premise release, news of V9 has been very quite.

    PS. Has anybody been able to get licence keys to transition to V9, we've only been able to develop and test using a demo key, and they only last for 90 days!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans