Partager via

Proxy Upgrades: How to Verify Skipped Proxy Endpoints

  • Article

TFS 2013 offers support for Proxy settings persistence during in-place upgrades.  This means we will allow you to configure with all your old settings (including multiple endpoints) and will automatically detect and pre-populate them in the Proxy configuration wizard for you, should you indicate that you wish to use them.  Given that Proxy can re-configure multiple endpoints at once using this feature, any endpoints that are blocking configuration for any reason may be "skipped" or "removed."  Removing an endpoint is very straightforward - all references to the collection or TFS server in question will be removed from the Proxy configuration file and the endpoint will be completely erased from your Proxy deployment.  Skipping an endpoint is a bit different.  You may want to use the "skip" option if you are not configuring Proxy with an account that has access to the endpoint (and thus cannot authenticate to it in order to validate that it is functional), but you believe the endpoint may still be in use.  Skipping an endpoint will not remove it from your Proxy configuration file and in most cases the endpoint should continue to work as expected once configuration is complete.  However, since TFS will not be able to verify this during configuration, you will need to do that verification manually afterwards.

 

To do this verification, try making a call to the endpoint in question from a client that uses a valid ID to retrieve files via the TFS Proxy.  Note that the call must be version control related (for example, checking in or checking out a file from source), as only version control artifacts are routed through the Proxy server.  If you do not yet have a client that is configured to use the TFS Proxy, you can set this in Visual Studio by selecting

Options --> Source Control --> Visual Studio Team Foundation Server --> Use Proxy Server 

 

If you are able to execute the command successfully, no further action is needed.  In the unlikely event that it fails, follow these steps to troubleshoot the issue and restore Proxy functionality for that endpoint:

  1. Check that your Proxy server and TFS server are up and running.  If you servers are down, they will not be able to process your request.
  2. Check the proxy.config file on your Proxy server to verify that the endpoint is listed there.  If the endpoint is not listed, then it is not configured and may have been accidentally removed prior to or during the upgrade.  Run the TFSConfig Proxy /add command to add the endpoint back.
  3. If neither of the first two cases apply, your administrator account probably does not have permissions to authenticate on the Proxy server.  Delete the entry for this endpoint, either in the proxy.config file or by using TFSConfig Proxy /delete, and run the TFSConfig Proxy /add command to add the endpoint back again under your current admin account.

Should you still have problems with any of your Proxy endpoints after running through these steps, please contact Microsoft Support for specialized assistance.

Comments

  • Anonymous
    October 22, 2013
    Hi Andrea, I just have configured the proxy server with the main tfs server. Now at remote site i am getting the Latest code and its being downloaded to my local mapped work space without giving me any error massage. How do i confirm that my code is being gotten through TFS proxy server and not directly from the main tfs server.?