SharePoint Products is not configured correctly

  • Article

The information in this article applies to:

  • Visual Studio Team Foundation Server 2010

  • Windows Server 2003 and Windows Server 2008 

  • Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007

  • Server that hosts SharePoint Products 

  • Team Foundation Server Complete Health Check

  • SharePoint Products Health Check

The Best Practices Analyzer tool for Team Foundation Server checks the configuration of the server that hosts SharePoint Products. An error appears if any of the following conditions is true:

  • A site definition configuration for SharePoint Products is missing

    The site definition configuration is required to create a SharePoint site when you create a team project. Two site definition configurations are installed with Team Foundation Server. These configurations are designed to work with the Microsoft Solutions Framework (MSF) process templates and have the following labels:

    • "TFS2010 Agile Dashboard" for the MSF for Agile Software Development v5.0 process template

    • "TFS2010 CMMI Dashboard" for the MSF for CMMI Process Improvement v5.0 process template

    To resolve this issue, you should first try to repair the SharePoint Web application by following the steps that are described in To repair or recreate a SharePoint Web application later in this topic. If that approach does not resolve the issue, delete and then recreate the SharePoint Web application.

  • Missing alternate access mapping for a SharePoint Web site

    You must create mappings between Team Foundation Server and one or more SharePoint Web applications to support team projects. To resolve this issue, see the following topic on the Microsoft Web site: Add a SharePoint Web Application to Your Deployment.

  • A service account cannot be detected or is missing permissions

    One or more of the following messages might appear if the service accounts that are used for SharePoint Products are not in the SharePoint Web Application Services group in Team Foundation Server:

    • SharePoint web application root service account is missing permissions (Error)

    • SharePoint web application service account is missing permissions (Error)

    • Cannot detect the service account used for the root site in SharePoint Products (Error)

    • Cannot detect the service account used for SharePoint Central Administration (Warning)

    When you grant access between a Web application in SharePoint Products and Team Foundation Server, you must add the service account for the Web application to the SharePoint Web Application Services group in Team Foundation Server.

    Note

    You do not have to manually grant access between a SharePoint Web application and Team Foundation Server if your account is a member of the Farm Administrators group. If your account is a member of that group, these settings are configured for you automatically when you grant access between Team Foundation Server and the SharePoint Web application. 

    To resolve this issue, you should first try to repair the SharePoint Web application by following the steps that are described in To repair or recreate a SharePoint Web application later in this topic.

  • The SharePoint Web Application Services group does not have a required permission on the catalog node for a team project

    The following message might appear if the service account group that is used for SharePoint Web applications (SharePoint Web Application Services) has had one or more permissions removed or changed in Team Foundation Server:

    • The [TEAM FOUNDATION]\SharePoint Web Application Services group does not have READ permission allowed on the catalog node for the team project ProjectName. (Error)

    For the deployment to function correctly, the server-level group SharePoint Web Application Services requires specific permissions at the server, team project collection, and project levels in Team Foundation Server. If you change or remove a default permission, team project portals might not display correctly, and project creation might fail. For more information about this group and its permissions, see Server-Level Groups, Team Foundation Server Default Groups, Permissions, and Roles and Interactions Between SharePoint Products and Team Foundation Server.

    Note

    You should not manually change the permissions for default groups at the server level in Team Foundation Server without a thorough understanding of your deployment and its dependencies. 

    To resolve this issue, you should first try to repair the SharePoint Web application by following the steps in To repair or recreate a SharePoint Web application later in this topic. If the problem persists, verify that the SharePoint Web Application Services group has the following permissions set to Allow:

    • Make requests on behalf of others (server-level)

    • View instance-level information (server-level)

    • Make requests on behalf of others (collection-level)

    • View collection-level information (collection-level)

    • View project-level information (project-level)

To repair or recreate a SharePoint Web application

  1. Open the administration console for Team Foundation.

    For more information, see Open the Team Foundation Administration Console [BPA].

  2. Under the Application Tier node, click SharePoint Web Applications.

  3. Click the application for which you want to repair the connection, and then click Repair Connection.

  4. Rerun the scan to determine whether the error is resolved.

  5. If it is not resolved, try removing and then re-adding the SharePoint Web application.

    For more information, see the following topic on the Microsoft Web site: Add a SharePoint Web Application to Your Deployment.

See Also

Tasks

Missing Team Foundation Server Extensions for SharePoint Products

Concepts

Issues that Relate to SharePoint Products and Integration with Team Foundation Server