服务器无法提供 Team Foundation 服务 - 无法解析远程名称
我们正在使用 Visual Studio 2010 和 Team Foundation Server 2010。大约半年以来我们没有遇到任何问题，但是：
几天后我们收到以下错误：服务器无法提供 Team Foundation 服务（... ) 无法解析远程名称； (...)
该问题随机发生（我们尚无法查明具体情况）它发生的地方）并持续存在，直到我们重新启动 Visual Studio。每个开发人员每天大约会出现 8 次该问题。
因为我们似乎没有解决这个问题，而且我们找不到任何人写关于这个特定组合（错误和“远程名称”部分）的文章，所以我认为向你们询问这个问题是明智的；）。有人可以帮忙吗？
We are working with Visual Studio 2010 and Team Foundation Server 2010. We did not have any problems for about half a year, but:
Since a couple of days we get the following error: Team Foundation services are not available from server (...) The remote name could not be resolved; (...)
The problem occurs randomly (we are unable - yet - to pinpoint the conditions on which it occurs) and persists until we restart Visual Studio. The problem occurs about 8 times per day per developer.
Because we seem not to get past this problem and we cannot find anybody writing about this specific combination (the error and the 'remote name' part), I thought it wise to ask you guys about it ;) . Could anyone please help?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（8）
这是网络级别上与客户端、服务器或基础设施相关的问题。对于主机 dfz-vm223，有时无法正确解析 TFS 服务器的 DNS 条目。
故障排除建议：
This is a client, server or infrastructure related problem on network level. The DNS entry for your TFS server cannot be resolved correctly at times for host dfz-vm223.
Suggestions for troubleshooting:
刚刚发现问题是什么：问题与代理相关。当我们禁用代理时，问题就消失了。看来我们的代理和 TFS 在一起很麻烦。如果有人遇到同样的问题并且您正在使用代理服务器，我建议您也尝试禁用代理。
Just found out what the problem was: the problem is proxy related. When we disable our proxy, the problem is gone. It appears our proxy and TFS are troublesome together. If anyone experiences the same problem and you are working with a proxy server, I would suggest you try disabling the proxy too.
我和我的一些同事也遇到过这个问题。大约 25 名开发人员中，大多数人从未遇到过此错误。但我们三个人的表现相当一致。症状是相同的，但我们几乎只使用 Visual Studio 2013。在此版本的 Visual Studio 中，错误前面带有代码：TF400324。
最终我们发现我们三个人都安装了Productivity Power Tools 2013。而没有受到这个错误影响的开发者则没有安装它。大多数人没有听说过。这曾经是一个非常流行的扩展，所以从 2007 年左右开始，我在设置系统时总是安装它。但显然，在 Visual Studio 2013 中它的现代版本中，也许与我们网络中的一些怪癖或其他东西相结合，它可能会导致此问题。我们都卸载了它，从那以后就没有收到此错误。 （现在已经过去几个月了。）
如果您安装了此扩展，您可能已经知道它了，因为您可能自己安装了它。您可能几年前就开始使用它，并且将其添加到每个新安装中已成为一种习惯。今天您会发现，Visual Studio 的默认安装实际上已经包含了它的大部分功能。要卸载，请转到“工具”-->“扩展和更新... 然后单击 Productivity Power Tools 2013，然后单击卸载。
Some of my co-workers and I had this problem as well. Out of about 25 developers, most never got this error. But three of us got it pretty consistently. The symptoms are identical, but we are using Visual Studio 2013 almost exclusively. In this version of Visual Studio, the error is preceded by the code: TF400324.
We found eventually that the three of us had all installed Productivity Power Tools 2013. And the developers that were not affected by this error had not installed it. Most had not heard of it. This used to be a very popular extension, so I have always installed it as I set up my system since about 2007. But apparently, in its modern incarnation in Visual Studio 2013, perhaps in combination with some quirk in our network or something, it can cause this problem. We have each uninstalled it, and have not gotten this error since. (It's been several months now.)
If you have this extension installed, you probably already know about it, because you probably installed it yourself. You probably started using it years ago, and it became a habit to add to each new installation. You will find that today, the default installation of Visual Studio actually includes most of its features already. To uninstall, go to Tools --> Extensions and Updates... Then click on Productivity Power Tools 2013, and click Uninstall.
尽管我使用的是 VS2012 和到 TFS 的 WAN 连接，但我也遇到了同样的问题。
我通过刷新 DNS 缓存解决了这个问题。
要刷新 DNS 缓存，请使用管理员权限启动命令提示符：
ipconfig /flushdns您需要在出现问题的所有计算机上执行此操作。
I had the same problem, although I'm using VS2012 and a WAN connection to TFS.
I solved the problem by flushing the DNS cache.
To flush the DNS cache, start a command prompt with admin rights:
ipconfig /flushdnsYou need to do this in all the computers where the problem occurs.
我知道这已经很旧了，但是当我运行 Fiddler 时有时会遇到这个问题。
有时 Fiddler 会崩溃或无法正确清理，整个机器会进入某种奇怪的状态，甚至重新启动也无济于事。解决方案通常是再次启动 Fiddler，关闭所有拦截器/收集流量，然后再次将其关闭。
I know this is old, but I had this problem sometimes when I ran Fiddler.
Sometimes Fiddler would crash or not clean up properly and the whole machine would get into some weird state where not even reboots were helping. The solution to it usually is to start Fiddler again, turn off any interceptors/collecting traffic and shut it down again.
有同样的问题。无论出于何种原因，我的 PC 上的 Windows DNS 客户端服务未运行。将其从“禁用”更改为“自动”为我解决了这个问题。
Hade the same issue. For whatever reason the windows DNS Client service on my PC wasn't running. Changing it from Disabled to Automatic solved this problem for me.
评论太长：
首先，正如 @kroonwijk 所说，这是一个基础设施问题。您的 DNS 查询超时或 DNS 服务器在某些时间没有响应。
在评论中，您提到了整个开发团队从普通计算机改为笔记本电脑。如果我必须打赌，我会说笔记本电脑上的 DNS 配置与其他计算机上的 DNS 配置不同。
您需要与基础设施人员一起解决这个问题。如果您仍然可以访问旧机器，请启动其中一台并比较 IP 配置。如果没有，请让他们解决问题。 DNS 解析问题可能是多种因素之一造成的。例如，新计算机可能指向存在网络问题的不正确的 DNS 服务器，或者 Win7 发出 DNS 请求的方式与您的 DNS 服务器之间可能存在某些不兼容。
Too long for comments:
First off, as @kroonwijk stated, this is an infrastructure issue. Your DNS queries are either timing out or the DNS server is not responding at certain times.
In a comment you mentioned a change over from regular machines to laptops for your entire dev team. If I had to make a bet I'd say that the DNS configuration on the laptops is not the same as what you had on the other machines.
You need to take this up with your infrastructure people. If you still have access to the older machines boot one of them up and compare the IP configuration. If not, get them to fix the problem. The DNS resolution problem could be any one of a number of factors. For example, the new machines could be pointing to an incorrect DNS server that has network issues or their might be some incompatibility between how Win7 makes DNS requests and your DNS server.
我也遇到过这个问题，它并不总是与名称解析有关。
如果您将一个条目添加到 TFS 服务器的 %systemroot%/system32/drivers/etc/hosts 文件中，它将消除对名称解析服务器的任何依赖。
如果您仍然遇到该问题，则可能与 Visual Studio 或您正在运行的 VS 扩展之一有关。某处可能存在内存泄漏。使用扩展管理器禁用所有扩展，重新启动 VS，然后查看是否仍然遇到问题。
I have also experienced this problem and it doesn't always have to do with name resolution.
If you add an entry to your %systemroot%/system32/drivers/etc/hosts file for your TFS server, it removes any dependance on your name resolution servers.
If you are still experiencing the problem, then it has to do with either visual studio or one of the VS Extensions that you are running. There may be a memory leak somewhere. Disable all your Extensions using the extension manager, restart VS, and see if you still experience the problem.