locked
custom workflow in mscrm online : could not load file or assembly plugin registration RRS feed

  • Question

  • Hi,

    I have migrated workflow from CRM 2011 to CRM 2013 on premise and then on to CRM online , it gets updated succesfuly but when I run it below error is coming . I have changed the .net Framework version to 4.5.

    "Unhandled Exception: Microsoft.Crm.CrmException: Unexpected exception from plug-in (Execute): CRM_Notification_Workflow.Notification: System.IO.FileNotFoundException: Could not load file or assembly 'PluginRegistration, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified"

    Friday, December 19, 2014 7:18 AM

All replies

  • It looks like your workflow assembly has a reference to the PluginRegistration.exe assembly. There is no reason for it to have this. I expect that this worked OK in CRM 2011 as the PluginRegistration.exe assembly (v 5.0.0.0) was on the server.

    If you have the source code, the way to resolve this is to remove the reference in the source code, recompile, and update the assembly in CRM


    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    Friday, December 19, 2014 10:10 AM
    Moderator
  • Thanks David , I did the same thing and the error is gone now but I am getting different error now while registering itself . I have checked each and every dll's version and they are 6.0 only but somewhere this reference is being is used and im not able to figure it out.

    Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: Unable to load plug-in assembly.

    Monday, December 22, 2014 11:50 AM
  • Are you using the Microsoft.Xrm.Sdk.dll from the CRM 2015 SDK in your project?  It looks like you may be referencing older SDK dll's.  If so, you will need to remove the old SDK dll's, reference the newer ones, check the code to make sure that nothing needs updated due to changes in the SDK dll's and recompile.

    Jason Peterson

    Tuesday, December 23, 2014 3:34 PM