Sharing the Point

Office 365, SharePoint, Project Server – Support Blog

How to find out SharePoint server missing features and remove those

Posted by Ashraf on August 30, 2011

This is moved to,

http://mroffice365.com/2011/08/how-to-find-out-sharepoint-server-missing-features-and-remove-those/

Advertisements

3 Responses to “How to find out SharePoint server missing features and remove those”

  1. Mark said

    Thank you very much.
    Your post helped me to find and remove missing features from SharePoint site collection.
    There was a missing feature that appeared in preupgradecheck errors, I tried many other solutions, feature managers, etc.
    To find it just ran WssAnalyzeFeatures tool against different SharePoint sites (e.g. http://hostname:portX, then http://hostname:portY, … ).
    And removed it with WssRemoveFeatureFromSite.

  2. tom circus said

    thanks a lot, very useful tools!

  3. mike said

    This worked great to remove problems with site collections and site features when we’re trying to run an Cumulative Upgrade but failing on errors.

    However when I ran the wssanalyzefeatures, I also got a number of “Problems with installe features:
    – Feature Id=3b5dc9dd-896c-4d6b-8c73-8f854b3a652b: Error: Missing File “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Template\Features\PowerViewStapling\feature.xml”
    – Feature Id=60978b5d-508c-42da-a401-52ff0adbb420: Error: Missing File “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Template\Features\ASN.MiniCalendarWebPart\feature.xml”
    and a few more.

    How do I handle the missing file problem? And, how did I get them in the first place? I assume I got a number of these problems from copying my production
    content to my test environment. We did a backup from Prod and restore to test. But then we had to re-install a few of our custom apps and other non OTTB apps.
    Do these errors come because the guid of the prod feature doesn’t match the guid of the feature in the test envionment?

    Thanks!

Sorry, the comment form is closed at this time.

 
%d bloggers like this: