Recently I was performing a test migration of a site from MOSS to SharePoint 2010, using the stsadm export & import options.
The site contents were with all the versions & no file compression:
stsadm -o export -url "
Then the site was imported into a blank SharePoint 2010 site:
stsadm -o import -url "
The import process failed with following error:
FatalError: The version of the package 12.0.10.0 is different from the current version this program supports, 14.0.0.0.
Debug: at Microsoft.SharePoint.Deployment.SPDeploymentSchemaVersion.Validate(SPSite site)
at Microsoft.SharePoint.Deployment.SPImport.Run()
Progress: Import did not complete.
The culprit is the line:
<SchemaVersion Version="12.0.10.0" Build="12.0.0.6514" DatabaseVersion="476278" SiteVersion="0" />
in SystemData.xml.
Replace Version="12.0.0.0" with Version="14.0.0.0"
and Build="12.0.0.6514" with Version="14.0.4762.1000".
Here the build number "12.0.0.6514" is the MOSS version of the servere where the backup was performed and "14.0.4762.1000" is the build number of the SharePoint 2010 server where the import is being performed. Check the versions on both the export & import servers and replace the above values with the ones on your servers.
I edited the SystemData.xml file and ran the stsadm import process after that and it completed smoothly. There were a few errors and warnings, however, but those did not abort the process. If there is another critical error resulting in the import operation being aborted, look at the import.log file (in th folder where the site contents are being imported from) and there will be afair indication of what went wrong. This is the reason I export contents with the nofilecompression option, as it gives me the ability to have a look at the contents and find/rectify the cause of the errors.
Hello,
ReplyDeleteI am new to sharepoint could you please help me. how to modified SystemData.xml. how to modified .cab file?
Hi B, I believe you have exported the site in compressed format.
ReplyDelete1. Browse to the folder where the cab file is generated
2. Double click on the file, you will be able to view its contents
3. Select all the files and copy the to another folder (create a new blank folder)
4. There you will find the SystemData.xml file.
5. Open it with either Notepad, Visual Studio or any other editing tool and modify.
6. After you have finished editing save the file and compress the folder, using windows explorer (right-click on folder and from pop-up menu select Send to --> Compressed(zipped) folder).
7. Rename the compressed file to .cab and you are ready to go.
Even if you do not recompress the folder, you can use the stsadm import with -nofilecompression switch. I hope this resolves your issue.
@ Arvit Thank you very much, I want to add some thing, i had proble with .cab file so, i used -nofilecompression and edit SystemData.xml file with out any problem.
ReplyDeleteNo probs B. The steps described are for the scenario when the site was exported in compressed format. But it holds well for a site exported in uncompressed mode (saves you the hassle of uncompressing & the comressing back again). The only thing to note will be the use of -nofilecompression parameter while importing site from the backup.
ReplyDeleteJust wanted to say thanks. I am using the Content Deployment Wizard provided by Codeplex, and this solution worked perfectly.
ReplyDeleteI get an error FatalError: The version of the package 14.0.0.0 is different from the current version this program supports, 14.0.0.0.
ReplyDeletePlease help me in this regard
Hi Muhammad, This might be due to the version & build being different. If you can get the correct version & build, replace the ones in in SystemData.xml with the correct values.
ReplyDeleteCheck the following link:
http://www.sharepointedutech.com/2010/09/06/sharepoint-server-2010-patch-levels-and-cumulative-updates/
If you cannot get the correct values, the easiest way would be to create a dummy site and then export it using stsadm (non compressed mode). The SystemData.xml of that export will provide you with the correct version & build numbers for your SharePoint installation.
I hope it helps.