none
SharePoint 2010 Site Collection Export

    Question

  • I am trying to migrate a site collection in SP 2010 from one server to another by using the command shell (stsadm -o export) and exporting the collection to a file for import on the other server.  I am running into an error that is prohibiting the full export:
    [9/27/2011 9:28:04 AM] [List] [Site Membership Review List] Progress: Exporting List Site Membership Review List.
    [9/27/2011 9:28:04 AM] [List] [Site Membership Review List]   Error: Feature 'd57f4817-f1f9-42aa-863c-139804c731b0' for list template '100' is not installed in this farm.  The operation could not be completed.
    [9/27/2011 9:28:04 AM] [List] [Site Membership Review List]   Debug:    at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
       at Microsoft.SharePoint.Library.SPRequest.ExpandListSchemaForExport(String bstrUrl, String bstrTitle, Int32 lTemplateID, String bstrFeatureId, String bstrFields, String& pbstrFullSchema, String& pbstrIndexSchema)
       at Microsoft.SharePoint.Deployment.ListSerializer.GetFieldsFromDataSet(ExportObject exportObject, DataRow listMetaData, SerializationInfo info, Boolean compressedXml)
       at Microsoft.SharePoint.Deployment.ListSerializer.GetDataFromDataSet(Object obj, SerializationInfo info, StreamingContext context)
    Tuesday, September 27, 2011 5:47 PM

Answers

  • The Feature ID 'd57f4817-f1f9-42aa-863c-139804c731b0' is related to a custom feature as the ID does not match to one of the standard features coming with SharePoint 2010.

    In order to export/import a site you have to ensure that all custom features are installed on source and target.

    It seems that the feature has been uninstalled on the source server without deactivating the feature on the source site collection or on one of the source sites first.

    In order to get the export/import working you need to fix this by either reinstalling the missing feature or by cleaning the site or site collection from the missing feature.

    To analyze which features are missing and whether they are site or site collection features and on which sites the feature is actually activated you can use the following tool:

    http://code.msdn.microsoft.com/WssAnalyzeFeatures

    If the missing feature is a site collection feature you can use STSADM -o deactivatefeature -id ... -url ... -force

    If the missing feature is a site feature you will need a custom tool to do the same:

    http://code.msdn.microsoft.com/WssRemoveFeatureFrom

    Cheers,
    Stefan


    Microsoft CSS - This post is provided "AS IS" with no warrenties and confers no rights.
    • Marked as answer by ndunn2000 Friday, October 07, 2011 1:06 PM
    Wednesday, September 28, 2011 7:53 AM
  • Hi,

    As indicated in the error digest, the feature is not installed on the farm, but the custom template references the feature. You could uninstall the custom '100' template, then attempt the export. The custom template can be reinstalled after the export.

    Also check the following directory on the server that Sharepoint is installed on for any custom features:

    "[Drive]\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Template\Features\"

    Make a note of any custom features that might be missing from Sharepoint.

    Sunday, October 02, 2011 7:28 PM

