背景介紹：web
本地部署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錯誤app
圖1-2 點擊打開商機報不一樣版本的錯誤ide
解決步驟：post
一、在bing以「unable to load plug-in assembly」關鍵搜索，發現補丁9.0.14.12有關於workflow和plug-ins的問題：學習
具體可看14補丁內容 https://support.microsoft.com/en-us/help/4538593測試
二、經過步驟1 發現若是是補丁打到9.0.14.12應該是能夠解決問題的，但打開server manager發現組織的version一直是9.0.9.4，以下圖this
圖2-1 原來組織圖沒有截，這裏version 的狀況你們能夠看看spa
圖2-2 在CRM中查看版本也發現CRM服務版本與數據庫版本不致 3d
三、在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 升級完成後登陸系統，發現服務與數據庫的版本已一致，並打開報價單，錯誤解決。
附外國網友的互動供你們學習：
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
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
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.