Share via


The number of SharePoint sites do not match

The information in this article applies to:

  • Visual Studio 2005 Team Foundation Server

  • Visual Studio Team System 2008 Team Foundation Server

  • Application-tier server

  • Windows SharePoint Services 2.0 

  • Health check

The Best Practices Analyzer tool for Team Foundation Server queries the database instance for Team Foundation to determine the number of content database sites and the number of sites that have been configured for Windows SharePoint Services 2.0. 

Note

This rule is checked only when Windows SharePoint Services 2.0 is installed.

The rule compares the number of sites that are stored in the STS_Config_TFS.Databases table for the STS_Content_TFS database with the number of sites that are stored in the STS_Content_TFS.Sites table. If the site count does not match across these tables, the content database might be corrupted, or some sites might be orphaned. An error appears if the numbers of sites do not match.

To resolve this error, use one of the following two methods:

  • Remove and re-add the content database by using the SharePoint Central Administration site.

  • Download the update that you can use to repair content databases for Windows SharePoint Services 2.0, and remove orphaned sites. For more information, see "Description of a new command-line operation that you can use to repair content databases in Windows SharePoint Services 2.01" on the Microsoft Web site.

Required Permissions

To perform this procedure, you must be a member of the Windows SharePoint Services Site Administrators group or a member of the Administrators group on the server that is running Windows SharePoint Services 2.0.

To remove and re-add the content database for Windows SharePoint Services 2.0

  1. Log on to the server that is running Windows SharePoint Services 2.0, open Computer Manager, and make sure that the following components are started:

    • IIS Admin Service (IISADMIN)

    • HTTP SSL (HTTPFilter)

    • SharePoint Timer Service

    • World Wide Web Publishing Service (W3SVC)

    • TFSWSSADMIN (application pool)

    • Windows SharePoint Central Administration (Web site)

  2. Click Start, point to Administrative Tools, and then click Windows SharePoint Central Administration.

    The Central Administration window for Windows SharePoint Services 2.0 opens.

  3. Click Configure virtual server settings, click Default Web Site, click Manage content databases, and click the name of the content database.

    By default, the name of this database is STS_Content_TFS.

  4. Select the Remove content database check box, and then click OK.

    Note

    This step detaches the database but does not delete any content.

  5. Click OK in the warning dialog box that appears.

  6. On the Manage Content Databases page, click Add a content database.

    The Add Content Database page opens.

  7. In Database Information, click Specify database server settings. In Database name, type STS_CONTENT_TFS.

    Note

    By default, the name of this database is STS_Content_TFS. Make sure that the name that you type matches the name of the database that you deleted in step 4.

  8. Under Database Capacity Settings, in Number of sites before a warning event is generated, type 9000. In Maximum number of sites that can be created in this database, type 15000, and then click OK.

  9. (Optional) If you backed up any custom site definitions, custom site templates, or custom Web parts for SharePoint Products and Technologies that you want to keep, restore these components now. For more information, see "Backup and Restore Options" on the Microsoft Web site.

  10. Click Start, point to Administrative Tools, and click Services.

  11. Right-click SharePoint Timer Service, and then click Start.

See Also

Tasks

SharePoint Products and Technologies is not configured correctly

Other Resources

Issues That Relate to SharePoint Products and Technologies