6

While trying to add a TFS server to VS 2017, I encountered an issue where it claims that the server already exists in the list. However, it does not.

The only thing that I can think of that could cause it to think that the server is in the list, is that the two servers used to be one. This was not an issue with VS 2015.

The TFS servers are both 2015 update 3.

Please feel free to ask for any more info.

svick
  • 236,525
  • 50
  • 385
  • 514
Michael Coxon
  • 5,311
  • 1
  • 24
  • 51
  • 2
    If the server was split into two servers, it's very important that the Server ID was changed when setting up the second server. Very weird behavior can happen otherwise. Same goes for collection IDs. – jessehouwing Mar 14 '17 at 19:20
  • I encountered this issue TFS2017 and IP Address didn't work. It was a slightly different cause: http://stackoverflow.com/a/43036526/495455 – Jeremy Thompson Mar 31 '17 at 04:13

3 Answers3

5

Give a try with directly using IP address instead of server name when you are adding Team Foundation Sever in VS2017. Something like:

http://192.168.0.1:8080/tfs

Update

You could find your Team Foundation Server 2015 GUID Info in below location:

 C:\Program Files\Microsoft Team Foundation Server 14.0\Application Tier\Web Services\web.config

There should be a value like

enter image description here

Then you could compare the GUID of two servers, change one of them and re-register db. More details about it take a look at this blog: How to find Team Foundation Server(TFS) GUID Info

PatrickLu-MSFT
  • 49,478
  • 5
  • 35
  • 62
  • Hi Patrick, cheers for your response. So I just tried to no avail - The server prompts me to login and everything, it just thinks I have already connected to it. I am thinking it has something to do with the ID's that @jessehouwing was talking about in the question comments. Do you have any comments/suggestions about this? – Michael Coxon Mar 15 '17 at 04:46
  • @MichaelCoxon About how to find the GUIDS info of your two servers, please see my update answer. – PatrickLu-MSFT Mar 15 '17 at 06:44
  • Patrick you are a legend. Changing the ID's worked perfectly. Thanks to @jessehouwing for also suggesting this. – Michael Coxon Mar 16 '17 at 07:03
  • @PatrickLu-MSFT How do you re-register the DB once you've changed the GUID? – Eritey Jan 23 '18 at 09:30
  • @Eritey Why you want to re-register the DB. Have you finished the TFS upgrade or something else? Could you describe more clearly about your situation? – PatrickLu-MSFT Jan 23 '18 at 12:00
3

This works for me:

  1. Close VS 2017.

  2. Open explorer and go to %appdata%\Microsoft\VisualStudio\15.0_92d7e574. Delete all files.

  3. Go to %localappdata%\Microsoft\VisualStudio\15.0_92d7e574. Delete all files.

  4. Start VS 2017 and enter the TFS server address.

Jan
  • 39
  • 2
1

We just did the upgrade and found out that VS 2017 expects (at least for now) that there should only be 1 TFS server present, so you would need to remove the old one, then add the new one. It's probably some confusion with the TFS Workspace. The "Connect" box may still give the error, but after removing the old, adding the new, and pressing the "Connect" button, it worked just fine for me.

Bryan Dickerson
  • 63
  • 10