Quantcast
Channel: SharePoint 2013 - Setup, Upgrade, Administration and Operations forum
Viewing all articles
Browse latest Browse all 21070

Missing server side dependencies for Search Service when Health Analyzer job runs on WFE server (not central admin server)

$
0
0

Hi there

I am experiencing this Health Analyzer error relating to Missing Server Side dependencies which I am unable to fix, will go into more detail below.

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 [SP_AdminContentDB], 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 [SP_AdminContentDB], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[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 [SP_AdminContentDB], 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 [SP_AdminContentDB], 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 [SP_AdminContentDB], 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 [SP_AdminContentDB], 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 [SP_AdminContentDB], 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 [SP_AdminContentDB], 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 [SP_AdminContentDB], 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 [SP_AdminContentDB], but are not installed on the current farm. Please install any feature or solution which contains these web parts.


I'm aware this is a very common issue, and has been around since SP2010.

The usual fix is to load searchfarmdashboard.aspx and searchadministration.aspx pages and some even suggest clicking on the "Shortcuts" links for "Add new link" and "Manage links".

This doesn't seem to fix the issue for me.

After some investigation, if the OWSTIMER.exe process for this Health Analyzer job runs on the same server(s) that host Central Administration, the error goes away.

If the timer job executes on Web Front End server (that doesn't run Central Admin), then the error comes back.

Stopping the "Microsoft SharePoint Foundation Workflow Timer Service " service in Central Admin on the WFE servers doesnot work, you have to actually stop the windows service SPTimerV4 to prevent this job running on the WFE server and stop the error from occurring. This workaround will obviously not work...

This only affects multi-server topologies where Central Admin runs on one server and not on other and when thebelow owstimer.exe job executes on the server which doesnot host central admin.

Here are some ULS logs

05/22/2014 14:19:08.95	OWSTIMER.EXE (0x1F60)	0x25C4	SharePoint Foundation	Upgrade	ajxj9	High	05/22/2014 14:19:08.95 OWSTIMER (0x1F60) 0x25C4 SharePoint Foundation Upgrade SPManager ajxj9 DEBUG Validating web parts referenced in content database SP_AdminContentDB that are installed. 653e939c-2d04-10bb-4f48-6122b11c17e8	653e939c-2d04-10bb-4f48-6122b11c17e8
05/22/2014 14:19:08.97	OWSTIMER.EXE (0x1F60)	0x25C4	SharePoint Foundation	Runtime	6610	Critical	Safe mode did not start successfully. Microsoft.SharePoint.WebPartPages.WebPartPageUserException: This page has encountered a critical error. Contact your system administrator if this problem persists.     at Microsoft.SharePoint.ApplicationRuntime.SafeControlsList.GetSafeControlsListFromPath(SPWebApplication app, SPUrlZone zone)     at Microsoft.SharePoint.ApplicationRuntime.SafeControlsList..ctor(SPWebApplication app, SPUrlZone zone)     at Microsoft.SharePoint.ApplicationRuntime.SafeControls..ctor(SPWebApplication app, SPUrlZone zone)	653e939c-2d04-10bb-4f48-6122b11c17e8
05/22/2014 14:19:08.97	OWSTIMER.EXE (0x1F60)	0x25C4	SharePoint Foundation	Health	8fs1	Verbose	Finished invoking the Check() method.  The rule Failed.	653e939c-2d04-10bb-4f48-6122b11c17e8
05/22/2014 14:19:08.97	OWSTIMER.EXE (0x1F60)	0x25C4	SharePoint Foundation	Health	8fs2	Verbose	Automatic repair is not possible for this error.	653e939c-2d04-10bb-4f48-6122b11c17e8
05/22/2014 14:19:08.98	OWSTIMER.EXE (0x1F60)	0x25C4	SharePoint Foundation	Health	2137	Critical	The SharePoint Health Analyzer detected an error.  Missing server side dependencies.  [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 [SP_AdminContentDB], 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 [SP_AdminContentDB], but are not installed on the current farm. Please install any feature or solution which contains these web parts.  [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 [SP_AdminContentDB], 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 [SP_AdminContentDB], 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 [SP_AdminContentDB], 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 [SP_AdminContentDB], 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 [SP_AdminContentDB], 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 [SP_AdminContentDB], 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 [SP_AdminContentDB], 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 [SP_AdminContentDB], but are not installed on the current farm. Please install any feature or solution which contains these web parts.       For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142689".	653e939c-2d04-10bb-4f48-6122b11c17e8


I can replicate the above issue with 100% certainty on three separate SharePoint environments. One is running October CU version 15.0.4551.1005 and two environments are running SP1 version 15.0.4569.1506

once again, clicking on all the search .aspx pages and links does not fix his error

if owstimer.exe health analyzer process runs on Central Admin server, error goes away

if owstimer.exe health analyzer process runs on WFE server which doesn't have Central Admin, error re-appears

Example

server1, server2 has Central Admin on it

server3, server4 have no Central Admin

stop SPTimerV4 process on server3 and server4

go into Central Admin -> Monitoring -> Review Rule Definitions -> Missing server side dependencies -> and click the "Run Now" button

you should not experience this error since the owstimer.exe process will run on server1 or server2 which has Central Admin

however, if you start the SPTimerV4 on server3 and server4, and re-run the "missing server side depenedencies job", and owstimer.exe happens to run on either server3 or server4, then this error should occur. There are two event log errors that get logged, and now you will have a "Missing server side dependencies" error in your Central Admin "Review problems and solutions" list as per above.

Can anyone else replicate this and has anyone else experienced this? Hopefully someone can confirm if this is a known bug or not, and hopefully provide some guidance on how to fix it.

Thanks heaps,

Vladimir


Viewing all articles
Browse latest Browse all 21070

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>