error while importing the solution Archives - Microsoft Dynamics 365 Blog http://microsoftdynamics.in/category/error-while-importing-the-solution/ Microsoft Dynamics CRM . Microsoft Power Platform Thu, 09 Jul 2020 17:56:50 +0000 en-US hourly 1 https://wordpress.org/?v=6.5.5 https://i0.wp.com/microsoftdynamics.in/wp-content/uploads/2020/04/cropped-Microsoftdynamics365-blogs.png?fit=32%2C32 error while importing the solution Archives - Microsoft Dynamics 365 Blog http://microsoftdynamics.in/category/error-while-importing-the-solution/ 32 32 176351444 Error – Assembly must be registered in isolation. while importing solution in Microsoft dynamics 365 On-premise environment http://microsoftdynamics.in/2020/07/09/error-assembly-must-be-registered-in-isolation-while-importing-solution-in-microsoft-dynamics-365-on-premise-environment/ Thu, 09 Jul 2020 17:56:50 +0000 http://microsoftdynamics.in/?p=3892 Doing some Browsing we end up Nishant Sir Blog, where he provided short and accurate Solution to the Error: Click Here For post 

Action failed for assembly 'AutoSubmitOrder, Version=1.0.0.0, Culture=neutral, PublicKeyToken=6b240a09e4448ad7': Assembly must be registered in isolation.

The User which were used to import the Solution was missing Deployment Administrator Role, So Deployment administrator role is the king of Global admin in On-Premise Environment
As per Microsoft Post: Click Here 

Deployment Administrators have unrestricted access to perform Deployment Manager tasks on all organizations and servers in a Dynamics 365 for Customer Engagement deployment.

The post Error – Assembly must be registered in isolation. while importing solution in Microsoft dynamics 365 On-premise environment appeared first on Microsoft Dynamics 365 Blog.

]]>

6 month back we were importing our Autonumber Solution to a Microsoft dynamics 365 On-Premise Environment and it failed with below error

Action failed for assembly 'AutoSubmitOrder, Version=1.0.0.0, Culture=neutral, PublicKeyToken=6b240a09e4448ad7': Assembly must be registered in isolation.

Doing some Browsing we end up Nishant Sir Blog, where he provided short and accurate Solution to the Error: Click Here For post 

Action failed for assembly ‘AutoSubmitOrder, Version=1.0.0.0, Culture=neutral, PublicKeyToken=6b240a09e4448ad7’: Assembly must be registered in isolation.

  • The User which were used to import the Solution was missing Deployment Administrator Role, So Deployment administrator role is the king of Global admin in On-Premise Environment
  • As per Microsoft Post: Click Here Deployment Administrators have unrestricted access to perform Deployment Manager tasks on all organizations and servers in a Dynamics 365 for Customer Engagement deployment.

Check1How to add new Deployment Manager

  1. Search Deployment Manager and Click Open as Administrator
  2. In the console tree, right-click Deployment Administrators, and then select New Deployment Administrator.

  3. In the Select User dialog box, in the Enter object name to select box, type the name of a user, who must exist in Active Directory, and then select Check Names.
  4. After the user name is accepted, select OK.

Reference: https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/deploy/deployment-administrators

The post Error – Assembly must be registered in isolation. while importing solution in Microsoft dynamics 365 On-premise environment appeared first on Microsoft Dynamics 365 Blog.

]]> 3892 Fields that are not valid were specified for the entity – Importing Solution Error mscrm 2011 , mscrm 2013 , mscrm 2015 http://microsoftdynamics.in/2015/02/25/fields-that-are-not-valid-were-specified-for-the-entity-importing-solution-error-mscrm-2011-mscrm-2013-mscrm-2015/ Wed, 25 Feb 2015 12:12:00 +0000 http://microsoftdynamics.in/2015/02/25/fields-that-are-not-valid-were-specified-for-the-entity-importing-solution-error-mscrm-2011-mscrm-2013-mscrm-2015/ Hey , I was importing a solution today from an other Organization and got a Error new to me :  Fields that are not valid were specified for the entity , as there was no description i was little confused , but after few R&D came up with perfect resolution of the error . Reason ...

The post Fields that are not valid were specified for the entity – Importing Solution Error mscrm 2011 , mscrm 2013 , mscrm 2015 appeared first on Microsoft Dynamics 365 Blog.

]]>
Hey , I was importing a solution today from an other Organization and got a Error new to me :  Fields that are not valid were specified for the entity , as there was no description i was little confused , but after few R&D came up with perfect resolution of the error .

Reason 

  • Organization “A” conatined attribute ‘new_mscrm’ that was of type “single line” ,Later  We changed that the field  to be an currency Type.
  • But in Organization “B” was containg same field ‘new_mscrm’ of type “Single line”.
  • When we tried to import back the new solution to test environment we got this Import failure message as the solution we were importing was having a field ‘new_mscrm’ of type Currency

Solution

  • Just delete the field in the Organization in which you are importing the solution and reimport the same solution to it
Hope this helped you Thanks

SOURCE : JUST2CODE.IN Subscribe to our YouTube channel : https://www.youtube.com/user/TheRussell2012

The post Fields that are not valid were specified for the entity – Importing Solution Error mscrm 2011 , mscrm 2013 , mscrm 2015 appeared first on Microsoft Dynamics 365 Blog.

]]> 2800