All replies

  • Try using PowerShell

     Export-SPWeb http://server:port/sites/ -ItemUrl "/sites/YourSite/" -Path "C:\MyExports\YourSiteName

    If you need more Power Shell commands, go here
    http://blogs.technet.com/b/heyscriptingguy/archive/2010/09/21/use-sharepoint-2010-powershell-cmdlets-to-get-and-manage-sites.aspx



    Aryan Nava | Twitter: @cloudtxt | Blog: http://virtualizesharepoint.com
    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.

    Disclaimer: This posting is provided "AS IS" with no warranties.


    • Edited by Aryan Nava Tuesday, September 27, 2011 5:56 PM
    Tuesday, September 27, 2011 5:54 PM
  • Same error.  See below:
    Export-SPWeb : Feature 'd57f4817-f1f9-42aa-863c-139804c731b0' for list template
     '100' is not installed in this farm.  The operation could not be completed.
    At line:1 char:13
    + Export-SPWeb <<<<  http://[mysite]:8901 -Path "C:\temp\mysite"
        + CategoryInfo          : InvalidData: (Microsoft.Share...CmdletExportWeb:
       SPCmdletExportWeb) [Export-SPWeb], SPException
        + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletExportWe
       b
    Tuesday, September 27, 2011 6:24 PM
  • Also with PowerShell you can move a site collection to its own database then move and mout the database that would be another way of doing this.

    Move a database with powershell

    http://technet.microsoft.com/en-us/library/cc825328.aspx

    Attach a content database

    http://technet.microsoft.com/en-us/library/ff628582.aspx

    Good luck,

    Gary

    blog www.sharepoint2010now.com

     


    Gary Newman MCSE, MCT, CCNA MCDBA, MCAD, MCSA MCTS SharePoint 2007 Dev & Admin MCPD SharePoint 2010 Development My Blog www.sharepoint2010now.com
    Tuesday, September 27, 2011 6:29 PM
  • Looks like your missing a feature.
    Please see Installing or Uninstalling Features : http://msdn.microsoft.com/en-us/library/ms442691.aspx

     



    Aryan Nava | Twitter: @cloudtxt | Blog: http://virtualizesharepoint.com
    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.

    Disclaimer: This posting is provided "AS IS" with no warranties.

    Tuesday, September 27, 2011 6:31 PM
  • Hi,

    As Aryan points out, it best to use powershell as STSADM has been deprecated in Sharepoint 2010. The error indicates a missing feature associated with a list template:

    "Feature 'd57f4817-f1f9-42aa-863c-139804c731b0' for list template '100' is not installed in this farm"

    Using powershell type the following command to locate the feature:

    GET-SPFeature -Identity "d57f4817-f1f9-42aa-863c-139804c731b0"

    If the feature is unavailable then install and activate it. You can run the following Powershell commands:

    INSTALL-SPFeature -Path "[Drive]\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Template\Features\[Feature Name]"

    ENABLE-SPFeature -Identity "d57f4817-f1f9-42aa-863c-139804c731b0"

    Be sure to run powershell under a sharepoint farm account.

    Failing this remove the list custom template named '100'. Then run the export.




    • Edited by kbyrne7 Tuesday, September 27, 2011 6:42 PM
    Tuesday, September 27, 2011 6:34 PM
  • here is the digest.  Still having issues:

     

     

    PS C:\Users\dsnet-ndunn> GET-SPFeature -Identity "d57f4817-f1f9-42aa-863c-139804

    c731b0"

    Get-SPFeature : Cannot find a Feature object with Path or Id: d57f4817-f1f9-42a

    a-863c-139804c731b0 in scope Local farm.

    At line:1 char:14

    + GET-SPFeature <<<<  -Identity "d57f4817-f1f9-42aa-863c-139804c731b0"

        + CategoryInfo          : InvalidData: (Microsoft.Share...mdletGetFeature:

       SPCmdletGetFeature) [Get-SPFeature], SPCmdletPipeBindException

        + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletGetFeatu

       re

     

    PS C:\Users\dsnet-ndunn> INSTALL-SPFeature -Identity "d57f4817-f1f9-42aa-863c-13

    9804c731b0"

    Install-SPFeature : A parameter cannot be found that matches parameter name 'Id

    entity'.

    At line:1 char:28

    + INSTALL-SPFeature -Identity <<<<  "d57f4817-f1f9-42aa-863c-139804c731b0"

        + CategoryInfo          : InvalidArgument: (:) [Install-SPFeature], Parame

       terBindingException

        + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.SharePoint.Powe

       rShell.SPCmdletInstallFeature

     

    PS C:\Users\dsnet-ndunn> GET-SPFeature -Identity "d57f4817-f1f9-42aa-863c-139804

    c731b0"

    Get-SPFeature : Cannot find a Feature object with Path or Id: d57f4817-f1f9-42a

    a-863c-139804c731b0 in scope Local farm.

    At line:1 char:14

    + GET-SPFeature <<<<  -Identity "d57f4817-f1f9-42aa-863c-139804c731b0"

        + CategoryInfo          : InvalidData: (Microsoft.Share...mdletGetFeature:

       SPCmdletGetFeature) [Get-SPFeature], SPCmdletPipeBindException

        + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletGetFeatu

       re

     

    PS C:\Users\dsnet-ndunn> INSTALL-SPFeature -Identity "d57f4817-f1f9-42aa-863c-13

    9804c731b0"

    Install-SPFeature : A parameter cannot be found that matches parameter name 'Id

    entity'.

    At line:1 char:28

    + INSTALL-SPFeature -Identity <<<<  "d57f4817-f1f9-42aa-863c-139804c731b0"

        + CategoryInfo          : InvalidArgument: (:) [Install-SPFeature], Parame

       terBindingException

        + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.SharePoint.Powe

       rShell.SPCmdletInstallFeature

     

    Tuesday, September 27, 2011 6:52 PM
  • The Feature ID 'd57f4817-f1f9-42aa-863c-139804c731b0' is related to a custom feature as the ID does not match to one of the standard features coming with SharePoint 2010.

    In order to export/import a site you have to ensure that all custom features are installed on source and target.

    It seems that the feature has been uninstalled on the source server without deactivating the feature on the source site collection or on one of the source sites first.

    In order to get the export/import working you need to fix this by either reinstalling the missing feature or by cleaning the site or site collection from the missing feature.

    To analyze which features are missing and whether they are site or site collection features and on which sites the feature is actually activated you can use the following tool:

    http://code.msdn.microsoft.com/WssAnalyzeFeatures

    If the missing feature is a site collection feature you can use STSADM -o deactivatefeature -id ... -url ... -force

    If the missing feature is a site feature you will need a custom tool to do the same:

    http://code.msdn.microsoft.com/WssRemoveFeatureFrom

    Cheers,
    Stefan


    Microsoft CSS - This post is provided "AS IS" with no warrenties and confers no rights.
    • Marked as answer by ndunn2000 Friday, October 07, 2011 1:06 PM
    Wednesday, September 28, 2011 7:53 AM
  • The WssAnalyzeFeatures (or any other method taken) never finds the feature id "d57f4817-f1f9-42aa-863c-139804c731b0", thus cannot remove using any of the methods so far sugested.  It seems the only thing that has been able to locate/identify the feature thus far is the /EXPORT function.  Any suggestions as to why the EXPORT function sees this feature, but the GET-SPFeature cannot?

    Thursday, September 29, 2011 2:02 PM
  • Hi,

    As indicated in the error digest, the feature is not installed on the farm, but the custom template references the feature. You could uninstall the custom '100' template, then attempt the export. The custom template can be reinstalled after the export.

    Also check the following directory on the server that Sharepoint is installed on for any custom features:

    "[Drive]\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Template\Features\"

    Make a note of any custom features that might be missing from Sharepoint.

    Sunday, October 02, 2011 7:28 PM
  • Although the WssAnalyzeFeatures and WssRemoveFeatureFrom tools did not find the missing feature, we were finally able to deduce the missing feature, re-install it on the site, and then export.

    Friday, October 07, 2011 1:08 PM
  • how was the missing feature traced ?

    Whrre did you find the feature id :d57f4817-f1f9-42aa-863c-139804c731b0

    I have run into the same issue and unable to trace this feature.

    Friday, February 28, 2014 9:59 AM
  • I apologize that I cannot remember as it was 2.5 years ago that we worked thru this problem.
    Friday, February 28, 2014 1:34 PM