Home » Sharepoint

Cannot Restore Backup from Sharepoint Server 2007 to Sharepoint Server 2010 Trial Version

After installing the trial version of Sharepointn 2010 I wanted to restore my Sharepoint 2007 sites to it but received the following error: 

"The site collection could not be restored. If this problem persists, please make sure the content databases are available and have sufficient free space."

I went on to create a new content database in sharepoint 2010 but it still did not work.

The old database i.e the one used by the sharepoint 2007 server is SQL 2005. During the installation of the sharepoint 2010 version I selected SQl Server Express for the database.

Is there any specifics for migrating from MOSS 2007 to sharepoint 2010?

Thanks for helping


5 Answers Found


Answer 1

You can't restore  a sharepoint  2007 backup  to SharePoint 2010.  You need to restore it to SharePoint 2007 and then upgrade it to 2010.  You also can't restore a full SQL database to SQL express.  You can go the other way, but not to Express.  YOu can find out more about upgrading SharePoint at the SharePoint 2010 upgrade resource centers.  There is one for IT-Pros and one for Devs.

IT Pros - http://technet.microsoft.com/en-us/sharepoint/ee517214.aspx

Dev - http://msdn.microsoft.com/en-us/sharepoint/ee514557.aspx


Answer 2

Thanks Paul

Answer 3

Hey Crash...  Kindly following steps

Database Attach Upgrade - Migration Steps





First let us take a look at the Pre-Requisites for Up-gradation Pre-Requisites

MOSS 2007 should have SP2 Installed. You should have SP2 installed on your MOSS 2007 machine. The pre-upgrade check command was added only in SP2. So if you do not have SP2 installed you will not have the pre-upgrade check command in stsadm.SharePoint 2010 should be set up on a different server  machine.


Below are the steps and their explanation

Step 1: We have to run the Pre-Upgrade check command on the MOSS 2007 server to find out if there are any issues in the SharePoint 2007 farm (like missing site definitions, features etc.).
Running the command will generate an html report for you. This report will not only notify you of any issues regarding your SharePoint farm such as missing Site Definition Information or missing Feature Information, but it also provides you with a blueprint of your SharePoint Farm setup

Some of the details that are provided by this report are

n        Search content sources and start addresses

n        Office Server Search topology

n        Servers in the current farm

n        SharePoint version  and list of components
running in the farm

n        Supported upgrade types (In-place Upgrade and Content Database Attach)

n        Site Definition and Feature Information

n        Language pack information

n        Alternate Access Mappings (AAM) that will need to be recreated

n        Customized List views (these will not be upgraded)

n        Customized field types (these will not be upgraded)

n        WSS Search topology

n        List of Content Databases and SQL server location

Syntax: stsadm –o preupgradecheck






After you have reviewed the report and fixed any issues which might be there in your farm you can move to the next step.

At this point your database is checked for up gradation and transferred to the SharePoint 2010 farm.

Now in the next steps we will start the Upgrade process on the SharePoint 2010 farm.

Step 2: backup  the content database of the Web Application from SQL Server. Copy it to the machine where SharePoint 2010 is installed and restore  the backup of database in SQL Server using SQL Server Management Studio. To restore the backup you will first have to create an empty database in SQL Server and the restore your database one top of this new Database. While restoring make sure that the Overwrite the Existing Database option is checked.
















Now Click on O.K. to confirm  new Authenticated users


Click O.k.




Step 3: Create a new Web Application in SharePoint 2010.


Once you will create a web application a content database will be attached to it, remove the database attached to the web application via Central Administration -> Application Management -> Manage Content Databases.
Make sure that no database is attached to the Web Application which you have just created








Step 4: Run the Test-SPContentDatabase cmdlet (PowerShell).
Running this command will check if the database is ready for upgrade or not. This will tell you about the things which are missing in this farm (E.g. Any setup files, web parts etc.). You can either attend to these missing features pre or post-upgrade but this depends on whether there are any items that will block the upgrade from proceeding.



PS C:\Users\MossAdmin> Test-spcontentdatabase -name Restored -webapplication htt



Output On Screen


Category        : MissingSetupFile

Error           : True

UpgradeBlocking : False

Message         : File [Features\ExcelServerSite\Microsoft.Office.Excel.WebUI.d

                  wp] is referenced [1] times in the database [Restored], but i

                  s not installed on the current farm. Please install any featu

                  re/solution which contains this file.

Remedy          : One or more setup files are referenced in the database [Resto

                  red], but are not installed on the current farm. Please insta

                  ll any feature or solution which contains these files.





Step 5: Run the stsadm addcontentdb command

Run the stsadm addcontentdb command to add the content Database to the web application which you created. This will initiate the upgrade process as shown in the screen below

PS C:\Users\MossAdmin> stsadm -o addcontentdb -url  http://moss:7000 -databasename Restored


Operation completed successfully.








Step 6: Review the Upgrade Log file and fix the errors.


The upgrade process generates two log files. (Under 14/LOGS)
The upgrade log file which contains all the information about the upgrade
The error log file which gives you the error which occurred during the upgrade
You can review the log files and fix the errors by manually upgrading the Customizations which were there in your site








