![]() So that started pointing towards some kind of problem with the customer’s servers or networking environment. We tried all the usual stuff like deleting the local Visual Studio / Team Explorer cache but nothing worked.Īs part of my effort to solve the problem, I created a bunch of virtual machines in my test environment (including installing Visual Studio 2013 for the first time in nearly a decade). According to the Azure DevOps / Visual Studio version support matrix, everything should be working. My first thought was to check if these clients were still supported. They were getting the dreaded “TF31002: Unable to connect to this Team Foundation Server” error if they tried to connect using Visual Studio 2013, Visual Studio 2012, Visual Studio 2010, and some older versions of the Eclipse plug-in. Everything upgraded smoothly but users running older versions of Visual Studio couldn’t connect. I recently ran into a strange problem while doing an upgrade from Team Foundation Server to Azure DevOps Server 2020 for a client.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |