Solving [MissingSetupFile] errors from SharePoint Health Analyzer

ISSUE DESCRIPTION:

After a SharePoint 2007 Migration to SharePoint 2010, on the Central Administration, the SharePoint Health Analyzer is generating the critical event [Missing server side dependencies] :

 

 And the event details is generating a lot of [MissingSetupFile] errors, examples:

[MissingSetupFile] File [Features\DocumentReviewDocsForReviewList\docsforreview\repair.aspx] is referenced [5] times in the database [Sharepoint_80_Content_04], 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 [Sharepoint_80_Content_04], but are not installed on the current farm. Please install any feature or solution which contains these files.
[MissingSetupFile] File [Features\DocumentReviewDocsForReviewList\docsforreview\Upload.aspx] is referenced [5] times in the database [Sharepoint_80_Content_04], 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 [Sharepoint_80_Content_04], but are not installed on the current farm. Please install any feature or solution which contains these files.
[MissingSetupFile] File [Features\DocumentReviewModules\default.aspx] is referenced [5] times in the database [Sharepoint_80_Content_04], 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 [Sharepoint_80_Content_04], but are not installed on the current farm. Please install any feature or solution which contains these files
[MissingSetupFile] File [Features\InfoPathFormViewer_c9ca3d89-c724-4265-9246-70ef8bf8bdbf\InfoPathFormViewer.webpart] is referenced [2] times in the database [Sharepoint_80_Content_04], 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 [Sharepoint_80_Content_04], but are not installed on the current farm. Please install any feature or solution which contains these files.
[MissingSetupFile] File [Features\KnowledgeBaseKnowledgeBaseList\kbase\repair.aspx] is referenced [2] times in the database [Sharepoint_80_Content_04], 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 [Sharepoint_80_Content_04], but are not installed on the current farm. Please install any feature or solution which contains these files.
[MissingSetupFile] File [Features\KnowledgeBaseKnowledgeBaseList\kbase\Upload.aspx] is referenced [2] times in the database [Sharepoint_80_Content_04], 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 [Sharepoint_80_Content_04], but are not installed on the current farm. Please install any feature or solution which contains these files.

ROOT CAUSE:

These events are logged because the migrated SharePoint 2010 Sites contains some references to custom Feature files and the linked feature are not installed in the Farm.
In my case, I have tried to clean up the SharePoint 2007 Sites before the migration by disabling and uninstalling the unused features, but most of the times, the feature custom files are not getting removed correctly.

SOLUTION:

The easy solution is obviously to install the features related to those files, but if you are in the same situation as me, you don't really need the features anymore and you just want the database to be clean and get rid of these events.

