Visual Studio 2013
- TF14083: The item '{0}' has a pending merge from the current merge operation, please resolve and check in the current merge ...
- TF14091: You cannot perform this operation on workspace {0} because you are not the owner of the workspace, or because you ...
- TF14092: The item {0} cannot be changed. There is either an existing pending delete or the current operation is trying to ...
- TF14099: One of the items you are trying to shelve has a pending merge conflict. The conflict must be resolved before shelving. ...
- TF14100: Unable to shelve the pending changes requested because the set of pending renames requested does not include a dependent ...
- TF14107: The checkin could not be completed. The rename of {0} caused a namespace conflict with item {1} being changed by ...
- TF14115: You can not branch from a workspace version spec {0} when the workspace contains a pending delete {1} underneath ...
- TF14116: You can not merge to a workspace version spec {0} when the workspace contains a pending delete {1} underneath the ...
- TF14117: You can not merge {0} when the end of the version range is a label {1} and the item does not exist in the label. ...
- TF14118: Warning: The source item {0} has been renamed. The rename cannot be merged because the new name of the target item ...
- TF14123: Cannot pend a change to '{0}' because the version you have locally has had its content destroyed. Please use get ...
- TF14124: Cannot merge/unshelve '{0}' because someone destroyed this item while the merge/unshelve operation was underway. ...
- TF14124: The content for changeset {0} of the file '{1}' was destroyed. Please try again using a later version of this item. ...
- TF14125: Cannot branch from '{0}' because the version you are branching from has had its content destroyed. Please branch ...
- TF14131: Unable to unshelve the pending changes requested because the set of pending renames requested does not include a ...
- TF14445: The user {0} has been deleted on the server - due to a new user with the same user name being created in your domain. ...
- TF14446: Cannot check out '{0}' for edit. Your client or the team project is configured to use "Get Latest on Check Out" ...
- TF14447: Cannot check out '{0}' for edit. Your client or the team project is configured to use "Get Latest on Check Out" ...
- TF15003: The cache root specified in the fileCacheRoot configuration value must be an absolute (rooted) path. File caching ...
- TF15027: The value provided for the "{0}" configuration node is invalid. The value should be in the range from {1} to {2}. ...
- TF15030: The configuration file was missing the server Uri node. Expected a node such as https://sourceControlServer:1234/SourceControl ...
- TF15040: The statistics file has been tampered. TotalDownloadRequests cannot be less than TotalCacheHits. CacheHit and TotalDownloadRequests ...
- TF15044: Unable to connect to this Team Foundation Proxy Server: {0}. Possible reasons for failure include: - The Team Foundation ...
- TF15044: Unable to connect to this Team Foundation Proxy Server: {0}. Possible reasons for failure include: - The Team Foundation ...
- TF200041: You have specified a name, {0}, that contains character(s) that are not recognized. Specify a name that only contains ...
- TF200051: Two URLs are required. You must provide a URL for Report Manager and a URL for the Reporting Services Web service. ...
- TF20009: The value for field '{0}' is not supported. Specify the value as a whole number between -2147483648 to 2147483647. ...
- TF20033: You do not have permission to modify work items in the area '{0}'. Contact your Team Foundation System administrator. ...
- TF20034: The area does not exist or you do not have permission to save work items in this area. Change the value for field ...
- TF201014: The link type {0} has been deleted. You cannot activate, deactivate, or delete a link type that has already been ...
- TF201015: {0} is not a supported link type name. See http://go.microsoft.com/fwlink/?LinkID=72977 for link type name restrictions. ...
- TF201016: {0} is not a valid link type reference name. See http://go.microsoft.com/fwlink/?LinkID=72977 for link type reference ...
- TF201017: You don't have permissions to complete the operation. To create, modify or delete link types, you must have the ...
- TF201021: The topology is not supported. See http://go.microsoft.com/fwlink/?LinkId=74075 for the supported link type topologies. ...
- TF201022: The reverse name is not specified or is not supported. See http://go.microsoft.com/fwlink/?LinkID=72977 for link ...
- TF201029: The link type cannot be deleted. See http://go.microsoft.com/fwlink/?LinkId=74121 for more information on deleting ...
- TF201031: {0} is not a valid type of link. Check the spelling and capitalization. If you're not sure, use witadmin.exe to ...
- TF201032: The {0} link between work items {1} and {2} that you are attempting to delete does not exist. It may have been ...
- TF201035: Adding a {0} link between work items {1} and {2} would result in a circular relationship. To create this link, ...
- TF201038: Linked item does not exist or access is denied. See Work Item Permissions for Links (http://go.microsoft.com/fwlink/?LinkId=75624) ...
- TF201040: The 'LinkColumn' element requires the 'LinkAttribute' or the 'RefName' attribute, but not both. Specify either ...
- TF201044: The link type filter '{0}' specifies a link type that does not exist on the Team Foundation Server. Specify a valid ...
- TF201045: The link attribute '{0}' is not a supported link column. Specify one of the valid link column types, {1}, {2}, ...
- TF201046: {0} is not a valid link type reference name. User defined reference names may not begin with 'System.'. See ht ...
- TF201047: The {0} links control element is not supported. When the {1} attribute is {2}, that element cannot contain elements. ...
- TF201048: The links control filter contains an element for link type {0} that is not supported. That link type is not directed, ...
- TF201051: {0} is not a valid link type reference name. See http://go.microsoft.com/fwlink/?LinkId=80887 for more information ...
- TF201052: {0} is not a valid link type name. See http://go.microsoft.com/fwlink/?LinkId=80887 for more information about ...
- TF201060: The query on links element {0} is not valid. Use LeftQuery for the main query, LinkQuery for the link query, and ...
- TF201063: Adding a {0} link to work item {1} would result in a circular relationship. To create this link, evaluate the existing ...
- TF201067: You do not have permission to modify the work item type or field. You must have permission to modify work item ...
- TF201067: You do not have permission to modify the work item type or field. You must have permission to modify work item ...
- TF201068: The work item metadata cache is out of date. Refresh any cached work item metadata and try the operation again. ...
- TF201068: You do not have permission to modify the work item type or field. You must have permission to modify work item ...
- TF201069: The work item metadata cache is out of date. Close Visual Studio, delete the cache folder {0}, and then try again. ...
- TF201072: A user or group could not be found. Verify that the users and groups used in your work item type definition have ...
- TF201074: The {0} link between work items {1} and {2} that you are attempting to modify does not exist. It may have been ...
- TF201075: You cannot create a new field using an existing name. Your work item metadata cache may be out of date. Close Visual ...
- TF201075: You cannot create a new field using an existing name. Your work item metadata cache may be out of date. Refresh ...
- TF201076: You cannot create a new field using an existing reference name. Your work item metadata cache may be out of date. ...
- TF201076: You cannot create a new field using an existing reference name. Your work item metadata cache may be out of date. ...
- TF201078: You are trying to import a type of work item that uses the field '{0}'. Your definition of the field includes a ...
- TF203003: You cannot specify a wildcard character for this working folder. The only wildcard character allowed is an '*' ...
- TF203004: The administrator has set a limit of {0} rows for this operation. Verify the parameters of your operation and try ...
- TF203005: The database does not contain any changesets. The most common cause for this error is database corruption caused ...
- TF203006: Cannot shelve {0}. The item exists in a deleted folder that has a pending undelete change. Include the root folder ...
- TF203007: Cannot create the label because the version controlled item {0} already exists or has been specified more than ...
- TF203013: The path {0} is in the DOS (8.3) short path format and is not supported. Enter a full path to the item and try ...
- TF203018: You cannot roll back item {0} because the file contents of the version to which you are rolling back has been destroyed. ...
- TF203021: You cannot simultaneously pend a delete and an edit on item {0} because you have a later version of the item in ...
- TF203022: You cannot provide a workspace or label as the beginning range of a version spec without specifying the /toversion ...
- TF203028: You cannot create a branch at {0} because a branch already exists at {1}. If {1} is not a branch convert it back ...
- TF203029: You cannot update the branch parent to {0} because it is already a child of the branch you are trying to update. ...
- TF203031: You cannot set the branch parent to {0}, because it will cause the branch-nesting to exceed the maximum value of ...
- TF203032: You cannot update the branch parent to {0} because no merge relationship exists between the current branch and ...