This documentation is archived and is not being maintained.

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

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 These forums provide searchable threads on a variety of troubleshooting questions and are monitored to provide quick responses.

After you click Finish in the New Team Project Wizard, the wizard connects to the appropriate servers and services and starts to create necessary components. The speed with which the wizard finishes the team project creation is, in part, dependent of the speed of the computer network. The configuration of network switches and your computers' network cards (for example, whether "autosense mode" or "auto-negotiation" is turned on, or whether information is transmitted in full-duplex mode or half-duplex mode) can affect the network speed. Confirm that these settings are correct. For more information about how to use an autodetect setting, see "The effects of using Autodetect setting on cluster network interface card" at For more information about full-duplex mode versus half-duplex mode, contact the network administrator.

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 automatically reconfigured and can no longer communicate with Windows SharePoint Services. The next time that you try to create a new team project, you may 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.


The most current version of the Team Foundation Administrator's Guide is available on the Web at the MSDN Online site ( The latest version of the Team Foundation Installation Guide is available on the Web at the Microsoft Download Center (

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 Team Foundation Server Contributor Permissions.

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 creating 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:

                  <httpWebRequest useUnsafeHeaderParsing="true"/>

After editing the file, try creating the new team project again.


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.