Looking for PowerObjects? Don’t worry, you’re in the right place! We’ve been part of HCL for several years, and we’ve now taken the final step in our acquisition journey: moving our website to the HCL domain. Nothing else is changing – we are still fanatically focused on Microsoft Business Applications!

PowerObjects Blog 

for Microsoft Business Applications


Installing Outlook CRM Client - Mandatory updates for Microsoft Dynamics CRM could not be applied successfully

Post Author: Joe D365 | January 21st, 2010

We recently ran into an interesting issue. During a rollout of the outlook crm client on various workstations running both vista and xp, we had one workstation where we simply could not configure the outlook crm client. The errors were "Mandatory updates for Microsoft Dynamics CRM could not be applied successfully" and in the actual log file "System.Configuration.ConfigurationErrorsException: Unrecognized configuration section system.serviceModel. (c:WINDOWSMicrosoft.NETFrameworkv2.0.50727Configmachine.config"

 

The interesting sections of the configuration log file are:

15:07:32| Error| Microsoft.Crm.Setup.Common.SetupException: Mandatory updates for Microsoft Dynamics CRM could not be applied successfully. Try running the application again.
at Microsoft.Crm.Config.Client.UI.ServerUrlPage.CheckForUpdates(ClientConfigInfo configInfo)
at Microsoft.Crm.Config.Client.UI.ServerUrlPage.InitializeServerInfo(Uri discoveryUrl, Uri extranetDiscoveryUrl)
at Microsoft.Crm.Config.Common.UI.ServerUrlPage.ServerUrlPage_NextClicked(Object sender, NavigationEventArgs e)
at Microsoft.Crm.Setup.Common.UI.WizardPage.RaiseNextClicked(Object sender, NavigationEventArgs e)
at Microsoft.Crm.Setup.Common.UI.Wizard.NextButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.PerformClick()
at System.Windows.Forms.Form.ProcessDialogKey(Keys keyData)
at System.Windows.Forms.Control.ProcessDialogKey(Keys keyData)
at System.Windows.Forms.Control.ProcessDialogKey(Keys keyData)
at System.Windows.Forms.ContainerControl.ProcessDialogKey(Keys keyData)
at System.Windows.Forms.Control.ProcessDialogKey(Keys keyData)
at System.Windows.Forms.TextBoxBase.ProcessDialogKey(Keys keyData)
at System.Windows.Forms.Control.PreProcessMessage(Message& msg)
at System.Windows.Forms.Control.PreProcessControlMessageInternal(Control target, Message& msg)
at System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg), Error, OK, Option1

11:48:10| Error| Configuration exception.System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.Configuration.ConfigurationErrorsException: Unrecognized configuration section system.serviceModel. (c:WINDOWSMicrosoft.NETFrameworkv2.0.50727Configmachine.config line 146)
at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors schemaErrors)
at System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors()
at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)
--- End of inner exception stack trace ---

 

After trying all the usual fixes, including burning incense, the fix was to remove Dot Net Framework 3.5 SP1. After removing dotnet 3.5 Sp1, the client was able to configure the outlook crm client right away even without a reboot.

Joe CRM
By Joe D365
Joe D365 is a Microsoft Dynamics 365 superhero who runs on pure Dynamics adrenaline. As the face of PowerObjects, Joe D365’s mission is to reveal innovative ways to use Dynamics 365 and bring the application to more businesses and organizations around the world.

5 comments on “Installing Outlook CRM Client - Mandatory updates for Microsoft Dynamics CRM could not be applied successfully”

  1. Hi, I found this worked for a problematic user install. Thank you very much. Can I ask if you resolved why this was conflicting for such a small minority of users? Also does MSD not need .NET 3.5 SP1 then?

    1. Hi Brett,

      We think this is perhaps caused by the order that dot net and dot net sps are installed. We were not able to replicate this issue on a test machine where dot net 2,3,3.5 were installed in an orderly fashion. We also tested applying dot net 3.5 sp1 AFTER the outlook crm client is configured and this worked ok.

  2. Hello everyone, my problem is this. I have a notebook with Windows 7, Outlook 2007 and Framework 3.5 without SP1; wants to work from home or when traveling with Dynamics CRM for Outlook with Internet access but not join it to domain and without VPN. I have already configured correctly and I can access IFD externally but with Outlook 2007 not. (It is configured with the port 5555)

    The test I did in the setup wizard was: select An online service provider and then type the web address to use correctly in Internet Explorer ...but appears message "Mandatory updates for microsoft dynamics crm could not be applied successfully. Try running the application again."
    What can be causing the error?

    On the server the necessary services are running. Also, if I can connect with IE I suppose we should do with the Outlook ...
    An extra information that I can give is that the external domain of the company assigned dynamic ip, therefore is changing.

    Thanks for the help! I'm new to this topic ...

    1. Hi,
      As a test, try to remove your dot net framework 3.5 then try to install and configure the outlook crm client. Also, look in your crm setup log. This should have detailed info on why it is failing.

PowerObjects Recommends