I have a new Team Foundation Server that we are hosting - Version 16.131.28226.3. It is over an SSL connection and has a valid certificate.
I have created a new Team Project named "Test".
The project source control type is Git.
In Visual Studio 2017 - 15.9.4 Team Explorer, I can clone this git repo under Local Git Repositories. And I have successfully added and pushed to the server.
However, if I try to connect to this new Team Foundation Server - Manage Connections, Connect To a Project, Add TFS Server; when I add the TFS server, there is an exclamation icon next to and if I hover on the server name it says
No Repositories Available
when selected, the Connect button is disabled. In the screenshot below, the second highlighted server is the one in question:
So the Local Repo is not associated with the Team Repo, thus I can't assign Work Items to my checkins, etc..
I have explicitly added myself as a User to the Project, I don't know what else to do. Any advice?
My issue was - on the server, Team Foundation Server Administrative Console, the Public URL was incorrect. Our public URL had changed to a full domain name with https and the public url was still set to the old http LAN address.
Bounty Edit:
This actually worked! I checked TfsMgmt.exe and had specified only https://MachineName for the Public URL.
I edited it and specified the Fully Qualified Domain Name, ignored an error when clicking the test link, then I restarted the TFS Server(s) including the SQL.
Ps I previously had to add the certificate, add a trusted URL: https://stackoverflow.com/a/43036526/495455 and I also added the TFS Server into Windows Credentials Manager with my username/password.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With