Welcome to TechNet Blogs Sign in | Join | Help

Browse by Tags

All Tags » Content Deployment   (RSS)

Pimp My Content Deployment Job

As a follow up to my article series about the content deployment and migration API here are some tips on how you can "fine-tune" the out of the box content deployment jobs. This will include information about how adjust settings in Content Deployment

MOSS - Common Issue - Content Deployment fails with "Failed to compare two elements in the array."

A common problem we see with content deployment and with STSADM -o export is the error message below: [4/11/2008 9:25:01 AM]: FatalError: Failed to compare two elements in the array. at System.Collections.Generic.ArraySortHelper`1.QuickSort[TValue](T[]

Deep Dive into the SharePoint Content Deployment and Migration API - Part 6

[ Part 1 - Part 2 - Part 3 - Part 4 - Part 5 - Part 6 ] Requirements for a successful content deployment Be aware that this article cannot provide a complete list of all requirements. I will update it from time to time if required. Today I will list all

WSS/MOSS - Common Issue - Error Message "Unknown compression type in a cabinet folder" during export

Another issue which I have seen a couple of times in the past when using STSADM -o export or content deployment is a failure during the export phase with the following error message: Failed to create package file Unknown compression type in a cabinet

MOSS - Common Issue - Incremental deployment fails with "The changeToken refers to a time before the start of the current change log."

I have seens this problem a couple of times in the past: sometimes when running incremental content deployment the deployment job fails with the following error message The changeToken refers to a time before the start of the current change log. To make

Deep Dive into the SharePoint Content Deployment and Migration API - Part 5

[ Part 1 - Part 2 - Part 3 - Part 4 - Part 5 - Part 6 ] Avoiding common problem This can be one of the most frequently updated chapters of this article series as "common problems" can change over time. In addition I can only talk about common problems

Deep Dive into the SharePoint Content Deployment and Migration API - Part 4

[ Part 1 - Part 2 - Part 3 - Part 4 - Part 5 - Part 6 ] Advanced content deployment scenarios Till now we have covered export and import of single list items or documents containers like folders, lists or webs complete site collection What we haven't

Deep Dive into the SharePoint Content Deployment and Migration API - Part 3

[ Part 1 - Part 2 - Part 3 - Part 4 - Part 5 - Part 6 ] Providing some real world samples for import After we managed to export content in part 2 lets now focus on the importing side. Import actually has two different ways to work: Import by preserving

Deep Dive into the SharePoint Content Deployment and Migration API - Part 2

[ Part 1 - Part 2 - Part 3 - Part 4 - Part 5 - Part 6 ] Providing some real world samples for export To demonstrate how powerful the Content Deployment and Migration API is I will now provide some real world examples: Export a complete Site Collection

Deep Dive into the SharePoint Content Deployment and Migration API - Part 1

[ Part 1 - Part 2 - Part 3 - Part 4 - Part 5 - Part 6 ] Introduction Today I would like to start an article series on an interesting new feature in WSS 3.0: the Content Deployment and Migration API. A similar API has previously been provided in MCMS 2002
 
Page view tracker