Visual Studio 2012

  1. TF291005: The data type for '{0}' Team Foundation work item field does not match the data type for the corresponding mirror ...
  2. TF291006: The '{0}' Team Foundation work item field does not exist in team project collection: {1}. Correct the field mapping ...
  3. TF291007: The following team project collection ID cannot be found on Team Foundation Server: {0}. Determine if the project ...
  4. TF291008: The following Team Foundation work item field type is not supported: {0}. Remove this field from the field mapping ...
  5. TF291009: Enterprise project plan with ID '{0}' cannot be found on the following Project Web Access: {1}. Determine if the ...
  6. TF291009: Enterprise project plan with ID '{0}' cannot be found on the following PWA instance: {1}. Determine if the project ...
  7. TF291010: The Team Foundation work item field '{0}' is assigned the following incorrect type: {1}. It should be type: {2}. ...
  8. TF291013: The '{0}' team project cannot be found in the following team project collection: '{1}'. Determine if the team project ...
  9. TF291014: The Team Foundation '{0}' work item field cannot be found in the following team project collection: '{1}'. Determine ...
  10. TF291015: The team project collection with the following ID cannot be found on Team Foundation Server: {0}. Determine if ...
  11. TF291016: The following Project Server field is not supported: {0}. Verify that the field is mapped in the field mapping ...
  12. TF291018: The following required Project Server fields are not mapped: {0}. Correct the field mapping for Team Foundation ...
  13. TF291019: A validation error occurred while uploading Project Server mapping data. The '{1}' element that maps to the Project ...
  14. TF291020: A validation error occurred while uploading Project Server mapping data. The '{1}' subelement of the '{2}' element ...
  15. TF291021: The following Project Server field allows multiple values: {0}. Multi-value fields are not supported. Correct the ...
  16. TF291024: The Team Foundation work item field '{0}', which is of type '{1}', specifies the following unsupported transform ...
  17. TF292900: Could not connect to the following Project Server URI: {0}. The server may not be valid or a network problem may ...
  18. TF292901: Could not access the following Project Server URI: {0}. Contact your Project Server administrator to verify that ...
  19. TF292902: Could not connect to Project Server. Details: "{0}". The server may not be valid or a network problem may exist. ...
  20. TF293000: The data warehouse has detected data conflicts for the following work item fields: {1}. The conflicts occur because ...
  21. TF293001: All data warehouse data conflicts that were previously detected have been resolved for fields from project collection ...
  22. TF294000: Access denied. {0} needs the {1} privilege to perform this action. For more information, contact your administrator ...
  23. TF294002: Cannot access enterprise project: {0}. Project Server returned the following error: "{1}". Verify that the project ...
  24. TF294003: Cannot access the following PWA instance: {0}. Project Server returned this error: "{1}". Verify that the PWA instance ...
  25. TF294004: An error occurred while downloading work item tracking data for the team project collection. Retry provisioning ...
  26. TF294007: The following enterprise project is already mapped to a team project: {0}. You cannot map an enterprise project ...
  27. TF294008: Enterprise project '{0}' is mapped to team project: {1}. You must unmap these projects before unmapping your team ...
  28. TF294010: Unable to determine the name of the Project plan from the Project Server id '{0}' for the PWA instance: {1}. Details: ...
  29. TF294012: Cannot access the following enterprise project: {0}. Verify that the project exists, has been published and that ...
  30. TF294014: The following error occurred while updating a Project Server lookup table: "{0}". Perform the corrective action ...
  31. TF294015: Field mappings already exist for the following team project collection: {0}. You must specify the /force option ...
  32. TF294016: You do not currently have any fields mapped. You must first upload the field mapping file before you can map projects. ...
  33. TF294017: You must first register PWA '{0}' with Team Foundation Server before you can map it to the team project collection. ...
  34. TF294018: You cannot perform the current operation because no team project is defined for the team project collection. Create ...
  35. TF294020: Team project collection '{0}' is already mapped to the following PWA: {1}. You must first unmap this collection ...
  36. TF294021: The following team project collection is not mapped to a PWA instance: {0}. Check the mapping for the team project ...
  37. TF294026: The following work item field does not exist: {0}. Contact your administrator for Team Foundation Server to add ...
  38. TF294028: The work item type '{0}' could not be found in the following team project: {1}. Check that you have specified the ...
  39. TF294029: The following PWA instance is not registered: {0}. If you just registered this PWA instance, wait a few minutes ...
  40. TF294031: The following team project is not associated with an enterprise project plan: {0}. You can only map work item types ...
  41. TF297004: You must specify a valid name for the project property. The name must not contain more than 256 Unicode characters. ...
  42. TF298000: Could not connect to the remote device: "{0}". Verify that the device name is correct, the Microsoft Test Tools ...
  43. TF298000: You cannot import global workflow. To import global workflow, the feature must be enabled on the application-tier ...
  44. TF298001: The network connection to the following remote device has been lost: {0}:{1}. Make sure the device is not switched ...
  45. TF298002: Cannot establish a testing session with the device since a session is already in progress from the computer: {0}. ...
  46. TF298003: A problem has occurred with the following message type: {0}. Messages of that type cannot be serialized or deserialized. ...
  47. TF298007: The operation could not be completed because the following user doesn't have permission to connect to Microsoft ...
  48. TF298008: Could not connect to the remote device "{0}". Verify the following and try again: 1. The device is reachable over ...
  49. TF298009: Microsoft Test Manager could not connect to the following remote device because Microsoft Test Tools Adapter process ...
  50. TF298009: You do not have sufficient permissions to map, unmap, or check the mapping of an enterprise project to a project ...
  51. TF298010: The connection to Microsoft Test Tools Adapter running inside the simulator session has been lost. Diagnostic data ...
  52. TF298012: The following file does not have an .appx extension: {0}. Select a file with {1} extension and try the operation ...
  53. TF298014: The following user could not be authenticated: {0}'. This operation can be performed by the user who is currently ...
  54. TF298015: The operation could not be completed because the following user doesn't have permission to connect to Microsoft ...
  55. TF298017: Could not initialize and connect to the Microsoft Test Tools Adapter inside the Simulator's session. Please close ...
  56. TF298018: Microsoft Test Manager could not connect to the following remote machine because there is currently no active desktop ...
  57. TF298020 : The assembly wmvcore.dll could not be found. If you are running Windows Server 2008 or later, make sure the Desktop ...
  58. TF298020: The session you are reconnecting to no longer exists on the remote device. This can happen if the remote device ...
  59. TF298021: Failed to add {0} to the list of firewall exceptions. Add {0} to the list of firewall exceptions manually and start ...
  60. TF298024: Microsoft Test Tools Adapter Service could not stop Microsoft Test Tools Adapter process. Restart the machine to ...
  61. TF298026: Microsoft Test Tools Adapter Service encountered an error while opening a WCF endpoint to listen to requests. Detailed ...
  62. TF298030 : Could not login to the Developer license server using the credential provided. Either the Developer license server ...
  63. TF298030: Cannot start a new testing session on the device '{0}' since a session is already in progress for the user: '{1}'. ...
  64. TF298033 : Could not load the assembly to perform the operations for Developer Licensing. Make sure Windows 8 is installed ...
  65. TF298040 : Install application has timed out. Either the connection to the remote device was lost or the user did not perform ...
  66. TF298047: Could not connect to the remote device "{0}:{1}". Verify the device is reachable and Microsoft Test Tools Adapter ...
  67. TF298500 : There was an error in capturing voice. Voice and screen recording will be disabled for this session. Error: {0} ...
  68. TF298502 : Could not locate the default voice recording device. Voice recording will be disabled for this session. Make sure ...
  69. TF298503 : Could not locate the default voice recording device for the remote session. Voice and screen recording will be ...
  70. TF298504 : Voice recording is not supported on this operating system. Voice recording will be disabled for this session. ...
  71. TF298506 : You cannot create a screen recording when there is content displayed that is protected by Office Information Rights ...
  72. TF298509 : An error occurred while starting the screen recorder. Media will not be recorded. Review the log file for more ...
  73. TF300003: You cannot link to a storyboard that is already linked: {0}. Either modify the existing link, or modify your link ...
  74. TF300005: To link to storyboards, you must connect to a version of Team Foundation Server that supports storyboard links. ...
  75. TF30001: Team Explorer could not retrieve a list of projects from the Classification Service. Contact your Team Foundation ...