Fatal Error while installing CRM updates in Dynamics 365 On A Back End Servers

-
I observed this fatal error while installing the update 2.1 for Dynamics 365 On Premise. The environment was a load balanced one with 2 Front End Servers, 2 Back End Servers, 1 SSRS Server and 1 SQL Server. The upgrade was attempted to be carried out in place, by just running the executable downloaded from the Microsoft official link. The Front End Server upgrades worked just fine and so did the SSRS Servers, but the Back End Ones kept failing  with a Fatal Error.

This error, however, did not popup when we attempted to upgrade from Dynamics 365 to 8.1 and 8.2 respectively. They were carried out in the exact same way as Update 2.1 (8.2.1).


The Environment & Issue

The Front End Servers were running the Web Application Server, Organization Web Service, Discovery Web Service, Help Server and the Deployment Web Service. The Back End Servers were running the Asynchronous Processing Service, Email Integration Service, Sandbox Processing Service, Deployment Tools and VSS Writer Service.

The log file after enabling tracing didn’t give much except for this error message (which doesn’t help at all)

10:56:11|   Info| InstallerException: 1603
10:56:11|  Error| System.Exception: Action Microsoft.Crm.UpdateWrapper.MspInstallAction failed. ---> Microsoft.WindowsInstaller.InstallerException: Fatal error during installation.
   at Microsoft.WindowsInstaller.Installer.ApplyPatch(String patchPackage, String installPackage, InstallType installType, String commandLine)
   at Microsoft.Crm.UpdateWrapper.MspInstallAction.Do(IDictionary parameters)
   at Microsoft.Crm.Setup.Shared.CrmAction.ExecuteAction(CrmAction action, IDictionary parameters, Boolean undo)
   --- End of inner exception stack trace ---, Error, RetryCancel, Option1
10:56:25|   Info| InputResult: Cancel
10:56:25|   Info| CrmAction execution time; MspInstallAction; 00:03:54.5708790
10:56:25|  Error| Exception occured when installing update:  System.Exception: Action Microsoft.Crm.UpdateWrapper.MspInstallAction failed. ---> Microsoft.WindowsInstaller.InstallerException: Fatal error during installation.
   at Microsoft.WindowsInstaller.Installer.ApplyPatch(String patchPackage, String installPackage, InstallType installType, String commandLine)
   at Microsoft.Crm.UpdateWrapper.MspInstallAction.Do(IDictionary parameters)
   at Microsoft.Crm.Setup.Shared.CrmAction.ExecuteAction(CrmAction action, IDictionary parameters, Boolean undo)
   --- End of inner exception stack trace ---
   at Microsoft.Crm.Setup.Shared.CrmAction.ExecuteAction(CrmAction action, IDictionary parameters, Boolean undo)
   at Microsoft.Crm.UpdateWrapper.HotfixMspInstaller.Install()
10:56:25|   Info| CrmAction execution time; PopulateUninstallDirectoryAction; 00:00:00.0156140
10:56:25|  Error| Install exception.System.Exception: Action Microsoft.Crm.UpdateWrapper.MspInstallAction failed. ---> Microsoft.WindowsInstaller.InstallerException: Fatal error during installation.
   at Microsoft.WindowsInstaller.Installer.ApplyPatch(String patchPackage, String installPackage, InstallType installType, String commandLine)
   at Microsoft.Crm.UpdateWrapper.MspInstallAction.Do(IDictionary parameters)
   at Microsoft.Crm.Setup.Shared.CrmAction.ExecuteAction(CrmAction action, IDictionary parameters, Boolean undo)
   --- End of inner exception stack trace ---
   at Microsoft.Crm.Setup.Shared.CrmAction.ExecuteAction(CrmAction action, IDictionary parameters, Boolean undo)
   at Microsoft.Crm.UpdateWrapper.HotfixMspInstaller.Install()
   at Microsoft.Crm.Setup.Shared.ComposedInstaller.InvokeInstall(Installer installer, IDictionary stateSaver)
   at Microsoft.Crm.Setup.Shared.ComposedInstaller.InternalInstall(IDictionary stateSaver)
   at Microsoft.Crm.Setup.Shared.ComposedInstaller.Install(IDictionary stateSaver)
   at Microsoft.Crm.UpdateWrapper.UpdateSetup.Install(IDictionary data)
   at Microsoft.Crm.Setup.Shared.SetupBase.ExecuteOperation()
10:56:25|Verbose| Method exit: Microsoft.Crm.UpdateWrapper.UpdateSetup.ExecuteOperation
10:56:25|   Info|  failed.
10:56:25|   Info|  Setup did not complete successfully.

Action Microsoft.Crm.UpdateWrapper.MspInstallAction failed.

Fatal error during installation.

10:56:25|  Error| Setup did not complete successfully.
10:56:25|Verbose| Method exit: Microsoft.Crm.UpdateWrapper.UpdateSetup.RunInternal
10:56:25|Verbose| Update Not Completed
10:56:25|Verbose| Update Not Completed
10:56:25|   Info| Dynamics 365 Server Update 2.1 (KB4013759) was not completed successfully because of the following problems:
 
Action Microsoft.Crm.UpdateWrapper.MspInstallAction failed.
Fatal error during installation.

Resolving the issue

The resolution was to go to Deployment Manager, then to Servers (which will list all your servers) and disable one of the Back End Servers/Disable All Running CRM Services, install the update in that Server/s and then enable it back on/start the stopped services.

When you try to disable a server, it will give you a warning that the services would be stopped. Just click OK.

This should disable the server and you can see it from the Server list.


Run the upgrade in the server, and once it’s done the server is restarted, go back to Deployment Manager and enable the server back/start the services.


These steps were carried out on the Back End Servers l had issues with and this resolved the issues! No errors were found!

Unfortunately, there is no information given by the Microsoft Support team as to why it happened, I have raised this with Microsoft for further investigation.

Comments

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