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 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 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
The time had come to upgrade from CRM 2011 to CRM 2013. So I upgraded the software and I now find that I can't upgrade the organisation due to there being references to an old Accelerator plugin. I have used the tool LegacyFeatureCheck and it returns details of the components which are all from the Accelerator plugin.
As the software is now CRM 2013 how can I remove these components? I can't enable the Organisation. Is there a command I can issue to just force their deletion. Or can I browse to them in the database using SQL Management Studio and delete them from there. They certainly aren't required anymore.
If so where will they be saved or what command line utility can I use to delete them?
There's no supported way to remove these components, as the web service API only gives access to an enabled organisation.
Theoretically it should be possible to make the changes via SQL Management Studio, but this would be unsupported, and there is no obvious way to know exactly what to change.
Your best option would be to install a CRM 2011 instance, import the organisation into it, remove the components, then you should be able to import and upgrade the organisation into the CRM 2013 instance
Thanks for your help.
I have gone back to server image with CRM2011 and then applied rollup 18. I then used the LegacyFeatureCheck to identify the components that referred to the 2007 web features and either deleted them (there were just two) and with the final one, edited the Java script to remove the references. This was all done via the CRM screens. I then published these changes. When I reran the LegacyfeatureCheck there were no errors reported. Great ! So I did an in place upgrade to the CRM2013 and chose my organisation in the process. When the upgrade had finished the organisation has a Status of Failed in the Deployment Manager and it shows that an update is available. I have another organisation called DemoData and I was able to update that OK which would indicate that the software install is good.
Is it possible to have another go at upgrading the organisation database or run through a wizard again?
In the meantime I have applied CRM2013 SP1 and the latest rollup 4
I have deleted the organisation and then tried to import it. On importing it says it will update the database and all seems well as it runs through but then the Deployment Manager errors saying there is a problem with the snap in. I'm running a Windows update to make sure everything is up to date and then will try again.
Business Applications communities