Visual Studio 2013
- TF208078: The following filter will not be added to the PivotTable and PivotChart reports. The filter is part of an OR expression ...
- TF208079: The following filter will not be added to the PivotTable and PivotChart reports. The filter is part of an AND expression ...
- TF208080: The following filter will not be added to the PivotTable and PivotChart reports. The Field Comparison operator ...
- TF208081: The '{0}' field will not be used to create PivotTable and PivotChart Current Reports because it is not related ...
- TF208082: Unable to update reporting metadata of the following work item list: {0}. To update the metadata, you must be able ...
- TF208083: This computer has been configured for a new locale by using the Regional and Language Options item in Control Panel. ...
- TF208084: Office Excel cannot refresh a worksheet in which a Date filter applies to a column. Click OK to refresh the worksheet ...
- TF208086: You cannot indent a work item that is already a subtask of the work item above it. The work item in row {0} was ...
- TF208089: You cannot indent the first work item in the list. The first work item defines the root of the hierarchical tree. ...
- TF208092: You cannot use work item queries to generate reports in Excel on this server. To use this feature, the server must ...
- TF208093: You cannot use work item queries to generate reports in Excel on this server because it is not configured for reporting. ...
- TF208094: Project Portal cannot be launched. Determine if a portal is associated with the team project that the document ...
- TF208096: It appears the Microsoft Excel section is in edit mode. Edit mode is activated when you use in-cell editing or ...
- TF208097: This report will not be created because the progress dialog could not be launched. Close Microsoft Excel and try ...
- TF208098: Office Excel is unable to access the Analysis Services database {0} on server {1}. Try the operation again at a ...
- TF208099: You cannot add a report that requires different connection properties than are defined for the current workbook. ...
- TF208101: You cannot access the Analysis Services database because you have specified alternative credentials and you do ...
- TF208102: You have performed an Excel sort on a tree list. This action removed the modified or newly introduced hierarchical ...
- TF208103: The initialization of the document to connect to Team Foundation Server was not successful. The document will close. ...
- TF209009: The account {1} is not authorized to communicate with Team Foundation Server {0}. Verify that the account is a ...
- TF209010: The build number {0} contains invalid character(s) or is too long. The maximum length of a build number is 64 characters. ...
- TF209010: The build number {0} contains invalid character(s) or is too long. The maximum length of a build number is 64 characters. ...
- TF209012: Access denied. You need the {0} permission in {1} to create a build definition. For more information, contact your ...
- TF209014: Failed to retrieve data from the server. Verify the network connection and try again. The network error is: {0}. ...
- TF209015: Failed to retrieve data from the server. Verify that Team Foundation server is accessible via the network and try ...
- TF209016: Access denied. You are not authorized to perform this action. For more information, contact the Team Foundation ...
- TF209022: Access denied. You need the {0} permission to perform this action. For more information, contact your Team Foundation ...
- TF209023: Either source control has not been configured for this team project or you do not have permission to access it. ...
- TF209024: Unexpected failure on the build agent computer: unable to queue ThreadPool request. Restarting the computer may ...
- TF209025: The build process is unable to set the permissions on the drop directory {0} (Detail Message: {1}). Make sure that ...
- 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 ...