Azure & Office 365

Posts Tagged ‘sharepoint server missing server site dependency’

Sample error message in SharePoint Health Analyzer.

Title Missing server side dependencies.
Severity 1 – Error
Category Configuration
Explanation

[MissingSetupFile] File [Features\Customfeature.SharePoint\feature1\feature.webpart] is referenced [1] times in the database [WSS_Content], but is not installed on the current farm. Please install any feature/solution which contains this file. One or more setup files are referenced in the database [WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these files.

[MissingWebPart] WebPart class [0e293c29-9caf-6fec-3c02-43e65bdf420d] (class [Customfeature] from assembly [SOMECustomapp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=539e3b144bfb558e1]) is referenced [1] times in the database [WSS_Content], 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 [WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [28c23aec-2537-68b3-43b6-845b13cea19f] is referenced [5] times in the database [SharePoint_AdminContent_2de70b74-66e7-4c03-9135-e4e7bd6f0491], 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_AdminContent_2de70b74-66e7-4c03-9135-e4e7bd6f0491], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
Remedy For more information about this rule, see “http://go.microsoft.com/fwlink/?LinkID=142689”.
Failing Servers Server1, Server2
Failing Services SPTimerService (SPTimerV4)
Rule Settings View

 

Points to notice in above issue:

1. It will mention the server where this issue was observed. Keep a note of those servers. If it is a single server installation, it might not give names.

Lot of time type of installation done on server and IIS feature enabled on site cause this issue. A workaround to resolve the issue to open web.config on all servers and match it. Make sure they are same on all servers.

1. Most important you need to note the name of custom features(e.g. [Features\Customfeature.SharePoint\feature1\feature.webpart]) mentioned above.

We should see details of this feature in the content database name associated with feature. To verify same open SQL management studio > connect to SQL server > Expand databases > expand content datbase(e.g. WSS_Content) > Tables > Now right click on dbo.FeatureTracking > Select top 1000 rows > You should see all the feature name and Feature is mentioned here.

To know more details of webpart run below code on SQL content database

SELECT tp_WebPartTypeId, COUNT(1), tp_Assembly, tp_Class FROM AllWebParts
 
 (NOLOCK) WHERE tp_WebPartTypeId IS NOT NULL AND tp_SolutionId IS NULL
 
 GROUP BY tp_WebPartTypeId, tp_Assembly, tp_Class

1. In another issue you will see only Feature ID and not feature name(e.g. [MissingWebPart] WebPart class [28c23aec-2537-68b3-43b6-845b13cea19f]). Here you can refer below article and check if you are able to find the feature id:

SharePoint 2013 Feature ID with Feature Name

If you see the feature ID in this list, it means it was once activated on some site in this database but it is now deactivated. May be somewhere on some page, the webpart related to that feature is still present which is causing this issue. You need to find that page and remove the webpart from that page or reactivate the feature.

 

1. Lot of time we will see this issue for Admin content database as shown below.

[MissingWebPart] WebPart class [28c23aec-2537-68b3-43b6-845b13cea19f] is referenced [5] times in the database [SharePoint_AdminContent_2de70b74-66e7-4c03-9135-e4e7bd6f0491],

They are actually search webpart. To validate the same run below query on SQL server:

use [SharePoint_AdminContent_GUID]
select DirName,LeafName from dbo.AllDocs where id in
 (select tp_PageUrlID from dbo.AllWebParts where
 (tp_WebPartTypeID='28c23aec-2537-68b3-43b6-845b13cea19f')
 )
go

Resolutions are:

• Normally issue is resolved when simply re-analyzing.
• Browsing to the pages may help
• Some article state it was a bug in SharePoint 2010.

 

5.Now if the above feature is a Custom solution:

• If you don’t have that custom solution with you. then I would suggest you to simply ignore the issue.
• If you have the solution then you can deploy the solution in farm and deactivate the feature in farm and then remove the solution from farm.

 

Once above steps are performed reanalyze and check for error

1. In Central Administration, navigate to: CA > Application Management > Manage Service Applications > Search Service Application > Manage.  This takes you to the SearchAdministration page.
2. Next, navigate to: CA > Application Management > Manage Service Applications > Search Service Application > Manage > Farm Search Administration.  This takes you to the SearchFarmDashboard page.
3. Then, navigate to: CA > Monitoring > Health Analyzer > Review problems and solutions.
4. Click the issue link, click Reanalyze Now, and then click Close.
5. Wait a few minutes, and then refresh the page.