Upgrade to TFS 2015.3 successful, but portal unavailable - tfs

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)

Related

Issues with TFS Aggregator implementation

We used TFS Aggregator to automatic update the User Story's state according to its sons state changes and also to automatic Update User Story's state of other project (if they are related).
Also important to mention that we hire an external freelance to help us doing it. When we tested it on his environment - it worked well. But when deploy it in
our environment - there's no change, the new functionality doesn't work.
what you recommend us to check ?
what can be the reasons for this integration problem?
What actions should we take?
Your advises are more than welcome!
First, try to follow the steps of installation on this website to install the plugin: https://github.com/tfsaggregator/tfsaggregator/wiki/Install
If it still doesn't work. Here is the troubleshooting page you can refer to: TFS Aggregator Troubleshooting:
You are using the right version of this server side plugin for the
right server. You can get multiple releases of this plugin at website
https://github.com/tfsaggregator/tfsaggregator
You have updated a work item that triggers a rule. (The TFS
Aggregation only works once a work item that has aggregation rules on
it is updated. This may change in a future version.)
If the rule navigates between work items, work items have a proper
Link (e.g. Parent-Child).
You copied the DLLs and the Policies file to the plugins location on
all TFS Application Tier Servers (Usually at: :\Program
Files\Microsoft Team Foundation Server {version}\Application Tier\Web
Services\bin\Plugins)
You have valid names for source and destination fields in
TFSAggregator2.ServerPlugin.policies.
When you saved the file you saved it as UTF-8 encoding (in Notepad++
it is called “utf-8 without BOM”).
You have given permission to the user running the plugin, e.g. add
the "TFS Service Account" to the Project Collection Administrators
TFS Group.
You may have to do this from the commandline using tfssecurity
/collection:http://server:8080/tfs/DefaultCollection /g+ "Project
Collection administrators" "LOCAL SERVICE" if your service account is
either LocalService, NetworkService or any other Windows Well-known
identity, since they are no longer shown in the permission UI.
When using the Impersonation option, make sure the user executing the
plugin (generally the TFS Service account) has the "Make requests on
behalf of others" permission at the server level
If you upgraded your TFS from 2013.x to 2015.* and from 2015rtm to
2015.1 and did not uninstall the TFS Aggregator before doing this TFS upgrade the aggregator does not work. Remove the TFS Aggregator from
the TFS 2013 Program Files folder or run the uninstall of the TFS
Aggegrator (backup your policies!). Then re-install the TFS
Aggegrator setup or install manually for TFS 2015 as described here.
Every TFS version has its "own" assembly for the aggregator so it is
important to use the right version against the right TFS.

Enterprise Architect cannot check in package to TFS

I am trying out Enterprise Architect integration with Team Foundation Server using EA trial version. I was able to create a model with several sub packages using DBMS based and TFS 2013 as a version control system. I was able to check out a package successfully from TFS via EA. However I could not check in that same package, EA keeps showing me the error message:
You cannot check-in package ‘blahblah’.
The associated file ‘blahblah.xml’ is not currently checked-out by you.
I double checked the xml file from TFS Source Control via Visual Studio, it showed that the xml file was “lock, edit” under my same credentials that was used in EA Version control settings.
Interestingly, I was able to Undo check out successfully.
Any help is appreciated.
I remember having this issue at work a couple of months ago. I don't have access to Enterprise Architect at the moment, nor am I in a position to recreate the problem to verify this solution, but I do remember how our team solved it:
The missing assumption to solving this, which may or may not be true in your case, is that your team went from the standard authentication method in the TFS settings, to SCC(or possibly the other way around). Now, assuming your credentials are the same in either method, you won't get an issue in Visual Studio, and can do everything apart from checking in in Enterprise Architect until you update your TFS settings in Enterprise Architect. Heck, everything will seem correct everywhere as your files IS checked out to you (no idea why this is permitted) but you cannot check in through the standard authentication method.
I had the same problem which I was able to solve only by resynchronizing the status with the version control.
Right click on Model, click on "Package Control", click on "Re-sync status with VC provider".

TFS 2013: Remove obsolete build controllers/agents not visible in admin

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.

Siren of shame build monitor, unable to connect to TFS 2008 or TFS 2012

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/

team foundation server (TFS) in the cloud not able to delete / adjust mapping

I tried out the TFS Service with a project of mine. After I experienced some problems (probably misuse) I used VSUnbindSourceControl.exe (see: http://vsunbindsourcecc.codeplex.com/) to detach the project (locally) from the TFS, but it looks as if on the server side, the project that was uploaded, is still bound to my computer.
See image:
and the error message in the output window:
Failed To Create Mapping
The working folder G:\Quant tool DotNet4 is already in use by the workspace USER-PC;myemail# somedomain dot com on computer USER-PC.
(I now use a different email address than the one above)
I've tried to delete the project from the server via the Source Control Explorer in VS, but the delete option is disabled. (also when I login with mldz at hotmail dot com.
I was also not able to delete the project or change it's settings via the TFS web interface.
Anyone experience with this problem and how to solve it with the new TFS in the cloud? i saw some similar problems with a normal TFS and some solutions could be done via the the team foundation administration tool, but that cannot be applied to the TFS in the cloud (AFAIK)
Some info about trying to install TFS integration tool
Hi,
I use VS2012 express and although I installed vs_teamexplorer.exe,
I'm not able to install Microsoft Team Foundation Server Integration Tool.
Already restarted the computer after installation and tried again. Doesn't work. Missing something?
regards,
Matthijs
You can use the same admin tools for tfs.visualstudio. See examples. At end of http://msdn.microsoft.com/en-us/magazine/jj130558.aspx article which show deletion of workspaces, for example.

Resources