Home > Administration, Configuration, Uncategorized > SP1 Upgrade issues

SP1 Upgrade issues


This post is for you if

* Build version was “14.0.5139.5003” before SP1 upgrade

* You get following error “There is no user table matching the input name ‘AllSites’

* Or you get Upgrade object too new (build version = 14.0.5139.5003, schema version = 4.1.7.0). Current server (build version = 14.0.6029.1000, schema version = 4.1.6.0).

Root Cause:

Sometime in May there was a hotfix for a discussion board issue(KB2547226). After this hotfix the Build version of the Config DB will be 14.0.5139.5003 & DB Schema version number is 4.1.7.0. You can check this schema version number on any of the content database table named versions. From one of the error message above it is very clear that this version is greater than what is coming from SP1.

But there are high chances that your admin content database schema version number is 4.1.10.0 (bcose some remedy steps what we attempt makes this possible, but still of no use to us)

Solution:

If you have installed the Hotfix then you don’t have choices.  As of today (11-Oct-2011) there is no supported way to overcome this issue other than modifying the DB directly (i know it is unsupported, but you get this solution even from Microsoft support).

So we have to manually modify the schema version to something lesser than 4.1.7.0   4.1.10.0 (actually to previous version number). It is highly recommended to backup the database before attempting any of these. Please try this in lower environment first (involving premium support is the best thing to do as they might have better solution as days goes on)

IF NOT EXISTS (SELECT * FROM sysobjects WHERE id = object_id(N'[dbo].[AllSites]’) AND OBJECTPROPERTY(id, N’IsUserTable’) = 1)

BEGIN

UPDATE Versions SET Version = ‘4.0.148.0’ WHERE Version = ‘4.1.7.0’ AND VersionId = ‘6333368D-85F0-4EF5-8241-5252B12B2E50’

END

Execute the above script on all content databases including admin content database. Don’t execute this on service application db’s & config db’s.  You might have to change the where clause based on the current value.

Once this is executed, run the config wizard and it should get completed successfully.

Hope this helps someone.

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s

%d bloggers like this: