The case:
The site is created from STP template with some data included.
The additional data imported through stsadm
–o import
The result:
List corruption
on the site.
The recommendation:
Don’t combine 2
approaches: STP with data and stsadm –o import.
Either go with:
-
STP with
fresh data ;
-
Stsadm –o import on the blank site template.
Consideration:
STSADM.EXE
-O EXPORT:
It exports data using Object Model and generated new
GUID for every object.
It doesn't copy workflow history and tasks lists.
This means that you
have some hard-coded logic in the site it will be broken after stsadm.exe
export.
(for further analysis, you welcome to read my blog entry - Sharepoint: How to backup site: stsadm export and SPD backup)
P.S.
Some of the errors that you find in the import log that will wreck the havoc:
Importing File Version 1.0
Invalid file name. The file name you specified could not be used
Item does not exist. It may have been deleted by another user.
at Microsoft.SharePoint.SPListItem.EnsureItemIsValid()
P.S.
Some of the errors that you find in the import log that will wreck the havoc:
Importing File Version 1.0
Invalid file name. The file name you specified could not be used
Item does not exist. It may have been deleted by another user.
at Microsoft.SharePoint.SPListItem.EnsureItemIsValid()
No comments:
Post a Comment