Database is in compatibility range and upgrade is recommended

Database is in compatibility range and upgrade is recommended

  1. In SharePoint Central Admin click BACKUP AND RESTORE, then PERFORM A Full BACKUP.
    3. CD into C:\Program Files\Common Files\Microsoft shared\Web Server Extensions\15\BIN>
    4. Paste following command and press enter PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
    5. this will take a few minutes to complete, so just wait
    6. Go back to your SharePoint Central Admin console and click MONITORING (left menu) >REVIEW PROBLEMS AND SOLUTIONS > if Databases Running in Compatibility Range, Upgrade Recommended still shows click on it and then click the REANALYZE NOW button on the top
    7. Hopefully it only complains about your content database and Bdc_Service_DB

How To upgrade your Content Database:

Paste the following into your SharePoint 2013 Management Shell Upgrade-SPContentDatabase and then enter the name of your content database at the Identity

How To upgrade your Bdc_Service_DB:

Paste the following into your SharePoint 2013 Management Shell (Get-SPDatabase | ?{$_.type -eq

Data base is up to date but some sites are not completely upgraded:

– See more at:



You can also run the following commands to determine if you need to complete the update process with PSCONFIG:

  • Launch an elevated (Run as Administrator) SharePoint 2010 Management shell from start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Management Shell.
  • Once the shell opens, type the following command followed by enter: 
    (get-spserver $env:computername).NeedsUpgrade


In order to update the SharePoint databases, you must manually run the PSconfig utility. To run the utility:

1. Open an Administrative command prompt. 
2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\BIN 
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

SharePoint 2013: Product Configuration Wizard stuck on task 9 of 10


  1. First, clear the upgrade in progress flag
    1. Open an elevated command shell.
      1. Navigate to: c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\BIN\.
      2. Execute the following: stsadm -o getproperty -propertyname command-line-upgrade-running.  If this returns <Property Exist=”Yes” Value=”no” />, go directly to step 2).  Otherwise, continue to the next step.
      3. Execute the following: stsadm –o setproperty –propertyname command-line-upgrade-running –propertyvalue no.
  2. Next, clear the configuration cache
    1. Open the Services.msc control panel, and then look for the SharePoint Timer Service.
    2. Stop this service.
    3. Open Windows Explorer, and then navigate to the cache folder at:C:\ProgramData\Microsoft\SharePoint\Config.
    4. Look for the most recent cache folder, and then open it.
    5. Delete all files in this folder EXCEPT cache.ini.
    6. Open the cache.ini file in a text editor, and then randomly modify the number, say, to “1”.
    7. Save the cache.ini file.
    8. Start the SharePoint Timer Service.
    9. Wait for the configuration cache to fill up again.  About 1700 items.  Once it stabilizes, proceed to the next step
  3. Perform a new upgrade
    1. Open an elevated command prompt as Administrator.
    2. Run the following command: Psconfig.exe -cmd upgrade -inplace b2b -wait -force. NOTE: The following services will be stopped after executing this command:
      1. SharePoint Timer Service
      2. SharePoint Server Search 15
      3. SharePoint Search Host Controller
      4. SharePoint Administration
      5. World Wide Web Publishing Service

      They will be automatically restarted again at the end of the upgrade process.

  4. Troubleshooting
    1. Stuck on 100%.  You may experience an apparent “stuck on 100%” issue, even after performing the steps above.  Wait before repeating the process or engaging in more troubleshooting.  I have experienced delays of up to 30 minutes, between seeing “100.00%” and seeing the message that the upgrade was complete. To check if this is the case, open the Upgrade log file, and then search for the phrase “End processing children of [SPFarm Name=[farm configuration database name] for upgrade” followed by “Exiting upgrade for [SPFarm Name=[farm configuration database name]].  If these are the last two statements currently in the Upgrade file, then it is likely that the upgrade is progressing fine and simply requires more time to complete.  This has been my experience to date.  For example, when upgrade two WFEs and one APP, in each case, the upgrade paused just after presenting 100%.  When I looked into the Upgrade file in each case, I found the above statements at the end of the file; and in every case, the process eventually completed successfully.


stsadm -o setproperty -pn command-line-upgrade-running -pv Yes


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.