From the Microsoft KB article:
“After you upgrade to Microsoft SQL Server 2014, you notice a decrease in performance in Microsoft Team Foundation Server (TFS) 2013 Update 2.”
“These issues occur because the hardware requirements for SQL Server 2014 are greater than those for ealier versions of SQL Server. “
What is the Test Attachment Cleaner?
A command line tool that only removes the attachments. It does not touch the test runs, which contain the pass/fail data. So, running Test Attachment Cleaner will not impact the record of the test runs.
You need to Test Attachment Cleaner if you:
- Do manual test runs and want to delete attachments without deleting the test runs
- Do automated test runs and want to delete attachment for builds which have been deleted already, but the build definition’s retention policy was not set to delete “test results” (because this is turned off by default)
You do not need the Test Attachment Cleaner if you:
- Have automated test runs triggered by a build, and you have configured the build definition’s retention policy to delete “test results” (which is not set by default)
- Delete the Test Runs manually (as this deletes the attachments)
Where do I get it from?
The Test Attachment Cleaner is available as part of the TFS Power Tools:
(Thanks Ravi Shenker from Microsoft for the input!)
After performing an in-place upgrade to TFS 2013, you might want to clean up the old TFS folder:
On the TFS application, if you try to access TFS using its FQDN you receive a “Not authorized” or “Unauthorized” error.
How to fix
Try disabling the authentication loopback check as described in KB 887993 (there are two methods, where setting BackConnectionHostNames is the preferred one).
There are three places where you might want to configure SMTP settings:
- On TFS itself via » TFS Admin Console » Email Alert Settings:
- SQL Server Reporting Services (SSRS) via » Reporting Services Configuration Manager: http://technet.microsoft.com/en-us/library/ms345234.aspx
- SharePoint (SP) via » Central Admin » System Settings » Outgoing e-mail settings:
Here are some screenshots:
TFS Admin Console:
Reporting Services Configuration Manager:
SharePoint Central Administration:
As a MSDN subscriber, the product key for Team Foundation Server 2012 does appears under the “Visual Studio 2012” section of “My Product Keys”:
See also: http://msdn.microsoft.com/en-us/library/cc668758(v=vs.110).aspx
Q: Why is the backlog view missing in TFS 2012 Web Access?
A: In TFS 2012, web access permissions control what Web Access features are available to users. By default users get “Standard” permissions.
Here’s how to fix it: http://blogs.msdn.com/b/visualstudioalm/archive/2012/06/04/enabling-feedback-requests-the-backlog-and-sprint-planning-in-team-foundation-server-2012.aspx
Note: Make sure that all users with “Full” permission have either Visual Studio Premium, Ultimate or Test Professional (more info can be found here).
Answer: It’s not supported, and thus not recommended.
If you want to use SQL Server 2012 consider upgrading to TFS 2012, which fully supports it.
- You are configuring SMTP Settings for TFS 2010 and want to specify a different port for your SMTP server than the default port (which would be port 25)
Figure: TFS 2010 does not allow to set a custom SMTP port.
Solution #1: Change config file
- As answered here and here, you could add the following XML to the TfsJobAgent.exe.config file (usually located in C:\Program Files\Microsoft Team Foundation Server 2010\Application Tier\TFSJobAgent):
- Keep in mind that this is only valid for TFS notifications itself and not for notifcations from SQL Server Reporting Services or the SharePoint-based Project Portal.
The Solution #2: Install a local SMTP server
- Install the SMTP Service on Windows Server and ask it to route all SMTP traffic to a different SMTP server.
- On the Delivery tab, click Advanced, an enter the SMTP server name as "smart host".
- On the Delivery tab, click Outbound Connections, and set the TCP port (= SMTP port).
Figure: Setting up a local SMTP server has the great benefit that you can use it SMTP for other applications, too (like notifications from SQL Server Reporting Services or SharePoint).
Cross-posted from my other blog:
- You have a database (e.g. TFS collection database) in SQL Server Enterprise Edition.
- You want to backup and restore this database on a SQL Server Standard Edition.
- You get an error message on restore that some features are not supported.
[Read the full post]