Failed to initiate the upgrade sequence.

Question

_{Thursday, April 4, 2019 5:51 PM}

Trying to run the SharePoint 2010 Products Configuration Wizard and getting the following error

Failed to initiate the upgrade sequence.
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: Exception of type 'Microsoft.SharePoint.Upgrade.SPUpgradeException' was thrown.
Microsoft.SharePoint.Upgrade.SPUpgradeException: Exception of type 'Microsoft.SharePoint.Upgrade.SPUpgradeException' was thrown.

Upgrade log shows the following:

Upgrade object too new (build version = 14.0.7225.5000, schema version = 4.1.2.0. Current server (build version = 14.0.7175, schema version = 4.1.2.0)

All replies (7)

_{Friday, April 5, 2019 3:33 AM | 1 vote}

Hi spaceace3232,

To troubleshoot the issue, check things below:

1. Check the build number in the Central administration. Go to central administration->System settings-> Manage servers in this farm.

2. Then go to the registry to check the build number in the current server. Go to start->run->type “regedit”->find the location below->find “BuildVersion”.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0

3. If the two build numbers are different, then we can modify the registry to the build number in central administration. After modifying the registry, then you should restart the computer.

For more detailed information, refer to the article below.

stsadm upgrade fails with too new exception.

http://ftduarte.blogspot.com/2011/04/stsadm-upgrade-fails-with-too-new.html

Best regards,

Sara Fan

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

SharePoint Server 2019 has been released, you can click

here to download it.
Click

here to learn new features. Visit the dedicated

forum to share, explore and talk to experts about SharePoint Server 2019.

_{Friday, April 5, 2019 4:34 AM}

I changed the registry key and rebooted.

Ran the command and log generated same error.

I replaced all registry entries to the other build version and rebooted.

I ran the command and the "too new" error went away, but still get the error

An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: Exception of type 'Microsoft.SharePoint.Upgrade.SPUpgradeException' was thrown.

_{Friday, April 5, 2019 8:30 AM}

Hi spaceace3232,

You could check the upgrade status in central administration. Go to central administration->Upgrade and Migration ->Check upgrade status.

And you also could check if there is detailed information about the issue in the ULS log.

Best regards,

Sara Fan

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

SharePoint Server 2019 has been released, you can click

here to download it.
Click

here to learn new features. Visit the dedicated

forum to share, explore and talk to experts about SharePoint Server 2019.

_{Friday, April 5, 2019 2:28 PM}

Hi Sara,

Upgrade status is reported as successful when it was completed prior to the upgrade. There are no missing updates to install.

I think the problem lies in the Cumulative roll-up pack that was installed post Sharepoint reinstallation. 

I had looked on the server before I upgraded it and noticed that the last patch was installed in early 2018. I saw it had kb4011272 which was CU from November 2017. So that's what I installed
after I reinstalled sharepoint.

However, the logs are showing the following when I try to upgrade through the configuration wizard

Upgrade object too new (build version = 14.0.7225.5000, schema version = 4.1.2.0)
Current server (build version = 14.0.7175.5000, schema version = 4.1.2.0)

Build version = 14.0.7225.5000 wich was CU for December 2018.

_{Tuesday, April 9, 2019 8:40 AM}

Hi spaceace3232,

Did you still get the error below in the ULS log after you change the register?

Upgrade object too new (build version = 14.0.7225.5000, schema version = 4.1.2.0) Current server (build version = 14.0.7175.5000, schema version = 4.1.2.0)

To troubleshoot the issue, you could clear the SharePoint configuration and run the SharePoint 2013 products configuration wizard.

To clear the SharePoint configuration, you could follow the steps in the article.

Best regards,

Sara Fan

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

SharePoint Server 2019 has been released, you can click

here to download it.
Click

here to learn new features. Visit the dedicated

forum to share, explore and talk to experts about SharePoint Server 2019.

_{Thursday, April 11, 2019 9:59 AM}

Hi spaceace3232,

How is everything going?

Is there anything update about this issue?

If the reply is helpful to you, you could mark the helpful reply as answer. Thanks for your understanding.

Best regards,

Sara Fan

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

SharePoint Server 2019 has been released, you can click

here to download it.
Click

here to learn new features. Visit the dedicated

forum to share, explore and talk to experts about SharePoint Server 2019.

_{Monday, April 15, 2019 2:42 AM}

Hi spaceace3232,

I am checking to see how things are going there on this issue. Please let us know if you would like further assistance.

If the issue was resolved, you can mark the helpful post as answer to help other community members find the helpful information quickly. 

Best regards,

Sara Fan

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

SharePoint Server 2019 has been released, you can click

here to download it.
Click

here to learn new features. Visit the dedicated

forum to share, explore and talk to experts about SharePoint Server 2019.