Dynamics 365 Server, version 9.0 On-Premises – issues and problems

4.5/5 - (2 votes)

The new version for Dynamics 365 version 9.0.2.3034 is a worse RTM version. I think there was no quality testing for this product. 🙁

There are many issues from technical part of view. Short overview:

On servers in my test environment, some prerequisites from installation are missing. The import or create of organization failed. (see “short issue list” below)

 

Migration from older version is not possible, you got problems with different things. Starting with enabled full-text catalog on organization, followed by error with “The AttributeLookupValue (Id=xxx) entity or component has attempted to transition from an invalid state…” and if you solve this by workaround you have the next issue with applying database updates…

 

In addition, I have some trouble with the App for Outlook while working with ADFS on Windows Server 2012 R2 and more… Frustrating.

 

Microsoft provides a hotfix for this with build number 9.0.2.3041 and if you install this, you will be able to import organization from earlier version like 8.2.3. BUT, then you have other issues. For example, I am no longer able to make a redeployment on the same deployment / installation… 🙁

Microsoft support says, between end of February until end of April an official update will be released. Hope Microsoft has a proper testing for this.

 

 

Short issue list:

Microsoft.Crm.CrmException: Error in Action: Bin\Microsoft.Crm.DataUpgrade.dll:TrackCustomDatabaseObjects on attempt 3. System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.SqlServer.Smo, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91’ or one of its dependencies. The system cannot find the file specified.

Solution:

Download & Install CLR + SMO (x64):

  1. Microsoft SQL Server System CLR Types: http://go.microsoft.com/fwlink/?LinkID=239644&clcid=0x409
  2. Microsoft SQL Server Shared Management Objects: http://go.microsoft.com/fwlink/?LinkID=239659&clcid=0x409

 

Microsoft.Crm.CrmException: Error in Action: Bin\Microsoft.Crm.Setup.DiffBuilder.dll:UpgradeIndexManagementDataWithoutDelete on attempt 3. System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Data.SqlClient.SqlException: Cannot drop index ‘cndx_PrimaryKey_ColumnMapping’ because it enforces the full-text key for table or indexed view ‘ColumnMappingBase’.

Solution: turn off full-text search for Quick find and wait more than 24 hours.

 

For other errors like

Error      : The AttributeLookupValue (Id=82cde3dc-2341-db11-878a-0006e9e27ebd) entity or component has attempted to transition from an invalid state: ComponentStateName: Solution; ComponentOperation: Delete; ComponentSolutionType: Active; SolutionOperationContext: MoveSystemComponentToFirstPartySolution; IsProtected: False; FinalComponentState: Publish.

You need support / a hotfix from Microsoft. Also refer this conversion: https://community.dynamics.com/crm/f/117/t/300064

 

Find more information about Dynamics 9.0 Server on-premises:

2 thoughts on “Dynamics 365 Server, version 9.0 On-Premises – issues and problems

  1. Hi Karin

    I agree very much with your post. We have been facing very similar/the same issues while upgrading from CRM2013 to Dynamics 365V9 on premise. We have been using as well the hotfix provided by MS.

    Btw – MS support told me that the final version should be available by end January. Well they didn’t specify which year.

    Just one question regarding your comment:
    “For example, I am no longer able to make a redeployment on the same deployment / installation…”

    What do you mean exactly ? Is this the issue which blocks you from reimporting another org via the Deployment Manager ? Because the Orgs are having the same GUIDs? If yes, there is unsupported workaround for this…

    Thanks
    Alen

    1. Hello Alen,

      what I mean with the statement of redeployment: I cannot make a copy from the database and import this on the same machine. If I have an organisation “vanilla” in the system, make backup and restore from database to “vanilla2” and import this into the deployment as “vanilla2”, the import fails. And yes, the orgid’s have the same id and the import process should calculate another one. I did not make a support case for this and wait for the next update. This should be available until the end of April.

      Kind regards.

Leave a Reply

Your email address will not be published. Required fields are marked *