Partager via

This SharePoint farm has pending upgrades error when running New-SPConfigurationDatabase for a new SharePoint 2010 installation

  • Article

 

We ran into this problem while setting up some test farms where we’d get an exception while running the powershell for New-SPConfigurationDatabase.  The exception simply mentions “This farm has pending upgrades error” and it would fail.  The funny thing is that it’s a new farm with no installation.  We had tested the script before and it was running fine.  So I tested running the wizard and it worked fine!

As it turns out, this new farm had one difference: the SharePoint 2010 bits were installed, but so where the Office Web Apps bits.  So we took another test environment that had the same base (SP2010 + Office Web Apps, no wizard/farm setup), and then I ran psconfig –cmd upgrade –inplace b2b –wait –force.  The command returned an exception but it did configure one setting – I reran the New-SPConfigurationDatabase after and it ran fine.

So if you script (PowerShell) an installation that has SP2010 + Office Web Apps, do run the psconfig command, except an exception, and move on with your script – it’ll run fine.

 

Maxime

Comments

  • Anonymous
    April 01, 2011
    A good post that saved my scripted installation. It should've helped somebody since it's been posted a few months ago. I'm the first one who said it.

  • Anonymous
    April 02, 2011
    Thanks!

  • Anonymous
    September 13, 2011
    Thanks! Worked like a charm!

  • Anonymous
    September 19, 2011
    The comment has been removed

  • Anonymous
    September 19, 2011
    GUI's fine but so is the command though.  Did you copy/paste or type it in?  this is a command that existed back in 2007 as well.

  • Anonymous
    October 12, 2011
    Thank you for the solution, it worked excellent. I had to manually type the command, it complained about a wrong cmd type when copy/pasting .... (if anybody runs into this)

  • Anonymous
    October 12, 2011
    yeah, i'm guessing the dash is getting encoded doesn't paste well.  Glad it's working :)

  • Anonymous
    March 21, 2014
    I received this exception with SharePoint Server 2013 SP1 with Project Server 2013 SP1 and for me running psconfig.exe as described worked. To reiterate Maxime's note, psconfig.exe will FAIL with an upgrade exception. This is expected! Once it fails New-PSConfigurationDatabase will work. Thank you Maxime! :)