Content Deployment Problem : Violation of PRIMARY KEY constraint : Revisited

In a previous article i blogged on how to get around a 'Violation of PRIMARY KEY constraint' error that i had cropping up in a Content Deployment Routine. This unfortunately doesn't mean that you won't see the error again! I've had this error return so some further research lead me to comments posted on Ton Stegman's content deployment blog by Ryan Steeno.

To summarise Ryans comments, after some extensive tracing (understatement) he ascertained that having the versioning settings of any of the Site Collection Libraries (Images/Documents/Style) set to Allow Multiple Only seemed to resolve the issue.

Note : There are also reports of this error using the stsadm utility import/export operations which Peter Holpar has managed to resolve.