You Must Manually Run PSCONFIG after Installing SharePoint 2010 Patches

You Must Manually Run PSCONFIG after Installing SharePoint 2010 Patches

  • Comments 12
  • Likes

[Today’s post comes to us courtesy of John Bay from Commercial Technical Support]

Patching SharePoint is a two-step process. The updated binaries are first installed and then psconfig must be run to update the SharePoint databases. SBS 2008 uses Windows SharePoint Services 3.0 and updates automatically run PSconfig when installed via Automatic Updates or Windows Server Update Services.   SharePoint Foundation 2010 changes the method in which patches are installed. PSconfig no longer runs automatically after an update is installed. The SharePoint binary files are updated with the patch but the databases are not automatically upgraded. SharePoint runs in a compatibility mode that still allows the sites to function with the older version databases. The SharePoint Health Analyzer will scan the databases every night at midnight to determine if an upgrade is required. If the SharePoint Health Analyzer detects an upgrade is required, it will log the following error in the application event log:

Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation
Event ID: 2137
Task Category: Health
Level: Error
User: CONTOSO\spfarm
Computer: CONTOSOSERVER.contoso.local

Description: The SharePoint Health Analyzer detected an error. Product / patch installation or server upgrade required. All required products must be installed on all servers in the farm, and all products should have the same patching and upgrade level across the farm.

Upgrade is required on server CONTOSOSERVER. Without the upgrade, the server is not in a supported state.

On server CONTOSOSERVER, once all required products and/or patches are installed, perform an upgrade by either running PSConfigUI.exe or by executing the command "PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures". If a former upgrade attempt has failed, you may need to resolve upgrade specific issues before attempting upgrade again. Refer to the upgrade status page (http://contososerver:19158/_admin/UpgradeStatus.aspx) for information about current and prior upgrade attempts, and to determine issues that may be preventing upgrade from succeeding. For more information about this rule, see "".

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\14\BIN
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

Note: The Companyweb site will be inaccessible while the command is running. It is best to run the command after business hours. The amount of time the command takes to run will vary on the size of the database and the speed of the machine. On a reference machine with 8 logical processors, 32GB of RAM and a 2GB content database, the command took approximately 5 minutes to execute.

The SharePoint configuration wizard will launch and perform the configuration tasks. When the command is finished, you should see the following message:

Successfully completed the SharePoint Products configuration.
Total number of configuration settings run: 6
Total number of successful configuration settings: 6
Total number of unsuccessful configuration settings: 0
Successfully stopped the configuration of SharePoint Products.
Configuration of the SharePoint Products has succeeded.

For additional information on SharePoint Foundation 2010 patches see the following TechNet site:

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • I'm assuming this is only relevant to SBS 2011?

  • As was pointed out to me - if you've manually installed SharePoint 2010 on your SBS 2008 you still have to do a psconfig.

    It's SharePoint 2010 that no longer automatically does the psconfig command.

    So IF you have a SharePoint 2010 - standalone - on SBS 2008 - included in SBS 2011, you need to do a psconfig.

  • an automatic update that breaks the backup routine, and then requires a vaguely complex command line to be run in order to fix it. This is a totally unacceptable bug

  • Agreed. This bug. Ran the command line process and still have the same problem. Thumbs UP to another quality product from Microsoft!

  • I am having an issue running the PSConfig after a windows update on my SBS2011 server, really could use some help.

  • Well This has fixed my windows sbs2011 back up so thanks for all info!

  • Thanks for this help - it really helped. We have SBS 2011 and couldn't add a new user. The psconfig helped. But this behavior - running strange cmdline jobs after an update and will NOT be prompted to do so - is not acceptable for an Small Business Server. With such a server i need more admins than workers!


  • You get your wish Dirk! No more SBS server.

  • Information was good, I like your post.
    Looking forward for more on this topic.">SharePoint 2013 Training

  • HI, thanx for info, in case you receive an error to do with configuration must be performed before you use sharepoint...

  • this does not work for us backups still fail, backup wiz fails of all types, i got a system state backup to run once from cmd line now they fail every time too. XCOPY is the only thing that works and i hope i don't have to rely on that to DR. Wasted hrs/weeks/months on a back that should just work. Where do i get my money back, don't most products that are broke out of the box get returned for a full refund?