Please wait, loading...

 

Error – Assembly must be registered in isolation. while importing solution in Microsoft dynamics 365 On-premise environment

July 9, 2020

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

https://i0.wp.com/microsoftdynamics.in/wp-content/uploads/2020/04/Microsoftdynamics365.png?fit=640%2C651&ssl=1
Microsoft Dynamics Community Profile

Learn more