Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Microsoft SharePoint project portal problems with Microsoft Team Foundation Server 2010


Symptoms

You are experiencing problems with the SharePoint Project Portal for a Team Foundation Server (TFS) 2010 Team Project. These problems may include errors on the main portal page about a missing default Team Project:

TF262600: This SharePoint site was created using a site definition that requires data from Team Foundation Server. However, the site is not currently associated with data for a team project. To ensure that this site functions correctly, you must configure a team project to refer data for that project to this site. For more information, see this topic on the Microsoft Web site: How to: Add a Team Project Portal.

TF250008: This SharePoint site is not currently associated with a team project in Team Foundation Server. To ensure that this site functions correctly, you must configure a team project to refer data for that project to this site. For more information, see this topic on the Microsoft Web site: How to: Add a Team Project Portal. You can use the following querystring argument to specify a specific project: tf:ProjectId.

This site doesn't have a default Team Project. You can explicitly select a specific Team Project.
This web part is not configured properly. Click here to configure web part in tool pane.

You may also experience unexpected behavior when you click the "Team Web Access" link on the team project portal. For example, you may have configured Team Foundation Server to use a fully qualified domain name or SSL\HTTPS, but when you click the "Team Web Access" link on the team project portal you are taken to the pre-change URL.

↑ Back to the top


Cause

At it's core this is a communication problem between SharePoint and the Team Foundation Server, and there may be any number of reasons for it, including network connectivity problems. This may also be caused by missing or incorrect Portal Settings for the Team Project in question, or by missing or incorrect Alternate Access Mappings in SharePoint. Finally, it may be caused by missing permissions for the [TEAM FOUNDATION]\SharePoint Web Application Services group to the team project.

↑ Back to the top


Resolution

You should first verify proper connectivity between the TFS application tier machine(s) and those hosting SharePoint. Then, using the Team Foundation Server Administration Console, verify that the SharePoint Web Applications entry for the Application Tier and SharePoint Web Application in question are established and working. You can use the "Repair Connection" option to confirm this:
  1. Open the Team Foundation Server Administration Console
  2. Expand the Application Tier in question (the one hosting the Team Project Collection and Team Project with the problem)
  3. Highlight the SharePoint Web Applications node.
  4. In the SharePoint Web Applications list, highlight the appropriate connection and then click "Repair Connection"
While you are here, verify the membership in the Service Accounts for SharePoint Web Applications as well. 

If the "Repair Connection" is successful, next verify the Portal Settings for the Team Project in question. You access this by connecting to the Team Project using Team Explorer. Then, right-click the Team Project name and select "Team Project Settings..." followed by the "Portal Settings..." option. Ensure the values here are correct.

You may also need to update your Alternate Access Mappings in SharePoint (see the More Information section below for details on this).

Also verify that in the “Extension for SharePoint Products” in TFS Administration Console section, make sure that the “Integration Target” column is pointing to the new or fully qualified domain name that you expect in the Team Web Access URL for the TFS Sharepoint portal.

To modify:

- Click and highlight the row, select “Modify Access”.

- Then update the “URL for Team Foundation Server” accordingly.

- Click OK, and then test to see if the TSWA URL is now updated.

If the SharePoint Web Applications connection, Portal Settings, and Alternate Access Mappings are all correct and you are still experiencing issues, you may be missing permissions for the [TEAM FOUNDATION]\SharePoint Web Application Services group to the team project.

As part of TFS Team Project creation we allow READ on the catalog nodes for the team project for the [TEAM FOUNDATION]\SharePoint Web Application Services group. However if at some point you explicitly add this group and then remove it from the Team Project permissions, the act of removing it will remove ALL permissions for this group, including the implied READ on the catalog from when the project was created. This may be the cause of your issues.

To repair this missing permission, add the [TEAM FOUNDATION]\SharePoint Web Application Services group to the permissions of the TFS Team Project experiencing the issue:
  • Use Team Explorer to connect to the Team Project with the issue.
  • Right-click on the Team Project name and then select Team Project Settings... Security.
  • Select the "Team Foundation Server Group" option in the "Add users and groups" section, and then click Add.
  • Select the "[TEAM FOUNDATION]\SharePoint Web Application Services" and add it.
Test the portal for the Team Project. If it doesn't work on first run, use tfsredirect.aspx to refresh the cache. For example, if the portal site address is http://SharePointServer/sites/TeamProjectCollectionName/TeamProjectName, you would navigate to the following address in your web browser: 
http://SharePointServer/sites/TeamProjectCollectionName/TeamProjectName/_layouts/TfsRedirect.aspx?tf:type=webaccess&tf:test=1&tf:clearcache=1. This will force a refresh of the SharePoint information about the TFS Team Project specified. This page should not return any errors and the value for TeamFoundation.Temp.LastRefreshDate should include the current date.

NOTE: If adding the [TEAM FOUNDATION]\SharePoint Web Application Services group to the permissions of the TFS Team Project resolved your issues it must remain there. If you remove that group the issues will return.

↑ Back to the top


More Information

For more information about adding or configuring a TFS Team Project Portal, please review the following resource:
http://msdn.microsoft.com/en-us/library/dd386320(VS.100).aspx

For more information on configuring Alternate Access Mappings in Microsoft Windows SharePoint Services 3.0, please review the following resource:
http://technet.microsoft.com/en-us/library/cc288173(office.12).aspx

↑ Back to the top


Keywords: kb

↑ Back to the top

Article Info
Article ID : 2451685
Revision : 1
Created on : 1/7/2017
Published on : 11/11/2011
Exists online : False
Views : 255