TF400324: Team Foundation services are not available from server <Server/CollectionName> in Visual Studio 2012

user_299990 0
Viewed 66088

When I open my existing solution in Visual Studio 2012 professional, I got the above error. This used to work but something messed up after the computer is rebuilt.

I have installed Visual Studio 2015 Community and can connect to the same collection correctly.

I also tried to use a browser to connect to the same collection. It works fine also.
Cleaning all files in AppData\Local\Microsoft\Team Foundation\4.0\Cache does not work.
It should not be a firewall or proxy issue since Visual Studio 2015 works.
Anyone knows what is wrong with Visual Studio 2012 and how to fix it?

Edit:

This error can happen with later versions of TFS:

Team Foundation Error

TF400324: Team Foundation services are not available from server TFSServer\DefaultCollection.

Technical information (for administrator):

Unable to connect to the remote server

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond xxx.xxx.xxx.xxx:443

visual-studio-2012 tfs version-control visual-studio
11 Answers

According to this blog the solution is (and Yes it worked for me)

  1. Close all instances of Visual Studio
  2. Open the Task Manager and check if any TFS Services are running.
    Select each of them and click on End Process Tree
    (in my case I did not find any of them to End)
  3. Browse to the folder %LocalAppData%\Microsoft\Team Foundation\
    and then select the folder with your TFS version and go inside the Cache folder.
    for example, in my machine the path was %LocalAppData%\Microsoft\Team Foundation\7.0\Cache and it should be the same on your machine with the difference of the TFS version folder name.
  4. Delete everything in that Cache folder.
  5. Start Visual Studio and build the project
user_43901330

Soluton for me was to run the standalone TFS installation. This is for 2017, but worked to fix my VS2019.

https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=TeamExplorer&rel=15

Bit of background...

I'd been having this issue since 2017. Tried all the usual suggestions on here, cache clearing, config file editing etc. but would always have to come off my organisation's network to check code in, as it was proxy related. TFS was trying to connect to a proxy server ip that had been decommissioned, no one from the service desk could work out why. Couldn't find any reference to this old ip in any config files.

Installed VS2019 hoping it would solve the issue but it persisted. Eventually I thought of trying to uninstall it as a component and re-installing it. Couldn't find a way to do that but in my search I found the standalone installer for Team Explorer, albeit for VS2017.

After installing, I ran this, opened up Manage Connections in the Team Explorer connections page and did what I needed to connect to the repository from there. Worked first time. Closed Team Explorer 2017, opened my VS2019, and everything seemed fine in there as well.

Amazed my problem is finally solved!

user_84352930

For me it was the windows firewall causing this problem : TF400324 The underlying connection was closed.

user_10716980
Related