Microsoft KB Archive/319254

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

Article ID: 319254

Article Last Modified on 10/23/2003

-

APPLIES TO


 * Microsoft Content Management Server 2001 Service Pack 1
 * NCompass Resolution 4.0

-



This article was previously published under Q319254



SYMPTOMS
A site deployment import operation sometimes results in duplicate postings on the importing server database. When this occurs, and when a user tries to access the page on which another posting exists in the same channel with the same name, the Content Management Server (CMS) server may select the older posting to display instead of the newer posting, or the displayed posting may have a URL that is based on the globally unique ID (GUID), such as the following:

NOTE: This example assumes that the user is accessing a default page in a channel.

HTTP:///NR/ExeRes/ASDFLKJD65321654SFE...default.asp

Note that the random characters in this URL are generated by CMS server when the page is cached on the disk cache.



CAUSE
CMS permits more than one posting with the same name to be placed under the same channel because CMS references each posting by its GUID in the database. However, when users access the posting, they reference the posting by the hierarchical name, so CMS must use its best judgment to decide which posting to display in the client browser. Depending on which posting CMS decides to display, the posting may be displayed as GUID names on the client browser.



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 Delete all existing containers contents when replacing containers feature deletes all of the contents in the channel of the importing server before it replaces the contents of the channel from the site deployment Resolution Object Package (ROP) file. The contents in the channel include all of the postings, the subchannels, and the contents of the subchannels. Only use this feature if you export the whole channel branch and do not manually exclude some of the subchannels and postings that are under the main channel hierarchy.

