Visual Studio 2013
- TF400930: Field '{0}' is defined multiple times with different field definitions. Correct the field definition and try again. ...
- TF400934: The SQL Instance is a SQL AlwaysOn Availability Group. Test or query the SQL Instance in the advanced, ATOnly or ...
- TF400939: The custom control type '{0}' does not implement the IWorkItemControl interface or is compiled for a different ...
- TF400940: The selected database is a newer version than this application tier. You need to cancel out of the wizard, install ...
- TF400941: The selected database has the following patch installed, which is not on the application tier: {0}. You should ...
- TF400941: The selected database has the following update installed, which is not on the application tier: {0}. You should ...
- TF400942: The selected database is from a previous release. You need to use Upgrade Wizard to configure Team Foundation Server. ...
- TF400944: An error occurred when sending status update to Project Server during synchronization. Returned error code "{0}" ...
- TF400945: The following database is not compatible with Team Foundation Server: {0}. The database collation supports supplementary ...
- TF400946: The following SQL Server instance is not compatible with Team Foundation Server: {0}. The default collation is ...
- TF400949: An item has exceeded the path limit of {1} characters. This may be the result of a move or rename operation of ...
- TF400950: The value of this element is set to: {0}. The value of this element must be set to a field with the following type: ...
- TF400951: The operation failed. You must use Visual Studio 2012 Update 1 or a later version to work with paths that are longer ...
- TF400952: An unexpected error occurred during Analysis Services validation, see log for details. The component might be damaged ...
- TF400955: The path '{0}' cannot be used because the Team Foundation Server you are connected to does not support file container ...
- TF400957: You do not have the permissions required to change the limits to work in progress. Only team members and project ...
- TF400958: The Project Server service account does not have sufficient permissions to call the Project Server Web services. ...
- TF400959: The limit of {1} characters for a directory, or {2} for a directory and file name, was exceeded by the path for ...
- TF400960: You are using a Visual Studio version older than Visual Studio 2012 Update 1. You also have changes pending in ...
- TF400961: You cannot copy build output to the server for {0}. To use a server drop, you must first upgrade build controller ...
- TF400962: The {0} file {1} could not be read with the encoding {2}. Please merge the changes with the configured merge tool ...
- TF400963: The supplied paths are considered identical by the database. Please change one or both of them. The paths are: ...
- TF400968: Build definition {0} cannot copy build output to the server using a build controller that is on premises. To copy ...
- TF400971: Cannot connect to Windows Azure Management because the service responded with a (403) Forbidden message. The X509 ...
- TF400972: The TFS Job Agent failed to send an email. Either it does not have permissions on your SMTP host or the password ...
- TF400980: Failed to restore the Reporting Services encryption key. You can try using RSKEYMGMT command to restore the encryption ...
- TF400981: Failed to backup the Reporting Services encryption key. You can try using RSKEYMGMT command to backup the encryption ...
- TF400989: The Backup Task account '{0}' either does not have permissions on your SMTP host or the password specified is invalid. ...
- TF400990: Database {0} exists on SQL instance {1}. Please drop or rename the existing database before the restore operation. ...
- TF400991: Database {0} exists on SQL instance {1}. If your intention is to replace this team project collection database ...
- TF400996: This tool does not support multiple SharePoint farms in TFS configuration. If your TFS server is using multiple ...
- TF400997: SQL Server service is running as {0}. Please change this account to an account that can be granted permission on ...
- TF400998: The current user failed to retrieve the SQL Server service account information from {0}. Please make sure you have ...
- TF401002: The database '{0}' on SQL Server '{1}' is included in multiple lists and should be in at most one. Please remove ...
- TF401002: The SQL Server Database Engine failed to save the database backup to path {0}. Please grant SQL service account ...
- TF401003: A backup copy of your existing web.config file was saved to the following location: {0}. If you have made customizations ...
- TF401005: Some customizations were not successfully transferred from your previous web.config file. For more details see ...
- TF401006: We were unable to transfer customizations from your previous web.config file. For more details see the configuration ...
- TF401009: The TFS service account {0} cannot access network shares. Change to an account that can access the backup path. ...
- TF401010: The backup path changed since Scheduled Backups were configured. This may cause future backups to fail. Rerun the ...
- TF401017: You cannot delete column: {0}. This column has {1} items in it. You must first move the items to another column, ...
- TF401018: Git objects cannot be read or written directly via the FileContainerService REST APIs. Please use the Git endpoints ...
- TF401019: The Git repository with name or identifier {0} does not exist or you do not have permissions for the operation ...
- TF401022: By policy, the Git object '{0}' is too large to materialize into memory. Its size, {1}, exceeds the threshold of ...
- TF401024: A Git repository for the team project '{0}' could not be created because another source control system is enabled ...
- TF401025: '{0}' is not a valid name for a Git repository. A repository name cannot start with a . or _, end with a ., or ...
- TF401027: {0} lacks the permission(s) required for the operation they are attempting. They need to have '{1}'. Please contact ...
- TF401028: The reference '{0}' was attempted to be updated and has already been updated by another client. Please try again. ...
- TF401040: {0} lacks the permission(s) required for the operation they are attempting at the Team Project level. They need ...
- TF401045: There is no source control repository associated with this Team Project, or you do not have permission to access ...
- TF401051: A local workspace transaction is already running on this thread. The second transaction has been automatically ...
- TF401057: There are no upgradeable configuration databases on this SQL Server instance; however, there are one or more databases ...
- TF401058: A connection cannot be made to the following SQL Server Instance after {1} tries: '{0}'. Verify that you have entered ...
- TF401059: Skipping team '{0}' due to invalid process configuration settings. The team cannot use the Agile planning features ...
- TF401060: We were unable to provision the settings for the kanban board / CFD chart for team '{0}' (Team ID: {1}). Visit ...
- TF401061: The server URL for this instance of Team Foundation Server is {0} and might need to be updated. You can modify ...
- TF401062: The notification URL for this instance of Team Foundation Server could not be retrieved and might need to be updated. ...
- TF401066: You are about to upgrade TFS on a machine that contains an underscore in its name. Running TFS on a machine with ...
- TF401067: Installing TFS on a machine that contains an underscore is strongly discouraged. Doing so will block certain administrative ...
- TF401072: Team Foundation Server requires Windows 7, Service Pack 1 or higher. See Microsoft KB976932 for additional information ...
- TF401073: Team Foundation Server requires Windows 2008 R2, Service Pack 1 or higher. See Microsoft KB976932 for additional ...
- TF401074 : TFS does not currently support the "/layout" switch. To proceed, please download the ISO images or use the web ...
- TF401090 : The build service was originally configured for HTTPS, but the certificate was not found in the certificate store. ...
- TF401091 : The build service was previously configured to run interactively. However, '{0}' was specified as the service ...
- TF401091: This element defines the color for the work item types for this team project. Multiple 'WorkItemColor' elements ...
- TF401092: This element defines the color for the work item types for this team project. A 'WorkItemColor' element has the ...
- TF401093: This element defines the portfolio backlogs for this team project. You have more than five portfolio backlogs defined. ...
- TF401094: This element defines a backlog for this team project. This PortfolioBacklog element and the following PortfolioBacklog ...
- TF401095: The value for the attribute '{0}' has already been defined on the element: '{1}'. The value must be unique within ...
- TF401096: This element defines the hierarchy relationship between portfolio backlogs and must define a linear hierarchy from ...
- TF401096: This element defines the hierarchy relationship between portfolio backlogs and must define a linear hierarchy from ...
- TF401097: This element defines the states for work items that appear on your backlog. This element must have at least one ...
- TF401098: This element defines the states for work items that appear on your backlog. The state configuration is incorrect. ...
- TF401099: This element defines the states for work items that appear on your backlog. The state configuration is incorrect. ...
- TF401100: This command is obsolete and not supported on this version of Team Foundation Server. To update the process configuration, ...