Hi I am very new to TFS and have not installed it before. I just installed TFS 2013 using the Basic Installation that was given in the wizard. Everything is done and the installation is complete. It has created a new Server in SQL Server and hs opened up the TFS Admin Console. All the details for the server and the collections are shown here, but when I try to connect to the server from visual studio it does not connect. It says server unavailable. The state in the TFS Admin console is "Online". I am not able to modify the url in the TFS Admin Console too. I am really not sure what is going wrong here and what should be done. Am clueless about the next step. Any help is appreciated.
Thanks
In a web browser or in the Connect dialog in VS, it is http://<ServerName>:8080/tfs/
You can find instructions for both the web and VS on MSDN.
Related
After my recent upgrade to Visual Studio 2019 (?) on Mac, I am unable to connect to my TFS server using the TFS Source Control extension.
My current setup:
Visual Studio for Mac, version 8.0.3.14
Source Control Extension:
Team Foundation Version Control for TFS and Azure DevOps Version
0.4.4.5
Steps: In Team Explorer, now I see two options:
1) Add Account
2) Add Server
When I try Add Account, a dialog pops up asking for my MS credentials - I enter them as usual, and then nothing further happens, no feedback whatsoever. Is this because it thinks this account is already "added"?
When I try Add Server, I enter my azure dev ops server name, then for user name/password I enter my MS account email and password. I leave domain empty. I get a message:
"Server already exists."
Here is what I expect to see (screenshot from VS 2017 on Windows):
Instead, nothing gets populated the way it normally does in Team Explorer: Pending changes, work items, settings - the entire panel is empty:
I do switch between Windows and Mac a lot, but if I remember correctly, everything worked fine from both workspaces before, so it probably happened when I upgraded to Visual Studio 8.0.3.14 on my Mac. Any ideas on how to fix this?
I wondered the same thing but without the update process in my back pocket... meaning I haven't written any C# in a while but I'm coming back to it. I set up a project with TFS in Azure Dev Ops on my pc, then went to check it out on my Mac and couldn't find any reference anywhere to TFS. Subversion and Git are in there, but no TFS. It took a little while to find it, but here's what I found. The short answer is they want you to use Git, not TFS as TFS is not supported in VS 2019 for Mac. The article does list work-arounds.
https://learn.microsoft.com/en-us/visualstudio/mac/tf-version-control?view=vsmac-2019
When I try to connect to TFS 2015 from within Visual Studio 2017, I get the message "No repositories available". The tfs server is listed, but I cannot connect.
No problems in Visual Studio 2015.
Do you have an idea, what I could do?
Thank you
This is a new UI design changed by Visual Studio 2017.
In Visual Studio 2017, we changed the behavior of the Connect page. We
now populate the Connect Page list with only the items you’ve
selected.
If you select a project and click "Connect", you will see only the project node in the Connect page. To get your repositories to appear
on the Connect page you need to select the repository node in the
Connect dialog and hit Connect.
This change was made in response to feedback from folks who had large
numbers of repositories in their team projects and wanted to not have
them all added whenever they connected to anything in said project.
More details please refer the visual studio team's comment in this similar question: Team Explorer does not show the repositories within a multi repository project
I had similar issue ,for me TFS is using Kerberos authentication. I changed the authentication to NTLM by running command from Developer tools under TFS server.
TFSConfig Authentication [/provider:NTLM|Negotiate] [/viewAll] [/siteType:ApplicationTier|Proxy]
Reference - https://learn.microsoft.com/en-us/azure/devops/server/command-line/tfsconfig-cmd?view=azure-devops#authentication
We also did IISRESET after this.
After this i am able to view the Repos under visual studio.
Web update our TFS2013 to TFS2015, most features worked well, but Test Manager could not connect to TFS2015,when create connection, no project collection could be found on server, as shown below:
But On web we can open test plans and
We can open Test Manager from this link:
I searched from MSDN about this problem, and did what they say in that article, but did not resolve my problem.
In order to narrow down the issue, please check items below:
Check whether the account to connect to TFS in MTM is the same as the account used on web access. Make sure you are using the same account.
Try to install MTM on TFS Application Tier machine, and connect TFS, to see whether you can connect it. In this way, you can find out the issue is from TFS side or MTM side.
I'm trying to migrate from on-premises TFS to Visual Studio Online. We have quite elaborate TeamCity build process that we don't want to migrate away from, so having TeamCity working with VSO would be ideal.
I've created alternative user credentials (as per this article) and using these credentials in TeamCity. But when I create new VCS in TeamCity, I get connection error:
TF30063: You are not authorized to access https://myproject.visualstudio.com/DefaultCollection/MyProject
I've tried my actual credentials (not alternative ones) but nothing changed - same error.
Also I've tried using alternative credentials with tf command line tool and could not enter alternative credentials - a window popped up, asking me for my LiveId.
Any idea how to fix this?
p.s. this is how TeamCity configuration look like:
To connect to Visual Studio Online you indeed need to enable alternate credentials on the account you'll use for Team City. Ensure that at least Team Explorer 2012 and update 4 is installed on the Team City server, install the whole Visual Studio 2012 incl Update 4. Team City requires at least update 2, but Microsoft only supports Visual Studio 2012 RTM and the latest update (which is update 4).
Then in the connection screen use the following information:
Repository URL: https://myaccount.visualstudio.com/DefaultCollection
Username: ##LIVEID##\your.email#live.com // Your visual Studio Online User Name, must match your LiveId.
Password: ********* // The password you setup for the alternate credentials.
You can also use the VSO Service Account credentials instead of using Alternate Credentials.
Then in your VCS Root configuration map your TFVC root in the following way:
Root: $/MyProject/Path/To/Branch/Root
Check out this post on the Jetbrains Confluence site for more details.
This has changed lately and the password needs to be generated.
Navigate to your site at https://[your project].visualstudio.com/_details/security/tokens
And generate a personal access token. And use it for password in your teamcity vcs root configuration. Username is your email.
https://streamlined.no/2016/09/19/connecting-teamcity-10-vcs-root-visual-studio-team-services/
Note: TeamCity 10 does not need the ##LIVE## workaround anymore.
I had the same problem today. The TC instance which was working fine last week mysteriously could not connect to any VCS Roots after the weekend. All VCS roots are git repos in visual studio online.
The Test Connection was failing and changing to known working user accounts still failed.
Restarting the TC service also had no impact on the problem. In the end, rebooting the whole TC Server fixed the issue. Hopefully this will help someone else out.
Well, I could not use Alternate credentials as I use it in many build configurations and it was set up to poll every 60 seconds. So I had to do much manual work to fix it up. Instead, I generated a Personal Access Token and in the Team City VCS setup for Git I entered "username" as the username and pasted the PAT into the password. That worked much better and more stable than Alternate credentials, which kept getting disabled because of background polling on behalf of Team City.
We have a problem with our current TFS installation. For some reason, which I won't get into, the Sharepoint DBs (sts_content, sts_config) got corrupted. So now, none of our team-project sites work, we have no access to our documents and can't create new team projects. We can still work with the version control, though.
We wanted to "play" with the server and try to fix it, without affecting the users. So we duplicated the server to a virtual one. We now continued and changed all of the relevant configuration to point to the new server, as explained in the MSDN article.
The step of rebuilding the warehouse (with setupwarehouse) failed. Also, we can't access the VersionControl web service (ourserver:8080/VersionControl/v1.0/repository.asmx). We are seeing errors in the EventLog:
TF53002: Unable to obtain registration data for application Build.
TF53005: Unable to retrieve the Team Foundation Server installed UI culture.
TF53002: Unable to obtain registration data for application VersionControl.
TF30040: The database is not correctly configured. Contact your Team Foundation Server administrator.
The solutions suggested in this blog post did not assist. So now we're kind of stuck.
Any assistance will be appreciated.
This is a really old question, but what I would suggest doing is installing a fresh copy of Team Foundation Server 2010, then in the configuration wizard, select 'Upgrade' and choose your existing TFS2005 databases. This will allow you to get a working server up and running, without SharePoint and the Cube/Warehouse configured. You can then tackle each of those problems separately via the TFS Administration Console.