Personalized Community is here!
Quickly customize your community to find the content you seek.
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
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 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 | Upcoming TechTalks
I'm attempting to install rollup 18 on CRM 2011, but see an error message "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 (HRRESULT=0x80040154). natived.dll must be in %windir%\system32\inetsrv.
Any thoughts why this is occuring and how to resolve? thanks
This seem like something related to .Net framework on your machine. Could you please check following items?
1. Is natived.dll in %windir%\system32\inetsrv on your machine?
2. Is Asp.Net installed correctly on your machine?
3. Is .Net framework installed correctly on your machine?
The error message does not go into detail about the install process not being able to load any particular DLL. I think either your server is missing a windows feature or .NET Framework on the machine could be causing the issue as well as suggested by Andy.
Have a look at these links below
Thanks everyone, your responses were accurate... the actual solution I used was from here to re-add the IIS 6 features :
Business Applications communities