Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I faced a situation when I have different SQL servers installed on the server which is using for the Dev organizations and on the server for the others organizations.On the dev, we have SQL server 12.0.2000.8 and on the other one 13.0.5102.14.Which kind of problems I can get while delivering?
Also, sometimes I'm getting issues related to the records with ComponentState = 2 that are stored in the DB and do not give me the ability to import solutions if I don't remove them. Could it be related to the different SQL servers case?
Thanks for reaching out. We strongly recommend have the same SQL version between the different environments that you may have in your deployment.
However, the issue related to componentState =2 I don't think is related to that fact.
These is the list of the component states:
3 Deleted Unpublished
What kind of issues are you getting ?
The issue with a component state is the following:
1. I'm unregistering existing plugin assembly (usually plugins, but not workflows)
2. I'm trying to import a new version of a managed solution to the target environment. This version contains the same plugin assembly but with some modifications that are not compatible with a previous version. e.g. step was renamed/removed. or something that usually throws an exception while importing.
3. I'm getting an error while importing like "There should not be more than one component instance for a solution being upgraded"
The way how I'm resolving it:
After removing there are a lot of images, messages, plugin types, assemblies that have component state 2 or overwrite time is not default one. After removing all of them I can import my managed solution without any issues.
To import solutions I'm using a package deployer
Please let me know if you need additional details
For the plugin issue, have you tried by upgrading the version in visual studio?
I think you should open a case with Microsoft Support to get that fixed if the issue is still happening when you upgrade the plug in version within VS.
Business Applications communities