Portal creation failed Microsoft.SharePoint.SPException: The database schema is too old to perform this operation in this SharePoint cluster. Please upgrade the database and try again. ---> System.Runtime.InteropServices.COMException (0x81070571): The database schema is too old to perform this operation in this SharePoint cluster. Please upgrade the database and try again.Restoring a Database Using MS SQL Server You can use MS Enterprise Manger for SQL Server 2000 or MS SQL Server Management Studio to restore the 3 .SPB files. 1. Restore .SPB files (they are really just standard MS SQL backup files) into the database of your choice. NOTE: The configuration database can and should be recreated when moving to a new machine and thus does not need to be backed manually (SharePoint Portal Server Data Backup and Restore doesn't back it up either) and does not need to be restored either. 2. Go to the SharePoint Central Administration web page and choose "Create a portal site" under the "Portal Site and Virtual Server Configuration" section. 3. Click the Restore radio button, and fill in the names of the databases you restored. 4. If this is a new server that you restored to, you will need to modify some of the data in the database. This of course is not support by Microsoft. I have not had any issues doing this, but I cannot be held responsible if it does cause any errors as any database changes to SharePoint is not supported by Microsoft (or me for that matter). 5. At this point, the SharePoint portal should come up without errors. You should be able to create a new Windows SharePoint Services site without errors. If you have Site Definitions, themes, etc defined specifically for your purposes, you will most likely need to install and configure them before existing WSS sites will come up without error. 6. If you are using SharePoint Portal Server to keep a listing of your sites through its Sites page, you will need to update each reference to the since they are stored in the database and still point to the old server. You can always type them in the browser directly, but it is probably best to correct this to avoid accidentally hitting the production or old server. If you have a few sites, you can change this by hand, if you have a lot of sites I recommend a SQL update statement. The easiest way I have found to do this is to do a global search in replace in all three databases (not config, just Profile, Services, Site). I use something like SearchAndReplaceAllTAbles 'http://sharepoint.myco.com:80', 'http://sharepointnew.myco.com:8080' SearchAndReplaceAllTAbles 'http://sharepoint.myco.com', 'http://sharepointnew.myco.com:8080' SearchAndReplaceAllTAbles 'http://sharepoint', 'http://sharepointnew.myco.com:8080'
SearchAndReplaceAllTAbles 'sharepoint.myco.com:80', 'sharepointnew.myco.com:8080' SearchAndReplaceAllTAbles 'sharepoint.myco.com', 'sharepointnew.myco.com:8080'
SearchAndReplaceAllTAbles 'sharepoint', 'sharepointnew.myco.com:8080'Here is the source code for this SearchAndReplaceAllTables stored procedure: http://justgeeks.blogspot.com/2007/01/sql-2005-search-and-replace-on-data.html I recommend looking at what will be replaced first, I recommend using SearchAllTables first. Here is the source: http://justgeeks.blogspot.com/2006/10/search-ms-sql-server-for-any-text.html The url is not always fully qualified, some have ports, http, sts, etc so you may need to be strategic in the order and what you replace. The above should get most of it though. Please remember, this is a very big change. I highly recommend you look at what is being replaced and test, test, test the first time you do it to make sure nothing broke. When you are done, searches and site directory should be accurate again. You may find some images on particular sites still point old server and / or don't load. You may need to change them manually.