Visual Studio 2012
- TF209027: Failed to locate all the required Team Foundation Build components. Reinstalling the Team Foundation Build application ...
- TF209029: The agent name {0} contains characters that you cannot use. Characters that you cannot use include ' ', '|', '*', ...
- TF209035: The build definition name {0} is not valid. Build definition names cannot end in the following characters: ' ', ...
- TF209038: The build number '{0}' ends with a character which is not allowed. Characters which are not allowed include '.' ...
- TF209039: The build process template for the build definition does not support the reason {0} for which this build was queued. ...
- TF209041: The controller name {0} contains characters that you cannot use. Characters that you cannot use include ' ', '|', ...
- TF209044: The build controller name {0} is not valid. Build controller names cannot end in the following characters: ' ', ...
- TF209045: The build service host name {0} contains characters that you cannot use. Characters that you cannot use include ...
- TF209046: The build service host name {0} is too long. The maximum length of a build service host name is {1} characters. ...
- TF209048: The build service host name {0} is not valid. Build service host names cannot end in the following characters: ...
- TF209057: You cannot perform the "Start Now" action on queued build {0} because its build definition ({1}) is not paused ...
- TF209058: You cannot perform the "Start Now" action on queued build {0} because its build controller ({1}) is disabled or ...
- TF209059: You cannot perform the "Start Now" action on queued build {0} because its build controller ({1}) is already running ...
- TF209059: You cannot perform the "Start Now" action on queued build {0} because its build controller ({1}) is running its ...
- TF210000: {0} is not a valid value. Verify that the group exists on the specified Team Foundation Server and then run the ...
- TF210002: The link control filter is defined so that no link types can be added. Have your work item form designer check ...
- TF210005: Your display name from Active Directory cannot be used to subscribe for work item events. It contains both and ...
- TF210006: You cannot add a link to this work item. Either restrictions apply for adding links to this type of work item or ...
- TF210007: A GROUP element that contains SPLITTER and COLUMN elements must specify exactly three COLUMN elements in the following ...
- TF212000: {0} is not a valid argument for this command. Type '{1} {2} /?' or '{1} help {2}' and press Enter for more information. ...
- TF212010: {0} is not a valid formula. For more information about how to use fields for reporting, see http://go.microsoft.com/fwlink/?LinkId=78060. ...
- TF212014: {0} is a system field and cannot be removed. For more information about system fields, see http://go.microsoft.com/fwlink/?LinkId=78061. ...
- TF212016: {0} is not a valid reporting type. For more information about how to use fields for reporting, see http://go.m ...
- TF212021: You cannot index field '{0}' because it is not one of the following types: String, Integer, Double, DateTime, Boolean, ...
- TF212022: You cannot specify '{0}' in a query that returns revisions of work items because that field is a computed field. ...
- TF212024: To find work items by comparing fields of linked work items, you can only specify fields that belong to the same ...
- TF212025: You cannot compare long text, HTML, or history fields to other fields in the WHERE clause of a work item query. ...
- TF212056: You cannot delete the work item field, {0}, because it is used in the global workflow for the team project collection. ...
- TF214001: An error was encountered while Team Foundation server was retrieving the build definition {1} for team project ...
- TF214007: No build was found with the URI {0}. Either the URI does not exist, or {1} does not have permission to access it. ...
- TF214008: No build definition was found with the URI {0}. Either the URI does not exist, or {1} does not have permission ...
- TF214009: No build agent was found with the URI {0}. Either the URI does not exist, or {1} does not have permission to access ...
- TF214010: More than one build was found with build number {0} and build definition {1}. Only one build was expected. Specify ...
- TF214011: More than one build definition named {1} was found for team project {0}. Specify a build definition without a wildcard ...
- TF214020: There is already a weekly schedule associated with the build definition {0}. You cannot specify more than one weekly ...
- TF214023: No build controller was found with the URI {0}. Either the URI does not exist, or {1} does not have permission ...
- TF214025: No build service host was found with the URI {0}. Either the URI does not exist, or {1} does not have permission ...
- TF214028: The type '{0}' in assembly '{1}' could not be instantiated. Classes marked with the BuildExtensionAttribute must ...
- TF214029: The Team Foundation Server you are connected to does not support deleting specific parts of a build (DeleteOptions: ...
- TF214030: The build '{0}' does not have a completed status. The current status is {1}. Completed statuses include {2}, {3}, ...
- TF215002: Access denied. {0} needs {1} permissions for team project {2} to perform the action. For more information, contact ...
- TF215032: Build definition {0} cannot be deleted because builds still exist for this definition. Delete all completed builds ...
- TF215033: Build definition {0} cannot be deleted because builds still exist for this definition. Ensure the queue for this ...
- TF215035: Queued build {0} on build controller {2} can only be updated if the status is either Postponed or Queued. The current ...
- TF215036: The build request cannot be queued at or below position {1} on build controller {0}. The resulting position would ...
- TF215067: Cannot cancel queued build {0} on build controller {2}. The current status is {1} and queued builds can only be ...
- TF215068: Failed to restart the code coverage analysis service on the Team Foundation Server while deleting the test run. ...
- TF215075: The definition name {0} contains characters that you cannot use. Characters that you cannot use include ' ', '|', ...
- TF215080: Failed to upgrade one or more build types to build definitions in changeset {0}. You must modify each build type's ...
- TF215084: The date {0} is not in a valid range and will be truncated. The valid range for dates is January 1, 1753, at 00:00:00 ...
- TF215094: The key for issuing gated check-in tickets could not be created. Submitting gated check-ins will require the user ...
- TF215104: Failed to stop build {0} because the build machine did not respond to a stop request within {1}. If the build machine ...
- TF215106: Access denied. {0} needs {1} permissions for build definition {2} in team project {3} to perform the action. For ...
- TF216001: More than one build agent matched the user input. Only one build agent may be updated when using the {0} option. ...
- TF216010: The command {0} was not recognized. At the command prompt, type 'TfsBuild.exe Help' to get a list of available ...
- TF218000: Project creation failed. The New Team Project Wizard was unable to access the Site Service Web Service (Sites.asmx) ...
- TF218001: Project creation failed. The New Team Project Wizard was unable to access the Site Service Web Service (Sites.asmx) ...
- TF218002: Project creation failed. The New Team Project Wizard could not access the Site Service Web Service (Sites.asmx) ...
- TF218003: Unable to create the SharePoint site to be used as the team project portal. The team project will not be created. ...
- TF218007: Cannot import the work item type. It changes fields in team projects in which you do not have permissions to make ...
- TF218007: The {0} plug-in is defined more than once in this process template. To correct this problem, download the process ...
- TF218008: A feature for SharePoint Products could not be activated for the team project site. The feature ID is :"{0}". The ...
- TF218009: The XML in the process template is malformed. Team Foundation Server does not support the permission class '{0}'. ...
- TF218012: A server running SharePoint Products has been found, but a SharePoint site could not be created to act as the team ...
- TF218013: SQL Server Reporting Services is installed on this computer, but the team project could not be created because ...
- TF218014: The project was created, but the following plug-in did not run successfully: {0}. The following error occurred: ...
- TF218015: An error occurred after the SharePoint site was created. A document library could not be found with the following ...
- TF218015: An error occurred while attempting to retrieve the SID for the application group or account: '{0}'. Contact the ...
- TF218016: The Area or Iteration path '{0}' specified in the process template GroupsandPermissions.xml file is not valid. ...
- TF218016: The team project could not be created because there was an error with the following SharePoint Web application: ...
- TF218018: The XML in the process template is malformed. A problem exists with the following permission class: {0}. The permission ...
- TF218020: The following team project could not be found: {0}. The project is a member of the following team project collection: ...
- TF218023: A report folder already exists and has items for the following team project: {0}. SQL Server Reporting Services ...
- TF218026: Adding features to an existing project is not supported. The following element in the XML file is not supported: ...
- TF218027: The following reporting folder could not be created on the server that is running SQL Server Reporting Services: ...