The legacy TFS build service, the one that sits in the service list as "Visual Studio Team Foundation Build Service Host 2015" and does XAML builds. What's the proper way to uninstall it?
When I go to TFS Admin Console and click Unregister, the service is stopped, but remains in the system.
I can get rid of it with sc delete, but that's crude.
I don't see anything relevant underneath Control Panel/Uninstall.
If it's a stand-alone build server, uninstall TFS entirely and if the service is still there, manually remove it. It doesn't really matter one way or the other, honestly.
If it's a combo app tier/build server, just leave it alone.
Related
I've got a project that I have in Team Foundation Server (TFS), on-premise. I've been trying, since yesterday, to check it into TFS. (I'm using TFVC, since I'm required to do so.) There's something wrong with the TFS server, as it is refusing to let me check in the changes. I was told by one of the TFS admins that I could remote to the server and restart it. Unfortunately, that is not true. I don't have the necessary privileges to remote to that server.
I'm wondering what would happen to the project in TFS, if I just close Visual Studio, while its stuck in the canceling check-in stage? For that matter, what will happen to the project in VS, while in this stage?
Just as Daniel said "Nothing bad will happen if you kill Visual Studio".
Generally the pending changes would not be checked into tfs and they would be preserved in your local workspace after killing the VS. So nothing would happen to the existing project in TFS.
Based on your clarification: Tried to re-open the project in VS. I'll be able to, but the TFS server isn't available. "... defaultcollection is currently unavailable"
Seems the TFS Server is down, just ask the admins to check if there are any services were stopped. Or simply restart the TFS server.
Today we have installed update 3 to our existing TFS 2015.2 server. The offline installation ran for about an hour and completed succesfully. However when trying to reach the portal site, nothing shows up (well a 404 page shows up actually).
When opening the Team Foundation Server Administration Console, it correctly displays the expected product version: 14.102.25423.0 (Tfs2015.Update3). However when I click on 'Application Tier', it displays the text:
This feature has been installed but needs to be configured. Click on
Configure Installed Features to begin initial configuration.
This same text is shown on many other administrative pages. Is this the cause of the portal missing? When I configure these features again, will it not erase our current team projects, history, build definitions and work items?
Are there any better ways to troubleshoot why the portal is missing?
Thanks in advance for any guidance.
Yes, you are right. After the upgrade, the configuration is needed to make sure the normal operation of TFS server. It will not erase your current team projects, history, build definitions and work items. There are just some settings will not effect your Database. Certainly, it's also important to keep good backup habits. After all, we didn't have a foolproof thing in the world.
After you upgrade TFS to 2015, each team project may need to be
configured to use some of the new features in TFS 2015. You don't have
to do this immediately, but those features aren't available in that
team project until they're configured. Depending on the team project,
you'll use some combination of the Configure Features wizard that
appears on the Work page and some manual configuration.
Source Link: Upgrade your deployment to the latest version of TFS
For your situation, there maybe some other error cause it. However, still suggest you to finish the configuration first. If it's still not work, then you can try below ways to narrow down the issue:
Check the Event View in the server to see whether there are some
related info
Check the configuration logs (Team Foundation Server Administration
Console-Logs or browser the folder in the server
C:\ProgramData\Microsoft\Team Foundation\Server Configuration\Logs)
We have upgraded our TFS from 2010 to 2013, and the same time moved the TFS and databases to new servers, with new names.
One of the very few annoying effects (Probably due to moving the TFS to a server with a new name) is that the build controller/agent from the old server is still visible in lists of available build controllers/agents, but is not visible in the admin gui for build configurations and therefore not possible to remove.
Does anyone have had the same experience and furthermore have a solution of how to remove the traces of old (and not used/wanted) build controllers/agents?
Kind regards,
J
Ok.
Sorry, I found the solution myself now after continue searching and yet again scanning through the microsofts documentation! :)
It's possible to disable and delete controllers and agents through the Manage Build Controllers in Visual Studio.
Also described here: http://msdn.microsoft.com/en-us/library/ee330987.aspx
Just make sure there is no builds in progress, but that's ofcourse also possible to handle through Manage Queues in Visual Studio.
We have several of our projects at my company in source control using Visual Studio Team Services (visualstudio.com). For the life of me I can't figure out how to get the workspace on my machine to flip to a Server workspace type. We don't want multiple checkouts and we want to get latest when we edit a file, and server workspaces (as I understand it) are the only way to accomplish this. Is it even possible to use server workspaces with the "cloud" version of TFS/Visual Studio Team Services?
Thanks!
Connect to your server with Visual Studio
Go to Team Explorer
Go to Settings
This part can be a little tricky so I attach a screen shot:
Under "Team Project Collection" go to Source Control
On the new dialog go to the second tab - Workspace Settings
So as you can see it is pretty obscure and I believe it is on purpose. By default the workspaces are of type "local" and these have their benefits. You may want to check out this article to make an informed decision: http://msdn.microsoft.com/en-us/library/bb892960.aspx
I'm trying to set up the siren of shame build monitor, but for some reason can't connect to my TFS.
TFS itself is running on port 8080, and TFSBuild on 9192 - but putting http://build-server:8080 or trying other ports does not work...
(Update 1) I've downloaded the source, and also looked using Wireshark into what is happening when it tries to authenticate. I'm confused, as the code is using standard .net Libraries for TFS - Microsoft.TeamFoundation.dll (v2.0.50727). It seems to be looking for web services that do not exist if I look in IIS on the server - namely POST /TeamFoundation/Administration/v3.0/LocationService.asmx
Is it the case that this is not compatible with TFS 2008 at all, and only TFS 2010 will work?
I downloaded the "Siren of Shame" to have a look.
To connect you need to enter the URL for TFS in the following format
http://tfs-Application-Server:8080/tfs
Note that it attaches to the TFS server not the build server (or build controller).
However having connected to TFS it looks like a pain to configure. It correctly detected all of the Team Project Collections that I have in TFS but when I selected one of the collections it wasn't showing any running builds. So I tried selecting a single Team Project, once again no builds were displayed. Finally I selected a build that I knew was running, only then did it show up in Siren of Shame.
I have thousands of builds and I don't want to have to select each one individually to be able to monitor it. At the very least I want to be able to select a team project and monitor all of the builds in that project with one click
There are a number of alternatives out there. But none of them are great
http://teambuildscreen.codeplex.com/
http://buildmonitor.codeplex.com/
http://tfsbuildinspector.codeplex.com/