Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

During migration - content db schema version not consistent

  Asked By: Karissa    Date: Dec 07    Category: MOSS    Views: 4161

I am looking for options to resolve my issue with version difference.

We have prod. Server with SharePoint version is 12.0.4318.We have built a new
new VM server and upgraded with latest Service packs & CU and thus the version
is 12.0.6539.When I try restoring the content database from prod. server to VM
server, I am getting the error - "The schema version (3.1.8.0) of the database
WSS_Content_7110 on SERVER_NAME is not consistent with the expected database
schema version (3.1.11.0) on SERVER_NAME. Connections to this database from
this server have been blocked to avoid data loss. Upgrade the web front end or
the content database to ensure that these versions match."
• The option of updating the production server to latest SharePoint version is
ruled out.

We have tried almost all the solutions from internet search, but haven't been
able to go past the issue.

Share: 

 

3 Answers Found

 
Answer #1    Answered By: Rose Silva     Answered On: Dec 07

Are both servers at the same patch level?

Both machines must be at the same patch level

 
Answer #2    Answered By: Maegan Ellison     Answered On: Dec 07

I don't think you can restore a content database that is a different version
from the existing farm. You've got two options (one I know works, but the
second one might work)



1. Create a VM that is the same version as your production farm.
Restore the database to that and then upgrade the VM farm. (I know that
approach works)

2. Back up just the database in production using SQL backup. Restore
it to the SQL server of the upgraded farm in the VM. THEN re-attach it to
the upgraded farm using STSADM. (This works when going from 2003->2007 or
2007->2010 but I've never tried it going from one service pack to another.
But it might work.)

 
Answer #3    Answered By: Yahaira Shannon     Answered On: Dec 07

I ran into this issue recently, and like others have mentioned, both
environments have to be on the same patch level. i used this site as a guide
to getting the correct
patcheswww.sharepointdevwiki.com/.../Sha\
rePoint+Versions.
After moving the databases, I upgraded to the latest patches for MOSS 2007,
and then upgraded the server to SharePoint 2010.

 




Tagged: