Comments on: MOSS content deployment tips and tricks http://www.sharepointconfig.com/2008/06/moss-content-deployment-tips-and-tricks/ Ari Bakker's thoughts on customising and configuring SharePoint 2007 and 2010 Thu, 02 Feb 2012 22:08:50 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Ari Bakker http://www.sharepointconfig.com/2008/06/moss-content-deployment-tips-and-tricks/comment-page-1/#comment-174 Ari Bakker Wed, 09 Jul 2008 21:53:31 +0000 http://ari.provoke.co.nz/Lists/Posts/ViewPost.aspx?ID=50#comment-174 Two hotfixes that address numerous content deployment issues are now available from Microsoft. See the links below or <a href="http://www.sharepointjoel.com/Lists/Posts/Post.aspx?ID=57" rel="nofollow">Joel Oleson's overview</a> for more details. WSS:<a href="http://support.microsoft.com/kb/952698" rel="nofollow">http://support.microsoft.com/kb/952698</a> MOSS: <a href="http://support.microsoft.com/kb/952704" rel="nofollow">http://support.microsoft.com/kb/952704</a> Two hotfixes that address numerous content deployment issues are now available from Microsoft. See the links below or Joel Oleson’s overview for more details.

WSS:http://support.microsoft.com/kb/952698

MOSS: http://support.microsoft.com/kb/952704

]]> By: Ari Bakker http://www.sharepointconfig.com/2008/06/moss-content-deployment-tips-and-tricks/comment-page-1/#comment-175 Ari Bakker Wed, 30 Nov -0001 00:00:00 +0000 http://ari.provoke.co.nz/Lists/Posts/ViewPost.aspx?ID=50#comment-175 Hi Paul, Is your deployment job set to 'Deploy only new, changed, or deleted content'? This setting should ensure content is only sent to the target when it changes on the source. Hi Paul, Is your deployment job set to 'Deploy only new, changed, or deleted content'? This setting should ensure content is only sent to the target when it changes on the source.

]]> By: Paul http://www.sharepointconfig.com/2008/06/moss-content-deployment-tips-and-tricks/comment-page-1/#comment-176 Paul Wed, 30 Nov -0001 00:00:00 +0000 http://ari.provoke.co.nz/Lists/Posts/ViewPost.aspx?ID=50#comment-176 We've had content deployment for MOSS working fine for around 6 months, but recently noticed that the target (production) content database is many times larger than the source (authoring) content database. Looks like issue relates to versioning. Example: Library in source has a document that hasn't been modified in six months. Corresponding library in target has 32 versions of the same document, each with the original "Modified" date from six months ago. Looks like content deployment is creating a new version of the document on each Full Deployment job (weekly). Both libraries are set to allow versions. Should we turn versioning off on target side? We need versioning on source side. Is there a configuraiton setting on the deployment job that we should consider? Appreciate your help! We've had content deployment for MOSS working fine for around 6 months, but recently noticed that the target (production) content database is many times larger than the source (authoring) content database. Looks like issue relates to versioning. Example: Library in source has a document that hasn't been modified in six months. Corresponding library in target has 32 versions of the same document, each with the original "Modified" date from six months ago. Looks like content deployment is creating a new version of the document on each Full Deployment job (weekly). Both libraries are set to allow versions.
Should we turn versioning off on target side? We need versioning on source side. Is there a configuraiton setting on the deployment job that we should consider?
Appreciate your help!

]]> By: Ari Bakker http://www.sharepointconfig.com/2008/06/moss-content-deployment-tips-and-tricks/comment-page-1/#comment-177 Ari Bakker Wed, 30 Nov -0001 00:00:00 +0000 http://ari.provoke.co.nz/Lists/Posts/ViewPost.aspx?ID=50#comment-177 @Jason it looks like the ListDisplaySettingFeature feature isn't available on the destination farm. I'd check the features folder (Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES) on the destination farm to make sure the ListDisplaySettingFeature is there and installed on the farm. This looks like a custom feature, so you might want to check that any solutions installed on the source farm are also installed on the destination farm (as this might be part of a custom solution i.e. wsp file). You can do this by navigating to Central Administration > Operations > Solution management. Hope that helps. @Jason it looks like the ListDisplaySettingFeature feature isn't available on the destination farm. I'd check the features folder (Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES) on the destination farm to make sure the ListDisplaySettingFeature is there and installed on the farm. This looks like a custom feature, so you might want to check that any solutions installed on the source farm are also installed on the destination farm (as this might be part of a custom solution i.e. wsp file). You can do this by navigating to Central Administration > Operations > Solution management. Hope that helps.

]]> By: Jason http://www.sharepointconfig.com/2008/06/moss-content-deployment-tips-and-tricks/comment-page-1/#comment-178 Jason Wed, 30 Nov -0001 00:00:00 +0000 http://ari.provoke.co.nz/Lists/Posts/ViewPost.aspx?ID=50#comment-178 I keep get this error: 'Microsoft.SharePoint.SPException' : 'Could not find Feature ListDisplaySettingFeature.' Any suggestions? I have looked at the farm and site features in both site and they are the same. I keep get this error:

'Microsoft.SharePoint.SPException' : 'Could not find Feature ListDisplaySettingFeature.'

Any suggestions?

I have looked at the farm and site features in both site and they are the same.

]]>