Installing SP3 fails with Upgrade object too new
I'm trying to update a MOSS 07 environment (one server working as WFE and App Server, one as the DB server) to Service Pack 3. Previously, someone else tried to install SP1 and ran out of disk space mid-install. After the dust settled, he wound up with a WFE running RTM bits and a database that was updated to SP1. Instead of rolling everything back, he changed the database versions by hand, and worked the last year in an unsupported state. Now, I'm trying to get things back on track and updated to SP3. I'm able to install WSS SP3 and run the Config Wizard, but it fails on Step 8 of 9 with this error: [SPManager] [INFO] [12/14/2011 9:58:06 AM]: Preparing to upgrade PersistedUpgradableObject: SPWebApplication Name=MySite01 Parent=SPWebService. This object's current status is Online. [SPManager] [DEBUG] [12/14/2011 9:58:06 AM]: Using cached [SPWebService Parent=SPFarm Name=SharePoint_Config] NeedsUpgrade value: False. [WebApplicationSequence] [ERROR] [12/14/2011 9:58:06 AM]: Upgrade object too new (build version = null, schema version = 12.0.4.0). Current server (build version = null, schema version = 12.0.3.0). [SPManager] [ERROR] [12/14/2011 9:58:06 AM]: CanUpgrade [SPWebApplication Name=MySite01 Parent=SPWebService] failed. [SPManager] [ERROR] [12/14/2011 9:58:06 AM]: The specified SPWebApplication Name=MySite01 Parent=SPWebService has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object. [SPManager] [ERROR] [12/14/2011 9:58:06 AM]: at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o) [SPManager] [ERROR] [12/14/2011 9:58:06 AM]: ReflexiveCanUpgrade [SPWebApplication Name=MySite01 Parent=SPWebService] failed. [SPManager] [ERROR] [12/14/2011 9:58:06 AM]: The specified SPWebApplication Name=MySite01 Parent=SPWebService has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object. [SPManager] [ERROR] [12/14/2011 9:58:06 AM]: at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o) at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o) at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) [SPManager] [DEBUG] [12/14/2011 9:58:06 AM]: Cannot upgrade [SPWebApplication Name=MySite01 Parent=SPWebService]. [SPManager] [DEBUG] [12/14/2011 9:58:06 AM]: Skip upgrading [SPWebApplication Name=MySite01 Parent=SPWebService]. [SPManager] [INFO] [12/14/2011 9:58:06 AM]: Resetting the status of PersistedUpgradableObject: SPWebApplication Name=MySite01 Parent=SPWebService to Online. [SPManager] [INFO] [12/14/2011 9:58:06 AM]: Finished upgrading SPWebApplication Name=MySite01 Parent=SPWebService. Is this something I can fix? -Scott
December 14th, 2011 5:24pm

Hi Scott, Did you get this error on all servers in your farm? This issue seems to be caused by that the servers in the farm are not on the same patch level. You should bring all servers in the farm to the same patch level. Hope this helps. Thanks.Pengyu Zhao TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
December 16th, 2011 2:23am

Thanks for the reply. The "farm" is as simple as it gets: one front end server running as WFE and App server, one DB server. Any idea what versions 12.0.4.0/12.0.3.0 are?
December 16th, 2011 11:50am

Hi, When you login into your central admin what versions it shows under servers in farm? I would suggest you to first upgrade it to SP2 and then SP3.Thanks, Rahul Rashu
Free Windows Admin Tool Kit Click here and download it now
December 18th, 2011 2:32pm

Same problem here. In my case the problem was that I launched SharePoint Configuration Wizard just after installing WSS 3.0 SP3. Always got the error: The B2B upgrader timer job failed And if I tried to execute: psconfig -cmd upgrade -inplace b2b –force –wait the process ended with the error of "Upgrade object too new". I installed MOSS 2007 SP3 and then the Wizard ended susccessfully. Hope it helps.
December 21st, 2011 10:03am

Hello, I think the problem is different. I have 3 WFE 1 db and 1 CenAdmin farm. When I do the update I have noticed something. The first server I run the psconfig will upgrade all databases to SP3 and the rest can not do it as it was upgaded previously. It seems the error thrown by psconfig is false, as when I check all the file versions, farm build are upgraded and everything works perfectly. Just a thought...
Free Windows Admin Tool Kit Click here and download it now
April 24th, 2012 3:46am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics