Anyone come across this error before? Progress: Exporting ListItem COLLAW/WAD/_catalogs/masterpage?id=3.Progress: Exporting ListItem COLLAW/WAD/_catalogs/masterpage?id=1.FatalError: This constraint cannot be enabled as not all values have corresponding parent values. at System.Data.ConstraintCollection.Add(Constraint constraint, Boolean addUniqueWhenAddingForeign) at System.Data.DataRelationCollection.DataSetRelationCollection.AddCore(DataRelation relation) at System.Data.DataRelationCollection.Add(DataRelation relation) at System.Data.DataRelationCollection.Add(String name, DataColumn[] parentColumns, DataColumn[] childColumns) at Microsoft.SharePoint.Deployment.ListItemObjectHelper.GetNextBatch() at Microsoft.SharePoint.Deployment.ObjectHelper.RetrieveDataFromDatabase(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ListItemObjectHelper.RetrieveData(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ExportObjectManager.GetObjectData(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ExportObjectManager.MoveNext() at Microsoft.SharePoint.Deployment.ExportObjectManager.ExportObjectEnumerator.MoveNext() at Microsoft.SharePoint.Deployment.SPExport.SerializeObjects() at Microsoft.SharePoint.Deployment.SPExport.Run()Progress: Export Completed.Finish Time: 11/7/2007 6:16:25 PM.Completed with 0 warnings.Completed with 1 errors. Log file generated: C:\Documents and Settings\ihadmin\wad.cmp.export.logThis constraint cannot be enabled as not all values have corresponding parent values. Suggestions? Can't find anything specific online...

I am having the same problem. I tried stsadm -export and also the SharePoint Designer to do this, same error message popup ... anyone has an idea to solve this? Thanks!

I am also getting this same type of error... Can anyone provide anything on this error.[11/27/2007 12:08:23 PM]: Progress: Starting to process objects of type ListItem.[11/27/2007 12:08:23 PM]: Progress: Exporting ListItem sites/nov26/laboratory/LIS/Task/_catalogs/masterpage?id=1.[11/27/2007 12:08:27 PM]: FatalError: These columns don't currently have unique values. at System.Data.ConstraintCollection.AddUniqueConstraint(UniqueConstraint constraint) at System.Data.ConstraintCollection.Add(Constraint constraint, Boolean addUniqueWhenAddingForeign) at System.Data.ConstraintCollection.Add(Constraint constraint, Boolean addUniqueWhenAddingForeign) at System.Data.DataRelationCollection.DataSetRelationCollection.AddCore(DataRelation relation) at System.Data.DataRelationCollection.Add(DataRelation relation) at System.Data.DataRelationCollection.Add(String name, DataColumn[] parentColumns, DataColumn[] childColumns) at Microsoft.SharePoint.Deployment.ListItemObjectHelper.GetNextBatch() at Microsoft.SharePoint.Deployment.ObjectHelper.RetrieveDataFromDatabase(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ListItemObjectHelper.RetrieveData(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ExportObjectManager.GetObjectData(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ExportObjectManager.MoveNext() at Microsoft.SharePoint.Deployment.ExportObjectManager.ExportObjectEnumerator.MoveNext() at Microsoft.SharePoint.Deployment.SPExport.SerializeObjects() at Microsoft.SharePoint.Deployment.SPExport.Run()[11/27/2007 12:08:28 PM]: Progress: Export Completed.[11/27/2007 12:08:28 PM]: Finish Time: 11/27/2007 12:08:28 PM.[11/27/2007 12:08:28 PM]: Completed with 253 warnings.[11/27/2007 12:08:28 PM]: Completed with 1 errors. Thank you, Bryan

I am running into the exact same error: [1/30/2008 3:07:53 PM]: Progress: Exporting ListItem IS/Infrastructure/_catalogs/masterpage?id=1.[1/30/2008 3:07:53 PM]: FatalError: These columns don't currently have unique values. So what is messed up with the masterpage list? Anyone come up with a work around / solution?

And again the same Error. No one has an Answer yet? [3/4/2008 11:09:57 AM]: Progress: Exporting ListItem phy/PHY07/Bildmaterial?id=106.[3/4/2008 11:09:58 AM]: FatalError: This constraint cannot be enabled as not all values have corresponding parent values. at System.Data.ConstraintCollection.Add(Constraint constraint, Boolean addUniqueWhenAddingForeign) at System.Data.DataRelationCollection.DataSetRelationCollection.AddCore(DataRelation relation) at System.Data.DataRelationCollection.Add(DataRelation relation) at System.Data.DataRelationCollection.Add(String name, DataColumn[] parentColumns, DataColumn[] childColumns) at Microsoft.SharePoint.Deployment.ListItemObjectHelper.GetNextBatch() at Microsoft.SharePoint.Deployment.ObjectHelper.RetrieveDataFromDatabase(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ListItemObjectHelper.RetrieveData(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ExportObjectManager.GetObjectData(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ExportObjectManager.MoveNext() at Microsoft.SharePoint.Deployment.ExportObjectManager.ExportObjectEnumerator.MoveNext() at Microsoft.SharePoint.Deployment.SPExport.SerializeObjects() at Microsoft.SharePoint.Deployment.SPExport.Run() Kind Regards Sam

This thread has been out there for a while. Does anyone know what's causing this, and how to get around it? I have one specific site that I cant export using the -versions 4 option. thanks.

I'll bump this one too - I'm having this error on about 50% of my document center sites, its always in the masterpage listitems that it goes wrong, doesn't matter what versions number you pass in to the command. Any ideas??

Bumping again. I'm now getting this message on about half of the site's that i'm trying to back up using the stsadm.exe -o export command. These are sites that were previously wss 2.0 sites that have been upgraded to 3.0 and then tried to back them up. I have an issue open with MS tech support, but they cant seem to figure it out.anyone have any suggestions?

Has anyone tried installing the infrastructure update and seeingif that addresses your issue?http://blogs.msdn.com/sharepoint/archive/2008/07/15/announcing-availability-of-infrastructure-updates.aspxJohnSharePoint911: SharePoint Consultinghttp://www.rossonmoss.com

no, but i've got a testing server all set up and ready to go. i'll test it today....

Nope, didnt work. The only difference is that it bombed on a different list than before. It actually made it a little farther before it threw this error: ( the last list itme is included)7/24/2008 10:39:50 AM]: Progress: Exporting ListItem sites/1/Universal and Health Net 2008/Charts, Contact Lists, Others?id=3.[7/24/2008 10:39:54 AM]: FatalError: These columns don't currently have unique values. at System.Data.ConstraintCollection.AddUniqueConstraint(UniqueConstraint constraint) at System.Data.ConstraintCollection.Add(Constraint constraint, Boolean addUniqueWhenAddingForeign) at System.Data.ConstraintCollection.Add(Constraint constraint, Boolean addUniqueWhenAddingForeign) at System.Data.DataRelationCollection.DataSetRelationCollection.AddCore(DataRelation relation) at System.Data.DataRelationCollection.Add(DataRelation relation) at System.Data.DataRelationCollection.Add(String name, DataColumn[] parentColumns, DataColumn[] childColumns) at Microsoft.SharePoint.Deployment.ListItemObjectHelper.GetNextBatch() at Microsoft.SharePoint.Deployment.ObjectHelper.RetrieveDataFromDatabase(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ListItemObjectHelper.RetrieveData(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ExportObjectManager.GetObjectData(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ExportObjectManager.MoveNext() at Microsoft.SharePoint.Deployment.ExportObjectManager.ExportObjectEnumerator.MoveNext() at Microsoft.SharePoint.Deployment.SPExport.SerializeObjects() at Microsoft.SharePoint.Deployment.SPExport.Run()[7/24/2008 10:39:54 AM]: Progress: Export Completed.[7/24/2008 10:39:54 AM]: Finish Time: 7/24/2008 10:39:54 AM.[7/24/2008 10:39:54 AM]: Completed with 2 warnings.[7/24/2008 10:39:54 AM]: Completed with 1 errors.

Hi All,I ran into the same problem after using content deployment successfully for over 3 months. I contacted Microsoft and was told that this issue has been identified as a bug and can be resolved by installing hotfix: KB955594. The hotfix has not been made publicly available but if you call Microsoft you can request it.Just to give you guys an idea of my environment I was running MOSS 2007 post SP1 with a version number of 12.0.0.6307. Once the patch was installed it bumped me up to 12.0.0.6324. NOTE: I had to install this on both the source and destination server for it to work. Please let me know if this has helped you guys get passed this annoying error.Thanks!Carlos Fernandez

I am having the same problem- even after installing the hotfix. Was that all that was done to resolve this?

I am also having this issue!?Denise

Yeah all I did was install the hotfix provided by Microsoft and then deleted all my previous content deploymentjobs. And recreated them.Then ran a content deployment which thencompleted successfully.Hope this helps

I notice Mike Walsh unproposed the above answer: is there better information available?I'm getting this error message with an STSADM export operation. FatalError: This constraint cannot be enabled as not all values have corresponding parent values. at System.Data.ConstraintCollection.AddForeignKeyConstraint(ForeignKeyConstraint constraint) at System.Data.ConstraintCollection.Add(Constraint constraint, Boolean addUniqueWhenAddingForeign) at System.Data.DataRelationCollection.DataSetRelationCollection.AddCore(DataRelation relation) at System.Data.DataRelationCollection.Add(DataRelation relation) at System.Data.DataRelationCollection.Add(String name, DataColumn[] parentColumns, DataColumn[] childColumns) at Microsoft.SharePoint.Deployment.ListItemObjectHelper.GetNextBatch() at Microsoft.SharePoint.Deployment.ObjectHelper.RetrieveDataFromDatabase(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ListItemObjectHelper.RetrieveData(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ExportObjectManager.GetObjectData(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ExportObjectManager.MoveNext() at Microsoft.SharePoint.Deployment.ExportObjectManager.ExportObjectEnumerator.MoveNext() at Microsoft.SharePoint.Deployment.SPExport.SerializeObjects() at Microsoft.SharePoint.Deployment.SPExport.Run() This is a pre-existing problem with a system I'm now maintaining, and I'm fairly new to SharePoint 2007, so I'm having some trouble trackingthis down. Probably a stupid question, but why is a foreign key issue coming up in SharePoint, which isn't relational as I understand it?Any insight anyone has greatly appreciated! I'm losing what's left of my hair.

Are you just trying to export a specific site?John SharePoint911: SharePoint Consulting Blog: http://www.rossonmoss.com Twitter: JohnRossJr MOSS Explained: An Information Workers Deep Dive into Microsoft Office SharePoint Server 2007

A specific subsite.Unfortunately,we have multiple SharePoint sites running in the same domain. The point of the export is to start separating them out to increase overall stability.I haven't found any unwanted "cross pollination" between the SharePoint instances that wouldinterfere with the export,although it might be there. We've been able to export a different subsite that's pretty similar without incident. Thanks.

After the error, check your Event Viewer to see if anything shows up there that might give a clue to what's going on.John SharePoint911: SharePoint Consulting Blog: http://www.rossonmoss.com Twitter: JohnRossJr MOSS Explained: An Information Workers Deep Dive into Microsoft Office SharePoint Server 2007

I know this is old, but in case anyone is looking for an answer to some of these. I had our sysadmin apply SP2 for Sharepoint in addition to the cumulative updates just so I could get to the point of receiving this error. After two weeks of patches and banging my head, I tried "cleaning up my data". I've discovered that SharePoint does a poor job of cleaning up after itself. Since I had emptied my lists and was receiving errors in the log indicating that the export was trying to export attachments and failing because the corresponding list item didn't exist, I decided to disable attachments in my problem list and then re-enable them. It cleared my problem. I think when lists items are removed and attachments exist, the attachments are orphaned. I'll probably work this theory out later, for now I have to get this stuff to production.

Great to see that this error is still there in SP2010... I'm trying to export a list in central admin, and the log file gives me : [2/1/2011 1:50:42 PM] FatalError: This constraint cannot be enabled as not all values have corresponding parent values. [2/1/2011 1:50:42 PM] Debug: at System.Data.ConstraintCollection.AddForeignKeyConstraint(ForeignKeyConstraint constraint) at System.Data.ConstraintCollection.Add(Constraint constraint, Boolean addUniqueWhenAddingForeign) at System.Data.DataRelationCollection.DataSetRelationCollection.AddCore(DataRelation relation) at System.Data.DataRelationCollection.Add(DataRelation relation) at System.Data.DataRelationCollection.Add(String name, DataColumn parentColumn, DataColumn childColumn) at Microsoft.SharePoint.Deployment.FileObjectHelper.GetNextBatch() at Microsoft.SharePoint.Deployment.ObjectHelper.RetrieveDataFromDatabase(ExportObject exportObject) at Microsoft.SharePoint.Deployment.FileObjectHelper.RetrieveData(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ExportObjectManager.GetObjectData(ExportObject exportObject) at Microsoft.SharePoint.Deployment.ExportObjectManager.MoveNext() at Microsoft.SharePoint.Deployment.SPExport.SerializeObjects() at Microsoft.SharePoint.Deployment.SPExport.Run() [2/1/2011 1:50:43 PM] Progress: Export did not complete. [2/1/2011 1:50:43 PM] Finish Time: 2/1/2011 1:50:43 PM. [2/1/2011 1:50:43 PM] Duration: 00:02:29 [2/1/2011 1:50:43 PM] Total Objects: 4017 [2/1/2011 1:50:43 PM] Finished with 0 warnings. [2/1/2011 1:50:43 PM] Finished with 1 errors. In my case the attachments were disabled on the list from the beginning (why is it enabled by default in the first place...), so this issue is not caused by orphaned attachments or anything. My list doesn't have lookup columns that use cascading/restricted deletion so that's not the cause either. My list is on an upgraded SP environment (2007 > 2010). Anyone else still struggling with this?

I had the same issues and tried all the available patches, the "-versions 4" parameter but nothing seemed to work. The only think that worked for me was from this article. http://www.eggheadcafe.com/software/aspnet/32139897/export-sharepoint-site-error-there-is-no-row-at-position-0.aspx I broke the inheritance for the Permission Levels and re-inherit back to the Parent and that did the job!