Profiler - Plug-in type does not exist in assembly error RRS feed

  • Question

  • I've seen this error asked a couple of times but none of the answers seem to fix my problem. As per the thread title, I'm trying to use profiler to debug a plug-in problem we are experiencing in CRM online. But it's not playing ball and throws the message:

    Unhandled Exception: System.InvalidOperationException: The plug-in type "<my plugin name>" does not exist in the specified assembly.
       at PluginProfiler.Library.AppDomainProxy.InitializeProxy(String assemblyFilePath, String typeName, String logFilePath)

    This is how I've set up the profiler:

    • Downloaded the latest SDK
    • Connected Plugin Registration Tool to my org (CRM 2013 Online)
    • Installed the Profiler and started a Profile on my plugin
    • Recreated the error to get the profile exception and clicked on download log
    • Clicked on the debug button back in Plugin Registration Tools
    • Selected my assembly and the log file I just downloaded
    • Attached Visual Studio to plugin registration tool
    • Clicked on start execution
    • Profiler logs out: 
    Profiler> Plug-in AppDomain Created
    Profiler> Profiler AppDomain Unloaded
    • But I get the above error

    I have checked the following is correct: 

    • It's the correct log file with the profile trace. I have opened it to make sure it's not just a business process exception trace file
    • I have redeployed my plugin DLL to make sure I don't have a version mismatch
    • When starting up the profiler debug it finds the correct plugin in the drop down when you select the assembly, and it also automatically selects it... but still throws the above error
    • The plugin definitely exists. I haven't accidentally attached a wrong DLL or anything. 

    The only thing I can think of that I'm doing differently is I am merging 2 DLLs (using ILMerge) as I am also using a 3rd party DLL. But it doesn't matter which DLL I pick it always throws the above error.

    Has anyone got any other ideas for me?

    Thanks in advance!


    Tuesday, January 21, 2014 11:33 PM

All replies

  • Hello Conor

    I am also facing the same issue as mentioned above. Did you manage to resolve it?

    If yes, please let me know the solution.

    Thanks in advance!!


    Bhavika Patel

    Saturday, March 22, 2014 12:22 PM
  • Hi Conor,

    I was facing the same problem a long time. Not in CRM Online, but in OnPremise.

    The problem is, that it seems not to be possible to debug Plugins with the Registration Tool, when you merged them using ILMerge. I was only able to debug standard Plugins that way.

    I have not figured out yet a way to debug (il)"merged" Plugins that way.

    I hope that helps,


    Saturday, March 22, 2014 1:43 PM
  • Same issue here with latest plugin registration tool ( and CRM online 2013.

    Anyone any ideas?

    Wednesday, May 14, 2014 8:51 PM
  • If anyone finds this:

    The problem was fixed by updating the 




    to the same version that came with the latest version of the SDK.

    My IDE was pointing at an old version.


    • Proposed as answer by toutski Wednesday, May 14, 2014 9:07 PM
    Wednesday, May 14, 2014 9:07 PM
  • @Toutski That didn't fix my problem.  Did you deploy an ILMerged Plugin to CRM?
    Thursday, June 25, 2015 7:00 PM
  • I was getting this error when attempting to debug my non-ILMerged plugin dll.  This was due to the base class of the plugin being in common dll, and since it was ILMerged as a part of the Execution Context, the type didn't match.

    The fix for me was to ensure the ILMerge was creating the PDB files by removing the /ndebug from the command line (or else i couldn't attach the Debugger in VS), and then select the ILMerged version of the plugin and everything worked fine after that.

    Thursday, June 25, 2015 8:45 PM
  • I was getting this. I was scratching my head trying to debug a simple plugin created using the SDK plugin template on CRM2016 online.

    It turned out my shortcut to my plugin registration tool was pointing to the 2015 SDK. Solution was to use the plugin registration tool from the 2016 SDK.

    Wednesday, May 18, 2016 10:03 AM