Dynamics 365 (on-premises), version 8.2 upgrade/import to v9.0.2 Failure

-
I have recently downloaded the MS on-premise installer for 9.0 which was released a few days ago, and I existing CRM servers set up and meeting the pre-requisites as stated here https://www.microsoft.com/en-us/download/details.aspx?id=57478&WT.mc_id=rss_alldownloads_all under System Requirements

The installation was successful, and I was able to create new vanilla organizations with no issues, but I cannot import (upgrade) any of the organizations from 8.2.2.  Here are some of the errors:

The following connections need to be closed before setup can continue:  Login: server\Administrator, Host: serverxxx.mmc, Database: xxxx_MSCRM  User: Administrator, Program: MSCRMmmc (seems like this is deployment manager?)
Error| Upgrade Organization with Id=xxxxxxxxxxxxxxxxx failed with Exception:

System.Exception: Error.ActionFailed Microsoft.Crm.Tools.Admin.UpgradeDatabaseAction ---> 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=xxxxxxxxxx' or one of its dependencies. The system cannot find the file specified.
   at Microsoft.Crm.DataUpgrade.DatabaseObjectChangeTracker.GenerateScriptForIndex(String tableName, String indexName, ISqlExecutionContext sqlContext)
   at Microsoft.Crm.DataUpgrade.DatabaseObjectChangeTracker.InsertObjectTrackerTableInput(List`1 inputData, String tableName, ISqlExecutionContext sqlContext)
   at Microsoft.Crm.DataUpgrade.DatabaseChangeTracker.TrackCustomDatabaseObjects()
   --- End of inner exception stack trace ---

The AttributeLookupValue (Id=81cde1dc-2241-db11-898a-0007e9e17ebd) entity or component has attempted to transition from an invalid state: ComponentStateName: Solution; ComponentOperation: Delete; ComponentSolutionType: Active; SolutionOperationContext: MoveSystemComponentToFirstPartySolution; IsProtected: False; FinalComponentState: Publish.

 An error occurred when trying import and upgrade organization database server.xxxxxx_MSCRM:
Microsoft.Crm.CrmException: Upgrade Organization with Id=1xxxxxxxxxxxxxxxxxx failed with Exception:
System.Exception: Error.ActionFailed Microsoft.Crm.Tools.Admin.UpgradeDatabaseAction ---> 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=xxxxxxxxx' or one of its dependencies. The system cannot find the file specified.

Therefore at present  8.2.2 org imports will fail when you attempt to do so and this looks a bug with the v9 on premise package.

Solution:
From  the Server Version 3020 (Insider) and 3034 (release). There is a bug in the Marketing Managed Solution. The script is the same but the version of the solution is a another.

This affected solution is found here: C:\Program Files\Dynamics 365\Setup\Serviceability\Latest\Actions_Org\Install\Packages\CRMApps\PkgCache_9_0_0002_3034\msdynce_MarketingSales\msdynce_MarketingSales

Option B:

Another option will be uncomment the marketingsales upgrade package in:

C:\Program Files\Dynamics
365\Setup\Serviceability\Latest\Actions_Org\Install\Packages\CRMApps\PkgCache_9_0_0002_3034\msdynce_MarketingSales\msdynce_MarketingSales\ImportConfig.xml

<!--<configsolutionfile solutionpackagefilename="msdynce_MarketingSalesPatch_managed.cab" publishworkflowsandactivateplugins="true" />-->

One of the above solutions will fix your issue.

Enjoy V9 on-prem



Comments

  1. saivenkat2 September 2020 at 05:57

    Thanks a lot very much for the high quality and results-oriented help. I won’t think twice to endorse your blog post to anybody who wants and needs support about this area.
    CRM

    ReplyDelete

Post a Comment

Popular posts from this blog

How to Query Microsoft Dataverse Data using SQL from Power BI or SSMS

-
Image
Microsoft in recent months made available a much requested feature by many with the additional way to access read-only data in Microsoft Dataverse. The TDS endpoint for Microsoft Dataverse allows read-only access to Dataverse for reporting and analytics requirements. The Tabular Data Stream (TDS) Protocol endpoint functionality is managed by an administrator with access to the Admin center. This feature becomes a game changer as many Microsoft customers who required this feature and often went down the root of the Data Export Service can now start exploring this capability Prerequisites: To get started using this feature, you will need to ensure that TDS endpoint is enabled as this is required to be able to use this feature via Power BI or SSMS. Sign into the Power Platform Admin Center :( https://admin.powerplatform.microsoft.com/environments ), and then select the appropriate sandbox environment. Note: Its always good practice to test new features in a Sandbox Environment Validate t
Read more

Users Unable to See Flow Button and run On Demand workflows in Dynamics 365 CE

-
Image
Overview. Dynamics 365 CE provides functionality to automate business processes in the background or on a click of a button requiring a user to initiate this automation. In this blog post the scenario is focused on an issue a user may experience while using dynamics 365 CE on automation which is initiated by a user looking to use an On Demand. This automation triggered by a user is called an on-demand workflow. Problem When a user goes into Dynamics 365,  they are unable to see or run a workflow/flow which may have been created. So how do you resolve this issue? Steps to Resolve System Settings 1.a) Login into the Power Platform Admin center ( https://admin.powerplatform.microsoft.com/environments ) and Select your Environment name > Settings  > Behavior . At this point validate that the " Show Power Automate on forms and in the site map " is toggled  1. b) Validate that the setting, you will need to navigate to Settings > Administration > System Settings >
Read more

How To Deploy Dynamics App For Outlook (On-Premise)

-
Purpose The purpose of this post is to set out the direction, steps,scope, and implementation approach for the Dynamics Outlook App configuration item Audience This post is intended for Technical Teams/Administrators looking to implement the Dynamics Outlook App for On-premise environments. Pre-Requisites Dynamics 365 with IFD Configuration Dynamics 365 Update 8.2.2.112 (KB4046795) Minimum ADFS requirement ADFS 3 upwards due to OAuth endpoint Minimum Exchange 2016 or 2013 with Cumulative Update 14 or later Office 2016 *Recommended, Office 2013 *Compatible Supported browsers for Outlook on the web Dynamics 365 App for Outlook can be used with Outlook on the web on the following browsers: Internet Explorer 10, Internet Explorer 11, or Microsoft Edge The following configuration is supported: Protected Mode is enabled for Internet security zone. To enable Protected Mode: in IE 10 or 11, go to Tools > Internet options > Security tab > Internet. Protected Mode
Read more