Visual Studio 2012
- 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. ...
- TF237019: You are working with a query hierarchy, but the hierarchy has been changed between now and when you last refreshed. ...
- TF237024: The item, query folder or query, is not from the specified team project. Select an item from the current team project. ...
- TF237025: The item, query folder or query, and the set of team projects are not all from the same Team Foundation Server. ...
- TF237050: {0} is not a valid work item type category name. See http://go.microsoft.com/fwlink/?LinkId=104504 for more information ...
- TF237051: {0} is not a valid work item type category reference name. See http://go.microsoft.com/fwlink/?LinkId=104505 for ...
- TF237052: The category is missing for InsertWorkItemTypeCategoryMember or UpdateWorkItemTypeCategoryMember. You must include ...
- TF237053: The work item type is missing for InsertWorkItemTypeCategoryMember. You must include WorkItemTypeID or TempWorkItemTypeID. ...
- TF237054: The category is missing for InsertWorkItemTypeCategory or UpdateWorkItemTypeCategory. You must include CategoryID ...
- TF237055: You cannot destroy a work item type that is being used. Verify that the work item type is not being used in any ...
- TF237056: You cannot supply a value for the field {0}. The field is read-only, and the value is provided by the Team Foundation ...
- TF237057: The string used in the query exceeds the maximum supported length of {1} characters for field {0}. This can be ...
- TF237059: The import of the category definition failed. In the type definition, category {0} refers to a work item type that ...
- TF237060: The import of the category definition failed. The category {0} type definition refers to work item type {1} more ...
- TF237061: The import of the category definition failed. The definition name you are trying to import already contains the ...
- TF237061: The import of the category definition failed. The definition name you are trying to import already contains the ...
- TF237064: Importing the work item type definition failed. The Control element must specify a Label attribute if a Link element ...
- TF237066: Importing the work item type definition failed. The parameter elements specified for the link are fewer than required ...
- TF237067: Importing the work item type definition failed. The Url parameter {0} is not a valid field name or a valid macro. ...
- TF237068: Importing the work item type definition failed. The definition you are trying to import lists a parameter index ...
- TF237069: Importing the work item type definition failed. The definition you are trying to import lists more than one parameter ...
- TF237070: Importing the definition failed. The definition you are trying to import did not validate against the schema. Edit ...
- TF237076: Importing the work item type definition failed. The definition you are trying to import contains an invalid UrlRoot ...
- TF237077:Importing the work item type definition failed. The definition you are trying to import uses unsupported Url protocol ...
- TF237078: Importing the definition failed. The definition you are trying to import uses unsupported Url protocol '{0}' for ...
- TF237079: Team Foundation could not update the work item because it was already updated by another user, it does not exist, ...
- TF237082: The attachment could not be uploaded. Verify that you have a network connection and that Team Foundation Server ...
- TF237091: Actual reporting settings for the field {0} are different from those specified in the XML. Changing these settings ...
- TF237092: Action '{0}' is defined for more than one transition from state '{1}'. Transitions from every single state must ...
- TF237112: Default state cannot be inferred from transitions. Default state is defined by a transition from an empty state, ...
- TF237148: The Team Foundation Server work item database can not be opened. It may be offline for system administration. Try ...
- TF237165: Team Foundation could not update the work item because of a validation error on the server. This may happen because ...
- TF237167: Importing the definition failed. The definition you are trying to import cannot use the attributes AllowScript ...
- TF237173: You cannot open the file {0} because it contains a query that is supported by a more recent version of Team Foundation ...
- TF237175: The import failed. The work item type filter {0} is specified more than once in the work item type definition. ...
- TF237176: The import failed. The work item type definition that you are trying to import contains a links control with an ...
- TF237179: The query or query folder that you referenced does not exist on the server. It might have been deleted. Refresh ...
- TF237180: You have set permissions that are not recognized query permissions. Change the permissions and try the operation ...
- TF237199: You cannot set query or query folder permissions with this version of Team Foundation Server. Upgrade to a newer ...
- 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 ...
- TF238001: The name that you typed contains one or more characters that are not valid, or it contains Unicode control characters. ...
- TF239000: Internet Information Services (IIS) has returned a value that is not valid. The value for ServerBinding was null ...
- TF239001: An error in the binding type caused report creation to fail. The binding type was not valid: {0}. Bindings must ...
- TF239002: The following binding string is not valid: {0}. The binding string must contain three parts, separated by colons. ...
- TF24003: The query or query folder name you entered contains characters that are not supported. Correct the name and try ...
- TF24023: Team Foundation Server Configuration Failure. The New Team Project Wizard work item component could not connect ...
- TF24042: You do not have permission to create work items in project '{0}'. Contact your Team Foundation System administrator. ...
- TF241004: A termination of the network connection caused the reconnect operation to server {0} to fail. Retry the operation ...
- TF241005: An unknown error caused the reconnect operation to fail. Close the file without saving it and retry the operation. ...
- TF241006: The reconnect operation failed because the team project collection you selected does not host the team project ...
- TF241008: The following field(s) contain invalid values: {0}. Click 'Correct this error' to open a field correction form ...
- TF241011: Project has reset the value for the Publish to Team Project column to Yes. You cannot change the value for Publish ...
- TF241012: After auto-correcting the '{0}' custom field to Yes, Project detected that the value assigned to the Publish to ...
- TF241013: Invalid {0} attribute value in mapping. This attribute value should be a task text custom field between pjTaskText1 ...
- TF241016: The following fields are not modified because the value(s) you selected for them are either not available in the ...
- TF241017: Your local enterprise project plan does not have access to recently provisioned custom fields. To update your plan, ...
- TF242402: Could not start or connect to Outlook. This problem can occur if Visual Studio is running with full administrator ...
- TF242402: Could not start or connect to {0}. This problem can occur if Visual Studio is running with full administrator access ...
- TF242408: The query you selected does not return any work items. Select a query that contains at least one work item, and ...
- TF243000: Verify that the TFS service account has full permission to MachineKeys folder on server (for example, C:\Documents ...
- TF243001: An error occurred initializing the proxy for the team project collection at {0}. The message returned from the ...
- TF244000: An error occurred while creating enterprise custom field: {0}. Project Server returned the following error: "{1}". ...
- TF244001: An error occurred while deleting enterprise custom field: {0}. Project Server returned the following error: "{1}". ...
- TF244002: The number of core enterprise custom fields is not valid. You must provide the name for all {0} core custom fields. ...
- TF244003: The version of Project Server is not valid. See http://go.microsoft.com/fwlink/?LinkId=253186 for information about ...
- TF244004: Cannot connect to the PWA instance. The URL might not be valid, a network problem might exist, or you might not ...
- TF244005: An error occurred while creating lookup table: {0}. Project Server returned the following error: "{1}". You might ...
- TF244006: An error occurred while deleting lookup table: {0}. Project Server returned the following error: "{1}". You can ...
- TF244009: Cannot connect to Team Foundation Server: {0}. The server name might not be valid, a network problem might exist, ...
- TF244011: The following PWA instance is not currently registered: {0}. If this PWA was previously registered under a different ...
- TF244016: Team project collection '{0}' is mapped to the following PWA instance: {1}. You must unmap this project collection ...
- TF244022: Could not access enterprise project: '{0}'. Project Server returned the following error: "{1}". Verify that the ...
- TF244023: An error occurred while reading a Project Server lookup table. The error is: "{0}". Perform the corrective action ...
- TF244024: The following enterprise project is either not valid or cannot be accessed: {0}. Verify that the project exists ...
- TF244027: An error occurred while updating a Project Server lookup table. The error is: "{0}". Perform the corrective action ...