SharePoint 2016, Sharepoint 2013, Sharepoint 2010, Windows Server 2012, Sql Server 2012,2014,IIS, Active Directory,User Profile Service, Managed MetaData Service, Search Service, Topology, Web Application, IIS, Site collection, List, Library, PowerShell, office web app, Windows Authentication, NTLM, Kerberos, Saml, ADFS, Active Directory Import, MIM, “Unable to import the folder” error in Content Deployment, Sharepoint 2010 – SharePoint

“Unable to import the folder” error in Content Deployment, Sharepoint 2010

Description:

If you have environment where you Content Deploy from Farm A to Farm B and you caught up by “Unable to import the folder” error.

Envirnoment: Sharepoint 2010 Sp1, Windows Server SP2 Std, Sql Server 2008 Std.

Error in the Import  Logs:

Verbose: Source URL: _catalogs/fpdatasources

[Folder] [fpdatasources]   Error: Unable to import the folder _catalogs/fpdatasources. There is already an object with the Id “GUID” in the database from another site collection

 [Folder] [fpdatasources]   Debug:    at Microsoft.SharePoint.Deployment.FolderSerializer.GetFolderFromDatabase(SPWeb parentWeb, Guid folderId, String sourceFolderUrl, Boolean restoreRecycleBinItems)

   at Microsoft.SharePoint.Deployment.FolderSerializer.GetFolder(SPWeb parentWeb)

   at Microsoft.SharePoint.Deployment.FolderSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)

   at Microsoft.SharePoint.Deployment.XmlFormatter.CallSetObjectData(Object obj, SerializationInfo objectData, ISerializationSurrogate surrogate, ISurrogateSelector selector)

FatalError: Unable to import the folder _catalogs/fpdatasources. There is already an object with the Id 6bed52c6-52ad-4a52-812e-6349a1f934d4 in the database from another site collection.

Debug:    at Microsoft.SharePoint.Deployment.FolderSerializer.GetFolderFromDatabase(SPWeb parentWeb, Guid folderId, String sourceFolderUrl, Boolean restoreRecycleBinItems) 

Reasons:

  • There are orphan site at destination farm.

Check: check the health analysis rules definitions under Availability and run the report “Content databases contain orphaned items” on both farms? You may have to let it sit a while and check back in the reports to see if it shows anything.

Solutions:

  1.  Run the below powershell to clean it
    get-spcontentdatabase | %{$_.Repair($false)}
    This will spit out the orphan count for each database – it’s a read-only operation.
  2. Detach and reattach the Content DB in which site collection is, also fix the orphan issue
  3. Create a new contentDB and create new site collection with using the new-spsite command:
    New-spsite –URL “http://sitecollection path” – OwnerAlias “user login name”

Now create NEW CD Path & Job and run it.

There are many reasons for this issue,

  1. For me, because my internal site got corrupted and I resorted it from tape (I lost couple of days data due to backup policy), after restoring the site at Source farm I am getting a lot of weird error because contents are different at Source & destination. I delete the Content Deployment Path & Job (recommended by MSFT)  and run the cd and it’s failed with above error.

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *