A site collection is not mapped to the configuration database after you move it in SharePoint Server 2010

Article translations Article translations
Article ID: 2532218 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

Assume that you move a site collection from one content database to a destination content database in Microsoft SharePoint Server 2010. You do this by using the Move-SPSite PowerShell command or the stsadm –o mergecontentdb command. If a failure occurs before the site data is completely copied to the destination content database, the site collection might not be mapped to the configuration database.

RESOLUTION

To resolve this issue, apply the following hotfix package:
2516472 Description of the SharePoint Server 2010 hotfix package (sts-x-none.msp): April 26, 2011
After you apply the hotfix package, follow these steps to troubleshoot this issue:
  1. Check the source database and the destination database to see which database contains the site collection and which databases are mapped in the site map. To do this, run the following commands:
    stsadm -o enumallwebs -databasename SourceDatabaseName>

    stsadm -o enumallwebs -databasename
    DestinationDatabaseName>
  2. Compare the status of the site map between the source database and the destination database. Then, look for a site whose URL is based on the URL of its root website, and confirm whether the site is in the site map by reviewing the InSiteMap value.
  3. After you finish step 1 and step 2, you must determine the orphaned site collection ID and the name of the database that contains the orphaned site collection from the results of the stsadm -o enumallwebs commands. The following possible results may exist:
    • A copy of the site collection is stored in both the source database and in the destination database. However, neither database is in the site map. To resolve this issue, run the following command to delete the copy that you no longer need:
      stsadm -o deletesite -force -siteid <Orphaned Site Collection ID> -databasename <Name of database that contains orphaned site collection>
      Then, run the following command to map the remaining copy to the site map:
      stsadm –o refreshsitemap
    • A copy of the site collection is stored in both the source database and in the destination database. However, only one database is in the site map. To resolve this issue, run the following command to delete the copy that you no longer need:
      stsadm -o deletesite -force -siteid < Orphaned Site Collection ID > -databasename <Name of database that contains orphaned site collection>
    • More than one copies of the site collection are stored in either the source database or in the destination database. To resolve this issue, run the following command to delete the copies that you no longer need:
      stsadm -o deletesite -force -siteid < Orphaned Site Collection ID > -databasename <Name of database that contains orphaned site collection>
      Then, run the following command to map the remaining copy to the site map:
      stsadm –o refreshsitemap
    Note For more information about how to delete a site, visit the following Microsoft TechNet website:
    General information about the Deletesite: Stsadm operation
     

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Properties

Article ID: 2532218 - Last Review: June 7, 2011 - Revision: 2.0
APPLIES TO
Keywords: 
kbqfe kbsurveynew kbexpertisebeginner KB2532218

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com