Solution:

SELECT a.ControllerId "Controller ID", a.DisplayName "Controller Name" , a.Status "Controller Status(1 - Active)",

b.AgentId "Agent ID", b.DisplayName "Agent Name", b.Status  "Agent Status(1 - Active)" FROM tbl_BuildController a , tbl_BuildAgent b where a.ControllerId = b.ControllerId

Explanation:

You are opening a solution made in Visual Studio 2010 with VS 2012.  When you run Code Analysis you get a series of CA0053 errors, saying it is unable to load the rule sets from the Visual Studio 2010 directory

In the Error window you get an error message saying “Code Analysis detected errors.” And in the Code Analysis window you will get the “CA0053 Error running code analysis” with its “Unable to load rule assembly”.

This means the project is bound to Visual Studio 2010, where it should have been Visual Studio version independent. The absolute path to the Visual Studio 10 binaries is what causes the problem.

What has happened was that this certain VS2010 specific information was “inadvertently” introduced in SP1, and it has not been fixed in any later update. It does NOT happen if you run in Debug|x86 or Release|x86, but any other configuration you have added will give you this error.

Solution:

Tool to fix the errors available at http://visualstudiogallery.msdn.microsoft.com/471da13b-d415-4a44-a4e9-a8222316b902

Explanation:

w3wp.exe an Internet Information Services (IIS) worker process is a windows process which runs Web applications, and is responsible for handling requests sent to a Web Server for a specific application pool. W3wp.exe process will not be started automatically after App tier reboot or IIS restart or application pool restart. w3wp.exe will be launched once the first request is made to the TFS Application.

Solution:

1. Try accessing TFS application once http://tfs:8080/tfs. See whether the w3wp.exe is available in "Windows Task Manager" --> "Processes Tab"

2. You can configure Worker process started automatically by adding startMode attribute to TFS application pool to AlwaysRunning in your applicationHost.config

<applicationPools>

   <add name="Default App Pool" startMode="AlwaysRunning" />

</applicationPools>

Solution 2 will work for IIS 7.5 or newer

Explanation:

Host Dormancy is a feature built-in to the 'kernel' of TFS that will pause jobs from running if a collection hasn't been accessed in a period of time. If a collection isn't being accessed, that means that the data isn't changing, so there's no need to run some jobs. This is key functionality that allows the Team Foundation Service to scale to thousands of collections.

Todeleteorphanworkspaces.sql (2.93 kb)

To delete orphan workspaces.sql (2.93 kb)

Explanation:

Deleting a team project through tfsdeleteproject command will result making the associated workspaces and shelvesets as orphan records in TFS collection database. The collection database size may not reduce as expected even after team project delete. 

tfsdeleteproject /force /q /excludewss /collection:"<Collection Name>" "<Project Name>"

Solution:

The attached script finds and deletes the workspaces\shelvesets that only have workspace\shelvesets mappings for projects that no longer exist and delete them. 

Please backup the collection database before you execute the script.

This script require TFS 2012 update 2 or newer

To delete orphan workspaces.sql (2.93 kb)

To delete orphan shelvesets.sql (2.58 kb)