【TFS2015】请问切换域控时报错“TF246017: Team Foundation Server 未能连接到数据库。请验证是否已正确指定实例，承载数据库的服务器是否能够正常运行，且没有网络问题阻止与服务器通信。”如何解决

Question

从A域控切换到B域控时，走到切完B域控后，sqlserver2012能用B\admB访问（从管控台登录），但在启动TFS服务时报下面错误：

1、TF246017: Team Foundation Server 未能连接到数据库。请验证是否已正确指定实例，承载数据库的服务器是否能够正常运行，且没有网络问题阻止与服务器通信。

2、后来我修改“D:\Program Files\Microsoft Team Foundation Server 14.0\Application Tier\Web Services\”

里的字符串为“<add key="applicationDatabase" value="Data Source=B;”

因为未改之前是“<add key="applicationDatabase" value="Data Source=A;”

在VS命令行下执行

“TFSConfig Identities /change /fromdomain:OldDomainName /todomain:NewDomainName”

报下面错误“

TF246083: Team Foundation Server 的配置无效。必须重新映射数据库以修复配置。从服务器收到以下错误: TF400673: 在指定实例中找不到任何兼容的 SQL Analysis Services数据库。
已经为“2”主机提供更新的连接字符串。

”

---

我参考的切域的步骤是这个

https://docs.microsoft.com/zh-cn/azure/devops/server/admin/move-across-domains?view=azure-devops

Answer 1

其中启动TFS控制台也报错，错误同上

---

Answer 2

重新安装TFS并配置应用层，也是上面那个错误，并且TFSjob服务没有安装成功，这是为啥？

---

Answer 3

Hi springcolor,

根据你的描述，你可以试试这个Remap DBs：https://docs.microsoft.com/en-us/azure/devops/server/command-line/tfsconfig-cmd?view=azure-devops#remapdbs

Best regards,

Sara

---

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail]

Answer 4

您好，又回到第一个错误了。

试了RegisterDB ，以及TfsConfig repairJobQueue 都不行。

---

Answer 5

Hi springcolor,

请确认下DB的service是否是启动状态， 然后在参考以下的相识问题：

https://stackoverflow.com/questions/45129042/tf246017-team-foundation-server-could-not-connect-to-the-database

https://social.msdn.microsoft.com/Forums/vstudio/en-US/6b4c0f9d-2e3f-4353-b073-d49c6500a8e7/tf246017-team-foundation-server-could-not-connect-to-the-database?forum=tfsadmin

Best regards,

Sara

---

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail]