Tuesday, November 11, 2014

Restore-SPSite Error: 0x80070003 on Backup-Restore SharePoint Site Collection Between Different Farms

When I was trying to backup restore between SharePoint DEV and QA Farms got this error message:
Restore-SPSite : <nativehr>0x80070003</nativehr><nativestack></nativestack>
Restore-SPSite : <nativehr>0x80070003</nativehr><nativestack></nativestack>

Root Cause:
The source and target SharePoint Farm's build version mismatch!

Solution: Upgrade either the source or destination SharePoint farm and then backup-restore.

Backdoor way:
What if you don't have the option of immediate upgrade and complete this backup restore operation? Here is the backdoor way to skip upgrades and backup-restore SharePoint sites or lists between farms with different versions/build numbers.

One way is: Backup-restore the content database of your old SharePoint site collection to the target farm. Mount and Upgrade the content database (Mount-SPContentDatabase followed by Upgrade-SPContentDatabase) in the target farm.

There is an another way: Binary Edit! Just open the backup file in any HEX editor tool, I've used HxD from: http://mh-nexus.de/en/hxd/ , and change the version build number to your target SharePoint farm version.
SharePoint Restore-SPSite Error:0x80070003
Try restoring the site collection again, It should work now.

Another Cases
1: Restore Operation interrupted and site corrupted: 
Experienced the same issue when the restore operation got interrupted in an another case. Since the restore is stopped in middle, that left the site in unsupported state. So the solution is: Delete the partially restored site and run restore again. Here is how: How to Delete Corrupted Site Collections in SharePoint using PowerShell

2. Database is not upgraded:
If the content database in which site collection exists - is not already upgraded to the current SharePoint build version, You'll receive this error. Solution? Do: Upgrade-SPContentDatabase "DatabaseName" before taking backup (or make sure the target database is upgraded!)

3. Last but not least: User who runs the backup-restore doesn't has enough permission on SQL Server!



You might also like:
SharePoint Usage Reports
Usage reports, collaboration and audit for SharePoint.
Document SharePoint Farm
Automatically generate SharePoint documentation.
*Sponsored


Check out these SharePoint products:

1 comment :

  1. Hi Salaudeen,
    Thanks for the solution.
    My case is Migration: Source: SPF Preview 2013 -> Destination: SPF 2013 SP1

    First, I tried the 2nd way with Hex-Editor. No luck :-(
    But 1st way worked like a charm :)
    Mount-SPContentDatabase followed by Upgrade-SPContentDatabase

    --Muthukannan.G

    ReplyDelete

Please Login and comment to get your questions answered!

You might also like:

Related Posts Plugin for WordPress, Blogger...