web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Plugin registration tool v9 unregisters all message processing steps

(2) ShareShare
ReportReport
Posted on by 2,100

I exported a solution from a Dynamics 365 v8.2 instance. The solution contains a plug-in assembly with ten plug-ins and at least two steps registered for each plug-in. Several of the plug-in steps also have pre- and post-images defined for them.

In a Dynamics 365 v9 instance, I imported the solution and then published all customizations.

I then opened the v9 plug-in registration tool and saw that all plug-ins and steps were shown.

Later, I needed to update one of the plug-ins so I made the change in Visual Studio 2017, rebuilt the plug-in assembly and used the v9 plug-in registration tool to update the assembly.  I was careful to make sure that I selected the checkbox to include all plug-in steps when updating the assembly.

After about 30 seconds, I started getting the feeling that something was wrong. Normally, updating a plug-in assembly only takes 5 seconds or so.

Finally, the message box appeared indicating that the plug-in assembly updated successfully.

Unfortunately, the v9 plug-in registration tool unregistered all plug-in steps... at least 20 of them!

Hopefully someone sees this and can avoid running into the same problem.  When using the v9 plug-in registration tool, I would be sure that you have a backup of the plug-in assembly and all processing steps before updating an assembly. Otherwise, it might take you a while to put all the pieces back together.

*This post is locked for comments

I have the same question (0)
  • Aric Levin - MVP Profile Picture
    30,190 Moderator on at

    Hi Tim,

    Where the plugin messages removed or where they just deactivated/disabled?

  • qqqqqqq Profile Picture
    on at

    @Tim I can confirm the same behaviour. The killer here is you need to use the v9 plug-in registration tool as you need it to support TLS 1.2. 

    A fix really needs to come from Microsoft as this is painful.

  • wtc.nvorhees Profile Picture
    on at

    I experienced the same issue, however once the assembly has been updated/registered through the V9 plugin reg tool subsequent updates appear to work normal.

  • Suggested answer
    Arun Vinoth Profile Picture
    11,615 Moderator on at

    We experienced it, but not quite consistent. Created a ticket with MS support, they closed it as it was not reproducible.

    Luckily we had another environment with steps & images registered. Exported them in a solution & imported to solve the headache.

    Better to keep a backup solution of plugin & steps.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans