服务器2016上的TFS 2017.2 [英] TFS 2017.2 on Server 2016

问题描述

这是一个很好的，至少我认为是。我有一个当前在TFS 2017 Update 2上运行的Staging环境，运行安全（使用Kerberos身份验证的https）和App Tiers（主要和DR）托管的Windows Server 2012服务器。已经从2013年的每个
TFS版本升级，现在在2017.2上运行。对我来说，一切正常。我可以从各种Visual Studio连接到它，是的，我必须测试各种各样的，Team Explorer 2013 + 2017和VS2012到VS2017以及各种版本的SP，浏览器
等连接到网站，一切正常。 

输入新的App Tier Server，但现在在托管/ vm Windows Server 2016上，设置所需的角色/功能等，防火墙规则，将证书导入到服务器，已安装TFS 2017.2并将服务器添加到暂存环境（仅限应用程序层安装），
 将DNS更改为新服务器并开始测试。与VS2017和VS2015完美连接，完全没有错误或问题。尝试连接安装在同一客户端计算机上的VS2013，它根本不会连接到服务器。只需获取有关'无法连接到Team Foundation Server的通用
消息 - 可能的失败原因包括'...等等等等等等。服务器或客户端上的事件日志中没有错误消息，服务器上的IIS日志没有从VS2013注册客户端连接，显示
我通过VS2015和VS2017连接，但VS2013没有。在客户端上，VS日志显示消息 - '基础连接已关闭：发送时发生意外错误'

如果我将DNS更改回Windows Server 2012服务器，则全部工作良好。问题只出现在Windows Server 2016上。我认为问题必须出现在Server 2016上的IIS中，但对于我的生活，我无法弄清楚问题是什么，因为IIS日志是
没有显示任何连接尝试。 

在Windows Server 2016上将VS2013连接到TFS 2017.2服务器的其他人遇到了什么问题？

解决方案

您好Simon，

您是否安装了VS2013的最新更新？

您可以尝试清理VS2013计算机上的缓存文件：％AppData％\ Local \ Microsrosoft \Team Foundation \\\ 06.\Cache。

祝你好运，

Here is a good one, well at least I think it is. I have a Staging environment currently running on TFS 2017 Update 2 running secured (https with Kerberos auth) with the App Tiers (Primary and DR) hosted Windows Server 2012 servers. Has been upgraded at each TFS release from 2013 and is now running on 2017.2. Yay for me, everything works. I can connect to it from various Visual Studio(s), yes, I have to test a variety, Team Explorer 2013 + 2017 and VS2012 through to VS2017 and various flavours of SP's, browsers etc connect fine to web site, all works fine. 

Enter a new App Tier Server, but now on a hosted/vm Windows Server 2016, Set up required Roles/Features etc, Firewall rules, import the certs onto the server, Installed TFS 2017.2 and added the Server into the Staging environment (App Tier Only install),  change DNS over to new server and started testing. Works fine connecting with VS2017 and VS2015, no errors or problems at all. Tried connecting with VS2013 installed on the same client machine and it won't connect to the server at all. Just get the generic message about 'Unable to connect to Team Foundation Server - possible reasons for failure include'... blah blah blah. No error messages in eventlogs on either the server or the client, IIS logs on server don't register a client connection from VS2013, shows me connecting via VS2015 and VS2017 but nothing for VS2013. On the Client, the VS logs show message - 'The underlying connection was closed: An unexpected error occurred on a send'

If I change DNS back to the Windows Server 2012 server, it all works fine. Problem only presents on Windows Server 2016. I think the problem has to be in IIS on Server 2016 but for the life of me I cant figure out what the problem is because IIS logs are not showing any connection attempt. 

Anyone else run into issues connecting VS2013 to a TFS 2017.2 server on Windows Server 2016?

解决方案

Hi Simon,

Do you install the latest update for your VS2013?

You may try to clean the cache files on the VS2013 machine: %AppData%\Local\Microsoft\Team Foundation\6.0\Cache.

Best regards,

这篇关于服务器2016上的TFS 2017.2的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！