I am running wss 3.0 and moss 2007 both with sp1 installed. I am trying to export our main intranet site so that I can import it into our dev enviornment. I am running this command: stsadm -o export -url https://sharepoint.domainname.com-filename <path> I am getting this error:"This constraint cannot be enabled as not all values have corresponding parent values."I found hotfix KB955594, installed it and I still get the error. I don't know where to go from here. Here is more info from the log file:[8/27/2008 12:36:37 PM]: Progress: Exporting ListItem deptsites/support/kb/Lists/Keywords?id=96.[8/27/2008 12:36:37 PM]: Progress: Exporting ListItem deptsites/support/kb/Lists/Keywords?id=97.[8/27/2008 12:36:37 PM]: Progress: Exporting ListItem deptsites/support/kb/Lists/Keywords?id=98.[8/27/2008 12:36:37 PM]: 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()[8/27/2008 12:36:48 PM]: Progress: Export Completed.[8/27/2008 12:36:48 PM]: Finish Time: 8/27/2008 12:36:48 PM.[8/27/2008 12:36:48 PM]: Completed with 46 warnings.[8/27/2008 12:36:48 PM]: Completed with 2 errors.Any one run into this issue before? Did you have a solution?

There is one more thing I have found regarding this issue. The page where it fails:deptsites/support/kb/Lists/Keywords?id=98 - when going there to try and troubleshoot I found that there is no id=99 on that site. The id numbers for the keywordsjump from 98 to 100. My guess is this is somehow related and it can't find the page it thinks is next.

I haven't run into a solution yet but I'm hoping someone here has because we recently encountered the same issue..

I'm having the same issue!?

We are currently working with Microsoft to try and resolve this issue. They are now having much luck either and they have elevated the case to the next level. I'll post the resolution once we have it figured out..

I'm having the same problem, even after the "hotfix" which did little more than make me loose sleep to help the situation. My setup is a little different. In my case it's another top-level site, and it is breaking on a subsite's subsite of that top-level site. So i try to back up just that subsite (and the sites below it), and it breaks at a different spot in that subsite.I'm going to be forced to take the whole huge site down, and peace-meal put it back together to try to fix this one, one step at a time, blowing out the sites that it breaks on. Really a pain in the butt considering how many pages that are involved in this whole collection.

More of a comment than a solution to (our) problem, but here it goes.Something i have noticed about stsadmn as i have been fixing problems with my massive site collection, one site at a time is that you can figure out what it is going to go to next with a little logic. My current process to find out what site is the offender has been the following:1. Go to your export log, find the last site it was exporting, note it.2. stsadmn -o enumsubwebs http://mycollectioniamexporting3. Find the last site that it was exporting before it errored out in the list. Your problem site is the next site.Once i find the site i ussaly try to export just it first, see if i can get any more information on why it wont export, or rather, get it to break differently, then either remove it/rebuild/reapply themes/templates or what ever is needed to correct the problem. And in my case, then move on to the next problem site.

hi apressley, The solution to your problem is avaialable at http://www.wssdemo.com/Lists/Resources/KB%20Articles.aspx Refer KB 955594