SharePoint 2013–Missing serverside dependencies

This health-analyzer warning popped up from time to time in SharePoint 2010 environments as well. So when I encountered it the other day I had already an idea on how to handle this.

This is what I saw in SharePoint Central admin:

image

The error message is not telling you that much usually I would use the webpart ID provided and figure out which webpart is referenced by using Powershell, but this time I just guessed Smiley.

So I went to Central admin >> General application settings >> Farm Search Administration

image

In 2010 clicking this link had the consequence that the error vanished from the health analyzer. So I refreshed the health rule and… found another error appeared instead.

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

This gives you something to read at least.

What jumped right into my eye is that all referenced controls are related to search. So I jumped to the Search Service Application, where I found everything working as expected.

The reference “WebControls.SearchApplicationShortcutsList” pointed me to the little shortcut list in the right hand corner of the service application config site.

image

I clicked both links listed below and when I refreshed the health analyzer rule it was gone.

So I think the lesson learned from that is that you can fix this particular issue (missing references in the Central Admin contentdatabase) in almost the same way as you did in SharePoint2010.

Advertisements

14 responses to “SharePoint 2013–Missing serverside dependencies”

  1. Yoshi says :

    I followed your suggestion, unfortunately the error still pops up.

  2. Tsvetelin Pavlov says :

    Thanks! It worked!

  3. Eric says :

    Your detailed error description is IDENTICAL to the one I’m seeing in our environment. Unfortunately, your solution didn’t do the trick. I even added a couple links to the Shortcuts List for good measure. Clicked Reanalyze and refreshed 25 times. No change. The Search Service is working flawlessly, so I don’t know if this is really that big a deal. Just annoying.

  4. SPSoldier says :

    It is weired to see that sometimes the issue can be solved and sometimes it can’t…For me it worked with numerous times… I will keep my eyes open, when I encounter it the next time and if there are any different solutions to it I will update this article. Thank you all for your feedback…

  5. Hilton Giesenow says :

    The solution works, thanks. I have found though that, if central admin is hosted on mulltiple servers, you need to make sure to visit the links on each server in turn, not just on one.

  6. gaurav says :

    It took some time but it got cleaned eventually. So just wait for some time so that sharepoint runs right timer job to delete the error log from health analyzer

  7. Toby says :

    Also receiving these identical errors on our farm. We actually have two separate search service applications to visit. Went and visited both search service applications and the farm search administration page, the errors still are showing up in Health Analyzer logs. Also, I’m 99.9% sure these pages had all been visited in the past multiple times by me (before i was aware of this solution) and in the months since then this has yet to resolve itself in time :(.

    I just spent a day clearing up a bucket of other errors and these are the last 3 😉 Would love to get these finally resolved!

    Any ideas on the next steps to solve this?

  8. thool says :

    Did not solve the error in my case.
    I had also Event ID 8313 – Topology errors in the event log.
    The following two steps solved both the topology and the Health Analyzer errors:

    1.) 1.Install the SharePoint Root Authority certificate in the Trusted Root Certification Authorities store (http://support.microsoft.com/kb/2639348)
    2.) start the application pool “SharePoint Web Services Root”

  9. Gaurav says :

    Here is the solution. Visit this blog & download the utility

    learn-sharepoint-2013.blogspot.in/…/find-missing-web-part.html

    Gaurav

  10. Clayton says :

    Worked like a charm, thanks!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: