Wednesday, 6 September 2017

Legacy Site Detected Error - Resolved

While working on SharePoint Migration from 2010 to 2016, I thought it to be smooth because the environment didn’t have any customizations and neither I had any custom solution deployed on it.
So, I started the migration from SharePoint using Content DB. I have migrated Content DB from SharePoint 2010 to 2013. After creating a web application and running “test-spcontentdatabase” PowerShell command (No errors in output), I mounted the content database successfully without any issue.
SharePoint site was working as expected. I have also done the visual upgrade of SharePoint sites without any error. Now, it's time to move to SharePoint 2016. Again, I have to follow the same approach I did in SharePoint 2013.
Moved and restored the Content Database on SQL Server from SharePoint 2013 and created the web applications but when I ran the “Test-Spcontentdatabase” Powershell command, I got an error that I never faced after doing around 10 migrations.
“Legacy Site Detected”

So, I have 2 sites which are still using SharePoint 2010 experience.
Error - “Legacy Site Detected”
Follow the below steps.
  1. Launch SQL Server Management Studio (SSMS).
  2. Connect to the offending content database.
  3. Execute the following query,
    1. SELECT, als.PlatformVersion, aw.Title, aw.FullUrl, aw.ProductVersion, als.Deleted  
    2. FROM dbo.AllSites als  
    3. INNER JOIN dbo.AllWebs aw  
    4. ON aw.Id = als.RootWebId  
  1. Locate the entry that doesn’t have product version 15 or Platform version It will look like the below screenshot.

  1. Note the GUID associated with the site you identified causing the issue.
    (This will be the id column)
  2. Run the following query using SSMS connected to the content database,

    1. UPDATE dbo.AllSites  
    2. SET PlatformVersion = ''  
    3. WHERE id = GUID"
Verify again by running the query at step 3 and once all platform version is, go to SharePoint Server and run the “Test-SPContentDatabase” again.
The legacy issue will be fixed and we are good to go with our SharePoint migration.
Hope this will help you. Happy SharePointing!!!