Breaking news from around the world
Get the Bing + MSN extension
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
New to the forums. I have found that my Windows 10 version 1903 computers cannot install the CRM Outlook plugin update rollup 18. Anyone else having that issue or have tips how to resolve this? I've reproduced the issue on 3 computers with 1903 (1 with all updates for OS, 1 with no updates (only 1903), and my current computer, same version of office on all computers. Then with Windows 10 version 1809 (all OS updates applied), same version of office, the rollup 18 does install as expected.
Error: The type initializer for 'Microsoft.Crm.FeatureControlChecker' threw an exception. The type initializer for 'Microsoft.Crm.LocatorService' threw an exception. Unable to initialize the native configuration support external to the web worker process (HRESULT=0x80040154). nativerd.dll must be in %windir%\system32\inetsrv
Any tips is appreciated.
I had the same problem and found that .Net Framework > WCF Services > HTTP Activation needs to be installed on Windows Features. You can find further instructions here: github.com/.../778
That is awesome, thank you very much. That tip helped fix the issue. And just as a side note for others if they happen to come across this too.
I added the HTTP activation using powershell using this command:
enable-windowsOptionalFeature -online -featurename "WCF-HTTP-Activation" -all
It enabled HTTP activation for .NET 2/3 (not .NET 4.x like the GitHub article suggested). Even with that, the Rollup 18 patch was able to install.
Business Applications communities