Sharepoint 2010 import spweb failed to read package file
To force overwrite of list items you have to retain the object identity. Without retaining the object identity you will end up with multiple list items with potentially the same content. The import is not able to decide whether you would like to overwrite an existing item with the same name or if you would like to have multiple list items with the same name. When doing an export and import without retaining the object identity on the destination server you can end up with duplicate items in lists as each import tries to create the same list item again with a different GUID. Problem 2: Running multiple imports without retaining object identity for updates of the same content => In order to avoid this problem you have to guarantee that content added to the destination database will not have any name/guid conflicts with the source database – even if new content is added to the source database in the future! OriginalException: There can only be one instance of this list type in a web. In case that items with the same name but different GUID are not allowed for the affected item the import will run into an exception similar to the one below and stop:įailed to create the 'Pages' library. This will be the case (e.g.) for usual ListItems. In case that items with the same name but different GUID are allowed for the affected item you will end up with two items with the same name on the destination server. This can happen if someone has authored on the destination server and created items with the same name but or if he imported content from the source server WITHOUT RetainObjectIdentity setting set to true. Problems occur if there is an item with the same name but a different Guid in the destination database. If the item already exists it will be updated.
The reason is that with RetainObjectIdentity enabled the imported object will have to be created with the same name and the same guid at the same location in the destination database as it was in the source database.
So why is there a problem when mixing imports with different RetainObjectIdentity settings?
STSADM -o import will not retain the object identity while content deployment does. Problem 1: Mixing deployments with and without retaining object identityįirst of all: if possible you should avoid this! Importing with different settings for this property into the same database can lead to serious problems during future deployment and such databases will become hard to maintain.īe aware that this also means that you should not use STSADM -o import against a database that should be used as the destination of a content deployment job! As it is often hard to find the right resource I have now decided to compile the different known issues into one large article: In the past I have released several blogs about the various problems that can occur with Content Deployment.