I am in the process of moving my databases from a standalone install on a 2003 server to a New Farm on a 2003 server but using 64 bit rather than 32 bit. I have updated and installed everything i need including SQL 2008 Express, i have installed the new farm and created the first default Web Application making sure it`s named the same as the old server, i have not proceeded to create the Site Collection yet (Do i need to do this?) My problem is that when i attach the database from the old server to the new Web App on the New Server i recieve this error message: The specified SPContentDatabase Name=WSS_Content Parent=SPDatabaseServiceInstance Name=SQLEXPRESS has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object. Can anyone Help me Please?

Make sure your new farm is at an identical or higher Service Pack. On the old farm go to Central Administration Operations Site Settings and get the version number, then do the same for the new farm. The following are version numbers: 12.0.0.6535 MOSS 2007¹ or WSS 3.0 SP2 + April 10 cumulative Update (KB981042 + KB981043) 12.0.0.6529 MOSS 2007¹ or WSS 3.0 SP2 + February 10 cumulative Update (KB978396 + KB978395) 12.0.0.6524 MOSS 2007¹ or WSS 3.0 SP2 + December 09 cumulative Update (KB977027 + KB977026) 12.0.0.6520 MOSS 2007¹ or WSS 3.0 SP2 + October 09 cumulative Update (KB974989 + KB974988) 12.0.0.6514 MOSS 2007¹ or WSS 3.0 SP2 + August 09 cumulative Update (KB973400 + KB973399) 12.0.0.6510 MOSS 2007¹ or WSS 3.0 SP2 + June 09 cumulative Update (KB971538 + KB971537) 12.0.0.6504 MOSS 2007¹ or WSS 3.0 SP2 + April 09 cumulative Update (KB968850 + KB968851) 12.0.0.6421 MOSS 2007¹ or WSS 3.0 SP2 (KB953338 + KB953334) [Updated 1st Aug 09: SP2 download now includes the hotfix (KB971620) that corrects the activation issue more information on the Microsoft SharePoint team blog] 12.0.0.6341 MOSS 2007¹ or WSS 3.0 February 09 cumulative Update (KB961755 + KB961756) 12.0.0.6335 MOSS 2007¹ or WSS 3.0 December 08 cumulative Update (KB960010 + KB960011) 12.0.0.6331 MOSS 2007¹ or WSS 3.0 October 08 cumulative Update (KB957691 + KB957693,KB958567 and KB958569) 12.0.0.6327 MOSS 2007¹ or WSS 3.0 August 08 cumulative update (KB956056 & KB956057) 12.0.0.6318 MOSS 2007¹ or WSS 3.0 Infrastructure Update (KB951695 & KB951297) 12.0.0.6303 MOSS 2007¹ or WSS 3.0 post-SP1 hotfix (KB948945) 12.0.0.6301 MOSS 2007¹ or WSS 3.0 post-SP1 hotfix (KB941274) 12.0.0.6300 MOSS 2007¹ or WSS 3.0 post-SP1 hotfix (KB941422) 12.0.0.6219 MOSS 2007¹ or WSS 3.0 SP1 12.0.0.6039 MOSS 2007¹ or WSS 3.0 October public update 12.0.0.6036 MOSS 2007¹ or WSS 3.0 August 24, 07 hotfix package 12.0.0.4518 MOSS 2007¹ or WSS 3.0 RTM 12.0.0.4407 MOSS 2007¹ or WSS 3.0 Beta 2 TR 12.0.0.4017 MOSS 2007¹ or WSS 3.0 Beta 2 12.0.0.3111 Office 12 (PDC image - pre-beta) - This version of Office does not have a support link in the Add/Remove programs dialog box Instructions to install Service Pack 2 To keep all the files in a SharePoint installation up-to-date, the following packages need to be applied on all servers in the farm. Service Pack 2 contains all fixes released through February of this year, so customers can install it directly on RTM build of the products. Service Pack 2 for Windows SharePoint Services 3.0 Service Pack 2 for Office SharePoint Server 2007 Deploy software updates for Windows SharePoint Services 3.0 http://technet.microsoft.com/en-us/library/cc288269.aspx Deploy software updates for Office SharePoint Server 2007 http://technet.microsoft.com/en-us/library/cc263467.aspx After applying the preceding updates, run the SharePoint Products and Technologies Configuration Wizard or "psconfig –cmd upgrade –inplace b2b -wait” in command line. This needs to be done on every server in the farm with SharePoint installed. The version of content databases should be 12.0.0.6421 after successfully applying these updates. -Ivan Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.

I think the problem you are having is as a result of this: >I have updated and installed everything i need including SQL 2008 Express,' (my bold) When creating a standalone version of WSS 3.0 you do not install SQL Server Express. The WSS 3.0 (Basic) installation will install its own version of SQL Server Express (the "WID" - Windows Internal Database). At the very least your decision to install the normal SQL Server Express means that you will be resticted to 4GB in database size. 2010 Books: SPF 2010; SPS 2010; SPD 2010; InfoPath 2010; Workflow etc. 2007 Books: WSS 3.0; MOSS 2007; SPD 2007; InfoPath 2007; PerformancePoint; SSRS; Workflow Both lists also include books in French; German; Spanish with even more languages in the 2007 list.

I have installed SQL 2008 Express to make use of the 10 GB database, but i did this install seperately due to i want to installing a Farm. Old Sharepoint Server = Win 2003 Server 32 bit using basic install (sql express 2005) Database from this server to New Server. New Sharepoint Server = Win 2003 64 Bit using Farm Install and SQL 2008 Express. Also do i need to attach all the other databases like Sharepoint Central Admin, Sharepoint Config etc, etc from the old server to the new server or just the WSS_Content Database?

Never use a Central Admin Content_Db or a SharePoint_Config_Db from another environment... These are specific to the environment where they were created and it doesnt make any sense to move them.. -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.

So, is it possible with my setup above to move the databses from one server to another and shutdown the old server and after repoint the url in DNS be able to browse to the sharepoint site as if i was using the old server? If so great, but i am still stuck on the first issue regarding the error below: The specified SPContentDatabase Name=WSS_Content Parent=SPDatabaseServiceInstance Name=SQLEXPRESS has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.

Yes, you can move Content_Dbs. Still stuck: The Content_Db you are attempting to move is patched to a more recent patch (more recent schema) than the server where you are moving it. Ensure the patch levels are the same as per my previous post.. The key part of your error is: Please upgrade this SharePoint application server before attempting to access this object. -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.

Thank you Ivan, sorry for being a pain, i am new to this but enjoying every step, i really appreciate all your help with this. So i can move content db`s but not any others? I have a large document control workflow that i made using sharepoint designer, will all the workflows and all the data that makes the site as it is all be in the Content_Db?

No worries Its my pleasure, SharePoint is a Community. Yes, as long as the ListID doesnt change. However, test the WF prior to letting your users start using the new farm.. -Ivan Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.

ListID? How do i check that this has not changed? Or how do i make sure it does not change? What steps i have taken so far are: Build new server to but using 64 bit and installed sql 2008 express. Installed sharepoint 2003 64 bit and created a web app (using the same name as the old server) Moved all databases from old server to new server. Attached WSS_Content database to SQL 2008 Express (do i need to attach all the others?) Or what ones do i need to attach? Now i need to delete the old web app and attach the database to the new web app, but have come across the error above of which i will follow your recommendation. I know i need to point the DNS to the new server, but is there anything else i need to do?