Solved

"This database is too old" error when trying to attach database from SharePoint Services 3.0  SP3 to SharePoint Foundation 2010

Posted on 2014-12-01
8
286 Views
Last Modified: 2015-01-14
I'm migrating SharePoint Services 3.0 currently on 32 bit architecture to SharePoint Foundation 2010 on 64 bit architecture.  I have a new VM running Windows 2008  SP1/SQL Server 2008 R2 and have installed SP Foundation 2010.

My current architecture is Windows 2003 R2 SP 2 and SQL Server 2005 SP4.   SharePoint Services is on SP3 (October 2011).  I have copied over and attached my current SP Services 3.0 content database and have run test-spcontentdatabase.   I get this error:


Category : DatabaseValidation
Error: True
UpgradeBlocking : False
Message: This database [WSS_Content_Test_2] is too old and cannot be upgraded.
Remedy: Upgrade this database to Windows SharePoint Services Version 3, SP2 or later.

As I mentioned above, I'm already running SharePoint Service 3 SP3.   Is this error occurring because I'm trying to move the database from a 32 bit install to a 64 bit install or is it something else?

Thanks.
0
Comment
Question by:Finlay11
  • 5
  • 3
8 Comments
 
LVL 78

Expert Comment

by:David Johnson, CD, MVP
ID: 40475123
The complete how-to do the upgrade.. your content databases may be at an earlier level.
http://technet.microsoft.com/en-au/library/ee947140.aspx#Second
0
 

Author Comment

by:Finlay11
ID: 40475200
Is it possible to upgrade my content database while it's attached to my current SP Services 3.0 installation or do I have to  install a temp version of the application to do the upgrade?  If I can upgrade on the current server what commands would I need to run to do this?
0
 
LVL 78

Expert Comment

by:David Johnson, CD, MVP
ID: 40475211
once they are upgraded they will not be available for your current SP installation, copy them and then upgrade the opies
0
 

Author Comment

by:Finlay11
ID: 40478931
Just for my clarification - are you saying that the database needs to be attached to a new SP Services 3.0 instance on a 64 bit platform and in doing so is essentially upgraded.  

Or does the database need to be upgraded because I've updated SharePoint to a higher service pack?

Thanks for your help.
0
Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

 
LVL 78

Expert Comment

by:David Johnson, CD, MVP
ID: 40479908
on the current SP3 machine
try this
cd /d %commonprogramfiles%\Microsoft Shared\Web Server Extensions\12\Bin
psconfig -cmd upgrade -force -inplace v2v -wait
0
 

Author Comment

by:Finlay11
ID: 40486880
Sorry about the delay.  If I run this command will it cause any problems if this is not the solution?  I don't want to cause any new issues.  Also just to confirm, this will update the entire farm?  One other question - should I be using 'b2b' instead of v2v?  I've read that b2b is when you're upgrading from one service pack to another within the same version and v2v is when you're upgrading to a different version.  Thanks again.
0
 

Accepted Solution

by:
Finlay11 earned 0 total points
ID: 40540738
I ended up mounting the database to my new SharePoint Foundation 2010 site and it worked fine.  The error message must have pertained to the fact that the database was coming from a 32 bit installation of SQL Server.
0
 

Author Closing Comment

by:Finlay11
ID: 40548538
I mounted the database and it worked fine.
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

Introduction In my previous article (http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SSIS/A_9150-Loading-XML-Using-SSIS.html) I showed you how the XML Source component can be used to load XML files into a SQL Server database, us…
JSON is being used more and more, besides XML, and you surely wanted to parse the data out into SQL instead of doing it in some Javascript. The below function in SQL Server can do the job for you, returning a quick table with the parsed data.
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now