SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Apart from the manifest.xml in, Event Viewer and the ULS logs, is there any way to identify which object is causing the problem in content deployment?

share|improve this question
What kind of problem are you referring to? – Anita Boerboom Jul 10 '11 at 20:46

You could try telling SharePoint to keep the temporary files. This can be done using stsadm:

STSADM -o editcontentdeploymentpath -pathname -keeptemporaryfiles Never|Always|Failure

You can then look inside the various cab files and figure out what is going on (I didn't say it would be easy). This blog article has some suggestions.

Stefan Gossner has a good blog article on common content deployment problems.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.