Troubleshooting the New Team Project Wizard
The following issues might occur when you are working with the New Team Project Wizard:
Creating a New Team Project Takes a Very Long Time
The New Team Project Wizard Cannot Connect to Windows SharePoint Services
No Permission to Access a Site
Server Protocol Violation Causes the Wizard to Fail
Missing Update Causes the Wizard to Fail
Underlying connection was closed
For additional troubleshooting information, see Troubleshooting Team Project Creation and Deletion. If you cannot resolve a problem after reviewing these tips and those in the individual error message help topics, see the Microsoft Technical Forums for Visual Studio Team System at https://go.microsoft.com/fwlink/?LinkId=54490. These forums provide searchable threads on a variety of troubleshooting questions and are monitored to provide quick responses.
Creating a New Team Project Takes a Very Long Time
After you click Finish in the New Team Project Wizard, the wizard connects to the appropriate servers and services and then starts to create necessary components. The speed with which the wizard creates the team project depends, in part, on the speed of the computer network. The configuration of network switches and your computers' network adapters can also affect the throughput speed. For example, "autosense mode" or "auto-negotiation" might be turned on, and information can be transmitted in either full-duplex mode or half-duplex mode.
To minimize the time required to create a project, you should confirm that network options are set for maximum throughput. On the client computers, you should also enable automatic detection of the link speed for the network adapter. For more information, see How to: Configure a Network Adapter to Automatically Adjust Speed.
The New Team Project Wizard Cannot Connect to Windows SharePoint Services
When Team Foundation Server is installed, the installation and configuration programs assign the correct port and network addresses for all the Team Foundation components. For example, during installation, Team Foundation Server identifies the correct port number for Windows SharePoint Services and configures Team Explorer to communicate with Windows SharePoint Services on that port. If you subsequently reinstall Windows SharePoint Services or modify Windows SharePoint Services to use a different port, Team Foundation Server is not reconfigured automatically. This means you lose your communications with Windows SharePoint Services. The next time you try to create a new team project, you will receive an error message stating that the New Team Project Wizard cannot connect to Windows SharePoint Services. The solution to this problem is to reconfigure the port number setting in Team Foundation Server.
For more information about port settings, see the Team Foundation Administrator's Guide and "Ports Required for Team Foundation Server Setup" in the Team Foundation Installation Guide.
Note
The most current version of the Team Foundation Administrator's Guide is available on the Web at the MSDN Online site (https://go.microsoft.com/fwlink/?linkid=79725). The latest version of the Team Foundation Installation Guide is available on the Web at the Microsoft Download Center (https://go.microsoft.com/fwlink/?linkid=79226).
No Permission to Access a Site
If you receive an error message that states that you do not have permission to access Windows SharePoint Services or SQL Server Reporting Services, contact your Team Foundation administrator or the administrators for the SharePoint or Reporting Services.
For more information about the permissions you need on your user account to access services, see How to: Set Team Foundation Server Contributor Permissions.
Server Protocol Violation Causes the Wizard to Fail
If the wizard cannot create the new team project and returns an error message that is similar to "TF30170: The plug-in {0} failed during task {1} from group {2}," the wizard might have experienced a server protocol violation. Open the team project creation log and review the entries at the end of the log. One or more entries might indicate that the Team Foundation server sent the wizard a message header that did not follow the correct HTTP protocol format. If so, wait several minutes and try to create the new team project again.
If the problem persists, turn off HTTP header validation for the managed code. Change the file devenv.exe.config to include the following code:
<configuration>
<system.net>
<settings>
<httpWebRequest useUnsafeHeaderParsing="true"/>
</settings>
</system.net>
</configuration>
After you edit the file, try to create the new team project again.
Note
Including this code in the file will disable HTTP header validation for all managed code in devenv.exe.config. You should carefully review your security requirements and the affect of header validation before you make this change.
Missing Update Causes the Wizard to Fail
The following error appears when you try to create a team project from a computer that is running the version of Team Explorer for Visual Studio 2005 and the version of SharePoint Products and Technologies for Team Foundation Server is Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007:
Error TF30170: The plugin Microsoft.ProjectCreationWizard.Portal failed during task SharePointPortal from group Portal.
Explanation Plugin error text: "The language id specified in the process template does not exist on the WSS server."
User Action Contact your Team Foundation Server administrator.
Solution
You must create the team project from a computer that is running the version of Team Explorer for Visual Studio Team System 2008, or you must update Team Explorer on those computers on which team projects are created. For more information, see How to: Upgrade Team Explorer for New Releases of SharePoint Products and Technologies.
Underlying Connection Was Closed
If an error message indicates that an underlying connection was closed, the client computer might not be configured to automatically detect the link speed of its network adapter. For more information, see Underlying connection was closed.
See Also
Reference
TF30170: The plug-in {0} failed during task {1} from group {2}.