Site Deployment Import Creates Duplicate Postings in the Same Channel (319071)

SYMPTOMS

After the site deployment import process, a user may see two default postings in the same channel where the user exported only one default posting.

CAUSE

This occurs when users import postings in the same channel that have the same name but have different GUID references in the database. Site deployment determines if the posting in the Resolution Object Package (ROP) file is associated with any posting in the importing server database by examining the GUIDs. If postings have the same GUID, site deployment replaces the version on the importing server with the version on the ROP file. If they are different, a new posting is created on the importing server.

RESOLUTION

To avoid this problem, avoid having duplicate postings that are created in the same channel. One way to do this is to use the Delete all existing containers contents when replacing containers feature in Site Deployment Manager. This feature can be found on the main page of Site Deployment Manager on the Container Rules tab. To enable this feature, you must also click to select Change container hierarchy on destination to match the package hierarchy.

MORE INFORMATION

The feature that this article describes deletes all of the contents in the importing server channel before it replaces the contents of the channel from the Site Deployment ROP file. The contents in the channel include all the postings, subchannels, and contents of the subchannel. As a result, only use this feature if you export the whole channel branch and do not manually exclude some of the subchannels and postings under the main channel heirarchy.

REFERENCES

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

319254 Page URLs Appear as GUID Base Names in the Client Browser Window