question

sns1 avatar image
0 Votes"
sns1 asked EchoDu-MSFT commented

Test-spcontentdatebase giving below missing feaure errors

We are migrating DB From 2013 to 2016, we dont have 2010 envirounment, DB is there directly in 2013 itself.
When we execute test-spcontentdatabase in 2013, giving following errors ( missing features) attached in the screenshots.
113479-missingsetupfile.png


113504-image.png


office-sharepoint-server-administration
missingsetupfile.png (453.1 KiB)
image.png (583.3 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

EchoDu-MSFT avatar image
0 Votes"
EchoDu-MSFT answered EchoDu-MSFT commented

Hi @sns1 ,

In SharePoint content db migration some error we can ignore this will not harm anything.Even though we get some error during the database upgrade we may ignore them, as this is generally common behavior in migration project.

One of the key parameter for succeeding the migration project is proper planning and analyzing the source environment. Try to get an inventory from your source system about all custom solution and where (in which sites) these custom features are activated, I am sure from the inventory report you will find there are many features those are not really being used in the source system. So you can clean those unwanted feature from target environment – after running the Test-SPContentDatabase command.

PowerShell sample for running Test-SPContentDatabase:

 $wa = Get-SPWebApplication http://sp13:26306/
 $outputPath = "\\tools\files\Output\Test_Wss_Content_MissingAssembly_{0}.txt" -f (Get-Date -Format hhmmss) 
 $dbName = "WSS_Content_MissingAssembly" 
 $slqServer = "SQL" 
 Test-SPContentDatabase -Name $dbName -WebApplication $wa -ServerInstance 
 $slqServer -ShowLocation:$true -ExtendedCheck:$false | Out-File $outputPath Write-Host "Test results written to $outputPath"

PowerShell sample for removing features by ID:

 $featureID = "ed37484a-c496-455b-b083-3fc157b1603c"
 $siteID = "108d28e9-dac1-4eea-9566-6591394e6d40"   
    
 #Display site information
 $site = Get-SPSite $siteID  
 Write-Host "Checking Site:" $site.Url
    
 #Remove the feature from all subsites
 ForEach ($web in $Site.AllWebs)
 {
     If($web.Features[$featureID])
         {
             Write-Host "`nFound Feature $featureID in web:"$Web.Url"`nRemoving feature"
             $web.Features.Remove($featureID, $true)
         }
         else
         {
             Write-Host "`nDid not find feature $featureID in web:" $Web.Url
         }   
 }
    
 #Remove the feature from the site collection
 If ($Site.Features[$featureID])
 {
     Write-Host "`nFound feature $featureID in site:"$site.Url"`nRemoving Feature"
     $site.Features.Remove($featureID, $true)
 }
 else
 {
     Write-Host "Did not find feature $featureID in site:" $site.Url
 }

PowerShell sample for removing setup files by ID:

 $setupFileID = "07462F03-A4C6-455C-B383-947DDE85DF36"
 $siteID = "108D28E9-DAC1-4EEA-9566-6591394E6D40"
 $WebID = "4E068646-2C87-4868-924E-850C31F607DF"
    
 #Get file
 $site = Get-SPSite -Identity $siteID
 $web = Get-SPWeb -Identity $WebID -Site $siteID
 $file = $web.GetFile([GUID]$setupFileID)
    
 #Report on location
 $filelocation = "{0}{1}" -f ($site.WebApplication.Url).TrimEnd("/"), 
 $file.ServerRelativeUrl
 Write-Host "Found file location:" $filelocation
    
 #Delete the file, the Delete() method bypasses the recycle bin
 $file.Delete()
    
 $web.dispose()
 $site.dispose()

Notes:

You may ignore the error or exception from Test-SPContentDatabase command, still your Mount-SPContentDatabase will work.

  • While running the Mount-SPContentDatabase for certain content database – if you get an exception or up to some extend some errors, you can ignore those and continue in further migration, still your migrated site will work fine and in these scenario if you see database upgrade status from central admin, we can see upgrade completed with errors status but we can live with this.

  • After content db migration thru database detach and attach approach – we may see some issues in the migrated master page, css and java script code as a result we may expect some differences in the migrated site look and feel and other css and scripting related issue – this is a general behavior which we need to fix manually even though it is time consuming.

Reference:

Post Upgrade Cleanup - Missing Server Side Dependencies

Thanks,
Echo Du
=================================
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @sns1 ,

Is there anything else I can help with regarding this issue?

You can comment us at any time and we will continue to follow up.

Thanks,
Echo Du

0 Votes 0 ·