Specifically in my case, I migrated from 2007 to 2010 using the Database attach upgrade method.
I found that although I have completed the individual database upgrades, as well as applied the SharePoint service pack (SP1) and CU's, I still receive the following message when looking at the SharePoint Database Status in Central Admin:
"Database is up to date, but some sites are not completely upgraded."
To resolve this issue, I performed the following:
For my migration, there were some of the infamous FAB40 templates being used, so I brought them over using these steps.
Little did I know, this would affect my ability to have properly updated databases in SharePoint 2010.
We've all heard about the different horror stories with regards to using the FAB40 templates with SharePoint 2010, and this is a reason why.
So first I de-activated the FAB40 feature at the top site Collection Features. It is called: "Fields and Content Types for the Windows SharePoint Services Application Templates"
Next, you need to run a powershell command on each database to perform the upgrade. Open an elevated SharePoint Management Shell window and run the following:
$DB =
Get-SPContentDatabase -Identity DB_NAME
Upgrade-SPContentDatabase
-id $DB
Once completed, perform the same steps for each additional site collection/database needing upgrade (given you have the site collections/databases separate).
When you are all finished, you should now see the database status showing correctly, 'Database is up to date' in the SharePoint Database Status in Central Admin.
At this point, you should also run the SharePoint Products Configuration Wizard if you have applied any CU's or Service Packs that need to be applied.
No comments:
Post a Comment