Visual Studio 2012

  1. TF244029: Unable to successfully register the PWA instance. Review the messages logged during the registration process for ...
  2. TF244040: Your Project Server synchronization mapping contains an invalid project ID. Verify that your plan is mapped to ...
  3. TF244043: Cannot create custom field '{0}' because a custom field with the same name already exists. Delete the custom field ...
  4. TF244044: Cannot create lookup table '{0}' because a lookup table with the same name already exists. Delete the lookup table ...
  5. TF244047: Cannot access the following PWA instance: {0}. Project Server returned this error: "{1}". The URL might not be ...
  6. TF244054: The following team project collection is not mapped to a PWA instance: {0}. Check the mapping for the team project ...
  7. TF244059: The value for the following custom field should be a Text field in Project Server: {0}. You can specify a text ...
  8. TF244062: The following PWA instance is not registered correctly: {0}. To correct the registration, you must unregister the ...
  9. TF244065: An error occurred while retrieving the list of event handlers for event ID: {0}. Project Server returned the following ...
  10. TF244068: An error occurred while provisioning the reporting database schema for a PWA instance. Project Server returned ...
  11. TF244069: An error occurred while checking the provisioning status of the reporting database schema for a PWA instance. Project ...
  12. TF244070: An error occurred while dropping the reporting database schema for a PWA instance. Project Server returned the ...
  13. TF244077: An error occurred while retrieving enterprise custom fields. Project Server returned the following error: "{0}". ...
  14. TF244078: An error occurred while retrieving lookup tables. Project Server returned the following error: "{0}". Contact your ...
  15. TF244081: A syntax error was detected in the field mapping definition file that you tried to upload. Correct the field mapping ...
  16. TF244082: The namespace that you specified in the field mapping definition file is incorrect. The namespace must be either ...
  17. TF244083: The following syntax error occurred in the field mapping definition file that you tried to upload: "{0}". Correct ...
  18. TF244085: The following PWA instance is registered to Team Foundation Server "{1}": {0}. You must unregister it from that ...
  19. TF244086: You cannot unmap the following team project from the enterprise project plan while tasks are actively synchronizing ...
  20. TF244087: The Microsoft Team Foundation Server Extensions for Project Server must be installed on those machines that host ...
  21. TF244087: You cannot unmap the specified types of work items while work items of these types are actively synchronizing with ...
  22. TF244088: To run this command, you must have been granted the Administer Project Server integration permission on Team Foundation ...
  23. TF244089: To run this command, you must be a member of the Team Foundation Administrators group on Team Foundation Server ...
  24. TF245000: You must specify attributes for the following XML element: . Correct the field mapping for Team Foundation Server ...
  25. TF245001: The contents of the field mapping file are not valid. The expected XML element is '{0}', but the actual element ...
  26. TF245002: An error occurred while validating the following section in the field mapping file: . Correct and upload the field ...
  27. TF245003: For each field that you map, you must specify a provider for the tfsToTarget element and the targetToTfs element. ...
  28. TF245004: An unexpected error occurred while validating the associations in the section in the field mapping file. Correct ...
  29. TF245006: An error occurred while validating the section in the field mapping file. Correct the field mapping for Team Foundation ...
  30. TF245007: An error occurred while validating the section in the field mapping file. Correct the field mapping for Team Foundation ...
  31. TF245008: You must specify a value for: {0}. Correct the field mapping for Team Foundation Server and Project Server integration. ...
  32. TF245009: The following provider is not supported: {0}. Correct the field mapping for Team Foundation Server and Project ...
  33. TF245010: The field mapping file contains a duplicate reference for enterprise custom field '{0}' from the following provider: ...
  34. TF245011: The field mapping file contains a duplicate reference of Team Foundation work item field: {0}. Correct the field ...
  35. TF245012: A validation error occurred for the following element '{0}'. Type "{1}" is already defined. You cannot add type ...
  36. TF245013: A validation error occurred for the following element '{0}'. Type "{1}" does not contain a default constructor. ...
  37. TF245014: A validation error occurred for the following element '{0}'. Type "{1}" does not implement IFactoryProduct interface. ...
  38. TF245015: The following transform is not supported: {0}. Available transforms are: {1}. Correct the field mapping for Team ...
  39. TF245016: The following transform is not currently supported on the tfsToTarget element: {0}. Correct the field mapping for ...
  40. TF246017: Team Foundation Server could not connect to the database. Verify that the server that is hosting the database is ...
  41. TF246018: The database operation exceeded the timeout limit and has been cancelled. Verify that the parameters of the operation ...
  42. TF246019: The Team Foundation Server trial period has expired, or the license is not valid. You must update your license ...
  43. TF246020: Microsoft SQL Server encountered an error while processing the results from one of the Team Foundation Server databases. ...
  44. TF246021: An error occurred while processing your request. Technical information (for administrator): SQL Server Error: {0} ...
  45. TF246022: Another synchronization task is already in progress. The additional background synchronization of identities will ...
  46. TF246023: The value must be unique for the following property: {0}. The following resource already has this value: {1}. You ...
  47. TF246024: An error occurred while attempting to build catalog nodes. A catalog node is missing the following path to its ...
  48. TF246025: The argument you specified is not valid. You cannot pass a value for Catalog Node to the Web service without also ...
  49. TF246026: The required node named '{0}' is missing from the catalog service. The most likely cause of this error is that ...
  50. TF246027: A catalog node cannot be created. No dependent node exists with the following association key: {0}. You must create ...
  51. TF246028: You cannot save the node. When saving a node with dependencies on the Web service you must specify the nodes upon ...
  52. TF246030: One or more changes that you specified are not valid. Two or more nodes at the same level point to the same catalog ...
  53. TF246032: You cannot non-recursively delete a catalog node of the following type: {0}. You must recursively delete this node ...
  54. TF246033: You cannot recursively delete a catalog node of the following type: {0}. You must non-recursively delete this node ...
  55. TF246034: One or more catalog nodes has a dependency upon itself. Catalog nodes cannot contain dependencies on themselves. ...
  56. TF246036: The following catalog resource type is not valid: {0}. The node must have a dependency with the following name: ...
  57. TF246037: No parent can be found for the following catalog node: {0}. Either the parent node does not exist, or it has not ...
  58. TF246039: The catalog service received an unexpected request from the following service host: {1}. The catalog service expected ...
  59. TF246040: The following catalog resource cannot be created: {0}. At least one node must reference the catalog resource in ...
  60. TF246042: The catalog node cannot be created with the following resource type: {0}. The catalog node cannot contain a resource ...
  61. TF246043: The catalog node cannot be created with the following resource type: {0}. The catalog node cannot contain a resource ...
  62. TF246044: A catalog node dependency is not valid, but has been loaded. The following catalog node path does not exist: {0}. ...
  63. TF246047: The following catalog resource type is not valid: {0}. A resource of this type must contain a property with the ...
  64. TF246048: The following catalog resource type is not valid: {0}. The type must contain a service reference with the following ...
  65. TF246049: You cannot move the node in the catalog web service unless you specify both the node being moved and the new parent ...
  66. TF246053: The location service received an unexpected request from the following service host: {1}. The location service ...
  67. TF246054: A service definition has already been registered with the specified service type and identifier. Service type: ...
  68. TF246055: The service definition cannot be updated. No service definition exists with the specified service type and identifier. ...
  69. TF246056: The following security token is not valid: {0}. This security namespace has a hierarchical structure with the following ...
  70. TF246057: The following security namespace is not valid: {0}. The ID of the namespace is: {1}. The namespace contains the ...
  71. TF246059: An error occurred in the following security namespace: {0}. The security namespace received an unexpected request ...
  72. TF246059: The security service received an unexpected request from the following service host: {1}. The security service ...
  73. TF246061: An unexpected ID was received from the database in the following location: The database is stamped with the following ...
  74. TF246062: Two or more databases are in conflict because they are each designated as the owners of the following schema: {0}. ...
  75. TF246063: No database could be found as the designated owner of the following schema: {0}. The schema is for the host with ...