Step 7:  Upgrade Customizations

Have to manually upgrade the customizations. If any of your customization is blocking the upgrade you will have to upgrade the customization first and then do the upgrade.

 The customizations in this upgrade included the following things

–A custom Solution (wsp)
–Custom Web Parts
–Custom Images (/_layouts/Images)

Add the solution to the farm solution store by using stsadm and then deployed it to web application then copy the Web Part assemblies to the GAC and added the Safe Control entries in the web.config file of the Web Application then copy all the images used in my Web Application to appropriate places (like /14/TEMPLATE/IMAGES)

Once you have upgraded all the customizations your upgrade is complete.








Answer 4

hmmmmm.....quite a mouthful this, but thanks ThegreatAbhi! I will try this and get back to you

Answer 5

For more details and pictures, TheGreatAbhi's post was copy & pasted from:




hi all

I am aware of a version dependency on the stsadm -o backup/restore operation.

But will the same dependency exist for a content DB backup restore..

i.e. for example will we able to restore a content DB backup taken from a server with version say to a server with say assuming that the versions of SQL is the same in both cases.

Will the version difference in SQL create issues

Thanks in advance




I need to transfer some Sites from 2007 to 2010. Is there a a way I can use my backup (done with stsadm.exe" -o backup -ur in 2007) on the Sharepoint Server 2010?

Is there any other easy way? I can't upgrade the previous installation from 2007 to 2010...



What if I want to backup Project Server 2010 AND SharePoint 2010 Products server farm (Configuration Database and Central Administration Content Database)?

From http://technet.microsoft.com/en-us/library/dd207294.aspx ("Prepare to back up and restore a Project Server 2010 farm"):

Although the configuration database and Central Administration content database can be backed up, we recommend against doing it with built-in tools on a running farm. Restoring backups of the configuration database and Central Administration content database taken from a running farm by using the tools built in to SharePoint 2010 Products or SQL Server is not supported.

This is because data in these databases may not be synchronized with data in other SharePoint 2010 Products databases. Therefore, the tools built in to SharePoint 2010 Products do not recover these databases during a farm-level recovery operation.

Thank you very much


Hi all!

I want to backup a complete environment SharePoint 2010 with Project Server 2010.

I read that there are 2 ways:

with built-in tool with powershell

but, if I use the built-in tool, from http://technet.microsoft.com/en-us/library/dd207294.aspx :

"Although the configuration database and Central Administration content database can be backed up, we recommend against doing it with built-in tools on a running farm. Restoring backups of the configuration database and Central Administration content database taken from a running farm by using the tools built in to SharePoint 2010 Products or SQL Server is not supported."

Question: if I use the PowerShell command Backup-SPFarm, the backup is really complete? I mean, with Configuration Database and Central Administration Content Database? And with Restore-SPFarm can I restore ALL the environment?

Thank you very much

I have a client who setup MOSS 2007 Trial and are coming up on the expiration.  Instead of buying a key for MOSS 2007 they purchased Sharepoint 2010.  I'm having some problems upgrading because its the trial.  What are my options for upgrading/migrating over to Sharepoitn 2010?


Why can't i install project server 2010 trial on sharepoint 2010 trial?

As stated on the trial download page: http://technet.microsoft.com/en-us/evalcenter/ee410540.aspx , i have to install sharepoint server 2010 first, and there is also a link to the sharepoint server 2010 trial.

I have already installed the sharepoint server 2010 trial, and confirmed that it is working.

When trying to install project server 2010 i receive the following error: http://i38.tinypic.com/6z118n.jpg

The project 2010 faqs at: http://www.microsoft.com/project/en/us/project-server-faqs.aspx also states that i have to install sharepoint server 2010 trial first.

is this i bug?


Johannes Pham

Hi, I am hoping someone can help me. I am currently using a trial version of Sharepoint 2010 server. I am attempting to copy one library to another library, but the copy (send to) feature is disabled. Actually, there are several features that are disabled. One more thing, the only option that is available to me is to "create a new folder." Any ideas? Are they disabled because it is a trial version or am I not doing something correctly? Do you have a user guide for the trial version of the Sharepoint 2010 server? Hoping to hear from you soon. - JMK10
I have a Sharepoint 2010 server running SQL Express. (SERVER A)     I have an identically configured Sharepoint 2010 server running SQL Express (SERVER B).   I want to migrate the data from SERVER A to SERVER B.   Does anyone out there have a step by step guide for this?

My company has been using a project 2007 server in a legacy domain for two years, and we recently migrated all files, accounts and usage to a new system in our new domain.

When our product group went back to refer to the old PWA system, we found that it was no longer licensed.

We see that when we connect to Sharepoint Central Administration and choose "Convert License Type" the current license listed is "Project Server 2007 Trial." Although I was not the original admin of the system, and did not perform the installation, I find it difficult to beleive we've been operating on a trial license for 2 years. We recently renewed our EA agreement, so I'm curious as to whether or not the EA change may have impacted the licensing on the system.

We are unable to connect to this old PWA, with the error "Trial Period Expired."

I've never run into automated changes in server product licensing before with Microsoft. Does anyone know what condition may have caused this? I'm completely baffled.

We are using sharepoint server 2007,we are moving to a new location after 2 months,and we want to test the upgrade to sharepoint 2010 at the new location yet we will still be using sharepoint 2007 at  our old location ,if we performed the upgrade now ,then after 2 months we want to restore the latest backup from sharepoint 2007 to sharepoint 2010,is this possible 

Hi All,

           I need to migrate a web application from MOSS 2007 to SharePoint 2010 but unable to figure out the right process to do. stsadm backup and restore will be right process or I need to take the backup of the content data base restore it in the SharePoint 2010 environment and then associate the web application with the restored Content data base. I am unable to figure out the right approach. Any help will be appreciated.

Thanks in advance





Is there a proper way to capture all of the data from a current installation of Project Server 2007 so that I can do a restore on a fresh install on the same server.  I have some hard drive issues that are forcing me to rebuild the server.  I want to be able to backup all of my data so that after I do a rebuild and new install, I will be able to restore everything, so that no data is lost from pwa.

also, i have SQL Server 2008 installed on this server.  Is there a proper way to do the install of Project Server and PWA so that it utilizes 2008 instead of the out of the box SQL 2005 Express.




Hi, is there any process flow diagram which I could use to understand the steps used to migrate from sharepoint 2007 version to 2010 version???



On trying to restore a site backup from one moss server to another using STSADM i encountered this error.

Your backup is from a different version of Windows SharePoint Services and cannot be restored to a server running the current version. The backup file should be restored to a server with version '763911617.771019783.639568184.357903087' or later.

The versions of MOSS at both server is  What is the version numbers indicated in the error message. Is it the Servers Operating System updates version. Where can i find the relevance of the numbers





You cannot vote on your own post 

I have been given the following TFS bak files from a cratered server where the original adminsitrator has left the company:

10/18/2010  05:03 PM         7,643,648 tfsActivityLoging.bakh
10/18/2010  05:04 PM        11,962,880 tfsBuild.bak
10/18/2010  05:04 PM        27,787,776 TFSIntegration.bak
10/18/2010  05:05 PM     1,403,571,712 tfsVersionControl.bak
10/18/2010  05:05 PM        70,339,072 tfsWarehouse.bak
10/18/2010  05:05 PM        51,671,552 tfsWorkItemTracking.bak
10/18/2010  05:05 PM         5,402,112 tfsWorkItemTrackingAttachments.bak

My question is it even possbile to restore them to Team Foundation Server 2010 client version so I can view them?

IF so, will some one point me to a technical article to give me the steps to try?

I really appreciate it I have been a TFS user for a while but never an admin before.


I made a backup of SharePoint farm from 2010 and tried to restore on a dev server and kept getting this error.  I looked at the versions of SharePoint on both servers, and they were identical:  14.0.4763.1000

I'm posting this although it is not a question, but a statement that might help someone else.  It took a while to notice that there had been an upgrade on the original server that the new dev box did not yet have... not an SP, but more like a hotfix type upgrade.

In Central Admin, go to "Upgrade and Migration".  Click on "Check product and patch installation status".  Scroll down the page of results and see if there are any links to updates that have been installed on the original server that are not on the new server, or vice-versa.  I did find a link on my original server.  Clicking on it opened the update page, so I copied the URL, went to my dev server, opened that page and installed the update, and voila!


Hi all,

I have a few questions about Sharepoint Workspace 2010, hopefully someone will be able to shed some light on it as it is difficult to find relevant information on the web.

Firstly it seems that it does not work with the BPOS suite, certainly that was my experience trying to get it working.

Secondly, does it run on a PC with office 2007 installed, I wanted to install a trial on a client PC to test it but I was unable to find a stand alone trial, does such a thing exist? I know the product can be purchased on its own.

I have many clients running the new Live Sync Beta and the Groove workspaces seem like a much better way to handle this requirement.



Will changes to MOSS 2007 with Sharepoint Designer 2007 work after upgrade to Sharepoint Server 2010?

Or do I have to make same changes again with Sharepoint Designer 2010 after upgrade? 

I have backuped and restored a site collection from our development server to our production server. These servers are on different active directory domains. I have got the site working except for search. When I attemp to run a search - just a basic site search - I get the error 'The search request was unable to connect to the search service' displaying on the results page. Any help would be appreciated - even if it is just help on how to apply the fixes that would have worked in 2007 to 2010. Thanks

Hello, from my reading of technet and other resources the best way to restore granular data (individual sites, document libraries/lists etc.) would be to mount a database backup in another SQL instance and use the 'Recover data from an unattached content database' feature to export the data to a .cmp file and use powershell to import it back into Sharepoint.

The question I have is that lets say a site (not site collection) has been deleted and I use powershell to import a backup of the deleted site back into Sharepoint - I must first recreate the site with the same template as the one that is being resored and I just wanted to know how I could find out what template the deleted site used in the first place (as I am not the one who initially created the site).

Thanks for any help given. 


<< Previous      Next >>

Microsoft   |   Windows   |   Visual Studio   |   Sharepoint   |   Azure