Database is up to date, but some sites are not completely upgraded

Database is up to date, but some sites are not completely upgraded

Version: 1.0, Updated 03/22/2016

Applies to: SharePoint and Project Server PPM 2010, 2013, 2016

Scenario:

You review the SharePoint Central Administration site for Servers and database statuses and notice below messages:

Server Status: Upgrade Required

Central Admin Site > System Settings > Manage servers in this farm

SP2013_SomeSiteNotUpgraded_01A

 

Database Status: Database is up to date, but some sites are not completely upgraded

Cental Admin Site > Upgrade and Migration > Review Database Status.

SP2013_SomeSiteNotUpgraded_01b

 

Resolution:

First lets try to find out which site is causing that error.

  1. On one of the SharePoint / Project Server PPM server, open command prompt with elevated permissions.
  2. Go to SharePoint Bin folder c:\Program Files\Microsoft Shared\Web Server Extensions\15\Bin\ [the two digit folder name for SharePoint 2010 = 14, 2013 = 15, 2016 = 16]
  3. Type STSAdm command and use pipe to export it to a text file: stsadm.exe -o localupgradestatus > e:\UpgradeStatus.txt  SP2013_SomeSiteNotUpgraded_02 
  4. After executing the command, open the UpgradeSTatus.txt file exported in previous step. Search the text file for the status Needs Upgrade. Those sections will list the site name in question. You can see in the image below that the site name is listed.SP2013_SomeSiteNotUpgraded_03
  5. Go to the bottom of this UpgradeStatus.txt file and you will see overall status of content database(s), Site collection(s) or objects that may need upgrade.SP2013_SomeSiteNotUpgraded_04
  6. In Review Database Status page we saw the name of database(s) that had the status with the error message (second image on the top). Open PowerShell with elevated rights and run the following commands: Get-SPContentDatabase -Identity wss_epm_content [where wss_epm_content is the name of the content database]. That will give us the database ID that we’ll use in next command to upgrade the database.SP2013_SomeSiteNotUpgraded_05
  7. Now run the PowerShell command: Upgrade-SPContentDatabase -Identity GUID# [where GUID# is the ID we got from previous step]. Click Y or A to confirm the command execution. SP2013_SomeSiteNotUpgraded_06
  8. Now go to Manage Servers in the Farm and Review Database Status pages and check the status. The Servers page will still show ‘Upgrade Required’ status. The database page will not show error this time and instead will show ‘No Action Required’ message. SP2013_SomeSiteNotUpgraded_07  SP2013_SomeSiteNotUpgraded_08
  9. Run the stsadm command again and export the status with a new file name UpgradeStatus2.txt. stsadm.exe -o localupgradestatus > e:\UpgradeStatus2.txt. Review the file after command executes and you will find that none of the database, site Collection or object need upgrade this time. SP2013_SomeSiteNotUpgraded_09
  10. At this point, run either the SharePoint Configuration Wizard GUI or run the command line option. SP2013_SomeSiteNotUpgraded_10 Run the PowerShell command on each server in the farm one at a time. PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresourcesSP2013_SomeSiteNotUpgraded_11
  11. After executing the command on all servers, go to the Central Admin site and review the status of servers in the farm. All the servers should have ‘No Action Required’ as the status. SP2013_SomeSiteNotUpgraded_13

 

 

References:

  1. Sharepoint Troubleshooting: Data base is Up to date but some sites are not completely upgraded
  2. Data base is Up to date but some sites are not completely upgraded
  3. sharepointdiary – Database is up to date, but some sites are not completely upgraded
  4. Stefan Gossner – Why I prefer PSCONFIGUI.EXE over PSCONFIG.EX

 

Leave a Reply

Enter the CAPTCHA * Time limit is exhausted. Please reload CAPTCHA.