CRM2011 Plugin tool not allowing update of existing DLL [closed]

Question

Closed. This question is off-topic. It is not currently accepting answers.

---

Want to improve this question? Update the question so it's on-topic for Stack Overflow.

Closed 8 years ago.

Improve this question

I am currently having a problem where when I try to update an existing DLL, if I update it with the location of Database then I have the following error being returned:

Error Code: 2147204725

Message: Plug-in assembly does not contain the required types or assembly content cannot be updated

However if I try to use the disk location option then I have a different error message:

Error Code: 2147220906

Message: Assembly must be registered in isolation.

Yet I do not understand why this is. Currently I have tried the following:

• Making sure I am a Deployment Manager (I am not deploying to a Sandbox, as I am trying to update the existing one that is on the server.)

• A colleague who is able to update the plugin has sent me the DLL which he has checked works, to ensure that it is not the DLL that is the problem

• I have tried using the plugin tool on the colleagues computer, to ensure that the version is not the problem - but it still does not work for me.

• The colleague has tried to use the plugin tool on my machine. However when they do then they get the same errors as I do (although on their machine it works just fine for them but not myself)

Does anyone have any suggestions on what could be my problem and why I can't seem to update a plugin on my machine?

Thanks

Answer 1

The error 2147204725 you are getting, could occur when the class name in your plugin is changed.

Your plugin may be registered the first time with a class named PluginClassName1, for example, and then registered (updated) a second time, after the class PluginClassName1 is changed to PluginClassName2. In this case, the plugin type, which is the plugin class implementing IPlugin, is not retrieved in the already registered assembly.

Other causes could be changing the original assembly metadata (Culture, PublicKeyToken, Name, Version) or the signature key.

To solve the resulting issue, you should unregister the assembly and then re-register it again and also re-add the related steps/images.