I have found an interesting bug where incremental content deployment fails with the following error message:
“Content deployment job ‘Incremental Deploy’ failed.The exception thrown was ‘System.Data.SqlClient.SqlException’ : ‘Violation of PRIMARY KEY constraint ‘PK__#ExportObjects____192930E1′. Cannot insert duplicate key in object ‘dbo.#ExportObjects’. The statement has been terminated.’”
I have found that this occurs if the same page is approved more than once between incremental updates. I have been informed that Microsoft are aware of this issue and are currently working on a hotfix that should be released shortly. I have just been informed that the hotfix is now available, to obtain the fix you will need to raise a support call (KB Article Number(s): 934577, 935958, 936867, 937038)
Check out the MOSS bugs list page for other MOSS bugs.
We first saw this problem on our project and are diligently following up with microsoft for a fix to this problem. We had to call up microsoft to open a ticket for this bug, and after several hours of driving the point home that this is a critical bug, they accepted it and started working on a solution.
This is caused by nested folders and fails every time when a site has this topology. There are more details to it but the point is microsoft actually wont be releasing a patch until the end of the month.. they have been working on a fix since early March and still have issues releasing a fix…
There are many issues still open with full deployment as well, but that’s a whole other topic
We had similar issue with using SPExport object from custom code. For details check my blog.
Great. Thanks for letting us know about the hotfix!
Thanks. This was helpful… Has anyone had problems with this hotfix at all since it’s private? I know the hotfix supposedly fixes other problems.
[...] to this blog entry, this is caused when a single page is approved more than once between incremental updates. [...]
We received the hotfix, but when we ran it on our server, we got a message stating that no applications were affected by this update, so it never fully installed….anyone get that message?
Is this fixed in SP1?
BTW… none of these KB articles listed above appear related to the #ExportObjects bug.
[...] incremental content deployment PKV is available from Microsoft, and we read the same information on William Cornwill’s blog. Although the export utility now runs with this setting we hope the fix will solve the issue of [...]