Site Deployment Import Creates Duplicate Postings in Same Channel (319512)
The information in this article applies to:
- Microsoft Content Management Server 2001 SP1
This article was previously published under Q319512 SYMPTOMS A site deployment import operation may place two copies of
the same page or posting on the import server although only one copy of the
page or posting was exported. Both of the duplicated pages or postings have a
status of "Published". The page or posting that is duplicated is frequently the
default page or posting of the folder or channel. CAUSE The site deployment import checks the globally unique
identifier (GUID) of the imported item with the GUID that is already present in
the database. If the GUIDs match, site deployment overwrites the item (that is,
the page, posting, template, or resources) in the database with the item that
is in the Resolution Object Package (ROP) file that the import process uses. If
the GUID of the page or posting in the ROP file is different from the one in
the database for any reason, site deployment creates a new page or posting in
the channel that is specified in the ROP file instead of overwriting the
previous version of the page or posting on the database. RESOLUTION To resolve this issue, use the Delete all existing containers contents when replacing containers feature during import. This feature deletes the previous version
of the default page or posting and leaves only one copy of the posting on the
production server.
NOTE: This feature also deletes all subchannels under the channel
where the default page is located. As a result, you must carefully plan the
export or you may accidentally delete the subchannels under a channel when you
update the default page or posting. MORE INFORMATION The GUID of the same page or posting on the export server
(typically the authoring server) and the import server (typically the
production server) may be mismatched because of the way that the page is
updated on the export server. If the authors update the page or posting by
creating a new page or posting in the channel, and the authors then expire the
old page or posting after the new page or posting is completed to make sure
that they can revert back to the previous version of the page or posting, the
newly created set of pages or postings has a different GUID than the original
page or posting.
| Modification Type: | Major | Last Reviewed: | 4/14/2003 |
|---|
| Keywords: | kbprb KB319512 |
|---|
|