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
327 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
8 Comments
 
LVL 81

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 81

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
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

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
 
LVL 81

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

Business Impact of IT Communications

What are the business impacts of how well businesses communicate during an IT incident? Targeting, speed, and transparency all matter. Find out more in this infographic.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
Recently we ran in to an issue while running some SQL jobs where we were trying to process the cubes.  We got an error saying failure stating 'NT SERVICE\SQLSERVERAGENT does not have access to Analysis Services. So this is a way to automate that wit…
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
Viewers will learn how the fundamental information of how to create a table.

751 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