Visual Studio 2012
- TF1031555: Either the trial period for the lab agent has expired or your license is not valid. To continue, install a licensed ...
- TF1031558: The lab agent service encountered the following error while registering exceptions in Windows Firewall for services: ...
- TF1031559: The communication channel used to receive the commands is not ready. Make sure that the correct version of "Hyper-V ...
- TF1031562: The lab agent encountered an error while accessing the registry key "{0}". Error: Required key is not found in ...
- TF14001: The source control server state {0} has been set to '{1}' by an administrative action on {2} with the comment "{3}". ...
- TF14006: Cannot change the owner of workspace {0} to {1} because the workspace has pending changes. To change the owner of ...
- TF14010: Cannot merge to '{0}' because a merge conflict already exists for this path. Run resolve to deal with the existing ...
- TF14011: Cannot move item to path {0} in the root folder. Use the New Team Project Wizard to branch it to a new team project ...
- TF14012: Cannot undelete team project folder {0}. Please use the Project Creation Wizard to create a new team project and ...
- TF14043: The error "{2}", occurred computing the delta between file {0} and file {1}. Since the delta computation has failed, ...
- TF14043: The error "{2}", occurred computing the delta between file {0} and file {1}. This error may be transient and creating ...
- TF14043: The error "{2}", occurred computing the delta for item {0} version {1}. Since the delta computation has failed, ...
- TF14043: The error "{2}", occurred computing the delta for item {0} version {1}. This error may be transient and creating ...
- TF14059: Unable to process the pending changes requested. The set of pending renames would cause a name collision for {0}. ...
- TF14070: Cannot resolve a conflict with AcceptMerge when {0} was deleted on the server. Please choose AcceptTheirs or AcceptYours ...
- TF14075: When creating or updating a shelveset, the owner specified must be the same as the user that is creating or updating ...
- TF14078: The mapped local path for '{0}' exceeded the limit of 248 characters for the directory or 259 for the directory ...
- TF14081: The item '{0}' could not be merged into the target tree because no related item in the target tree could be found. ...
- 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 ...
- TF14095: The performance counter '{1}' within the performance category '{0}' could not be initialized. Note that the system ...
- 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 ...
- TF200004: The following argument is not valid: {0}. The following uniform resource identifier (URI) in the argument is not ...
- TF200007: The following structure type is not recognized: {0}. For more information about customizing process templates, ...
- TF200008: One or more XML elements do not match the schema. For more information about customizing process templates, see ...
- TF200009: The number of root structures is incorrect. You must provide two (2) root structures. For more information about ...
- TF200010: The root structure types are the same. Each root structure must have a unique type. For more information about ...
- TF200011: The child structure type does not match the parent structure type. Verify that all child structures have the same ...
- TF200012: Two child structures share the same name and parent. All child structures must have unique names under their parent. ...
- TF200016: The following project does not exist: {0}. Verify that the name of the project is correct and that the project ...
- TF200018: The following reclassification node does not exist: {0}. Verify that the uniform resource identifier (URI) is correct. ...
- TF200019: The following project already exists on the Team Foundation Server: {0}. You cannot create a new project with the ...
- TF200022: An error occurred when trying to move the following node: {0}. This move would move the node outside of the valid ...
- TF200024: The following node cannot be moved: {0}. The node is in a different hierarchy than the requested parent node: {1}. ...
- TF200025: A deleted node cannot be reclassified to itself. Reclassify work items to a node that is not about to be deleted. ...
- TF200026: The reclassification node cannot be beneath the deleted node in the hierarchy. Deleted node: {0}. Reclassification ...
- TF200031: An error has occurred when trying to add or synchronize the following user identity: {0}. The identity contains ...
- TF200032: An error occurred while Team Foundation Server was synchronizing identities. Synchronization could not complete ...
- TF200033: The email address {0} configured as the from address for project alerts is not a valid or recognized email address. ...
- TF200035: One or more errors occurred when Team Foundation Server attempted to synchronize the following identity: {1}. Number ...
- TF200036: An error occurred while attempting to read information from the following Active Directory domain: {0}. The Active ...
- TF200037: You cannot update the MSPROJ property when using Microsoft Visual Studio Team System 2008 or an earlier version. ...
- TF200038: You cannot create a team project with your version of Team Explorer. Contact your system administrator to determine ...
- TF200039: You cannot manage a process template with your version of Team Explorer. Contact your system administrator to determine ...
- TF200040: You cannot delete a team project with your version of Team Explorer. Contact your system administrator to determine ...
- TF200041: You have specified a name, {0}, that contains character(s) that are not recognized. Specify a name that only contains ...
- TF200042: An error occurred which trying to view or modify an item that is scheduled for synchronization. Verify that the ...
- 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 ...