Title Missing server side dependencies.
Severity 1 - Error
Category Configuration
Explanation
[MissingWebPart] WebPart class [8307a780-2546-f10b-551f-0e692d0fce39] (class [Microsoft.Office.Server.Search.WebControls.SearchApplicationShortcutsList] from assembly [Microsoft.Office.Server.Search, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [SharePoint_Content_Admin], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [SharePoint_Content_Admin], but are not installed on the current farm. Please install any feature or solution which contains these web parts.This issue usually occurrs when you have Central Admin on several servers and/or you have disabled the SharePoint Foundation Web Application Service on servers in the farm.
[MissingWebPart] WebPart class [63104819-a32f-88b6-ab4a-7bbd4fbb40e8] (class [Microsoft.Office.Server.Search.WebControls.FarmSystemStatus] from assembly [Microsoft.Office.Server.Search, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [SharePoint_Content_Admin], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [SharePoint_Content_Admin], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [9328cc53-be2c-1cca-f310-ddd573a106a5] (class [Microsoft.Office.Server.Search.WebControls.FarmSearchApplicationList] from assembly [Microsoft.Office.Server.Search, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [SharePoint_Content_Admin], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [SharePoint_Content_Admin], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [4465f30a-0604-4d3c-39fd-ecdb8812f3f3] (class [Microsoft.Office.Server.Search.WebControls.SearchTopologyOverview] from assembly [Microsoft.Office.Server.Search, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [SharePoint_Content_Admin], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [SharePoint_Content_Admin], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [a9bc1035-cf56-e003-8a4d-fff0bb3da148] (class [Microsoft.Office.Server.Search.WebControls.SearchApplicationSystemStatus] from assembly [Microsoft.Office.Server.Search, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [SharePoint_Content_Admin], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [SharePoint_Content_Admin], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
I resolved the issue by following these steps:
1. Visit the Farm Search Administration site
2. Click the shortcut links to the right on SSA site
3. Visit the pages on your other servers with Central Admin in the farm.
3. If you have stopped the SharePoint Foundation Web Application service on a server, problem can be resolved by provisioning the service again. If however you do not want the service on this service, obviously this is not a valid solution.
In my case the problem was due to provisioning Central Admin on another server (by accident) and removing the AAM to this server was not sufficient.
I had to remove the server from farm and then re-add it again. While server was out of the farm, i ran an IISRESET + resettet SP Timer service on my current CA server. Voila! Rule dissapeared.
