Dynamics 365 CRM On premise Unable to Load plug-in assembly

背景介绍：

本地部署Microsoft Dynamics CRM 9.0正常可用，后打补丁到9.0.16.7，打开系统quote报 “ Unable to Load plug-in assembly” 错误（打商机opportunity窗体时也会报“Assembly content(Microsoft.Dynamics.Sales.Plugins, Version=9.0.1.0) does not match the expected assembly identity (Microsoft.Dynamics.Sales.Plugins, Version=9.0.0.0)”错误）。

  

图1-1 打开报价单报unable to load plug-in assembly错误

 

 

 

 图1-2 点击打开商机报不同版本的错误

 

解决步骤：

1、在bing以“unable to load plug-in assembly”关键搜索，发现补丁9.0.14.12有关于workflow和plug-ins的问题：

• Workflow or Plug-ins were not triggered on the creation of a Document Location record.
• Creation of an opportunity or associate a web role to an entity permission would result in the following error message, “Assembly content(Microsoft.Dynamics.Sales.Plugins, Version=9.0.1.0) does not match the expected assembly identity (Microsoft.Dynamics.Sales.Plugins, Version=9.0.0.0)”

      具体可看14补丁内容 https://support.microsoft.com/en-us/help/4538593

2、通过步骤1 发现如果是补丁打到9.0.14.12应该是可以解决问题的，但打开server manager发现组织的version一直是9.0.9.4，如下图

 

 

图2-1 原来组织图没有截，这里version 的情况大家可以看看

 图2-2 在CRM中查看版本也发现CRM服务版本与数据库版本不致 

 

3、在bing中搜索“Dynamics CRM version mismatch with DB”，大家可找到如下文章介绍 https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/278383/8-2-2-112-update---version-mismatch-with-db---is-that-normal，发现如果CRM服务的版本与数据的版本不致这种现像是不正常的，因为系统在打补丁的时候，当有多个组织时，系统不会自动更新组织的版本，这个时候需要我们手动点击一下右侧的更新(Update)按钮，手动更新组织的版本（当组织只有一个的时候，是否自动更新组织的版本尚未测试）。根据以上文章提示，我新建一个组织的时候，发现组织版本与服务是一致的，并且登录系统发现没有报错，于是马上手动更新目标组织的版本，更新后再登录系统，发错报错解决。

 

 图 3-1 打完补丁后CRM服务版本

图 3-2 新建一个salesdev组织后，组织的版本与服务的版本是一致的

 图 3-3 手动升级目标组织 

图 3-4 升级完成后登录系统，发现服务与数据库的版本已一致，并打开报价单，错误解决。

附外国网友的互动供大家学习：

Shannon Davis asked a question on 24 Apr 2018 1:00 PM

 

8.2.2.112 update - version mismatch with DB - is that normal?

Verified

Hello all, we recently updated our 8.2 on-premises CRM to 8.2.2 (the latest released update from October).

Since doing so, NOTHING is working.  Views don't work, ribbons disappear, links don't work, basically the whole system is unusable. 

I did observe however that the database version was different from the server version.  Is that normal?  There was no update file for the database. 

Version 1612 (8.2.2.112) (DB 8.2.0.749) on-premises

 

Alex Shlega responded on 24 Apr 2018 2:10 PM @ashlega 

8.2.2.112 update - version mismatch with DB - is that normal?

Unanswered

Hi,

 for what it's worth, when a new organization is created for 8.2.2.112, it gets 8.2.2.112 DB version.. Are you offered "Upgrade Organization" option when looking at that organization in the deployment manager?

technet.microsoft.com/.../dn920271.aspx

 

Aric Levin responded on 24 Apr 2018 6:30 PM 

8.2.2.112 update - version mismatch with DB - is that normal?

Verified 

Hi Shannon,

I have seen in Online mismatches between the CRM Version and the database version.

Online the best course of action is to contact MS Support and request them to fix it.

Since this issue you are encountering is On-Premise, it is likely that your CRM Server got updated, and the Server has multiple organizations, but not all organizations did get updated. If that is the case, go to deployment manager (as Alex suggested above), and upgrade each of the organizations.

If you are unable to do that, or if you do not get an option to upgrade a particular organization, I would contact MS Support for help with this issue.

Hope this helps.