Quantcast
Channel: SharePoint 2013 - Setup, Upgrade, Administration and Operations forum
Viewing all articles
Browse latest Browse all 21070

SharePoint 2013 - Fatal Error During Content Export

$
0
0

I am trying to export content from a SharePoint 2013 Site Collection that has Variations enabled, but only English installed/in use.  I used the Export-SPWeb (used the IncludeUserSecurity switch) PowerShell command, but I receive the following error in the export logs (including files it was processing before error for context):

=====================================

[7/17/2013 8:12:09 AM] [File] [DispForm.aspx] Progress: Exporting File /Style Library/Forms/DispForm.aspx.
[7/17/2013 8:12:09 AM] [File] [DispForm.aspx]   Verbose: Exporting Web Part 
[7/17/2013 8:12:09 AM] FatalError: This constraint cannot be enabled as not all values have corresponding parent values.
[7/17/2013 8:12:09 AM] Debug:    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.ExportObjectManager.ExportObjectEnumerator.MoveNext()
   at Microsoft.SharePoint.Deployment.SPExport.SerializeObjects()
   at Microsoft.SharePoint.Deployment.SPExport.Run()
[7/17/2013 8:12:09 AM] Progress: Export did not complete.

==================================

I also tried exporting from Central Admin to ensure it was not an issue with the command, but I received the same error. 

Other forums for past versions of SharePoint recommended a hotfix/CU, but I do not think this is addressed with any SP 2013 hotfixes/CUs.

Any help would be greatly appreciated!

-Chris-


Viewing all articles
Browse latest Browse all 21070

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>