Solution

TFS rollback is a client side component which is available in TFS 2010 power tools install. http://visualstudiogallery.msdn.microsoft.com/c255a1e4-04ba-4f68-8f4e-cd473d6b971f

1) Through UI

Right click on the source folder
Select View History menu 

 Select rollback entire changeset menu 

 Check-in the pending rollback changes 

2) Through Command line :
 
tf rollback /changeset:changesetfrom~changesetto [itemspec] [/recursive]
[/lock:none|checkin|checkout] [/version:versionspec]
[/keepmergehistory] [/noprompt] [/login:username,[password]]

tf rollback /toversion:versionspec itemspec [/recursive]
[/lock:none|checkin|checkout] [/version:versionspec]
[/keepmergehistory] [/noprompt] [/login:username,[password]]

Note :If you are attempting to rollback changes for another user, make sure you get latest on the files you are attempting to rollback; otherwise you will see the error: "No changes to roll back."

Explanation:

TFS2012 server process the build request but the build controller fails.

Workaround:

Reimaged the build controller,Since the controller was not responding to any command and also TFS admin console crashed.

Error:

The values provided for the root activity's arguments did not satisfy the root activity's requirements: ''Build Parameter':
The following keys from the input dictionary do not map to arguments and must be removed: <Parameter Name>. 
Please note that argument names are case sensitive. Parameter name: rootArgumentValues

Explanation:

The error appears when the build parameter is removed from the template template and still avaiable in the build tables.

The table tbl_BuildDefinition contains all information for a build definition. ProcessParameters column will contains the build parameter details

Solution:

Refresh the build definition and save it. In the process tab, there is a Refresh button that will reload the build definition and the process template and synchronize them

ERROR

"Run On Agent (reserved build agent <Agent1>). There was no endpoint listening at <TFS url> that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.Cannot stop the build. Details: Operation did not complete in 00:01:00. (After trying to stop the build) TF215104: Failed to stop build 23649: it did not respond to a workflow cancellation request."

Solution

1) Identify and Remove the queued builds data from dbo.tbl_BuildQueue table in the Tfs_CollectionName database.

select * from dbo.tbl_BuildQueue
delete from dbo.tbl_BuildQueue where QueueID = 'ID'

2) Remove the build agent from the controller

Identify the build agent and note the value of ReservationId and AgentId.
SELECT * FROM tbl_BuildAgent

DELETE FROM tbl_BuildAgentReservation WHERE ReservationId = [ReservationId]
UPDATE tbl_BuildAgent SET ReservationId = NULL WHERE AgentId = [AgentId].

Remove the Build Agent from TFS Admin Console.

Explanation
The users should have project level permission to label any folders and files in version control using visual studio IDE. The error occurs when team project does not have project users/groups permissions set at project level but its set on folders.

Solution
Add the users/groups permission at project level.