Dynamics CRM in the Field

Information from the Microsoft Dynamics CRM PFE team working in the field

Error message “Assembly must be registered in isolation” when registering Plugins in Microsoft Dynamics CRM 2011

Error message “Assembly must be registered in isolation” when registering Plugins in Microsoft Dynamics CRM 2011

Rate This
  • Comments 9

I had a customer run into the error message “Assembly must be registered in isolation” when trying to register a CRM 2011 plugin. We found this error was being thrown because the user was not a deployment administrator.  If the user is only a System Administrator in the organization, they will be forced to register plugins in the sandbox isolation mode.  After adding the user as a deployment administrator he was able to register the plugin to database without any issues.

In the Security Restrictions section of the following MSDN article it states, “There is a security restriction that enables only privileged users to register plug-ins. For plug-ins that are not registered in isolation, the system user account under which the plug-in is being registered must exist in the Deployment Administrators group of Deployment Manager.“ 

Register and Deploy Plug-ins
http://msdn.microsoft.com/en-us/library/gg309620.aspx

Generic Error

image

Detailed Error

image

Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: Action failed for assembly 'SamplePlugins, Version=0.0.0.0, Culture=neutral, PublicKeyToken=829f574d80e89132': Assembly must be registered in isolation.
Detail: <OrganizationServiceFault xmlns="http://schemas.microsoft.com/xrm/2011/Contracts" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
  <ErrorCode>-2147220906</ErrorCode>
  <ErrorDetails xmlns:a="http://schemas.datacontract.org/2004/07/System.Collections.Generic" />
  <Message>Action failed for assembly 'SamplePlugins, Version=0.0.0.0, Culture=neutral, PublicKeyToken=829f574d80e89132': Assembly must be registered in isolation.</Message>
  <Timestamp>2011-08-17T19:15:20.1988144Z</Timestamp>
  <InnerFault>
    <ErrorCode>-2147220906</ErrorCode>
    <ErrorDetails xmlns:a="http://schemas.datacontract.org/2004/07/System.Collections.Generic" />
    <Message>Action failed for assembly 'SamplePlugins, Version=0.0.0.0, Culture=neutral, PublicKeyToken=829f574d80e89132': Assembly must be registered in isolation.</Message>
    <Timestamp>2011-08-17T19:15:20.1988144Z</Timestamp>
    <InnerFault i:nil="true" />
    <TraceText i:nil="true" />
  </InnerFault>
  <TraceText i:nil="true" />
</OrganizationServiceFault>

Server stack trace:
   at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.Xrm.Sdk.IOrganizationService.Create(Entity entity)
   at Microsoft.Xrm.Sdk.Client.OrganizationServiceProxy.CreateCore(Entity entity)
   at PluginRegistrationTool.RegistrationHelper.RegisterAssembly(CrmOrganization org, String pathToAssembly, CrmPluginAssembly assembly) in C:\Users\jemorl\SDK\CRMSDK 2011\tools\pluginregistration\RegistrationHelper.cs:line 227
   at PluginRegistrationTool.PluginRegistrationForm.btnRegister_Click(Object sender, EventArgs e) in C:\Users\jemorl\SDK\CRMSDK 2011\tools\pluginregistration\PluginRegistrationForm.cs:line 461

  • Thank You!

  • Yes thanks.  We were having this issue when importing a solution out of our development system that contained a plugin we wrote.  Adding the user as a deployment admin fixed it!  

  • Thanks a lot.

  • Thanks!

  • Awesome!! It was driving me nuts for a while.

    Thanks a lot.

  • Thanks!

  • Thanks for the explanation :)

  • I just restarted Microsoft Dynamics CRM Asynchronous Processing Service and again registered the plugin and it worked.

  • Great blog post! Thank you

Page 1 of 1 (9 items)
Leave a Comment
  • Please add 6 and 6 and type the answer here:
  • Post