Visual Studio 2010

  1. TF208096: It appears the Microsoft Excel section is in edit mode. Edit mode is activated when you use in-cell editing or ...
  2. TF208097: This report will not be created because the progress dialog could not be launched. Close Microsoft Excel and try ...
  3. TF208098: Office Excel is unable to access the Analysis Services database {0} on server {1}. Try the operation again at a ...
  4. TF208099: You cannot add a report that requires different connection properties than are defined for the current workbook. ...
  5. TF208101: You cannot access the Analysis Services database because you have specified alternative credentials and you do ...
  6. TF208102: You have performed an Excel sort on a tree list. This action may remove the hierarchical link relationships of ...
  7. TF208102: You have performed an Excel sort on a tree list. This action removed the modified or newly introduced hierarchical ...
  8. TF208103: The initialization of the workbook to connect to Team Foundation Server was not successful. The workbook will close. ...
  9. TF208104: You have modified one or more hierarchical link relationships that may have been locked by other processes, such ...
  10. TF209009: The account {1} is not authorized to communicate with Team Foundation Server {0}. Verify that the account is a ...
  11. TF209010: The build number {0} contains invalid character(s) or is too long. The maximum length of a build number is 64 characters. ...
  12. TF209012: Access denied. You need the {0} permission in {1} to create a build definition. For more information, contact your ...
  13. TF209014: Failed to retrieve data from the server. Verify the network connection and try again. The network error is: {0}. ...
  14. TF209015: Failed to retrieve data from the server. Verify that Team Foundation server is accessible via the network and try ...
  15. TF209016: Access denied. You are not authorized to perform this action. For more information, contact the Team Foundation ...
  16. TF209022: Access denied. You need the {0} permission to perform this action. For more information, contact your Team Foundation ...
  17. TF209023: Either source control has not been configured for this team project or you do not have permission to access it. ...
  18. TF209024: Unexpected failure on the build agent computer: unable to queue ThreadPool request. Restarting the computer may ...
  19. TF209025: The build process is unable to set the permissions on the drop directory {0} (Detail Message: {1}). Make sure that ...
  20. TF209027: Failed to locate all the required Team Foundation Build components. Reinstalling the Team Foundation Build application ...
  21. TF209029: The agent name {0} contains characters that you cannot use. Characters that you cannot use include ' ', '|', '*', ...
  22. TF209035: The build definition name {0} is not valid. Build definition names cannot end in the following characters: ' ', ...
  23. TF209038: The build number '{0}' ends with a character which is not allowed. Characters which are not allowed include '.' ...
  24. TF209039: The build process template for the build definition does not support the reason {0} for which this build was queued. ...
  25. TF209041: The controller name {0} contains characters that you cannot use. Characters that you cannot use include ' ', '|', ...
  26. TF209044: The build controller name {0} is not valid. Build controller names cannot end in the following characters: ' ', ...
  27. TF209045: The build service host name {0} contains characters that you cannot use. Characters that you cannot use include ...
  28. TF209046: The build service host name {0} is too long. The maximum length of a build service host name is {1} characters. ...
  29. TF209048: The build service host name {0} is not valid. Build service host names cannot end in the following characters: ...
  30. TF210000: {0} is not a valid value. Verify that the group exists on the specified Team Foundation Server and then run the ...
  31. TF210002: The link control filter is defined so that no link types can be added. Have your work item form designer check ...
  32. TF210005: Your display name from Active Directory cannot be used to subscribe for work item events. It contains both and ...
  33. TF210006: You cannot add a link to this work item. Either restrictions apply for adding links to this type of work item or ...
  34. TF210007: A GROUP element that contains SPLITTER and COLUMN elements must specify exactly three COLUMN elements in the following ...
  35. TF212000: {0} is not a valid argument for this command. Type '{1} {2} /?' or '{1} help {2}' and press Enter for more information. ...
  36. 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. ...
  37. TF212014: {0} is a system field and cannot be removed. For more information about system fields, see http://go.microsoft.com/fwlink/?LinkId=78061. ...
  38. TF212016: {0} is not a valid reporting type. For more information about how to use fields for reporting, see http://go.m ...
  39. TF212021: You cannot index field '{0}' because it is not one of the following types: String, Integer, Double, DateTime, Boolean, ...
  40. TF212022: You cannot specify '{0}' in a query that returns revisions of work items because that field is a computed field. ...
  41. TF212024: To find work items by comparing fields of linked work items, you can only specify fields that belong to the same ...
  42. TF212025: You cannot compare long text, HTML, or history fields to other fields in the WHERE clause of a work item query. ...
  43. TF212056: You cannot delete the work item field, {0}, because it is used in the global workflow for the team project collection. ...
  44. TF214001: An error was encountered while Team Foundation server was retrieving the build definition {1} for team project ...
  45. TF214007: No build was found with the URI {0}. Either the URI does not exist, or {1} does not have permission to access it. ...
  46. TF214008: No build definition was found with the URI {0}. Either the URI does not exist, or {1} does not have permission ...
  47. TF214009: No build agent was found with the URI {0}. Either the URI does not exist, or {1} does not have permission to access ...
  48. TF214010: More than one build was found with build number {0} and build definition {1}. Only one build was expected. Specify ...
  49. TF214011: More than one build definition named {1} was found for team project {0}. Specify a build definition without a wildcard ...
  50. TF214020: There is already a weekly schedule associated with the build definition {0}. You cannot specify more than one weekly ...
  51. TF214023: No build controller was found with the URI {0}. Either the URI does not exist, or {1} does not have permission ...
  52. TF214025: No build service host was found with the URI {0}. Either the URI does not exist, or {1} does not have permission ...
  53. TF214028: The type '{0}' in assembly '{1}' could not be instantiated. Classes marked with the BuildExtensionAttribute must ...
  54. TF214029: The Team Foundation Server you are connected to does not support deleting specific parts of a build (DeleteOptions: ...
  55. TF214030: The build '{0}' does not have a completed status. The current status is {1}. Completed statuses include {2}, {3}, ...
  56. TF215002: Access denied. {0} needs {1} permissions for team project {2} to perform the action. For more information, contact ...
  57. TF215032: Build definition {0} cannot be deleted because builds still exist for this definition. Delete all completed builds ...
  58. TF215033: Build definition {0} cannot be deleted because builds still exist for this definition. Ensure the queue for this ...
  59. TF215035: Queued build {0} on build controller {2} cannot be modified. Queued builds can only be modified if the status is ...
  60. TF215036: The build request cannot be queued at or below position {1} on build controller {0}. The resulting position would ...
  61. TF215067: Cannot cancel queued build {0} on build controller {2}. The current status is {1} and queued builds can only be ...
  62. TF215068: Failed to restart the code coverage analysis service on the Team Foundation Server while deleting the test run. ...
  63. TF215075: The definition name {0} contains characters that you cannot use. Characters that you cannot use include ' ', '|', ...
  64. TF215080: Failed to upgrade one or more build types to build definitions in changeset {0}. You must modify each build type's ...
  65. 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 ...
  66. TF215094: The key for issuing gated check-in tickets could not be created. Submitting gated check-ins will require the user ...
  67. TF215106: Access denied. {0} needs {1} permissions for build definition {2} in team project {3} to perform the action. For ...
  68. TF216001: More than one build agent matched the user input. Only one build agent may be updated when using the {0} option. ...
  69. TF216010: The command {0} was not recognized. At the command prompt, type 'TfsBuild.exe Help' to get a list of available ...
  70. TF218000: Project creation failed. The New Team Project Wizard was unable to access the Site Service Web Service (Sites.asmx) ...
  71. TF218001: Project creation failed. The New Team Project Wizard was unable to access the Site Service Web Service (Sites.asmx) ...
  72. TF218002: Project creation failed. The New Team Project Wizard could not access the Site Service Web Service (Sites.asmx) ...
  73. TF218003: Unable to create the SharePoint site to be used as the team project portal. The team project will not be created. ...
  74. TF218007: Cannot import the work item type. It changes fields in team projects in which you do not have permissions to make ...
  75. TF218007: The {0} plug-in is defined more than once in this process template. To correct this problem, download the process ...