Visual Studio 2019 “no repositories available” for an Azure DevOps Server

0
votes

We have an Azure DevOps server that's used as source control. I am able to open DevOps in the browser (tested with Chrome and IE) with my credentials and see all the repositories but I can't connect to it through VS.

When I go to Visual Studio -> Team Explorer -> Manage Connections -> Connect to a Project -> Add Azure DevOps Server and type in the URL of the server, the server is successfully added but it has a warning sign (yellow triangle with an exclamation mark) and if I hover it, it says "no repositories available" -- see screenshot.

Are there any more details available to me? I tried launching VS with the /logs argument but that had nothing useful. It sounds like a permissions issue to me, my user being able to connect to the server, but not having read permissions to the repos, but, my user can see everything through the browser so I am not sure what to make of this. I installed the latest VS update and am on 16.3.9.

The DevOps server is technically hidden behind a VPN, not sure if that's important. I can't open DevOps in the browser if my PC is not connected to the VPN.

screenshot of the error icon/message

2
azure-devopsvisual-studio-2019
try logining online, then try reauthentication and lastly check if there are any repositories – user12053089
Logging in online works great; I've tried reauthenticating by deleting network credentials in control panel. We believe that there are repositories in place since I see them online + other developers see them in their Visual Studio. We can't figure out what's different between me and other developers. – Sasha Kachanov
check permissions on repos – user12053089
For troubleshooting, what about connect to TFS by using the VS in the server? This could know whether the issue caused by VPN – Merlin Liang - MSFT
i doubt it. a vpn would still show repos, more like they are not authorized – user12053089

2 Answers

2
votes

I had the exact same scenario and the same issue and I managed to solve it eventually.

Background * Two company sites connected via company fixed VPN (not on client machine) * Two local tfs installations (different versions) * Visual Studio 2019

When I add the remote tfs using tfs name http://tfs01.xxx.yyy.net (port 80) it seems to work but no repositories found, only a yellow warning sign.

Reason The url name http://tfs01.xxx.yyy.net/ is stored as http://tfs01/ in all local cache. The name http://tfs01 is not found (can't ping it, not resolved)

Solution Edit files in cache and change http://tfs01/ to the full url path on every occation (at least two places) - Go to c:\users[users]\appdata\local\microsoft\team foundation\8.0\cache - Look in LocationServerMap.xml - Note every unique guid for your server with issues - Find every occation of the file LocationServiceData.config in sub directories with your guids

or use the ugly solution and add the tfs server name (tfs01 in my case) to the local host file to ensure it resolves. c:\windows\system32\drivers\etc\hosts - add new row with ip address and short name

0
votes

Thanks everybody for replying. Here are our latest finds:

Domain-joined computers would present this bug, whereas non-domain joined would work fine. Go to cmd, type systeminfo. If your domain is WORKGROUP you will be fine. If it's anything else, you might have the same issue.

This was enough for us to work around the issue without resolving it. Just wanted to reply in case somebody runs into this in the future.