<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SharePoint 2007 Content Deployment Failures</title>
	<atom:link href="http://itrants.net/2008/04/23/sharepoint-2007-content-deployment-failures/feed/" rel="self" type="application/rss+xml" />
	<link>http://itrants.net/2008/04/23/sharepoint-2007-content-deployment-failures/</link>
	<description>Your peers, your partners, YOUR IT PORTAL!</description>
	<lastBuildDate>Thu, 24 Apr 2008 03:15:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jonest</title>
		<link>http://itrants.net/2008/04/23/sharepoint-2007-content-deployment-failures/comment-page-1/#comment-3</link>
		<dc:creator>jonest</dc:creator>
		<pubDate>Thu, 24 Apr 2008 03:07:48 +0000</pubDate>
		<guid isPermaLink="false">http://itrants.net/?p=14#comment-3</guid>
		<description>The content deployment failure that occurs when we were renaming some of the default home pages was:  the page already exists. 

Something to do with the GUID being the same but the name was different when compared to the destination site.  We tried putting the original back and no go.  We tried deleting the site on the source and destination farms and then starting with the defaults.  Still it failed.

We had to recreate in another arm of the tree to get it to work.  Who doesn&#039;t love Content Deployment?</description>
		<content:encoded><![CDATA[<p>The content deployment failure that occurs when we were renaming some of the default home pages was:  the page already exists. </p>
<p>Something to do with the GUID being the same but the name was different when compared to the destination site.  We tried putting the original back and no go.  We tried deleting the site on the source and destination farms and then starting with the defaults.  Still it failed.</p>
<p>We had to recreate in another arm of the tree to get it to work.  Who doesn&#8217;t love Content Deployment?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
