Visual Studio 2013

  1. TF233004: You must install Office Primary Interop Assemblies (PIA) in order for Team Foundation Server to validate the Office ...
  2. TF234000: Work item field {0} is mapped to the wrong field type in Microsoft Project. You can map work item fields of type ...
  3. TF234001: Work item field {0} is mapped to the wrong field type in Microsoft Project. You can map work item fields of type ...
  4. TF234002: Work item field {0} is mapped to the wrong field type in Microsoft Project. You can map work item fields of type ...
  5. TF234003: Work item field {0} is mapped to the wrong field type in Microsoft Project. You cannot map work item fields of ...
  6. TF234004: Project units were not specified for Microsoft Project field {0}. Specify project units by using the ProjectUnits ...
  7. TF234005: Project units were specified for Microsoft Project field {0}. This work item field is mapped to a Microsoft Project ...
  8. TF234014: Cannot open this file because it is bound to a work item query. Binding a Microsoft Project file to a work item ...
  9. TF234015: The following link types could not be mapped because the type of link does not exist or the link is the wrong type: ...
  10. TF234017: The following column could not be used as the reserved field. It is either not a numeric column or is already mapped ...
  11. TF234018: You cannot change the value of a read-only field. If you modified the field within the Task Information dialog ...
  12. TF234019: Cannot open the project file. There are work items with field values that conflict with the list separator. From ...
  13. TF234020: There are work items with field values that conflict with the list separator. From Control Panel, change the list ...
  14. TF234021: The URL that you have specified is not valid for Office Project Server. Specify a valid URL for Office Project ...
  15. TF234023: An error occurred while retrieving custom field metadata. Verify that the PWA instance is correctly configured. ...
  16. TF234025: You cannot publish the project because the {0} custom field value for the selected task is not consistent with ...
  17. TF234026: Work item field {0} is mapped to an incompatible type of field in Microsoft Office Project. All work item fields ...
  18. TF234027: Work item field {0} is mapped to an incompatible type of field in Microsoft Office Project. All work item fields ...
  19. TF234028: The following work item fields are no longer valid: {0} Close your project plan and have your project administrator ...
  20. TF234029: The PublishOnly attribute is not defined for the Microsoft Project field {0}. You must set the attribute to 'true' ...
  21. TF234030: An invalid value is set for the PublishOnly attribute for the Microsoft Project field {0}. You must set the attribute ...
  22. TF234031: One or more work items that were imported to the project plan are missing data because a list separator value appears ...
  23. TF234035: You cannot publish your enterprise project plan as it is mapped to a team project on the following Team Foundation ...
  24. TF234036: You have modified one or more hierarchical link relationships that may have been locked by other processes, such ...
  25. TF237000: This file was created by a newer version of Team Explorer. Saving this file might result in loss of data and make ...
  26. TF237005: You cannot create a query folder with this version of Team Foundation Server. Upgrade to a newer version of Team ...
  27. TF237006: The destination folder {0} already contains a query or a query folder named {1}. You cannot add an item with the ...
  28. TF237007: You cannot create a query item (a query or a query folder) without a name. Use a valid name when you create an ...
  29. TF237010: You cannot add a query or a query folder from a folder in a WorkItemStore object to a folder in a different WorkItemStore ...
  30. TF237015: The query or query folder that you referenced either does not exist, or you do not have permissions to access it. ...
  31. TF237018: A query or a query folder on the server has the same name as an item you tried to save. Refresh your query hierarchy. ...
  32. TF237019: You are working with a query hierarchy, but the hierarchy has been changed between now and when you last refreshed. ...
  33. TF237024: The item, query folder or query, is not from the specified team project. Select an item from the current team project. ...
  34. TF237025: The item, query folder or query, and the set of team projects are not all from the same Team Foundation Server. ...
  35. TF237050: {0} is not a valid work item type category name. See http://go.microsoft.com/fwlink/?LinkId=104504 for more information ...
  36. TF237051: {0} is not a valid work item type category reference name. See http://go.microsoft.com/fwlink/?LinkId=104505 for ...
  37. TF237052: The category is missing for InsertWorkItemTypeCategoryMember or UpdateWorkItemTypeCategoryMember. You must include ...
  38. TF237053: The work item type is missing for InsertWorkItemTypeCategoryMember. You must include WorkItemTypeID or TempWorkItemTypeID. ...
  39. TF237054: The category is missing for InsertWorkItemTypeCategory or UpdateWorkItemTypeCategory. You must include CategoryID ...
  40. TF237055: You cannot destroy a work item type that is being used. Verify that the work item type is not being used in any ...
  41. TF237056: You cannot supply a value for the field {0}. The field is read-only, and the value is provided by the Team Foundation ...
  42. TF237057: The string used in the query exceeds the maximum supported length of {1} characters for field {0}. This can be ...
  43. TF237059: The import of the category definition failed. In the type definition, category {0} refers to a work item type that ...
  44. TF237060: The import of the category definition failed. The category {0} type definition refers to work item type {1} more ...
  45. TF237061: The import of the category definition failed. The definition name you are trying to import already contains the ...
  46. TF237061: The import of the category definition failed. The definition name you are trying to import already contains the ...
  47. TF237064: Importing the work item type definition failed. The Control element must specify a Label attribute if a Link element ...
  48. TF237066: Importing the work item type definition failed. The parameter elements specified for the link are fewer than required ...
  49. TF237067: Importing the work item type definition failed. The Url parameter {0} is not a valid field name or a valid macro. ...
  50. TF237068: Importing the work item type definition failed. The definition you are trying to import lists a parameter index ...
  51. TF237069: Importing the work item type definition failed. The definition you are trying to import lists more than one parameter ...
  52. TF237070: Importing the definition failed. The definition you are trying to import did not validate against the schema. Edit ...
  53. TF237076: Importing the work item type definition failed. The definition you are trying to import contains an invalid UrlRoot ...
  54. TF237077:Importing the work item type definition failed. The definition you are trying to import uses unsupported Url protocol ...
  55. TF237078: Importing the definition failed. The definition you are trying to import uses unsupported Url protocol '{0}' for ...
  56. TF237079: Team Foundation could not update the work item because it was already updated by another user, it does not exist, ...
  57. TF237082: The attachment could not be uploaded. Verify that you have a network connection and that Team Foundation Server ...
  58. TF237091: Actual reporting settings for the field {0} are different from those specified in the XML. Changing these settings ...
  59. TF237092: Action '{0}' is defined for more than one transition from state '{1}'. Transitions from every single state must ...
  60. TF237112: Default state cannot be inferred from transitions. Default state is defined by a transition from an empty state, ...
  61. TF237148: The Team Foundation Server work item database can not be opened. It may be offline for system administration. Try ...
  62. TF237165: Team Foundation could not update the work item because of a validation error on the server. This may happen because ...
  63. TF237167: Importing the definition failed. The definition you are trying to import cannot use the attributes AllowScript ...
  64. TF237173: You cannot open the file {0} because it contains a query that is supported by a more recent version of Team Foundation ...
  65. TF237175: The import failed. The work item type filter {0} is specified more than once in the work item type definition. ...
  66. TF237176: The import failed. The work item type definition that you are trying to import contains a links control with an ...
  67. TF237179: The query or query folder that you referenced does not exist on the server. It might have been deleted. Refresh ...
  68. TF237180: You have set permissions that are not recognized query permissions. Change the permissions and try the operation ...
  69. TF237199: You cannot set query or query folder permissions with this version of Team Foundation Server. Upgrade to a newer ...
  70. TF237200: You cannot add a {0} link from work item {1} to work item to {2}. Adding a link between these work items will increase ...
  71. TF238001: The name that you typed contains one or more characters that are not valid, or it contains Unicode control characters. ...
  72. TF239000: Internet Information Services (IIS) has returned a value that is not valid. The value for ServerBinding was null ...
  73. TF239001: An error in the binding type caused report creation to fail. The binding type was not valid: {0}. Bindings must ...
  74. TF239002: The following binding string is not valid: {0}. The binding string must contain three parts, separated by colons. ...
  75. TF24003: The query or query folder name you entered contains characters that are not supported. Correct the name and try ...