Share via

Registering an Instance of PWA to Team Foundation Server

  • Article

Before you can synchronize data between Visual Studio Team Foundation Server 2010 and Microsoft Project Server 2007 with Service Pack 2 (SP2) or Project Server 2010, you must first configure several points of integration between them. First, you must register the instance of Project Web Access or Project Web App (PWA) that supports an enterprise project plan with the application-tier server that hosts the team project collection that contains a team project. You can manage the registration of these instances of PWA by using the following options of the TfsAdmin ProjectServer command-line tool:

  • /RegisterPWA: Registers an instance of PWA to Team Foundation Server.

    Important

    The SharePoint web application for the instance of PWA must be set to Classic Mode Authentication. You will not be able to register the instance of PWA if it is set to Claims Based Authentication.

  • /GetRegisteredPWA: Lists the registered instances of PWA and the names of servers that are running Team Foundation Server to which the instances are registered.

  • /UnregisterPWA: Removes the registered association between an instance of PWA and Team Foundation Server. When you move a team project collection or a deployment of Team Foundation Server, you can remove the registered instances of PWA and then re-register them after the move.

For more information about the configuration and integration of Project Server and Team Foundation Server, see Configuring the Integration of Team Foundation Server and Project Server.

To use the TfsAdmin command-line tool, you open a Command Prompt window on a computer that is running Team Explorer and Service Pack 1 for Visual Studio Team Foundation Server 2010. You run the tool from the following directory: Drive:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE. For 64-bit machines, the tool is in Drive:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE.

Required Permissions

To use these commands, you must belong to the Team Foundation Administrators group. To register or unregister an instance of PWA, you must also belong to the Administrators group for the instance. For more information, see Assigning Permissions to Support Integration of Project Server and Team Foundation Server.

Note

Even if you log on with administrative permissions, you must open an elevated Command Prompt window to perform this function on a server that is running Windows Server 2008. To open an elevated Command Prompt window, click Start, right-click Command Prompt, and then click Run as Administrator. For more information, see the following page on the Microsoft website: User Access Control.

Syntax

TfsAdmin ProjectServer /GetRegisteredPWA /tfs:tfsUrl

TfsAdmin ProjectServer /RegisterPWA /pwa:pwaUrl /tfs:tfsUrl [/previousPwa:pwaUrl] [/force]

TfsAdmin ProjectServer /UnregisterPWA /pwa:pwaUrl /tfs:tfsUrl

Parameters

Parameter

Description

/tfs:tfsUrl

Specifies the uniform resource locator (URL) of an application-tier server for Team Foundation. You specify the URI in the following format:

http://ServerName:Port/VirtualDirectoryName

If you do not specify a virtual directory, specify the URL in the following format:

http://ServerName:Port

/pwa:pwaUrl

Specifies the URL of an instance of PWA. You specify the URL in the following format:

http://PWAServerName/PWAInstance

/previousPwa:pwaUrl

Specifies the URL that was most recently registered for an instance of PWA. When the URL changes for a registered PWA, you can use this switch to re-register the PWA. You specify the URL in the following format:

http://PWAServerName/PWAInstance

/force

Registers an instance of PWA with a different server that is running Team Foundation Server, and unregisters the instance from the server to which it was most recently registered. For example, when you move a project collection to another application-tier server, you must re-register the PWA for the collection with the new server.

/? or help

Displays information about the command.

Back to top

Remarks

When you run a TFSAdmin ProjectServer command, a message appears and confirms that the command is running. For example, the following message states that the instance of Project Web Access is being registered:

Registering PWA http:// PWAServerName/PWAInstance/

Another message appears after the command finishes. For example, the following message states that the instance of Project Web Access has been registered with Team Foundation Server:

You have successfully registered PWA http://PWAServerName/PWAInstance/

You can register an instance of PWA with only one application-tier server for Team Foundation. You must register an instance before you can associate it with a team project collection. When you register an instance, the location service for Team Foundation Server is updated with that information. In addition, the instance of PWA is updated with the custom fields and lookup tables that integration requires.

When you run a registration command, the following operations occur:

  • If you run /RegisterPWA more than once and a record of the registration already exists, the following message appears:

    The following PWA instance has already been registered: <PWAInstance>.

  • When you run /GetRegisteredPWA, the following information appears:

    The following PWA instances are registered:  
PWA URL 1
PWA URL 2

  • When you run the /UnRegisterPWA option, the command removes not only the mapped association but also the custom fields and lookup tables from the instance of PWA.

Back to top

Failed Command with 401 Error Returned

The /registerpwa command fails with a 401 error if the URL for the instance of PWA specifies a non-NetBIOS name for the machine that runs Project Server. This error results from an authentication failure that occurs if the fully qualified domain name (FQDN) or the custom host header that has been configured for a machine does not match the local computer name.

To resolve this error, you must add the NetBIOS name to the alternate access mappings in the SharePoint site that is defined for the instance of PWA, and you must add an exception to allow intra-machine communication. For more information, see the following page on the Microsoft website: You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or a later version. To resolve the error, use the first method listed, "Method 1: Specify host names (Preferred method if NTLM authentication is desired)". This method uses the BackConnectionHostNames entry, which allows communication with a specific machine name. You must add the non-NetBIOS machine name to the list of host names that are mapped to the loopback address and can connect to websites on your computer. You do not need to restart your computer or perform an IISReset with this method.

Back to top

Examples

The following values apply in each example:

  • URL for the instance of PWA: http://PWAServerName/PWAInstance/

  • URL for Team Foundation Server: http://AdventureWorksServer:8080/tfs/

List the Registered Instances of PWA

The following example lists the instances of PWA that are registered to AdventureWorksServer:

TfsAdmin ProjectServer /GetRegisteredPWA /tfs:http://AdventureWorksServer:8080/tfs/

Register an Instance of PWA

The following example registers PWAInstance to AdventureWorksServer:

TfsAdmin ProjectServer /RegisterPWA /pwa:http://PWAServerName/PWAInstance /tfs:http://AdventureWorksServer:8080/tfs/

Remove Registration of an Instance of PWA

The following example removes the registration of PWAInstance from AdventureWorksServer:

TfsAdmin ProjectServer /UnregisterPWA /pwa:http://PWAServerName/PWAInstance/ /tfs:http://AdventureWorksServer:8080/tfs/

Back to top

See Also

Tasks

Configuring the Integration of Team Foundation Server and Project Server

Concepts

Managing Project Server Integration with TFSAdmin ProjectServer

Change History

Date

History

Reason

September 2011

Added section to troubleshoot a failed /registerpwa command.

Information enhancement.

June 2011

Added a note that the SharePoint web application for the instance of PWA must be set to Classic Mode Authentication.

Customer feedback.