Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 377
  • Last Modified:

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

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
Finlay11
Asked:
Finlay11
  • 5
  • 3
1 Solution
 
David Johnson, CD, MVPOwnerCommented:
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
 
Finlay11Author Commented:
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
 
David Johnson, CD, MVPOwnerCommented:
once they are upgraded they will not be available for your current SP installation, copy them and then upgrade the opies
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
Finlay11Author Commented:
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
 
David Johnson, CD, MVPOwnerCommented:
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
 
Finlay11Author Commented:
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
 
Finlay11Author Commented:
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
 
Finlay11Author Commented:
I mounted the database and it worked fine.
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now