Serious SharePoint

This means something, this is important!

Missing server side dependencies

Posted by Jonathan Adams On April - 7 - 2011

Detail: (Truncated due to length)

[MissingFeature] Database [WSS_Content] has reference(s) to a missing feature: Id = [fc5e2840-0b48-42eb-9ad7-076f5add58ad]. The feature with Id fc5e2840-0b48-42eb-9ad7-076f5add58ad is referenced in the database [WSS_Content], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

[MissingSetupFile] File [Features\VASCSiteAction\VASC-core.css] is referenced [6] 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.

[MissingSetupFile] File [themes\THEME\alldaydefault_granite.gif] is referenced [4] 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.

Solution:  There are several things going on here. 

Firstly the error warning of  [MissingSetupFile] referring to files in the theme directory can be resolved easily.  The THEME folder and all its files needs to be added to all servers configured as web front-ends.  This most likely includes your application servers.  If you do not have the exact theme referenced, try copying an existing theme and renaming its folder in the root (14 hive).

[MissingFeature] Database [WSS_Content] has reference(s) to a missing feature: Id = [fc5e2840-0b48-42eb-9ad7-076f5add58ad] and [MissingSetupFile] File [Features\VASCSiteAction\VASC-core.css] both refer to the same issue.  These errors are due to the farm looking for a feature that was installed but is not present.  A common cause for this is an upgrade from MOSS to SharePoint 2010 without correcting errors found from the pre-upgrade check.  Correct this by adding the missing solution to the farm and re-deploying to the web application.

6 Responses to “Missing server side dependencies”

  1. Daniel says:

    Hi

    I really like the site and this article. I have backed up and restored a site collection using the PS Backup-SPSite. However, I seem to have these issues. I wonder if there is a way of tracking these missing farm features via the feature ID.

    Regards

    Daniel

    [MissingFeature] Database [WSS_Content_Dan] has reference(s) to a missing feature: Id = [8dfaf93d-e23c-4471-9347-07368668ddaf]. The feature with Id 8dfaf93d-e23c-4471-9347-07368668ddaf is referenced in the database [WSS_Content_Dan], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
    [MissingFeature] Database [WSS_Content_Dan] has reference(s) to a missing feature: Id = [893627d9-b5ef-482d-a3bf-2a605175ac36]. The feature with Id 893627d9-b5ef-482d-a3bf-2a605175ac36 is referenced in the database [WSS_Content_Dan], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

  2. Mike says:

    Hi there,

    The following command should help:

    stsadm -o deactivatefeature -id -url (-force).

    • Jonathan Adams says:

      STSADM is technically deprecated but it will still work in a pinch. I would learn PowerShell sooner than later, it really is fantastic.

    • Sharepoint Novice says:

      Where is the command executed? I get an error if I try this in PowerShell.

      Thanks.

      • Jonathan Adams says:

        STSADM.exe is an executable file in the bin folder of your SharePoint root(14 hive to some). It is run from the command prompt and you will likely need to reference the full exe’s path since there is no reference in your server’s PATH system variable (by default).

  3. Gennadi says:

    Hi,
    In my case I didn’t have any site in site collection that were using a THEME that caused trouble. I figured out later that the files of this THEME were sitting in the “Recycle bin”. I’ve deleted the files from both Recycle bins and that solved the problem.

Leave a Reply

About Me

Twitter

    Photos

    Activate the Flickrss plugin to see the image thumbnails!