To safely remove the files, we need to be able to identify their specific location on the Farm, I have created an automated PowerShell script based on Phil's article (Thanks Phil), this script will get all the required information for you:

 param (  
   [string]$DBserver = $(throw "Missing server name (please use -dbserver [dbserver])"),  
   [string]$path = $(throw "Missing input file (please use -path [path\file.txt])")  
 )  
 #Set Variables  
 $input = @(Get-Content $path)  
 #Addin SharePoint2010 PowerShell Snapin  
 Add-PSSnapin -Name Microsoft.SharePoint.PowerShell  
 #Declare Log File  
 Function StartTracing  
 {  
   $LogTime = Get-Date -Format yyyy-MM-dd_h-mm  
   $script:LogFile = "MissingSetupFileOutput-$LogTime.txt"  
   Start-Transcript -Path $LogFile -Force  
 }  
 #Declare SQL Query function  
 function Run-SQLQuery ($SqlServer, $SqlDatabase, $SqlQuery)  
 {  
   $SqlConnection = New-Object System.Data.SqlClient.SqlConnection  
   $SqlConnection.ConnectionString = "Server =" + $SqlServer + "; Database =" + $SqlDatabase + "; Integrated Security = True"  
   $SqlCmd = New-Object System.Data.SqlClient.SqlCommand  
   $SqlCmd.CommandText = $SqlQuery  
   $SqlCmd.Connection = $SqlConnection  
   $SqlAdapter = New-Object System.Data.SqlClient.SqlDataAdapter  
   $SqlAdapter.SelectCommand = $SqlCmd  
   $DataSet = New-Object System.Data.DataSet  
   $SqlAdapter.Fill($DataSet)  
   $SqlConnection.Close()  
   $DataSet.Tables[0]  
 }  
 #Declare the GetFileUrl function  
 function GetFileUrl ($filepath, $DBname)  
 {  
     #Define SQL Query and set in Variable  
     $Query = "SELECT * from AllDocs where SetupPath = '"+$filepath+"'"  
     #Runing SQL Query to get information about the MissingFiles and store it in a Table  
     $QueryReturn = @(Run-SQLQuery -SqlServer $DBserver -SqlDatabase $DBname -SqlQuery $Query | select Id, SiteId, DirName, LeafName, WebId, ListId)  
     foreach ($event in $QueryReturn)  
       {  
         if ($event.id -ne $null)  
         {  
         $site = Get-SPSite -Limit all | where { $_.Id -eq $event.SiteId }  
         #get the URL of the Web:  
         $web = $site | Get-SPWeb -Limit all | where { $_.Id -eq $event.WebId }  
         #Write the SPWeb URL to host  
         Write-Host $filepath -nonewline -foregroundcolor yellow  
         Write-Host ";" -nonewline  
         write-host $web.Url -NoNewline -foregroundcolor green  
         #get the URL of the actual file:  
         $file = $web.GetFile([Guid]$event.Id)  
         #Write the relative URL to host  
         write-host "/" -nonewline -foregroundcolor green  
         write-host $file.Url -foregroundcolor green  
         }  
       }  
 }  
 #Start Logging  
 StartTracing  
 #Log the CVS Column Title Line  
 write-host "MissingSetupFile;Url" -foregroundcolor Red  
 foreach ($event in $input)  
   {  
   $filepath = $event.split(";")[0]  
   $DBname = $event.split(";")[1]  
   #call Function  
   GetFileUrl $filepath $dbname  
   }  
 #Stop Logging  
 Stop-Transcript  

Paste the above code in a PowerShellScript file, like [MissingSetupFileDetails.ps1] and copy it on your local SharePoint Server Drive.

Launch the script from a Windows Powershell Cmd Prompt using the following parametters:

.\MissingSetupFileDetails.ps1 -DBserver <SQLServerName> -path <fullpath\missingfiles.txt>

[path\missingfiles.txt] is a input file you need to create based on the [MissingServerFile] errors that you get on the SharePoint Health Analyzer

The input.txt file should be formated like this (FeaturesFilePath;ContentDatabase), example:

Features\DocumentReviewDocsForReviewList\docsforreview\repair.aspx;Sharepoint_80_Content_01
Features\DocumentReviewDocsForReviewList\docsforreview\Upload.aspx;Sharepoint_80_Content_01
Features\DocumentReviewModules\default.aspx;Sharepoint_80_Content_01
Features\InfoPathFormViewer_c9ca3d89-c724-4265-9246-70ef8bf8bdbf\InfoPathFormViewer.webpart;Sharepoint_80_Content_02
Features\KnowledgeBaseKnowledgeBaseList\kbase\repair.aspx;Sharepoint_80_Content_03
Features\KnowledgeBaseKnowledgeBaseList\kbase\Upload.aspx;Sharepoint_80_Content_03

After execution, the script generates a CSV output file in the same folder with details about the file location.

Note: If you want to get rid of all files unused, update the above script by adding the line $file.delete() after the line write-host $file.Url -foregroundcolor green  in the IF statement 
(to be used at your own risk - I would strongly recommend to first analyse the CSV generated (excel) before updating the script with the delete option, to avoid removing important files.)

------------

For [MissingWebPart] events, please check my next article
For [MissingAssembly] events, please check next article
For [MissingFeature] events, feel free to use the great tool FeatureAdmin, it can scan the whole farm and remove the corrupted feature references.