Managed solution import (upgrade) fails - missing type from plugin assembly

(0) Share

Report

Posted on by Community Member

We have a version of our product in the wild, released as a Managed Solution with a Plugin Assembly.

Since this release, we have developed new Plugins added to the existing assembly.

However, when attempting to upgrade the Managed Solution while using the import option to Maintain Existing customizations, the import fails and claims that either there is a missing type from the Plugin Assembly or else that the Plugin Assembly is not updatable. (The trace log is loquacious but says nothing more meaningful.)

I have tried bumping the solution and assembly versions to see if CRM is perhaps being picky about how I version changes; neither has made a difference.

Since I dev with Unmanaged Solutions, I was surprised to see this; and I’m out of ideas, since reflector confirms that both my deployed assembly and newly compiled ones expose the same types (plus the ones added to the new one).

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Community Member on at

Like (0)

Report
Copy link

Link copied!

The original sdkmessageprocessingstep has been disabled and replaced. (8 times for other plugins that appear to be processed successfully)

Unable to load the plugin type: [our.plugin.here]

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Here is the error snippet from log:

The original sdkmessageprocessingstep has been disabled and replaced. (8 times for other plugins that appear to be processed successfully)

Unable to load the plugin type: [our.plugin.here]

Was this reply helpful? Yes No
Inogic 748 on at

Like (0)

Report
Copy link

Link copied!

You may want to check the version # of the plugin assembly and set it to match the version of the assembly included in the installed managed solution.

You could also try to manually unregister the plugin using plugin registration tool.

HTH

Sam

Was this reply helpful? Yes No
Nizar JLASSI 2 on at

Like (0)

Report
Copy link

Link copied!

Hi Liz P,

Is the managed solution yours ? or you get it form another publisher ?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Yes, it is our solution. In fact it's two packages that work together. The team has since found that if you install package 2 and then package 1, it seems to load. However our client configuration require that it be possible to install package 1 standalone; and then optionally install package 2 as well.

Was this reply helpful? Yes No
Verified answer

Nizar JLASSI 2 on at

Like (0)

Report
Copy link

Link copied!
In this case,

Export the new version of your managed solution and extract it in a separate folder.

Open Solution.xml file and edit it in a text editor.

Change the unique name of the managed solution :

<ImportExportXml version="6.0.0001.0061" SolutionPackageVersion="6.0" languagecode="1033" generatedBy="OnPremise" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <SolutionManifest>

    <UniqueName>ManagedSolutionUniqueName</UniqueName>

    <LocalizedNames>

      <LocalizedName description="Managed Solution Friendly Name" languagecode="1033" />

      <LocalizedName description="Managed Solution Friendly Name" languagecode="1036" />

    </LocalizedNames>

with a new unique name :

<ImportExportXml version="6.0.0001.0061" SolutionPackageVersion="6.0" languagecode="1033" generatedBy="OnPremise" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <SolutionManifest>

    <UniqueName>NewManagedSolutionUniqueName</UniqueName>

    <LocalizedNames>

      <LocalizedName description="Managed Solution Friendly Name" languagecode="1033" />

      <LocalizedName description="Managed Solution Friendly Name" languagecode="1036" />

    </LocalizedNames>

- Save the file and re-compress the folder.

- Rename the new compressed solution file with a new name.

Now, you will have two solutions :

* one with the old name (we will call it Solution A)

* and the second one with the new unique name (we will call it Solution B)

- Go to your organization > Settings > Solutions and click on Import Solution.

- And Import the solution B (with the new unique name).

- After importing the solution B, delete the old solution already existing in your organization (we will call it solution C). Don't worry, neither data nor entities will be deleted.

- After deleting the solution C, import the solution A.

- Delete solution B.

This method is to use when you have an installed managed solution with an old component (entity, chart, dashboard, etc...) that you want to replace with a new version of the same managed solution but without this ild component.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

It happens to me always when I forget to uninstall the Plugin Profiler before importing a solution. However usually this error is caused because something is using and so blocking the plugin assembly. What I usually do is an IISRESET or to stop all the Services that are maybe using the plugin dll like the asynchronous processing service

Was this reply helpful? Yes No