Visual Studio 2012
- TF400804: The TFS Job Agent was terminating execution but the following jobs would not come to a stop in a timely manner: ...
- TF400810: The name {0} is not a valid identifier for a message queue. The queue name should be a valid URI host name with ...
- TF400822: The custom display name is invalid. It can not be over 256 characters. It can not contain periods alone. It can ...
- TF400830: The streaming collection does not support multiple enumerators or resetting an enumerator. A streaming collection ...
- TF400842: The following collation is not supported: {0}. You must choose a collation that is supported by the database when ...
- TF400843: Account preferences have already been set. You can only set the preferences for language, culture, and time zone ...
- TF400847: The language is not installed for the following culture identifier: {0}. You must choose a language that is already ...
- TF400853: The identity descriptor is mal-formed. A bind-pending identifier must start with "{0}" followed by an email address. ...
- TF400857: The following type does not define ComponentFactory field: {0}. Component must define ComponentFactory public static ...
- TF400858: The type of the ComponentFactory field on the following component is invalid: {0}. Component must define ComponentFactory ...
- TF400885: Destination database name must differ from source database name: {0}. ven if source and destination are on different ...
- TF400886: Application shutdown has timed out. The application is abruptly terminating. State of selected threads at termination ...
- TF400887: The {0} service was expecting a request context from service host '{1}' but instead got one from service host '{2}'. ...
- TF400888: The tagging service was expecting a request context from service host '{0}' but instead got one from service host ...
- TF400893: Team Foundation Server services are not available. This is most likely caused by a network error. Please check ...
- TF400899: Access Denied. You are not authorized to perform this action. For further information, contact the Team Foundation ...
- TF400911: There was an error creating the project. Please try again and if the problem persists contact our support team ...
- TF400916: The current configuration is not valid for this feature. This feature cannot be used until a Team Foundation Administrator ...
- TF400917: The current configuration is not valid for this feature. This feature cannot be used until you correct the configuration. ...
- TF400919: For the {0} operation both /sqlInstance and /databaseName parameters have to be specified pointing to the configuration ...
- TF400920: Neither /account nor /password parameters are allowed with the {0} operation. The current user's credentials will ...
- TF400924: The specified database {0} on the SQL server {1} has the unexpected type '{2}'. The database of the type '{3}' ...
- TF400924: The specified database {0} on the SQL server {1} has the unexpected type '{2}'. The database of the type '{3}' ...
- TF400926: When getting constant records using Team Foundation identity ID, the supplied search value must be a valid GUID. ...
- TF400927: The following team project collection is in detached state: {0}. Sql Server hosting the database: {1}. Database ...
- TF400928: An error occurred while verifying that all team project collections are attached. The following error was reported: ...
- TF400930: Field '{0}' is defined multiple times with different field definitions. Correct the field definition and try again. ...
- TF400933: The SQL instance used does not meet the minimum requirements for Team Foundation Server. You should update SQL ...
- 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 ...
- 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 ...
- TF400953: An invalid baseline revision was provided for the synchronization property or mapping. Retrieve the latest value ...
- TF400954: Team Foundation could not update the synchronization property or mapping because it was already updated by another ...
- 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 ...
- 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: MSSQL Server service is running as {0}. Please change this account to an account that can be granted permission ...
- 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 ...
- 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 ...
- TF401027: A user lack the permission(s) required for the operation they are attempting. They need to have '{0}'. Please contact ...
- TF401028: The reference '{0}' was attempted to be updated and has already been updated by another client. Please try again. ...
- 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 ...
- TF401053: The requested service level property {0} was not found. This property is required and must match the job agent's ...