Voici la liste des différentes erreurs retournés par Team Foundation Server :
Code | Message | Description |
---|---|---|
TF10001 | The Team Foundation Server name is not present in configuration file. Contact your Team Foundation Server administrator. | Ce message d'erreur permet d'indiquer que le nom de Le nom de Team Foundation Server n'est pas présent dans le fichier de configuration. |
TF10002 | Source control is unable to determine the SID for user name: | Ce message d'erreur permet d'indiquer que le contrôle de Source n'est pas capable de déterminer le SID pour le nom d'utilisateur spécifié. |
TF10008 | Source control encountered an unexpected error. Contact Microsoft Product Support Services. | Ce message d'erreur permet d'indiquer qu'une erreur inattendu est rencontré par contrôle de source, vous devriez contacter le service de support de Microsoft. |
TF10009 | The code page you specified is either not recognized or not installed: {0} | Ce message d'erreur permet d'indiquer que la page de code spécifié n'est reconnu ou installé. |
TF10010 | Source control unexpectedly encountered the end of the stream: {0} | Ce message d'erreur permet d'indiquer que le contrôle de code source a rencontré la fin du flux de manière inattendue. |
TF10011 | The {0} property cannot be changed after it is set. | Ce message d'erreur permet d'indiquer que la propriété spécifié ne peut pas être modifiée après qu'elle a été définie. |
TF10097 | The information about the version of the file is ambiguous. Specify a different file version and try again. | Ce message d'erreur permet d'indiquer que les informations sur la version du fichier sont ambiguës. Spécifiez une version de fichier différente et réessayez. |
TF10098 | {0} arguments cannot contain {1} | Ce message d'erreur permet d'indiquer que les paramètres spécifiés ne peuvent pas contenir le contenu que vous avez spécifié. |
TF10099 | {0} was not found on the Team Foundation Server. | Ce message d'erreur permet d'indiquer que l'élément spécifié n'est pas trouvé par Team Foundation Server. |
TF10100 | The option {0} is not supported. | Ce message d'erreur permet d'indiquer que l'option spécifié n'est pas supporté. |
TF10101 | Item {0} is not used in any branch trees. | Ce message d'erreur permet d'indiquer que l'item spécifié est utilisé dans aucune arborescence de branche. |
TF10102 | The branches command requires at least one item. Type or select either a local or server path to the item. | Ce message d'erreur permet d'indiquer que la commande de branches nécessite au moins un élément, vous devez donc tapez ou sélectionnez un chemin local ou un serveur vers l'élément. |
TF10104 | Source control cannot add the project: {0} | Ce message d'erreur permet d'indiquer que le contrôle de source ne peut pas l'ajouter au projet spécifié. |
TF10105 | Source control cannot add the solution: {0} | Ce message d'erreur permet d'indiquer que le contrôle de source ne peut pas l'ajouter a la solution spécifié. |
TF10107 | Source control cannot compare binary files. | Ce message d'erreur permet d'indiquer que le contrôle de source ne peut pas comparer les fichiers binaires. |
TF10108 | Source control cannot compare a file with a folder. Select two files and try again. | Ce message d'erreur permet d'indiquer que le contrôle de source compare un fichier avec un dossier. Vous devriez plutôt sélectionner 2 fichiers et recommencer. |
TF10109 | Check that you have a network connection and that your Team Foundation Server is available. If the problem persists, contact your Team Foundation Server administrator. | Ce message d'erreur permet d'indiquer que le contrôle de code source ne peut pas localiser le service de contrôle de code source sur Team Foundation Server. Vérifiez que vous disposez d'une connexion réseau et que votre serveur Team Foundation est disponible. |
TF10110 | The Team Foundation source control server information is not registered or not available. | Ce message d'erreur permet d'indiquer que les informations serveurs du contrôle de source ne sont pas enregistrés ou ne sont pas disponibles. |
TF10111 | You must provide a name for the check-in note. | Ce message d'erreur permet d'indiquer que vous devez fournir un nom pour le «Check-In». |
TF10112 | The check-in note field '{0}' is not supported for changeset {1}. | Ce message d'erreur permet d'indiquer que le champ de note du «Check-In».n'est pas prise en charge pour l'ensemble de modifications. |
TF10113 | You must provide a value for check-in note field '<field name>'. | Ce message d'erreur permet d'indiquer qu'il faut fournir une valeur pour le champ de note de «Check-In». |
TF10114 | You must provide a name for the check-in note. | Ce message d'erreur permet d'indiquer qu'il faut fournir un nom pour le champ de note de «Check-In». |
TF10115 | '<check-in note name>' is too long for a check-in note name. | Ce message d'erreur permet d'indiquer le nom de la note du «Check-In» est trop longue. |
TF10116 | The following check-in notes do not pass check-in requirement: | Ce message d'erreur permet d'indiquer que les notes du «Check-In» ne passe pas les requis. |
TF10117 | The following check-in note does not pass check-in requirement: | Ce message d'erreur permet d'indiquer que la note du «Check-In» ne passe pas les requis. |
TF10118 | Check-in notes cannot be configured for the root. You must specify a team project. | Ce message d'erreur permet d'indiquer que les note du «Check-In» doivent être configuré pour la racine. |
TF10119 | Warning {0} - Ignoring deletion ID {1} | Ce message d'erreur permet d'indiquer de l'identificateur de suppression a été ignoré. |
TF10120 | The value {0} is not supported for option {1}. | Ce message d'erreur permet d'indiquer que la valeur n'est pas supporté par l'option. |
TF10121 | The path '{0}' is not found or not supported. Type or select a different path. | Ce message d'erreur permet d'indiquer que le chemin spécifié est introuvable ou n'est pas supporté. |
TF10122 | The path '{0}' contains a '$' at the beginning of a path component. Remove the '$' and try again. | Ce message d'erreur permet d'indiquer que le chemin contient un «$» au début de la composante de chemin. |
TF10123 | The path '{0}' contains the character '{1}'. Remove the '{1}' and try again. | Ce message d'erreur permet d'indiquer que le chemin contient un mauvais caractère. |
TF10124 | The path '{0}' cannot start with {1}. Remove the {1} and try again. | Ce message d'erreur permet d'indiquer que le chemin ne peut pas commencé avec le caractère spécifié. |
TF10125 | The path '{0}' must start with $/ | Ce message d'erreur permet d'indiquer que le chemin doit commencé avec le caractère «$/». |
TF10126 | The path '{0}' has no parent in common with '{1}' | Ce message d'erreur permet d'indiquer que le chemin n'a aucun parent commun avec celui spécifié. |
TF10127 | The path does not include a source control item. Type or select a different path. | Ce message d'erreur permet d'indiquer que le chemin n'est pas inclus dans l'élément de contrôle de source. |
TF10128 | The path {0} contains more than the allowed 260 characters. Type or select a shorter path. | Ce message d'erreur permet d'indiquer que le chemin contient plus de 260 caractères. |
TF10129 | The path {0} contains too many instances of '..' (it goes above the root). Type or select a different path. | Ce message d'erreur permet d'indiquer que le chemin contient trop d'instance «..». |
TF10130 | '{0}' is a reserved name and may not be included in a path. | Ce message d'erreur permet d'indiquer que le nom est réservé et ne doit pas être inclus dans un chemin. |
TF10131 | The shelveset name {0} contains more than 64 characters or contains some of the following characters. Type a valid name and try again. | Ce message d'erreur permet d'indiquer que le nom de l'ensemble de niveau spécifié contient plus de 64 caractères ou contient certains des caractères spécifiés. |
TF10132 | {0} is not a supported user name. | Ce message d'erreur permet d'indiquer le nom d'utilisateur spécifié n'est pas supporté. |
TF10133 | An attempt to create a working folder mapping was canceled. The current source control operation was canceled. | Ce message d'erreur permet d'indiquer qu'une tentative de création de dossier de travail cartographié à été annulé. |
TF10136 | "{0}" is not a recognized source control permission. | Ce message d'erreur permet d'indiquer que les permissions du contrôle de source. |
TF10137 | Check-in policies may only be associated with team projects. | Ce message d'erreur permet d'indiquer que les politiques de «Check-In» peuvent seulement être associé avec les projets d'équipe. |
TF10138 | The check-in policy settings for <policy definition> are corrupted. | Ce message d'erreur permet d'indiquer que les politiques d'ajustements de Check-In pour les définitions de politiques spécifiés sont corrompus. |
TF10139 | The following check-in policies have not been satisfied | Ce message d'erreur permet d'indiquer que les politiques de «Check-In» ne sont pas satisfaites. |
TF10140 | Cannot check in {0}, there is a problem creating a parent item. | Ce message d'erreur permet d'indiquer qu'il est impossible de faire un «Check-In», il y a un problème lors de la création d'un élément parent. |
TF10140 | The following check-in policies were not satisfied | Ce message d'erreur permet d'indiquer que les politiques de «Check-In» n'ont pas été satisfaites. |
TF10141 | No files checked in: resolve the conflicts and try again. | Ce message d'erreur permet d'indiquer qu'il n'y a pas de fichiers a mettre en «Check-In», vous devez d'abord résoudre les conflits. |
TF10143 | Specifying /user:* is not supported when also specifying the /workspace option. | Ce message d'erreur permet d'indiquer que l'utilisateur spécifié n'est pas supporté quand il est aussi spécifié avec l'option «/workspace». |
TF10144 | '<Version specification>' is not a supported version specification type. | Ce message d'erreur permet d'indiquer le type de spécification de version n'est pas supporté. |
TF10145 | The version specification is not in a supported date or time format. | Ce message d'erreur permet d'indiquer la spécification de version ne support pas le format de la date ou de l'heure. |
TF10146 | The deletion id given (<deletionID>) is not a supported deletion number. | Ce message d'erreur permet d'indiquer que l'identificateur de suppression spécifié n'est pas un numéro de suppression supporté. |
TF10149 | You cannot create files in the root folder. Create a team project and then add the files under the team project folder. | Ce message d'erreur permet d'indiquer qu'il n'est pas possible de créer des fichiers dans le dossier racine. |
TF10151 | Cannot lock item {0} for check-out. This item is checked out by {1} in workspace {2}. | Ce message d'erreur permet d'indiquer qu'il n'est pas possible déverrouiller l'élément spécifié dans un «Check-Out». |
TF10152 | The item {0} must remain locked because its file type prevents multiple check-outs. | Ce message d'erreur permet d'indiquer que l'élément doit verrouiller parce que son type de fichier empêche plusieurs «Check-Out». |
TF10154 | The extension {0} cannot be used in file type {2}, it is already being used in {1}. | Ce message d'erreur permet d'indiquer que l'extension spécifié ne peut être utilisé dans un type de fichier spécifié car elle déjà utilisé ailleurs. |
TF10156 | The computer name {0} contains unsupported characters, is empty, or too long. | Ce message d'erreur permet d'indiquer que le nom de l'ordinateur spécifié contient des caractères non-supporté, des caractères vides ou est trop long. |
TF10157 | The file {0} is empty. | Ce message d'erreur permet d'indiquer que le fichier spécifié est vide. |
TF10158 | The user or group name {0} contains unsupported characters, is empty, or too long. | Ce message d'erreur permet d'indiquer que le nom d'utilisateur ou le nom du groupe contient des caractères non-supporté, des caractères vides ou est trop long. |
TF10159 | The label name '{0}' is not supported. It must be less than 64 characters, cannot end with a space or period, and cannot contain any of the following characters: "/:<>|*?@, double back-slash | Ce message d'erreur permet d'indiquer que le nom d'étiquette spécifié n'est pas supporté. |
TF10160 | The item {0} is not a supported server item. | Ce message d'erreur permet d'indiquer que l'élément du serveur n'est pas supporté. |
TF10161 | The log level {0} is not supported. | Ce message d'erreur permet d'indiquer que le niveau de journal de bord spécifié n'est supporté. |
TF10162 | The server state {0} is not supported. | Ce message d'erreur permet d'indiquer que l'état du serveur spécifié n'est pas supporté. |
TF10163 | It must be less than 64 characters, cannot end with a space or period, and cannot contain any of the following characters: ";/:<>|*?, double back-slash | Ce message d'erreur permet d'indiquer le nom de l'ensemble de niveau spécifié n'est pas supporté. |
TF10164 | The URL is not found or unsupported. Check the URL and try again. | Ce message d'erreur permet d'indiquer que l'URL n'est pas trouvé ou n'est pas supporté. |
TF10165 | The workspace name {0} is not supported. It must be less than 64 characters, cannot end with a space or period, and cannot contain any of the following characters: "/:<>|*? | Ce message d'erreur permet d'indiquer que le nom de l'espace de travail n'est pas supporté. |
TF10167 | An unsupported ConflictId was specified | Ce message d'erreur permet d'indiquer que l'identificateur de conflit spécifié n'est pas supporté. |
TF10168 | The extension {0} is not supported. It cannot contain any of the following characters /:*?"<>|, double back-slash. | Ce message d'erreur permet d'indiquer que l'extension n'est pas supporté. |
TF10169 | Unsupported pending change attempted on team project folder {0}. Use the Project Creation Wizard in Team Explorer to create a project or the TfsDeleteProject tool to delete one. | Ce message d'erreur permet d'indiquer que la modification en attente n'est pas prise en charge dans le dossier de projet d'équipe spécifié. |
TF10171 | The identity {0} is not a recognized Team Foundation Server identity. | Ce message d'erreur permet d'indiquer que l'identifiant spécifié n'est pas reconnu dans les identité de Team Foundation Server. |
TF10172 | The version number {0} is not found or supported. | Ce message d'erreur permet d'indiquer le numéro de version n'est pas reconnu ou supporté. |
TF10173 | More than one label named {0} was found. Specify a scope for the label. | Ce message d'erreur permet d'indiquer que plus d'un noms d'étiquette a été trouvé, spécifié un filtre pour l'étiquette. |
TF10174 | You do not have permission to delete the team project {0}. Contact your Team Foundation Server administrator and ask that the team project be deleted. | Ce message d'erreur permet d'indiquer que vous n'avez pas la permission de supprimer le projet d'équipe. |
TF10175 | The team project folder {0} does not exist. Contact your Team Foundation Server administrator and ask that it be created. | Ce message d'erreur permet d'indiquer que le dossier de projet d'équipe n'existe pas. |
TF10176 | The path for '{0}' exceeded the limit of 248 characters for a directory, or 260 for a directory and file name. | Ce message d'erreur permet d'indiquer que le chemin spécifié dépasse la limite de 248 caractères pour un répertoire ou 260 pour un dossier et un nom de fichier. |
TF10177 | The annotation {0} cannot be accessed through the public interface. It is reserved for internal use only. | Ce message d'erreur permet d'indiquer que l'annotation spécifié ne peut pas accéder à l'interface publique. |
TF10178 | The Team Foundation source control server {0} logging state has changed to {1} from {2} by {3}. | Ce message d'erreur permet d'indiquer que l'état du journal de bord du serveur de contrôle de source The Team Foundation spécifié a été modifié. |
TF10179 | The Team Foundation source control server {0} state has changed to {1} from {2} by {3}. | Ce message d'erreur permet d'indiquer que l'état du serveur de contrôle de source The Team Foundation spécifié a changé. |
TF10180 | The Team Foundation source control server {0} is not available. The server's state was changed to '{1}' on {2} with the comment "{3}". | Ce message d'erreur permet d'indiquer que le serveur de contrôle de source The Team Foundation spécifié n'est plus disponible. |
TF10181 | The Team Foundation source control server {0} started at {1} | Ce message d'erreur permet d'indiquer que le serveur de contrôle de source The Team Foundation spécifié débute à l'emplacement spécifié. |
TF10182 | The Team Foundation source control server {0} stopped at {1} | Ce message d'erreur permet d'indiquer que le serveur de contrôle de source The Team Foundation spécifié arrête à l'emplacement spécifié. |
TF10183 | Source control encountered an unexpected error: {0} | Ce message d'erreur permet d'indiquer que le contrôle de source a rencontré une erreur inattendue. |
TF10185 | The work item URL is null or empty. | Ce message d'erreur permet d'indiquer que l'URL de l'élément de travail est nulle ou vide. |
TF10186 | Source Control Explorer is unable to get check-in policy list from the server | Ce message d'erreur permet d'indiquer l'explorateur de contrôle de source n'est pas capable de demander la liste de politique de «Check-In» dans le serveur. |
TF10187 | Could not open document {0} | Ce message d'erreur permet d'indiquer qu'il n'est pas possible d'ouvrir le document. |
TF10190 | {0} has changed. Undo check-out and discard changes? | Ce message d'erreur permet d'indiquer que l'élément spécifié a changé, faut-il faire un «Check-Out» ou annulé le changement. |
TF10195 | Source control cannot branch from the root node. | Ce message d'erreur permet d'indiquer que le contrôle de source ne peut pas se brancher du noeud de la racine. |
TF10196 | Source control cannot branch to the root node. | Ce message d'erreur permet d'indiquer que le contrôle de source ne peut pas se brancher vers le noeud de la racine. |
TF10198 | Source control must branch into an existing team project. {0} is not a team project. | Ce message d'erreur permet d'indiquer que le contrôle de source doit être branché dans un projet d'équipe existant. |
TF10201 | Source control could not start the manual merge tool. | Ce message d'erreur permet d'indiquer que le contrôle de source n'a pas pu démarrer l'outil de fusion manuelle. |
TF10207 | Source control cannot open the Merge Wizard from a stand-alone client. | Ce message d'erreur permet d'indiquer qu'il n'est pas possible d'ouvrir l'assistant de fusion d'un client autonome. |
TF10208 | Source control cannot show differences for deleted files. | Ce message d'erreur permet d'indiquer que le contrôle de source ne voit pas de différence pour les fichier supprimés. |
TF10209 | Source control cannot show differences between the specified file and the local file. Either the local file doesn't exist or was not properly specified. | Ce message d'erreur permet d'indiquer que le contrôle de source ne voit pas de différence entre le fichier spécifié et le fichier local. |
TF10210 | Source control encountered an error during {0} operation: {1} | Ce message d'erreur permet d'indiquer que le contrôle de source a rencontré une erreur spécifié durant l'opération spécifié. |
TF10211 | {0}: Source control encountered the following error while initializing {1} | Ce message d'erreur permet d'indiquer que le contrôle de source a rencontré l'erreur suivante lors de l'initialisation. |
TF10212 | {0}: Source control encountered the following error while establishing subscriptions for {1} | Ce message d'erreur permet d'indiquer que le contrôle de source a rencontré l'erreur suivante lors de l'établissement des abonnements spécifiés. |
TF10213 | Source control encountered the following error while sending the check-in event to Team Foundation Core Services | Ce message d'erreur permet d'indiquer que le contrôle de source à rencontré l'erreur suivante lors de l'envoi d'un événement «Check-In» vers les services de Team Foundation Core. |
TF10216 | Team Foundation services are currently unavailable. Try again later. If the problem persists, contact your Team Foundation Server administrator. | Ce message d'erreur permet d'indiquer que les services de Team Foundation sont actuellement indisponible. |
TF10217 | Team Foundation was unable to complete your request due to an unexpected error. For more details, see the event log on the Team Foundation Server. | Ce message d'erreur permet d'indiquer que le Team Foundation n'a pas complété votre requête à cause d'une erreur inattendue. |
TF14000 | A critical error occurred while generating new download key. Shutting down the current AppDomain | Ce message d'erreur permet d'indiquer qu'une erreur critique s'est produit lors de la génération d'une nouvelle clef de téléchargement. |
TF14001 | The source control server state {0} has been set to '{1}' by an administrative action on {2} with the comment "{3}". | Ce message d'erreur permet d'indiquer que l'état du serveur de contrôle de source spécifié a été fixé à la valeur spécifié par une action administrative spécifié avec le commentaire spécifié. |
TF14002 | The identity {0} is not a member of the Team Foundation Valid Users group. | Ce message d'erreur permet d'indiquer que l'identité spécifié n'est pas un membre de groupe d'utilisateur valide de Team Foundation. |
TF14003 | You are not authorized to perform this operation. | Ce message d'erreur permet d'indiquer que vous n'êtes pas autorisé a faire la vérification du contrôle de source. |
TF14004 | The item {0} has not been checked in to source control yet. | Ce message d'erreur permet d'indiquer que l'élément spécifié n'est pas encore été vérifié dans le contrôle de source. |
TF14005 | Changes cannot be made to the root folder. | Ce message d'erreur permet d'indiquer qu'on ne peut pas faire des changements au dossier racine. |
TF14006 | You may not change the owner of a workspace. | Ce message d'erreur permet d'indiquer que vous ne pouvez pas changer le propriétaire d'un espace de travail. |
TF14007 | You may not cloak the root folder {0}. | Ce message d'erreur permet d'indiquer que vous ne pouvez pas masquer le dossier racine. |
TF14008 | Cannot delete team project folder {0} | Ce message d'erreur permet d'indiquer que vous ne pouvez pas effacer le dossier d'un projet d'équipe. |
TF14008 | Cannot delete team project folder {0} | Ce message d'erreur permet d'indiquer qu'il est impossible de supprimer le dossier du projet d'équipe. |
TF14009 | Cannot merge source '{0}' into target '{1}' because the target is underneath source. | Ce message d'erreur permet d'indiquer qu'il est impossible de fusionner la source spécifié dans la cible spécifié car la cible est sous la source. |
TF14010 | Cannot merge to '{0}' because a merge conflict already exists for this path. Run resolve to deal with the existing conflict. | Ce message d'erreur permet d'indiquer qu'il est impossible de fusionner car un conflit de fusion existe déjà pour ce chemin. Exécutez la résolution pour traiter le conflit existant. |
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 and then delete it. | |
TF14012 | Cannot undelete team project folder {0}. Please use the Project Creation Wizard to create a new team project and then undelete individual items as desired. | |
TF14013 | Cannot undelete '{0}' because you have already pended an undelete to it. | |
TF14014 | Cannot query effective item or global permissions for other users. | |
TF14015 | Cannot rename '{0}' back to its original path of '{1}'. Use undo instead. | |
TF14016 | Cannot resolve '{0}' because doing so requires doing an undelete which cannot be automated. | |
TF14017 | Cannot set a working folder mapping for {0} since you currently have a rename pending on the item. | |
TF14018 | The identity name {0} refers to a group; only user names can be specified when checking in for others. | |
TF14019 | The changeset {0} does not exist. | |
TF14020 | Could not pend change for item {0}. The change type {1} is not supported in this version. | |
TF14021 | '{0}' is before any changeset in the repository. | |
TF14022 | The deleted item {0} does not exist. | |
TF14023 | The specified download key length ({0}) is not valid. Defaulting to a {1} bit key. | |
TF14024 | The item {0} was specified more than once | |
TF14025 | The workspace cannot be created or updated because there were duplicate working folder mappings supplied. | |
TF14026 | You must specify at least one permission in the add, deny, or remove list or set the inheritance flag. | |
TF14027 | You must specify a changeset or a list of server paths, but not both. | |
TF14028 | Patch has been corrupted. | |
TF14029 | Error decoding the patch. | |
TF14030 | Error encoding the patch. | |
TF14031 | Failure using imagehlp. | |
TF14032 | Invalid options were passed to the patch library. | |
TF14033 | Patch is in a newer format. | |
TF14034 | Patch not necessary. | |
TF14035 | Retain ranges differ. | |
TF14036 | File versions are identical. | |
TF14037 | Attempted to apply patch for wrong file. | |
TF14038 | The fileCacheRoot configuration value was not provided. File caching will be disabled. | |
TF14039 | The folder {0} may not have content uploaded. | |
TF14040 | The folder {0} may not be checked out. | |
TF14041 | The folder {0} is mapped more than once. | |
TF14042 | Specified date occurs in the future. Use a tip version specification instead. | |
TF14043 | An error occurred computing the delta for item {0} version {1}. | |
TF14044 | Access Denied: User {0} needs the {1} global permission(s). | |
TF14045 | The identity {0} is not a recognized identity. | |
TF14047 | The comment exceeds the maximum allowed length of {0} characters. | |
TF14048 | The field name '{0}' may not exceed 64 characters. | |
TF14049 | The policy name '{0}' may not exceed 256 characters. | |
TF14050 | Cannot change item {0} because it already has a pending change that is not compatible. | |
TF14051 | All requests types for PendChanges must be identical. Expected: {0} Actual: {1} | |
TF14052 | Cannot specify AcceptYours to resolve a namespace conflict. | |
TF14053 | Cannot specify AcceptYoursRenameTheirs on non-namespace conflicts. | |
TF14054 | The Encoding {0:d} is not valid. The client should never send this value. | |
TF14055 | The identity {0} is not a recognized domain identity. | |
TF14056 | The process id {0} does not exist. | |
TF14057 | The project {0} must be a top level folder. | |
TF14058 | Patch not available. | |
TF14059 | Unable to process the pending changes requested. The set of pending renames would cause a name collision for {0}. | |
TF14060 | The folder {0} cannot be deleted. One or more children have pending changes. | |
TF14061 | The workspace {0} does not exist. | |
TF14062 | Cannot merge to an item '{0}' that is cloaked. | |
TF14063 | Cannot check in partial undelete of {0}. You must check in all items from the undelete operation. | |
TF14064 | Could not find label {0}. | |
TF14065 | Cannot lock {0} for checkin when multiple checkout is disabled. | |
TF14066 | You must have the target '{0}' of the merge locally. | |
TF14067 | The item {0} could not be found in the {1} workspace. | |
TF14068 | No matching items found in {0} in the {1} workspace. | |
TF14069 | Cannot resolve rename conflict between your item {0} and the server item {1} without an explicit destination. | |
TF14070 | Cannot resolve a conflict with AcceptMerge when {0} was deleted on the server. Please choose AcceptTheirs or AcceptYours for this conflict. | |
TF14071 | An error occurred while accessing {0}; information for this artifact was not returned. | |
TF14072 | The contents of the file {0} must be uploaded before it can be checked in. | |
TF14073 | The stored download key is not valid. The key will be regenerated. | |
TF14074 | The file type {0} has already configured in this call. Each file type specified must have a unique name. | |
TF14075 | When creating or updating a shelveset, the owner specified must be the same as the user that is creating or updating the shelveset. | |
TF14076 | Cannot create the label {0} because it has child labels. Use /child:replace or /child:merge. | |
TF14077 | The owner of a label cannot be changed. | |
TF14078 | The mapped local path for '{0}' exceeded the limit of 248 characters for the directory or 260 for the directory and filename. | |
TF14079 | The item {0} is not part of your workspace. Please perform a get operation on this item. | |
TF14080 | The item '{0}' has a pending merge conflict, run resolve before checking in. | |
TF14081 | The item '{0}' could not be merged into the target tree because no related item in the target tree could be found. Consider using the branches command to locate directly related items, consider using /baseless, or reformulate your merge request. | |
TF14082 | Cannot lock item {0} for merging. This item is checked out to another workspace. | |
TF14083 | The item '{0}' has a pending merge from the current merge operation, please resolve and check in the current merge and merge again to pick up this change. | |
TF14084 | Cannot merge {0} to {1} because a parent of {1} has a pending delete. | |
TF14085 | Cannot merge {0} to {1} because there is an incompatible pending change (not edit or encoding) at {1} already. | |
TF14086 | Cannot merge {0} to {1} because there is an unrelated item at {1}. | |
TF14087 | Cannot undelete '{0}' because not all of the deletion is being undeleted. | |
TF14088 | '{0}' must be checked in because it is a rename or an undelete. | |
TF14089 | Cannot undelete the item {0}, {1} was deleted and needs to be undeleted. | |
TF14090 | Cannot unlock {0}. It is not currently locked in your workspace. | |
TF14091 | You cannot perform this operation on workspace {0} because you are not the owner of the workspace. | |
TF14092 | The item {0} cannot be changed. A parent of this item has a pending delete which must be checked in first. | |
TF14093 | The item '{0}' has a pending merge conflict, please run resolve before pending a change against it. | |
TF14094 | Unable to find content for the specified pending change {0} | |
TF14095 | The performance counters could not be initialized. Note that the system will continue to run without maintaining performance counter values. | |
TF14096 | Failed to load the team project cache. Team project methods are not available. | |
TF14097 | Cannot rename {0} when it has a working folder mapping assigned to it. | |
TF14098 | Access Denied: User {0} needs {1} permission(s) for {2}. | |
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 dependant rename. {0} | |
TF14101 | The item {0} cannot be moved into an unmapped location because it (or one of its children) is checked out. | |
TF14101 | The range parameter was not correctly formatted. | |
TF14102 | Resolve failure: The item {0} was in the way of undeleting a set of changes. | |
TF14103 | Internal error: The database procedure {0} returned the wrong number of rows. | |
TF14104 | Unknown merge error: Source: {0}, Target: {1}, error number: {2} | |
TF14105 | An exception occurred in the Team Foundation Source Control System. | |
TF14105 | The initial permission (item and global) permission assignments cannot be made. | |
TF14106 | Cannot create or update workspace {0}, the computer name is required for all workspaces. | |
TF14107 | The changes could not be checked in due to an incompatible change in another workspace. | |
TF14108 | The compressed file is not in a supported compression format. | |
TF14109 | Parts of the file {0} were not uploaded. | |
TF14110 | Cannot undo change on {0} because it would conflict with the {4} lock on {1} owned by {2} in workspace {3}. | |
TF14111 | Delta is longer than the original. | |
TF14112 | Cannot branch {0} to {1} because a parent of {1} has a pending delete. | |
TF14113 | Cannot branch {0} to {1} because there is an unrelated item at {1}. | |
TF14114 | Cannot unshelve {0} because a parent of {0} has a pending delete. | |
TF14115 | You can not branch from a workspace version spec {0} when the workspace contains a pending delete {1} underneath the source of the branch. Please either shelve or undo the delete and try the branch again. | |
TF14116 | You can not merge to a workspace version spec {0} when the workspace contains a pending delete {1} underneath the source of the merge. Please either shelve or undo the delete and try the merge again. | |
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 {1} cannot be computed. | |
TF14119 | Cannot merge a delete of {0} to {1} because one of its children has been moved to another location. | |
TF14120 | Cannot unshelve a delete of {0} because one of its children has been moved to another location. | |
TF14121 | The changes previously made to {0} that have not been merged will be discarded by merging the deletion of {1}. | |
TF15000 | Port number is empty or is not valid. Please enter an integer between 1 and 65535. | |
TF15001 | Server name cannot contain '/', ':' or start with 'http' or 'https'. | |
TF15002 | Server name cannot be empty. | |
TF15003 | The cache root specified in the fileCacheRoot configuration value must be an absolute (rooted) path. File caching will be disabled. | |
TF15004 | The download request signature has expired. | |
TF15005 | The request file ID was malformed. | |
TF15006 | The request file ID was missing or empty. | |
TF15007 | The request server ID was missing or empty. | |
TF15008 | The request signature was missing or empty | |
TF15009 | The proxy could not validate the request signature. | |
TF15010 | The request timestamp is malformed. | |
TF15011 | The request timestamp was missing or empty. | |
TF15012 | Unknown proxy exception. | |
TF15013 | The requested Team Foundation Server is not registered with the proxy server. | |
TF15014 | CommitPath not set - unable to commit file to proxy | |
TF15015 | Metadata file not in expected format: {0} | |
TF15016 | Server not initialized. | |
TF15017 | An unknown error occurred while performing a get operation. | |
TF15018 | An error occurred while committing the files to the cache. | |
TF15019 | An error occurred while attempting to start the download thread. | |
TF15020 | A proxy cache miss turned into a cache hit. Performing second chance cache hit detection. | |
TF15021 | Redirecting the client to the Team Foundation Source Control server. | |
TF15022 | Invalid CacheRoot folder. | |
TF15023 | Invalid CacheLimit. | |
TF15024 | Invalid CacheLimitPercent. Value should be in the range of 0-100 | |
TF15025 | Invalid CacheDeletionPercent. Value should be in the range of 0-100 | |
TF15026 | The application tier failed to respond to the request in a timely manner. | |
TF15027 | The value provided for the "{0}" configuration node is invalid. The value should be in the range from {1} to {2}. Using the default value: {3}. | |
TF15028 | An error occurred while downloading a file from the application tier. | |
TF15029 | Unable to parse the Uri node of the configuration file. Expected a valid absolute Uri but read "{0}". | |
TF15030 | The configuration file was missing the server Uri node. Expected a node such as <uri>https://sourceControlServer:1234/SourceControl</uri> | |
TF15031 | Configuration value "{0}" must be numeric. The value read was: "{1}". Using the default value "{2}" | |
TF15032 | The proxy configuration file has no registered servers. | |
TF15033 | The proxy statistics XML file is missing the {0} node. Statistics for this server will not be used. | |
TF15034 | The metadata file {0} was missing the required value: {1} | |
TF15035 | CacheLimit calculation resulted in invalid value : {0}, defaulting to 1GB limit | |
TF15036 | An error occurred while computing statistics for : {0} | |
TF15037 | An error occurred while determining cache cleanup list for : {0} | |
TF15038 | An error occurred while reading proxy statistics xml file. The Performance Counter values are defaulted to 0. | |
TF15039 | The proxy configuration file has duplicate {0} node. Proxy will ignore the duplicate and continue normally. | |
TF15040 | The statistics file has been tampered. TotalDownloadRequests cannot be less than TotalCacheHits. CacheHit and TotalDownloadRequests performance counters will be reset to zero. | |
TF15041 | Error occurred while trying to retrieve ProxyConfig.xsd. | |
TF15042 | Unable to download the file from the server : {0} | |
TF15043 | A critical error occurred while processing Proxy.config. Shutting down the current AppDomain | |
TF20001 | The value for field '{0}' is not a recognized date. | |
TF20003 | Could not validate one or more e-mail addresses. Correct the e-mail addresses and try again. | |
TF20004 | Could not find the specified file "{0}". Check the file name and try again. | |
TF20005 | Could not find the specified directory. | |
TF20006 | Could not save the query. | |
TF20007 | The value for Width is not supported. Choose a Width between 0 and 65536. | |
TF20008 | The value for field '{0}' is not supported. Specify the value as a decimal number. | |
TF20009 | The value for field '{0}' is not supported. Specify the value as a whole number between -2147483648 to 2147483647. | |
TF20010 | The value for field '{0}' has unsupported characters. | |
TF20012 | Field '{0}' cannot be empty. | |
TF20013 | Field '{0}' cannot be empty, and must be different from the original value. | |
TF20014 | The value for field '{0}' is not in a recognized format. | |
TF20015 | The field '{0}' contains a value that is not in the list of supported values. | |
TF20016 | The value for field '{0}' must be updated, the current value is no longer supported. | |
TF20017 | The area or iteration provided for field '{0}' could not be found. | |
TF20018 | The field '{0}' is unsupported because of a value in another field. | |
TF20019 | The field '{0}' is unsupported because a value is missing in another field. | |
TF20022 | Zero is not a supported work item ID. Enter a positive integer and try again. | |
TF20024 | The work item ID must be a positive integer. | |
TF20026 | A work item cannot contain a related link to itself. | |
TF20027 | Could not open the link. | |
TF20028 | Could not open the link. The linked item may not be registered in the system. | |
TF20029 | The query is not complete. Please correct and try again. | |
TF20032 | The operator for row {0} is not recognized or missing. | |
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 the area '{0}'. Change the value for field '{1}' to an area where you have write permissions. | |
TF24000 | Cannot make a copy of this query. The file name must be unique. | |
TF24001 | Field '{0}' has an unsupported value. | |
TF24003 | The query name you entered contains unsupported characters. Supply another name and try again. | |
TF24005 | Could not open query '{0}'. | |
TF24006 | Could not open query results '{0}'. | |
TF24008 | Could not open work item '{0}'. | |
TF24011 | You are not currently connected to a Team Foundation Server. | |
TF24016 | Cannot find team project '{0}'. | |
TF24017 | Could not find query {0} in team project {1}. | |
TF24018 | Team Foundation Server Configuration Failure. Team project '{0}' already exists on this Team Foundation Server. | |
TF24021 | Team Foundation Server Configuration Failure. No registration entries for tool: {0}. | |
TF24023 | Team Foundation Server Configuration Failure. The New Team Project Wizard work item component could not connect to the Team Foundation Server {0}. | |
TF24041 | Unsupported service URL for ServiceInterface "{0}" registered to tool "{1}" | |
TF24042 | You do not have permission to create work items in project '{0}'. Contact your Team Foundation System administrator. | |
TF26000 | Could not connect to the Team Foundation Server. Check that you have a network connection and that your Team Foundation server is available. | |
TF26002 | Team Foundation does not support comments over {0} characters long. Shorten your comment and try again. | |
TF26003 | Team Foundation could not find the file. Check the file name and path and try again. | |
TF26006 | Team Foundation could not find {0}. | |
TF26007 | Team Foundation could not find {0} for the path {1}. | |
TF26009 | Team Foundation does not support sorting by this field. | |
TF26012 | Cannot connect to Team Foundation Server. | |
TF26016 | The field {0} has been defined more than once in the work item type definition file. Remove or rename one of the definitions and try again. | |
TF26018 | The global list '{0}' is defined more than once in the work item type definition file. Remove one of the definitions and try again. | |
TF26019 | The global list '{0}' appears more than once in the list of values. Remove the redundant references and try again. | |
TF26022 | The list contains a duplicate value {0}. Remove the duplicate and try again. | |
TF26024 | The transition from '{0}' to '{1}' has a duplicate reason {2}. Remove the duplicate reason and try again. | |
TF26025 | The field '{0}' already exists in the collection. | |
TF26026 | A field definition ID {0} in the work item type definition file does not exist. Add a definition for this field ID, or remove the reference to the field ID and try again. | |
TF26027 | A field definition {0} in the work item type definition file does not exist. Add a definition for this field, or remove the reference to the field and try again. | |
TF26028 | A field definition in the work item type definition file does not exist. Add a definition for this field, or remove the reference to the field and try again. | |
TF26031 | The Team Foundation Server returned a field type that was not recognized. | |
TF26032 | The field specified by ID {0} does not exist in this work item type. Remove the reference or correct the work item type definition and try again. | |
TF26033 | The field {0} does not exist in this work item type. Remove the reference or correct the work item type definition and try again. | |
TF26035 | The definition for the field {0} was not found. Add a definition for this field and try again. | |
TF26036 | Team Foundation does not support querying on this field '{0}'. Change your query and try again. | |
TF26037 | Rule '{0}' is declared for the field '{1}' and references the same field. | |
TF26038 | Field type for {0} does not match the existing type. It was {1}, but now is {2}. | |
TF26039 | Field value overflow. | |
TF26041 | Global list '{0}' does not exist in this database. | |
TF26045 | The field '{0}' has the 'Reportable' attribute set to 'Detail', but its field type does not support this attribute. This attribute supports the following field types: Integer, Double, String, or DateTime. Change this attribute for the field, or change the field type and try again. | |
TF26046 | The field '{0}' has the 'Reportable' attribute set to 'Dimension', but its field type does not support this attribute. This attribute supports the following field types: Integer, Double, String, or DateTime. Change this attribute for the field, or change the field type and try again. | |
TF26047 | The field '{0}' has the 'Reportable' attribute set to 'Measure', but its field type does not support this attribute. This attribute supports the field types 'Integer' and 'Double'. Change this attribute for the field, or change the field type and try again. | |
TF26048 | The rule '{0}' for field '{1}' refers to field '{2}', which is a different field type. Change the field type or the field reference so that the field referred to is the same type and try again. | |
TF26049 | The field '{0}' has rules '{1}' and '{2}' that are inconsistent. | |
TF26050 | The work item type definition has a definition for field '{0}' that is a reserved system field name and cannot be used. Rename or remove this field definition and try again. | |
TF26051 | The field name '{0}' is not a supported field name. | |
TF26051 | The field name '{0}' is not a supported field name. | |
TF26052 | Attempt to set the field to an unsupported value. | |
TF26054 | The last write time of this stored query is not recognized. | |
TF26055 | The value '{0}' is not supported for the field type of field '{1}'. | |
TF26056 | This operation is not supported on an open work item | |
TF26057 | This operation is not supported on a parameterized query | |
TF26058 | The query ID is not recognized. | |
TF26059 | The query name is not recognized. | |
TF26060 | The query text is not recognized. | |
TF26061 | '{0}' is not a recognized reference field name. | |
TF26061 | '{0}' is not a supported reference field name. | |
TF26062 | Rule '{0}' is not supported for the field '{1}'. | |
TF26063 | '{0}' is not in the list of supported states. | |
TF26064 | The query is not recognized. | |
TF26065 | The project hierarchy node is not recognized. | |
TF26066 | The URL is not recognized. | |
TF26071 | This work item has been updated in the work item database. Open the latest revision. | |
TF26073 | This operation cannot be performed on an item that has not yet been saved. | |
TF26079 | Team Foundation does not support link comments over {0} characters long. Shorten the comment and try again. | |
TF26083 | The state '{0}' is defined more than once in the work item type definition (WITD) file. Remove or rename the duplicate state and try again. | |
TF26084 | The attachment could not be added because the work item already has the maximum number of supported attachments {0}. Remove attachments that are no longer being used and try again, or create a link to the file instead. | |
TF26085 | Unknown constant with id {0}. | |
TF26154 | Work item type Import failed. | |
TF26155 | You are not a recognized Team Foundation administrator in the current team project. Contact the Team Foundation Server administrator. | |
TF26156 | You are not a recognized administrator in the current team project. Contact another Team Foundation Server administrator to request permissions to this team project. | |
TF26157 | You are not a recognized user in the current team project. Contact your Team Foundation Server administrator to request permissions to this team project. | |
TF26158 | The query has too many levels of nesting. Restructure the query and try again. | |
TF26159 | The request cannot be canceled. | |
TF26160 | The Team Foundation Server work item database is in read-only mode. It may be offline for system administration. Try again later or contact your Team Foundation Server administrator. | |
TF26161 | You have been denied permissions to the SQL Server database. Team Foundation Server is not properly configured. Contact your Team Foundation Server administrator. | |
TF26163 | Team Foundation does not support query descriptions over {0} characters long. Shorten the description and try again. | |
TF26167 | The query name was empty. Add a query name and try again. | |
TF26168 | Team Foundation does not support query names over {0} characters long. Shorten the query name and try again. | |
TF26169 | Query name cannot be empty | |
TF26171 | User/group '{0}' is not found. | |
TF26173 | Team Foundation could not connect to the application tier. Check that you have a network connection and that the Team Foundation Server is available. If the problem persists, contact your Team Foundation Server administrator. | |
TF26173 | Team Foundation could not connect to the application tier. Check that you have a network connection and that the Team Foundation Server is available. If the problem persists, contact your Team Foundation Server administrator. | |
TF26174 | Team Foundation timed out trying to connect to the server. Check that you have a network connection and that the Team Foundation Server is available. If the problem persists, contact your Team Foundation Server administrator. | |
TF26175 | Team Foundation Core Services attribute '{0}' not found. | |
TF26176 | Team Foundation could not find the registration for the application server URL. Contact your Team Foundation Server administrator. | |
TF26176 | Team Foundation could not find the registration for the application server URL. Contact your Team Foundation Server administrator. | |
TF26177 | The field {0} cannot be renamed from '{1}' to '{2}'. Team Foundation does not support renaming fields. | |
TF26178 | Field type '{0}' can be used only with the '{1}' field. | |
TF26179 | Field type '{0}' can be used only with '{1}' and '{2}' fields. | |
TF26180 | A work item with this ID already exists in the work item database. | |
TF26181 | This work item already has a duplicate link. | |
TF26182 | This operation is not supported on revision history items. | |
TF26184 | The default namespace is unrecognized. It must be either empty or set to '{0}', but it is set to '{1}'. | |
TF26185 | Team Foundation does not support link paths over {0} characters long. Shorten the link path and try again. | |
TF26186 | The project hierarchy node '{0}' was not found. | |
TF26188 | Access Denied: You must be a Team Foundation administrator. | |
TF26191 | The query name already exists. Rename the query and try again. | |
TF26192 | The team project specified by the ID {0} does not exist. Check the team project ID and try again. | |
TF26193 | The team project {0} does not exist. Check the team project name and try again. | |
TF26194 | The value for this field cannot be changed. | |
TF26195 | The related work item does not exist. | |
TF26196 | Team Foundation does not support relating a work item to itself. Select a different related work item. | |
TF26198 | The work item does not exist, or you do not have permission to access it. | |
TF26199 | Cannot connect to a different server for a work item store that has successfully connected to a Team Foundation Server | |
TF26201 | This work item has unsupported fields, or user does not have permissions. | |
TF26202 | Validation failed. Field '{0}' not supported. | |
TF26203 | Could not import the project hierarchy. | |
TF26204 | The account you entered is not recognized. Contact your Team Foundation Server administrator to add your account. | |
TF26205 | Workitem Type Import failed. Unsupported field name. | |
TF26205 | Workitem Type Import failed. Unsupported field reference name. | |
TF26206 | Workitem Type Import failed. Unsupported Field Type. | |
TF26207 | Workitem Type Import failed. Unrecognized project. | |
TF26208 | The item does not exist, or you do not have permission to it. | |
TF26209 | The work item linked to as a related link does not exist. | |
TF26210 | '{0}' is not a supported reference field name. Only reference field names can be used in stored queries. | |
TF26212 | Team Foundation Server could not save your changes. There may be problems with the work item type definition. Try again or contact your Team Foundation Server administrator. | |
TF26213 | Saving work items failed. Check the log for more details. | |
TF26213 | Too many new fields. You are trying to create {0} field(s), while the server has space for {1} of them. | |
TF26214 | Cannot save the work item. Fields with errors: {0} | |
TF26214 | State '{0}' is specified in source and destination states in the transition. These states must be different. | |
TF26215 | Cannot save the work item. | |
TF26215 | Transition from state '{0}' to state '{1}' (for='{2}', not='{3}') is defined more than once. | |
TF26216 | The form '{0} element has mutually exclusive attributes '{1}' and '{2}'. | |
TF26217 | The form '{0}' element has neither '{1}' nor '{2}' attributes. | |
TF26218 | Field names {0} and {1} map to the same field name {2} in reporting and cannot be used together. | |
TF30001 | Team Explorer could not retrieve a list of projects from the Classification Service. Contact your Team Foundation Server administrator. | |
TF30002 | The New Team Project Wizard encountered an error deleting the project {0} | |
TF30004 | The New Team Project Wizard encountered an unexpected error while initializing the {0} plug-in. | |
TF30005 | The New Team Project Wizard group security component could not connect to the Team Foundation Server {0}. | |
TF30006 | Artifact destinationId does not define a valid URI or artifactId. ArtifactId: {1} from Group {0} | |
TF30009 | The New Team Project Wizard was not able to open the project creation log file. | |
TF30012 | Team Foundation cannot set AllWorkItemTypesText to null or empty string. | |
TF30013 | Team Foundation cannot set PickItemsFromRadioLabel to null or empty string. | |
TF30014 | Duplicate name for the SQL Server Reporting Services site on server {0}. | |
TF30015 | The New Team Project Wizard could not connect to the specified SQL Server Reporting Services server {0}. | |
TF30016 | You do not have permission to create a new SQL Server Reporting Services site on the server {0}. | |
TF30017 | Team Explorer cannot connect to Team Foundation Server {0}. The security certificate is either not installed, misconfigured, or expired. | |
TF30018 | Team Explorer could not find the Reporting Service XML node | |
TF30019 | The Group Security Service on the Team Foundation Server did not return any user identity information | |
TF30020 | The New Team Project Wizard was not able to load the information from the process template. | |
TF30021 | Duplicate name for the site on Windows SharePoint Services server {0}. | |
TF30022 | The New Team Project Wizard could not connect to the Windows SharePoint Services server {0}. | |
TF30025 | Application error | |
TF30026 | You cannot change the file name extension using Team Explorer. Do you want to continue? | |
TF30027 | Team Explorer encountered an error adding the document library. | |
TF30028 | Team Explorer encountered an error deleting the document library. | |
TF30030 | Team Explorer could not connect to Team Foundation Server. | |
TF30031 | Team Explorer cannot open the document because the WebClient service is not running. | |
TF30032 | The New Team Project Wizard common structure component could not connect to the Team Foundation Server {0}. | |
TF30034 | You do not have permission to create a new team project. | |
TF30037 | The Classification Service task XML is missing the Nodes node | |
TF30039 | The count threshold must be between {0} and {1}, inclusive. | |
TF30040 | The database is not correctly configured. Contact your Team Foundation Server administrator. | |
TF30041 | Team Foundation Server could not connect to the database. Contact your Team Foundation Server administrator. | |
TF30042 | The database is full. Contact your Team Foundation Server administrator. | |
TF30043 | You must specify an event log source for your application. | |
TF30045 | The instance information has not been configured or is not available for this Team Foundation Server. Please contact your Team Foundation Server administrator. | |
TF30046 | The instance information does not match. Team Foundation expected {0} but found {1}. Please contact your Team Foundation Server administrator. | |
TF30047 | The log level {0} specified in the configuration file is not a recognized log level. | |
TF30048 | The file {0} specified to store the trace output could not be found or created. Confirm that the file name is correct and that your user account has permission to access the file: {1} | |
TF30049 | Team Foundation Server encountered an error initializing listener {0}. | |
TF30050 | The listener {0} issued an exception while submitting records to the database. | |
TF30051 | The log age parameter specified in the configuration file {0} is not recognized, and the default value is being used instead. | |
TF30053 | You must supply a Team Foundation event log object. | |
TF30054 | You must set the event log source, instance, and Watson reporting name. | |
TF30055 | Visual Studio could not find or read the Team Foundation Server server name in the configuration file. Contact your Team Foundation Server administrator. | |
TF30057 | The database log connection string is null or empty. | |
TF30058 | Unable to execute a resultset stored procedure, no stored procedure was prepared | |
TF30059 | Fatal error while initializing web service | |
TF30060 | A system error occurred while submitting a record. No action is required to correct. | |
TF30061 | The trace switch {0} is not a valid Team Foundation Server trace switch. | |
TF30062 | An error occurred while manipulating the trace state of the application | |
TF30063 | You are not authorized to access {0}. | |
TF30064 | You are not authorized to access the server. | |
TF30065 | An unhandled exception occurred. | |
TF30066 | The web method table has not been initialized. | |
TF30067 | The web method enum is not in the web method table. | |
TF30068 | An exception has occurred in a Team Foundation component: {0} | |
TF30069 | An unexpected condition has occurred. | |
TF30070 | An unexpected condition has occurred in the Team Foundation server. Information about the condition has been gathered. | |
TF30071 | Unable to create and file a Watson report. | |
TF30072 | The Team Foundation Server trial period has expired or its license is otherwise invalid. Install a licensed edition of Team Foundation Server to continue | |
TF30072 | You cannot modify the service for type {0}. | |
TF30073 | The string must have at least one character. | |
TF30075 | Team Foundation could not find the specified root folder or the folder is missing. | |
TF30076 | The server name <server> provided does not correspond to a server URI that can be found. Confirm that the server name is correct. | |
TF30076 | The server name or Uniform Resource Identifier (URI) you typed, {0}, cannot be resolved to a Team Foundation server. If you type a server name, it must match the name you typed in the Add Team Foundation Server dialog. If you type a URI, it must use the following syntax: http[s]://<server name>:<server port> | |
TF30078 | Team Foundation could not open the dialog because the threading model must be single-threaded apartment. | |
TF30079 | A list, survey, discussion board, or document library cannot have the same name as another list, survey, discussion board, or document library in this Web site. Type a new name. | |
TF30079 | Team Explorer encountered the following error while creating a new document from template '{0} : {1}' | |
TF30080 | Team Explorer encountered the following error while copying folders or files: {0} | |
TF30081 | Team Explorer encountered an error while deleting the document or folder. | |
TF30082 | Team Explorer encountered the following error while launching a document: {0}. | |
TF30083 | Team Explorer encountered an error while uploading the file {0}. This error can be caused by either the web service timing out, a problem with the network connection to the Team Foundation Server, or you attempted to upload a file type that is not supported by Windows SharePoint Server. | |
TF30084 | Team Explorer could not find the file on the Windows SharePoint Services site. | |
TF30085 | Team Explorer could not create a new folder. | |
TF30090 | Team Explorer encountered an error renaming document or folder. | |
TF30091 | Your Favorites cache file '{0}' is corrupted. | |
TF30092 | Team Explorer encountered an error getting the name of the node. | |
TF30093 | Team Explorer could not find the favorite {0}. | |
TF30094 | A favorite item named {0} already exists. | |
TF30095 | This folder already contains a link named '{0}'. Would you like to replace it? | |
TF30100 | Team Foundation cannot set PrivateQueriesText to null or empty string. | |
TF30100 | Project creation failed with error: {0} | |
TF30101 | Team Foundation cannot set PublicQueriesText to null or empty string. | |
TF30102 | Team Foundation cannot set QueryRadioLabel to null or empty string. | |
TF31003 | You are not authorized to access https://[client].visualstudio.com | Ce message d'erreur permet d'indiquer que les ressources ne sont pas disponibles pour les accès au site Web https://[client].visualstudio.com. |
TF30104 | Team Foundation cannot set RunButtonLabel to null or empty string. | |
TF30105 | Team Foundation cannot set SelectAQueryText to null or empty string. | |
TF30107 | Team Foundation cannot set WorkItemTypeLabel to null or empty string. | |
TF30108 | This folder already contains a report named '{0}'. Would you like to replace it? | |
TF30109 | Team Explorer encountered an error during the renaming. Try your change again. | |
TF30123 | Error while deleting template | |
TF30124 | Error occurred during launching log file | |
TF30125 | Error occurred during retrieving templates data | |
TF30126 | Failed to download process template. {0} | |
TF30127 | Export Failed. Reason: {0} | |
TF30128 | Failed to get Team Foundation Server host. | |
TF30129 | Failed to upload process template. | |
TF30132 | Process template size exceeds {0} MB. Unable to upload process template. | |
TF30135 | The Process Template Manager can not upload the process template from '{0}' because the folder does not contain a valid process template. A valid process template includes the file ProcessTemplate.xml as well as other necessary files. Correct the process template, or select a different folder and try again. | |
TF30136 | The Process Template Manager can not download the template to '{0}' because there is already a subfolder with the name '{1}'. The Process Template Manager must be able to create a new subfolder with the same name as the process template. Select a different destination folder, or rename the conflicting sub-folder and try again. | |
TF30139 | The process template is not configured properly. | |
TF30144 | The New Team Project Wizard attempted to roll back all of the steps taken to this point but was unsuccessful. Contact your Team Foundation Server administrator for further instructions. | |
TF30146 | The New Team Project Wizard could not retrieve the confirmation values from the plug-in. Close the wizard and try creating the team project again. If the problem persists, review the log file for additional information and contact the provider of the plug-in. | |
TF30147 | The New Team Project Wizard could not retrieve the confirmation values because of the error: {0} Close the wizard and try creating the team project again. If the problem persists, review the log file for additional information and contact the provider of the plug-in. | |
TF30150 | Duplicate name for the team project. | |
TF30155 | Error occurred while trying to create project : "{0}" | |
TF30156 | Error occurred while updating project properties for : "{0}" | |
TF30157 | Invalid node name | |
TF30158 | Invalid property name | |
TF30160 | The artifact {0} declared in task "{2}" from group "{1}" is not published. | |
TF30162 | Task "{1}" from Group "{0}" failed | |
TF30164 | Deleting directory "{0}" failed | |
TF30165 | The temporary folder {0} used to store the process template does not exist and, therefore, could not be deleted. | |
TF30167 | The New Team Project Wizard could not finish creating the project {0}. | |
TF30168 | The New Team Project Wizard experienced a failure checking your permissions to create projects. | |
TF30169 | The New Team Project Wizard was unable to download the process template {0}. | |
TF30170 | The plug-in {0} failed during task {1} from group {2}. | |
TF30171 | The {0} plug-in used to create the new team project could not be initialized and returned the following error: {1}. | |
TF30172 | You do not have permission to create a new team project. | |
TF30173 | No well formed process template folder name to delete | |
TF30174 | A ProjectCreatedEvent handler failed with an Exception | |
TF30175 | Process template validation failed | |
TF30177 | Team Project Creation Failed | |
TF30181 | Error occurred while adding access entry : action name: "{0}" sid: "{1}" deny: "{2}" retrying ... | |
TF30182 | Error occurred while getting list object class actions for : "{0}" | |
TF30183 | Error occurred while creating application group for : "{0}" retry #: {1} | |
TF30184 | Error occurred while trying to get list of structures for: "{0}" retrying ... | |
TF30185 | The action {0} you requested is not available for the object {1}. This error usually occurs when a process template is being loaded and the template requests an action that is not applicable to the target object. Contact your Team Foundation Server administrator or the provider of the process template. | |
TF30186 | The XML in the process template is malformed. The process template must contain a single Groups node. Contact the provider of the template to correct the XML, upload a new copy of the template to the Team Foundation Server, and try again. | |
TF30187 | The permission {0} does not match the list of permissions required by the XML schema. Contact the provider of the template to correct the XML, upload a new copy of the template to the Team Foundation Server, and try again. | |
TF30188 | The team project URI returned from {0} is either a null or empty string or not a recognized URI. Try again. If the problem persists, review the event log for additional information and call Microsoft Product Support Services. | |
TF30189 | The process template contains a cycle in dependencies. | |
TF30190 | The process template contains a duplicate artifact ID: artifactId {2} in Task {1} from Group {0}. | |
TF30191 | The dependency {0} in the process template is not correct. | |
TF30192 | Process template metadata references invalid or not registered plugin '{0}'. | |
TF30193 | The process template provided is not recognized. Contact your Team Foundation Server administrator. | |
TF30194 | The ProcessTemplate.xml does not conform to schema. | |
TF30195 | The source artifact referenced in group "{0}" is not defined in the process template. | |
TF30196 | Tasks file for the group "{0}" failed schema validation. | |
TF30198 | Engine failure while processing the completion of the task "{0}" from group "{1}". No further tasks will be executed | |
TF30199 | Critical project creation execution failure | |
TF30200 | Process template did not contain any tasks | |
TF30201 | Group {0} Task "{1}" will not be run because the user has cancelled execution | |
TF30202 | Task "{1}" from Group "{0}" will not be run because a prior task failed. | |
TF30203 | The destination id '{0}' for the link is either invalid or not previously defined. | |
TF30204 | The source artifact id "{0}" for the link is not previously defined. | |
TF30207 | Initialization for plugin "{0}" failed | |
TF30210 | The plug-in does not support linking. | |
TF30211 | The New Team Project Wizard could not create the team project because a valid project URI was not returned. | |
TF30212 | The New Team Project Wizard could not create the team project. | |
TF30214 | The ProjectCreated property must have a value of true before you can invoke this property. | |
TF30215 | The New Team Project Wizard finished creating team project, but there was an error updating the user interface. | |
TF30217 | New Team Project Wizard discontinued due to the following error and is removing the partially created team project from the server. This may take several minutes or longer depending on the status of your team project. | |
TF30218 | Out of memory while processing the completion of task "{0}" from group "{1}", no further tasks will be executed. | |
TF30220 | Error occurred creating data source {0} | |
TF30221 | File '{0}' does not exist | |
TF30222 | The New Team Project Wizard could not find the data source TfsOlapReportDS on the SQL Server Reporting Services server {0}. Contact the administrator for the server and confirm that your user account has Content Manager permission to create reports. If the problem persists, contact your Team Foundation Server administrator and ask that Team Foundation Server be repaired. | |
TF30224 | Failed to retrieve projects from the report server. Please check that the SQL Server Reporting Services Web and Windows services are running and you have sufficient privileges for creating a project. | |
TF30225 | Error uploading report : {0} | |
TF30226 | User did not have project creation permissions | |
TF30227 | Project creation permissions retrieved | |
TF30229 | Failure retrieving user information | |
TF30230 | Malformed template metadata XML for template "{0}" | |
TF30234 | Process template data returned from Team Foundation Server as null | |
TF30235 | Null template header data returned from Team Foundation Server | |
TF30243 | Process template returned with no data (zero length) | |
TF30244 | No template found on server with name "{0}" | |
TF30245 | The Process Template Manager could not retrieve the instance of IVSTeamExplorer. | |
TF30246 | The file "{0}" was not found in "{1}" | |
TF30247 | The New Team Project Wizard could not load the plug-in "{0}" for process template "{1}". Select another process template or see the log file for more details. | |
TF30249 | The New Team Project Wizard could not retrieve the process template information. | |
TF30253 | Missing attribute "{0}" from XmlNode "{1}" | |
TF30254 | Unable to read the schema from resources | |
TF30255 | XmlNode "{0}" not found as child of node "{1}" | |
TF30260 | Folder and/or source attributes are invalid | |
TF30261 | Invalid project name -- project names: must be less than {0} for this TFS Server, cannot contain any of the following characters: / : ~ && %, double back-slash, and must not be a system reserved name. | |
TF30262 | Error occurred while creating document library : {0} retrying ... | |
TF30263 | Error creating document library {0} Exception = {1} | |
TF30264 | Error occurred while creating folder : {0} in library : {1} retrying ... | |
TF30265 | Duplicate site task | |
TF30266 | Error creating folder : {0} in document library : {1} | |
TF30267 | Exception: {0} | |
TF30268 | Windows SharePoint Services could not find the XML node in the file. | |
TF30269 | Node '{0}' not found | |
TF30270 | Project site folder "{0}" already exists | |
TF30271 | Exception while setting properties for file : {0} | |
TF30272 | Template not found on the server | |
TF30273 | Unknown SoapException encountered: Details = {0} | |
TF30274 | Error occurred while uploading file to : {0} retrying after 5 seconds ... | |
TF30275 | Error while uploading file source = {0} target = {1} | |
TF30276 | The taskXml did not contain a "wss" XML node. | |
TF30277 | You do not have sufficient permissions on the Windows SharePoint Services at {0} to create a new site. | |
TF30279 | Plug-in with ID "{0}" of type "{1}" could not be loaded | |
TF30282 | The file or folder you are copying or moving has the same name as the target folder and is a child of that folder. Change the name of either the object you are copying or the target folder. | |
TF30283 | Fail to delete virtual directory '{0}' | |
TF30284 | Could not connect to server '{0}' | |
TF30285 | Virtual directory '{0}' already exists | |
TF30286 | A simple failure in ELead's code | |
TF30288 | Failure in ELeadXmlTraceListener | |
TF30290 | There was a problem accessing the database on the server. See the Team Foundation Server event log for details. Time: {0} | |
TF30290 | There was a problem accessing the database on the server. See the Team Foundation Server event log for details. Time: {0} | |
TF30290 | There was a problem accessing the database on the server. See the Event log on the Team Foundation Server for details. Time: {0} | |
TF30290 | There was a problem accessing the database on the server. See the Event log on the Team Foundation Server for details. Time: {0} | |
TF30291 | There was a problem on the server of unknown cause. See the Team Foundation Server event log for details. Time: {0} | |
TF30291 | There was a problem on the server of unknown cause. See the Team Foundation Server event log for details. Time: {0} | |
TF30291 | There was a problem on the server of unknown cause. See the log file on the Team Foundation Server for details. Time: {0} | |
TF30291 | There was a problem on the server of unknown cause. See the log file on the Team Foundation Server for details. Time: {0} | |
TF30292 | There was a security exception. See the log file on the Team Foundation Server for details. Time: {0} | |
TF30294 | You do not have sufficient permissions to perform this operation. For further information contact the Team Foundation Server administrator. | |
TF30295 | Trace log size exceeds maximum file length | |
TF30297 | The PortfolioDisplayName and Portfolio are not set and the ProjectPickerControl is disabled. | |
TF30298 | The ProjectPickerControl could not find the PortfolioDisplayName in DomainNameSpace. | |
TF30299 | Cannot set CancelButtonLabel to null or empty string. | |
TF30300 | Cannot set DialogTitle to null or empty string. | |
TF30301 | Cannot set OKButtonLabel to null or empty string. | |
TF30306 | Cannot set AddRequiredButtonLabel to null or empty string. | |
TF30307 | Cannot set AllWorkItemTypesText to null or empty string. | |
TF30308 | Cannot set AvailableColumnsLabel to null or empty string. | |
TF30309 | Cannot set ColumnPickerDescriptionText to null or empty string. | |
TF30310 | Cannot set ColumnPickerWorkItemTypeLabel to null or empty string. | |
TF30311 | Cannot set ColumnResetButtonLabel to null or empty string. | |
TF30312 | Cannot set RequiredItemTag to null or empty string. | |
TF30313 | Cannot set SelectedColumnsLabel to null or empty string. | |
TF30314 | ColumnsPickerControl: The ExcludedColumns items in the ColumnsPickerControl were not string types. | |
TF30315 | The RequiredItemTag value must include a substitution token ({0}) for the column name. | |
TF30316 | ColumnsPickerControl: PortfolioDisplayName and Portfolio are null or empty strings. | |
TF30317 | ColumnsPickerControl: SelectedVirtualColumns items were not of type VirtualColumn. | |
TF30318 | ColumnsPickerControl: SpecialAvailableVirtualColumns items did not have SpecialFieldInfo set. | |
TF30319 | Disconnecting from the Team Foundation Server {0} will close all queries, work items, documents, all solutions under Team Foundation source control, and the Team menu. To connect to the server again, from the Tools menu, select Connect to Team Foundation Server. Are you sure you want to disconnect? | |
TF30320 | The New Team Project Wizard could not retrieve the list of team projects on the Team Foundation Server {0}. | |
TF30321 | The name you typed is already used for another team project on the Team Foundation Server. | |
TF30322 | The report or folder you are copying or moving has the same name as the target folder and is a child of that folder. Change the name of either the object you are copying or the target folder. | |
TF30323 | The New Team Project Wizard could not retrieve the wizard page from the plug-in {0}. | |
TF30324 | The name "{0}" exceeds the limit of 128 characters. Type or select a shorter name and try again. | |
TF30325 | Team Explorer encountered an unexpected error while refreshing the {0} plug-in. The following error message was returned by the plug-in: {1}. Contact your Team Foundation Server administrator and ask that the plug-in be reinstalled. If the problem persists, contact the developer or provider of the plug-in for further instructions. | |
TF30326 | The team project name you typed is not valid. A project name cannot: - contain more than {0} characters for this Team Foundation Server - contain Unicode control characters or Surrogate characters - contain any of the following characters: / : ~ && % ; @ ' " ? < > | # $ * }} {{ , + = - , double back-slash, start with an underscore ( _ ) - start or end with a period ( . ) - be a system reserved name. | |
TF30327 | Are you sure you want to remove the team project '{0}' from Team Explorer? If you remove the team project from the tree, you can add it again later from the File menu by pointing to Open, clicking Team Project, and the selecting the name of the team project. | |
TF30329 | The item you are copying or moving has the same name as the target folder and is a child of that folder. Change the name of either the object you are copying or the target folder. | |
TF30330 | Team Explorer cannot write to the project list configuration file. Free up space on the local hard disk. | |
TF30331 | Team Explorer could not connect to the Team Foundation server {0} used during your last session. The server may be offline or the network is unavailable. Contact your Team Foundation Server administrator to confirm that the server is available on the network. Use the Connect to Team Foundation Server command on the Tools menu to reconnect to your previous server. The server returned the following error: {1} | |
TF30332 | Document and folder names cannot contain any of the following characters: / : * ~ && % ; @ " ' ? < > | #, double back-slash. Enter a valid name. | |
TF31001 | Team Foundation cannot retrieve the list of team projects from Team Foundation Server {0}. The Team Foundation Server returned the following error: {1}. | |
TF31002 | Unable to connect to this Team Foundation Server {0}. Team Foundation Server URL: {1}.. | |
TF31003 | Your user account does not have permission to connect to the Team Foundation Server {0}. Contact your Team Foundation Server administrator and request that the appropriate permission be added to your account. | |
TF31004 | Team Foundation encountered an unexpected error while connecting to Team Foundation Server {0}. Wait a few minutes and try again. If the problem persists, contact your Team Foundation Server administrator. | |
TF31005 | Team Foundation cannot retrieve the list of team projects because it is not able to connect to Team Foundation Server {0}. | |
TF40001 | The build could not be started. Failed to connect to the server. Please verify the network connection and try again. | |
TF40002 | The build could not be completed. Failed to connect to the server. Please verify the network connection and try again. | |
TF40003 | The input argument {0} is required but missing. | |
TF41001 | Team project {1} does not have a build type {0}. | |
TF41011 | Team project {0} does not exist | |
TF41012 | The Team Foundation Server {0} is not reachable. | |
TF41013 | Team Build could not connect to the server because of problems with the network. The following error was returned by the server: {0} | |
TF41014 | The value for switch /{0} is missing. | |
TF42001 | A build quality name must be between 1 to 256 characters in length. | |
TF42002 | A build quality with this name already exists. Please type a unique name. | |
TF42003 | Team Build failed to open file {0}. {1} | |
TF42004 | Team Build failed to open folder {0}. {1} | |
TF42005 | Failed to get build type files. | |
TF42006 | The build service could not get the build type information. Please ensure that {0} is a valid build type and the build service account is a member of build services group of the team project. | |
TF42007 | The test run id {0} is invalid or does not exist. | |
TF42008 | The test case management package could not be loaded. Please verify that Visual Studio Test Tools is installed and try again. | |
TF42009 | Team Build could not add the build quality {0} because of the error: {1} | |
TF42010 | Team Build could not remove the build quality {0} because of the error: {1} | |
TF42011 | Team Build could not update the build quality. {0} | |
TF42012 | The build type {0} is either not valid or was not found. Please verify that all required files such as TfsBuild.proj are valid and are checked in. | |
TF42013 | The build type {0} already exists. | |
TF42014 | The build type name contains more than the maximum characters allowed. Please type a shorter name and try again. | |
TF42015 | The format of the file {0} for build type {1} is invalid and cannot be used by Team Build | |
TF42016 | The build type template file {0} is missing. The generated build type file may be incorrectly formatted. Reinstalling the application may fix this problem. | |
TF42017 | Unable to create the build type specified because the connection to the server timed out. Please wait for few minutes and try again. If the problem persists, contact your network administrator. | |
TF42018 | The DoNotDownloadBuildType flag in configuration file of TFSBuildService.exe is set to true but {0} does not exist. Please set the DoNotDownloadBuildType flag to false and restart the service or ensure that the file exists. | |
TF42019 | Failed to load the file {0} due to error: {1}. Reinstalling the application may fix this problem. | |
TF42020 | The MSBuild executable file {0} not found. Please re-install .NET Framework 2.0 on build machine and try again. | |
TF42021 | Failed to update build information | |
TF42022 | The workspace {0} does not have any working folder mappings. Please verify the working folder mappings of selected workspace and try again. | |
TF42023 | Failed to get test metadata (.vsmdi) file for the selected workspace {0}. Please verify that the workspace contains one or more test metadata files. | |
TF42024 | Failed to start the wizard. The workspace {0} is preventing the wizard from creating temporary workspace required for this operation. Please change the folder mapping of the workspace to some other local folder. | |
TF42025 | The wizard could not check-in the build type files into source control. Please verify the network connection and try again. | |
TF42026 | Failed to start the wizard. The temporary workspace {0} needed for this operation already exists. Please delete this workspace and try again. | |
TF42027 | Team Build could not get the solution files for the team project. Please verify that the {0} workspace mapping is correct and it contains one or more solution files. | |
TF42028 | The following error occurred while creating build type {0}: {1} | |
TF42029 | The selected workspace {0} no longer exists. Please exit the wizard and try again. | |
TF42030 | Failed to synchronize build type files. Please verify the network connection and try again. | |
TF42031 | Failed to create the directory {0} - {1} | |
TF42032 | Failed to load the file {0} because {1} XML element could not be located in the file. Reinstalling the application may fix this problem. | |
TF42033 | The build directory must be a valid local path on the build machine. | |
TF42034 | The drop location must be a valid UNC path. | |
TF42035 | There are one or more duplicate or incorrect configurations. Remove the duplicate or fix the configuration and try again. | |
TF42036 | There is no build type available to build the team project '{0}'. Please create a new build type and try again. | |
TF42037 | You have not selected a solution. Do you want to proceed? | |
TF42038 | You must specify at least one configuration. | |
TF42039 | Team project {0} does not exist. | |
TF42040 | Build process could not be terminated: {0} | |
TF42041 | Invalid drop location {0} specified | |
TF42042 | Failed to connect to drop location {0}. Please ensure that it is a valid share. | |
TF42043 | Team Build could not load the report. Please verify that the Team Foundation Client is installed and try again. | |
TF42044 | The build could not be delete because it is in progress. You can stop this build using the stop command. | |
TF42045 | A build for the team project: {0} is in progress on build machine: {1}. On each build machine, only one build can be active for each team project. Use a different build machine or try again later. | |
TF42046 | The build service used in the build process is not reachable. This error occurs when either the build machine is off-line, the required service is not running, Team Build is not installed on the build machine, Team Build is configured for a different Team Foundation Server or the network is not available. Please contact your Team Foundation Server administrator to verify that Team Build is correctly installed and running. | |
TF42047 | The build data was deleted. The drop location {0} does not exist or is inaccessible and could not be deleted. | |
TF42048 | The input argument {0} is required but missing. | |
TF42049 | The drop location {0} already exists. Please provide different drop location and try again. | |
TF42050 | Invalid build directory: {0}. The build directory cannot be a UNC path, relative path or drive name. Please specify the full path to a local folder on the build machine. The folder will be created if it does not exist. | |
TF42051 | The build process ended with the exit code {0}. Please check the log file or the event viewer on the build machine for more information. | |
TF42052 | The file system on the build machine does not support access control lists. Please specify build directory on a file system that supports access control lists like NTFS. | |
TF42053 | The build machine is not configured to build for server {0}. The build machine is configured for one Team Foundation Server only. To change the Team Foundation Server for the build machine, update the AllowedTeamServer key in the configuration file for TFSBuildService.exe and restart the service. | |
TF42054 | Team Foundation could not start the build. Please check the event log on the build machine for additional information. | |
TF42055 | Team Build encountered the following unexpected error: {0} | |
TF42056 | The build service could not connect to the Team Foundation Server: {0} | |
TF42057 | The build request is not from the configured Team Foundation Server. Please contact your Team Foundation Server administrator for help. | |
TF42058 | The build process was not able to set access control on {0}. Please grant the user account running the build process full rights on this directory. Please set proper access control on this directory to ensure access only to authorized users. | |
TF42059 | Failed to delete test run results. The test run {0} is invalid or does not exist. | |
TF42060 | Failed to retrieve the build type definition for {0}. Please verify the network connection and ensure you have permission to access the version control file {1}. | |
TF42062 | The build quality {0} is the default build quality and cannot be deleted | |
TF42091 | A workspace needed for build could not be created. Please verify that WorkspaceMapping.xml has valid folder mappings. All the server paths should belong to the active team project and should point to existing server folders. | |
TF42092 | A Work Item could not be created for failures in build '{0}'. Please verify that the work item type '{1}' is supported in team project '{2}' and it has field '{3}' defined. | |
TF42093 | The work item '{0}' could not be updated with build information for the changeset '{1}'. The field '{2}' is not available on this work item. | |
TF42094 | A work item could not be created for build failure. Please verify valid properties are specified as [name=value] pairs separated by ; in the WorkItemFieldValues property in TfsBuild.proj. | |
TF42095 | A work item could not be created for build failure. An invalid value was passed for field {0}. | |
TF42096 | A work item could not be created for failure in build '{0}' as no matching team project was found. | |
TF42097 | A work item could not be created for build failure. The value for the following required fields is invalid or missing: | |
TF42098 | A work item could not be created for build failure. The build service account does not have the permissions to save the work item. | |
TF50001 | Created or found an existing subscription. The subscription ID is {0}. | |
TF50002 | Unrecognized command-line arguments. | |
TF50003 | Unrecognized command-line argument: {0} | |
TF50004 | uccessfully unsubscribed subscription {0}. | |
TF50200 | DataChangedEvent cannot be triggered. {0} {1} | |
TF50201 | NodeCreatedEvent cannot be triggered. {0} {1} | |
TF50202 | NodeMovedEvent cannot be triggered. {0} {1} | |
TF50203 | NodeRenamedEvent cannot be triggered. {0} {1} | |
TF50204 | NodesDeletedEvent cannot be triggered. | |
TF50205 | ProjectCreatedEvent cannot be triggered. {0} {1} | |
TF50206 | ProjectDeletedEvent cannot be triggered. {0} {1} | |
TF50207 | ProjectRenamedEvent cannot be triggered. {0} {1} | |
TF50208 | PropertiesChangedEvent cannot be triggered. {0} {1} | |
TF50209 | The SQL stored procedure did not raise an exception. | |
TF50210 | You must specify either IfTrue or IfFalse for a conditional statement. | |
TF50211 | Format exception reading int from Web.Config: {0} | |
TF50212 | Missing setting in Web.Config: {0}. Defaulting to: {1} | |
TF50213 | EventMeta did not recognize the type of field named: {0} | |
TF50214 | The event status could not be parsed from the following database: {0} | |
TF50215 | Received a Core Services asynchronous event of the following type: {0} | |
TF50216 | The subscription URI is not valid. | |
TF50217 | Received a Core Services event of the following type: {0} | |
TF50218 | The UserId field should not be empty. | |
TF50219 | The e-mail address was not set correctly. | |
TF50220 | Missing the schema for the following event type: {0} | |
TF50221 | The artifact URI is incorrectly formed. Retype the URI. | |
TF50222 | The link filter is incorrectly formed. Retype the filter. | |
TF50223 | The artifact cannot be null. | |
TF50224 | The artifact array cannot be null. | |
TF50225 | The URI for the artifact cannot be null. | |
TF50226 | The value for External ID cannot be null. | |
TF50227 | The value for the External ID array cannot be null. | |
TF50228 | The URI list cannot be null. | |
TF50229 | Unknown change type: | |
TF50230 | The GAP ArtifactChangedEvent cannot be triggered. | |
TF50231 | The following setting is missing: {0}. Please define it in Web.Config | |
TF50232 | Team Foundation Core Services unhandled application error: {0} | |
TF50233 | A cyclic group containment error occurred when adding a group member. The group {1} already a has the group {0} as a contained member. | |
TF50234 | You must specify a group when adding a member to a group. | |
TF50235 | The group {0} already has a member {1}. | |
TF50236 | You must specify an identity to add to the group. | |
TF50237 | An error occurred when adding a group member. The group with security identifier (SID) {0} does not exist. | |
TF50239 | Missing cache entry for {0}. Update the cache. | |
TF50240 | The specified application group cannot be found. | |
TF50241 | The specified group name is forbidden. | |
TF50242 | The requested operation cannot be applied to a built-in group. | |
TF50243 | Failed to update cache entry for {0} with {1} retries. {2} | |
TF50244 | The Team Foundation Valid Users group cannot be added to any other group as a member. | |
TF50245 | Cannot bind to the specified application group. | |
TF50246 | Cannot obtain the security identifier (SID) of the caller. | |
TF50247 | You cannot remove the last member of a special group. | |
TF50248 | You cannot remove the service account from the Service Accounts group. | |
TF50249 | Cyclic group membership is not allowed. | |
TF50253 | The specified identity is already a member of the group. | |
TF50254 | The specified group name already exists. | |
TF50255 | Unrecognized Team Foundation Server identity. The user must belong to the Team Foundation Valid Users group. | |
TF50257 | An error occurred finding the group. There is no group with the project URI {0} and the name {1}. | |
TF50258 | An error occurred finding the group. There is no group with the security identifier (SID) {0}. | |
TF50259 | A global group with the name {0} already exists. | |
TF50260 | GSS: ID_created event triggered for: {0} | |
TF50261 | GSS: ID_deleted event triggered for: {0} | |
TF50262 | GSS: ID_member_changed event(s) triggered for: {0} | |
TF50263 | The caller is not authenticated. | |
TF50264 | The specified project has not been registered. | |
TF50265 | An error occurred removing the group. There is no group with the security identifier (SID) {0}. | |
TF50266 | An error occurred removing the group member. There is no group with the security identifier (SID) {0}. | |
TF50267 | You cannot remove the last member of the Team Foundation Administrators group. | |
TF50268 | You must specify a group to remove a member from the group. | |
TF50269 | You must specify an identity to remove from the group. | |
TF50270 | Failed to retrieve the following members: {0}. | |
TF50271 | The specified access check type is unknown. | |
TF50273 | An error occurred updating the group. The group with the security identifier (SID) {0} does not exist. | |
TF50274 | An irrecoverable Team Foundation Core Services setup error occurred. The value for ArtifactUriRoot was not set. | |
TF50275 | The following filter is incorrectly formed: {0} | |
TF50276 | The following URI is incorrectly formed: {0} | |
TF50277 | The uniform resource identifier (URI) in the input is incorrectly formed: {0} | |
TF50278 | The URI list cannot be empty. | |
TF50279 | The Team Foundation Server Group Security subsystem has returned an error. See the Team Foundation Server event log for details. Time: {0} | |
TF50280 | Could not connect to the service at: '{0}'. Check the service configuration. Full Exception: {1} | |
TF50281 | Could not parse the notification status from the following database: {0} | |
TF50282 | Could not connect to the following e-mail server: {0} Error message: {1} | |
TF50283 | A problem occurred when sending e-mail: {0} | |
TF50284 | The event has a title field that is not a string: {0} | |
TF50285 | Exception matching subscription: {0}: {1} | |
TF50286 | A timeout occurred waiting for reader lock for events of the following type: {0}, {1} | |
TF50287 | A timeout occurred waiting for writer lock on subscriptions of the following type: {0}: {1} | |
TF50288 | A timeout occurred waiting for writer lock to delete a subscription of the following type: {0}: {1} | |
TF50289 | Unbalanced tags. Expected /{0} got {1} | |
TF50290 | Unbalanced tags. Expected </{0}> | |
TF50291 | Process Guidance: Index unavailable for | |
TF50292 | Incorrect input. The input type is not in the database. | |
TF50296 | There should have been only one uniform resource locator (URL) for each tool or interface pair: {0} | |
TF50297 | You must type a tool name, not a tool ID: {0} | |
TF50298 | Did not find the expected registration entry: | |
TF50299 | The value named '{0}' was not found when evaluating a condition. | |
TF50300 | Caught an exception in Send loop: {0} | |
TF50301 | Could not add or update subscription of event type: {0} | |
TF50302 | Incorrect subscription found in database for the following type: {0} | |
TF50303 | There was a problem saving the subscription for the following user: {0} | |
TF50304 | There is a syntax error in the subscription condition. Check the syntax. | |
TF50305 | There were invalid arguments passed to a Web method. | |
TF50308 | There was a security exception. See the event log on the Team Foundation Server for details. Time: {0} | |
TF50309 | You do not have sufficient permissions to perform this operation. | |
TF50310 | Unable to find user context. | |
TF50311 | You cannot have more than 14 levels of hierarchy. | |
TF50312 | The forwarding URI is one of the deleted nodes. | |
TF50313 | The forwarding URI belongs to a different structure or project. | |
TF50314 | Unrecognized XML format. | |
TF50315 | Unrecognized forwarding URI. | |
TF50316 | Invalid name '{0}'. | |
TF50317 | Unrecognized node name. | |
TF50318 | Unrecognized node path. | |
TF50319 | Unrecognized node type. | |
TF50320 | Unrecognized node URI. | |
TF50321 | Unrecognized node URIs. | |
TF50321 | Unrecognized parent URI. | |
TF50322 | Unrecognized project name. | |
TF50323 | Unrecognized project URI. | |
TF50324 | Unrecognized property name. | |
TF50325 | Unrecognized property value. | |
TF50326 | Unrecognized URI. | |
TF50327 | The structure cannot be null. | |
TF50328 | The network path is too long. | |
TF50329 | The root nodes of a project cannot have the same name. | |
TF50330 | You must include a name attribute for the variable. | |
TF50331 | Unknown field type: {0} | |
TF50332 | An error occurred while preparing a Team Foundation alert; the event is being ignored and an alert will not be generated. Event contents: {0} | |
TF50355 | Subscription not found. | |
TF50600 | Invalid database configuration, please contact your Team Foundation administrator. | |
TF50601 | Unable to retrieve domain object from Active Directory. | |
TF50603 | Active Directory search did not return an identity. | |
TF50604 | There was an error getting identity information from Active Directory. | |
TF50605 | There was an error looking up the SID for {0}. | |
TF50606 | Invalid argument: {0} | |
TF50607 | Unable to retrieve information for {0}, it does not exist. | |
TF50608 | Unable to retrieve information for security object {0}, it does not exist. | |
TF50609 | Unable to retrieve information for permission {0}, it does not exist. | |
TF50610 | Unable to delete access control entry for object {0}, permission {1}, user {2}, and deny {3} since it does not exist. | |
TF50611 | Failure creating access control entry, the object {0} does not exist. | |
TF50612 | Failure creating access control entry, one of the specified actions don't exist. | |
TF50614 | GSS: DirectoryServicesCOMException with : GetSidBySearchFactor ({0}, {1}) | |
TF50615 | GSS: There was a failure reading group membership from Active Directory. No action is required, and another method to read group membership will be used. | |
TF50616 | Error renaming group, a group named {0} already exists. | |
TF50617 | Error in internal stored procedure, the stored procedure can not be run outside of a transaction. | |
TF50618 | The Team Foundation Valid Users group can not be modified directly. | |
TF50619 | The group you are adding is not a security group. | |
TF50620 | There is no project associated with project uri {0} | |
TF50621 | GSS: Failed to retrieve identity from source : [{0}] | |
TF50622 | Used the direct DirectoryEntry from Active Directory for group {0} member {1}. | |
TF50623 | There has been an unexpected database error. Please contact your Team Foundation administrator. | |
TF50624 | A group named {0} already exists in project {1}. | |
TF50625 | Failure unregistering Team Project, Team Project {0} does not exist. | |
TF50626 | Maximum users ({1}) in License group. Unable to add {0}. | |
TF50627 | Failure registering an object, the object {0} already exists. | |
TF50628 | Failure registering an object, the object class {0} does not exist. | |
TF50629 | Failure registering an object, the Team Project {0} does not exist. | |
TF50630 | Failure registering an object, the parent object {0} does not exist. | |
TF50631 | Failure registering Team Project, Team Project {0} already exists. | |
TF50632 | An error occurred removing the group member. There is no group member with the security identifier (SID) {0}. | |
TF50633 | An error occurred removing the group. You can not remove the global Team Foundation Administrators group with security identifier (SID) {0}. | |
TF50634 | An error occurred removing the group. You can not remove the global Team Foundation Valid Users group with the security identifier (SID) {0}. | |
TF50635 | An error occurred removing the group. You can not remove the global Service Accounts group with the security identifier (SID) {0}. | |
TF50636 | An error occurred removing the group. You can not remove the group with the security identifier (SID) {0}. | |
TF50637 | Only Windows users can be added to the License group. Unable to add {0}. | |
TF50638 | Invalid database configuration, missing row, please contact your Team Foundation administrator. | |
TF50639 | Invalid database configuration, extra rows, please contact your Team Foundation administrator. | |
TF50640 | Invalid database configuration, missing result set, please contact your Team Foundation administrator. | |
TF50641 | Invalid database configuration, missing final result set, please contact your Team Foundation administrator. | |
TF50642 | A problem occurred updating the Identity {0} (with SID {1}). Changes to this Identity and any of its members have not been propagated into the Team Foundation Server database. The Team Foundation Server will retry the update at the next scheduled synchronization. | |
TF50643 | Team Foundation Server was unable to retrieve identity information from Active Directory for {0}\ \{1} because the Team Foundation Server application pool identity is not authorized to access this information, or is a local user account. To access this information, the Team Foundation Server application pool identity must be an Active Directory user account. | |
TF50800 | The TFSServerScheduler service successfully initialized, but the Team Foundation Registration Service did not return any tasks that needed scheduling. | |
TF50801 | The TFSServerScheduler service did not initialize. The Team Foundation Registration Service returned the following error: {0} | |
TF50802 | GetNextInterval Error: Web service "{0}" returned a negative time interval {1}. | |
TF50803 | The TFSServerScheduler service received a request to reset itself. The service is resetting the scheduled tasks. | |
TF50804 | The TFSServerScheduler service could not complete the scheduled task at: {0}. The Web service returned the following error: {1} | |
TF50805 | The TFSServerScheduler service successfully completed the scheduled task at: {0}, after a previous, unsuccessful attempt. | |
TF50806 | The TFSServerScheduler service successfully initialized, after an earlier unsuccessful initialization. | |
TF51000 | An unsupported date format. | |
TF51002 | The query statement contains a duplicate ASOF element. | |
TF51003 | The EVER operator can only be used in conjunction with the "=" or "contains" operators. | |
TF51004 | The query statement is missing a boolean expression in an expected place. | |
TF51005 | The query references a field that does not exist. | |
TF51006 | The query statement is missing a FROM clause. | |
TF51007 | The constant specified in the query expression is not supported for the field type. | |
TF51008 | Classification paths cannot start with a backslash. | |
TF51009 | The query specifies an unknown table. | |
TF51010 | The query contains a value for the EVER operator that is not supported. | |
TF51011 | The node specified is not found in the classification hierarchy. | |
TF51012 | The UNDER operator can only be used with classification fields. | |
TF51013 | The field specified has an unsupported type. | |
TF51015 | The add or subtract operators can only be used with dates or numerical constants. | |
TF51016 | The value for an add or subtract operator must be a number. | |
TF51100 | SetupWarehouse: The specified configuration file cannot be opened, or the formatting is unexpected: {0} | |
TF51102 | SetupWarehouse: Cannot write to the specified log file: {0} | |
TF51103 | SetupWarehouse: The -c option must be specified for the given command line arguments. | |
TF51104 | SetupWarehouse: An unexpected error occurred. | |
TF51209 | A run-time error {1} occurred on adapter {0}. | |
TF51211 | The configuration file did not load. Default configuration values will be used. | |
TF51212 | The following error has been reported by WarehouseController.GetNextInterval: {0}. | |
TF51213 | The ProcessWarehouse command is already in progress. | |
TF51214 | Unrecognized adapter type:{0} | |
TF51215 | Unrecognized dimension name: {0} | |
TF51216 | Unrecognized fact name or missing TrackingId: {0} | |
TF51217 | Unrecognized fact link name: {0} | |
TF51218 | Missing field value for: {0} | |
TF51219 | Cannot update warehouse schema without RunInit signaling it. | |
TF51220 | The requested fact does not exist in the configuration: {0} | |
TF51221 | The registration service does not have the warehouse entries. | |
TF51223 | The Team Foundation Server domain URL is set to null. Specify a valid URL. | |
TF51224 | Unknown settingID: <{0}> | |
TF51226 | The following dimension use already exists in the warehouse configuration: {0}.{1}.{2} | |
TF51226 | The following dimension use already exists in the warehouse configuration: {0}.{1}.{2} | |
TF51227 | The following fact field already exists in the warehouse configuration: {0}.{1} | |
TF51227 | The following fact field already exists in the warehouse configuration: {0}.{1} | |
TF51228 | Level {0} is not a member in dimension {1}. | |
TF51229 | There is no conversion from {0} to a MeasureDataType. | |
TF51230 | There is no conversion from {0} to an OleDbType. | |
TF51231 | The following fact does not exist and its dimension use cannot be deleted: {0}.<{1},{2}> | |
TF51232 | The following fact does not exist and its field cannot be deleted: {0}.{1} | |
TF51233 | The following fact does not exist and its measure's aggregation function cannot be renamed: {0}.{1} | |
TF51234 | The following fact does not exist and its dimension use cannot be renamed: {0}.<{1}, {2}> | |
TF51235 | The following fact does not exist and its field cannot be renamed: {0}.{1} | |
TF51236 | You must set the measure group partitions. | |
TF51237 | The following measure aggregation function is unsupported: {0} | |
TF51300 | Either access to the database is denied, or the item does not exist. | |
TF51301 | You must specify an argument. Arguments cannot be empty strings. | |
TF51302 | The server configuration is incorrect. Check your server settings. | |
TF51304 | Either the requested file was not found, or you have insufficient permissions to download this file. Make sure the file exists and that the user has permission to download this file. | |
TF51305 | Either the file identification number is incorrect, or the file is missing. | |
TF51306 | Cannot download the file because the user is not authenticated. | |
TF51307 | Cannot download the file because the user's identity cannot be established. | |
TF51309 | Cannot upload the file because the value for Area Node URI is missing. Check and make sure the work item version is up to date. | |
TF51310 | Cannot upload the file because the user is not authenticated. | |
TF51311 | Cannot upload the file because the user does not have permissions to upload files to work items. | |
TF51312 | The argument is not recognized. | |
TF51312 | The argument is not recognized. | |
TF51313 | The request ID is incorrect or not recognized. | |
TF51314 | The row version cannot be a negative value. Supply a non-zero, positive value. | |
TF51316 | The maximum attachment size exceeds the allowable maximum of {0} kilobytes. Upload a smaller file, or change the maximum value for the work item attachment size. | |
TF51317 | The file attachments database name could not be obtained from Team Foundation Server {0}. | |
TF51318 | The file attachments server name could not be obtained from Team Foundation Server {0}. | |
TF51319 | The data-tier database name could not be obtained from Team Foundation Server {0}. | |
TF51320 | The data-tier server name could not be obtained from Team Foundation Server {0}. | |
TF51322 | The registration server location is missing from the Workitem Tracking web.config file. | |
TF51323 | You must specify the metadata tables in your information request. | |
TF51328 | The request cannot be cancelled. | |
TF51329 | The Work Item Tracking data tier version ({0}) is incompatible with the application tier version ({1}). | |
TF51330 | The service account was not found. | |
TF51332 | There was an unexpected error. Check the Event Log for more information. | |
TF51334 | An unknown Web service error occurred: {0}. Check the Event Log for more information. | |
TF51335 | An update is required. | |
TF51337 | The user was not found. | |
TF51338 | The user account does not have the required permissions to handle Sync events. Check if the App Pool account is a member of ServiceAccounts group. | |
TF51339 | The user is not a member of the service group. Check the user name and verify the account permissions. | |
TF51342 | The GUID for the file is incorrect or missing. | |
TF51343 | Unsupported ACL synchronization frequency: {0}. | |
TF51344 | Unsupported CSS synchronization frequency: {0}. | |
TF51345 | Unsupported users and groups synchronization frequency: {0}. | |
TF51501 | An error occurred when triggering the following Work Item event: {0}. | |
TF51502 | An error occurred when attempting to queue the following event: {0} | |
TF51503 | The attachment ID number must be greater than zero. | |
TF51504 | The field name is not supported. Enter a field name that is alphanumeric. | |
TF51505 | Could not retrieve team project information for : {0} {1} {2}. | |
TF51506 | An error occurred while creating the IAuthorizationService proxy. | |
TF51507 | An error occurred while creating the ICommonStructureService proxy. | |
TF51508 | An error occurred while creating the IGroupSecurityService proxy. | |
TF51509 | An error occurred while creating the ILinkingService proxy. | |
TF51510 | Unrecognized or missing FROM state constant ID in InsertAction. | |
TF51511 | Unrecognized or missing TO state constant ID in InsertAction. | |
TF51512 | Unrecognized or missing work item type ID in InsertAction. | |
TF51513 | The InsertAction name is too long. | |
TF51514 | The InsertConstant name is too long. | |
TF51515 | The constant ID for InsertConstantSet is missing. | |
TF51516 | The field name contains characters that are not supported. Field names can contain alphanumeric characters, underscores, and spaces. | |
TF51517 | Insert/Update Field unsupported reference name. | |
TF51518 | Missing Field ID for InsertFieldUsage action. | |
TF51519 | The Insert TreeProperty name is too long. | |
TF51521 | Unsupported reporting formula for insert/update field. | |
TF51522 | Unsupported reporting type for insert/update field. | |
TF51523 | Missing name constant ID for InsertWorkItemType. | |
TF51524 | Missing field ID for InsertWorkItemTypeUsage. | |
TF51525 | Missing work item type ID for InsertWorkItemTypeUsage. | |
TF51526 | The application path cannot be empty. | |
TF51527 | Artifact URI cannot be empty. | |
TF51528 | Work item revision numbers must be greater than zero, except for the latest revision, which must be -1. | |
TF51529 | Unsupported security group configuration. The Administrative group {0} must contain at least one member. | |
TF51530 | Unsupported Identity Type. | |
TF51531 | Missing or unrecognized Build name. | |
TF51532 | Missing or unrecognized ChangeType. | |
TF51533 | Missing or unrecognized Database name. | |
TF51534 | Missing or unrecognized event XML. | |
TF51535 | Missing or unsupported field name. | |
TF51538 | The maximum attachment size must be greater than or equal to zero. | |
TF51539 | Missing or unrecognized message. | |
TF51540 | There are no metadata tables requested. At least one metadata table must be requested. | |
TF51541 | The Node ID is not recognized. | |
TF51542 | The Node name is not recognized | |
TF51543 | The XML for the Deleted Nodes contains an unrecognized node URI for the deleted node. | |
TF51545 | Missing or unrecognized project name. | |
TF51546 | Missing or unrecognized project URI. | |
TF51547 | The XML for the Deleted Nodes contains an unrecognized node URI for the reclassify node. | |
TF51548 | There are no metadata row versions provided, or the versions do not match the number of metadata tables requested. | |
TF51549 | Missing or unrecognized server name. | |
TF51550 | Missing or unrecognized SID. | |
TF51551 | Missing or unrecognized Project Model or Lifecycle node. | |
TF51552 | Missing or unrecognized URI. | |
TF51553 | Missing or unrecognized user name. | |
TF51553 | Missing or unrecognized user SID. | |
TF51554 | Unrecognized user. Account name may be empty. | |
TF51555 | No work item IDs were requested. | |
TF51556 | Work item ID must be greater than zero. | |
TF51557 | Work item IDs must be greater than zero. | |
TF51558 | Could not retrieve global security groups. {0} | |
TF51559 | Could not retrieve team project security groups for : {0} {1} {2}. | |
TF51560 | Could not retrieve team projects: {0} | |
TF51561 | TablesRequested and rowVersions must be the same length. | |
TF51562 | Missing attribute {0} in XML. | |
TF51563 | Cannot remove link. | |
TF51564 | Cannot update link. | |
TF51565 | Cannot remove a file for a new work item. | |
TF51566 | Cannot have a value for RemoveRelation for a new work item. | |
TF51567 | Cannot have a value for UpdateRelation for a new work item. | |
TF51568 | DenyDependency is missing a work item ID. | |
TF51571 | {0} is not a recognized user. | |
TF51573 | Null node encountered. | |
TF51574 | updateElement exception encountered. | |
TF51575 | The value supplied for {0} cannot be null or empty. | |
TF51575 | The value supplied for {0} cannot be null or empty. | |
TF51576 | Missing or unrecognized Project name. | |
TF51577 | Missing or unrecognized Project XML. | |
TF51578 | The depth of the query is greater than the maximum query depth allowed of {0}. | |
TF51579 | The expand constant flag cannot use the equals and not equals operators. | |
TF51580 | The Query Expression operator is not supported. | |
TF51581 | The Query Group operator not is supported. | |
TF51582 | The column name you entered contains unsupported characters. Enter a column name using only alphanumeric characters. | |
TF51583 | Query contains an unsupported date for AsOfDate. | |
TF51584 | Query contains an unrecognized Boolean value in the expression value. | |
TF51586 | Unsupported date value in the expression value. | |
TF51587 | Unsupported double value in the expression value. | |
TF51588 | Unsupported Ever Contains operator in an expression in the Query XML. | |
TF51589 | The ExcludeLower attribute is not supported. It must be a Boolean string "True" with a value of "1" for true or "False" with a value of "0" or "-1" for false. | |
TF51590 | The ExcludeUpper attribute is not supported. It must be a Boolean string "True" with a value of "1" for true or "False" with a value of "0" or "-1" for false. | |
TF51591 | ExcludeUpper and ExcludeLower can only be used with operators "between" and "notBetween". | |
TF51592 | The ExpandConstant attribute is not supported. It must be a Boolean string "True" with a value of "1" for true or "False" with a value of "0" or "-1" for false. | |
TF51593 | An expression in the query XML contains unsupported expand flags. | |
TF51594 | The ExpandValue attribute is not supported. It must be a Boolean string "True" with a value of "1" for true or "False" with a value of "0" or "-1" for false. | |
TF51595 | An expression in the query XML is missing or contains an unsupported operator. | |
TF51596 | The Field Type is not recognized. | |
TF51598 | An expression in the query XML contains unsupported long text. | |
TF51599 | An expression in the query XML contains an unsupported long text operator. | |
TF51600 | An expression in the query XML contains an unsupported number of values. | |
TF51601 | An expression value in the query XML contains an unsupported number value. | |
TF51605 | There is an empty or null column name specified in the sort order. Provide a column name. | |
TF51606 | Temp ID contains an unsupported value. The value for Temp ID must be a positive integer. | |
TF51608 | An expression operator in the query XML contains an unsupported value type. | |
TF51609 | The ""Contains"" operator only supports string types. | |
TF51611 | An expression in the query XML is missing a column name. | |
TF51612 | The query does not contain any groups or expressions. | |
TF51613 | [BIS.ReadIdentities] Could not read the following identities : {0}. | |
TF51614 | [BIS.ReadIdentity] Could not read the identity for '{0}' {1} {2}. | |
TF51615 | ReadXML is not implemented by {0}. | |
TF51616 | Deleted Nodes XML does not contain reclassify element. | |
TF51617 | Work Item Tracking Counters are not installed properly. | |
TF51618 | Service Error: {0} | |
TF51619 | The Work Item Tracking Web Service application shut down. | |
TF51621 | The Work Item Tracking Web Service application started. | |
TF51623 | Could not synchronize CSS. {0} {1}. | |
TF51624 | Could not synchronize CSS on soap exception from Integration Services: {0} {1}. | |
TF51625 | Could not synchronize CSS for the project: {0} {1} {2}. | |
TF51626 | Could not synchronize users and groups: {0} {1}. | |
TF51627 | Could not synchronize users and groups on soap exception from Integration Services: {0} {1}. | |
TF51628 | Could not synchronize users and groups for the team project: {0} {1} {2}. | |
TF51629 | A service error occurred triggering a work item event: ThreadPool.QueueUserWorkitem failed. | |
TF51630 | The number of tables returned in the dataset did not match the expected number. | |
TF51632 | Nothing to update in UpdateAction. | |
TF51633 | Action '{0}' is not supported in Update XML. | |
TF51634 | Missing or unsupported work item ID for a dependent link. | |
TF51635 | There are duplicate temp IDs in the Update XML. | |
TF51636 | Could not find the attachment in the database. | |
TF51637 | InsertFile has an unrecognized or missing creation date attribute. | |
TF51638 | Unrecognized or missing value in fileNameGuid provided for InsertFile. | |
TF51640 | There are too many file attachments in this update (limit={0}). | |
TF51641 | Expecting an attribute with an integer value. | |
TF51642 | The attribute contains an unrecognized Boolean value. | |
TF51643 | The column name you entered contains unsupported characters. Enter a column name using only alphanumeric characters. | |
TF51644 | The attribute contains an unrecognized GUID value. | |
TF51645 | Object type missing or not supported. | |
TF51647 | Unsupported integer value for column name {0}. | |
TF51648 | Missing column value in update XML. | |
TF51649 | Update missing required ID. | |
TF51650 | No actions in Update XML | |
TF51651 | Unsupported file ID for Remove File in Update XML | |
TF51652 | Unsupported link ID for RemoveResourceLink in Update XML | |
TF51653 | Unsupported link ID for ResourceLink in Update XML | |
TF51655 | The update being performed generates a SQL batch with too many parameters. Try a smaller update. | |
TF51656 | There are no values to update for the work item type. | |
TF51657 | There are no values to update for the work item type usage. | |
TF51658 | There are too many work items requested (limit={0}). | |
TF53000 | The client version is not supported by the server {0}. | |
TF53001 | The database operation was canceled by an administrator. | |
TF53002 | Unable to obtain registration data for application {0}. | |
TF53003 | The client version is not supported by the server {0}. Supported range is {1}. | |
TF53004 | Unable to retrieve AT Stamp. | |
TF53005 | Unable to retrieve the Team Foundation Server installed UI culture. | |
TF53006 | There is not an application tier name recorded in the database. Please contact your Team Foundation Server administrator. | |
TF53007 | The application tier name {0} recorded in the database does not match the local machine name {1}. Please contact your Team Foundation Server administrator. | |
TF53008 | The authentication type {0} is not supported. | |
TF53009 | The log level {0} specified in the configuration file is being ignored; the default value is being used instead. | |
TF53010 | An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff. Technical Information (for the administrative staff): | |
TF53011 | {0} is not a licensed user. | |
TF53012 | A crash report is being prepared for Microsoft using the Watson Crash Reporting Mechanism. The prepared report will be queued when ready and may be sent to Microsoft through administrator control. | |
TF53013 | A crash report is being prepared for Microsoft. The following information is included in that report: {0} | |
TF53014 | A crash report for this problem was recently created; a new crash report for this occurrence of the problem is not being created. This problem has occurred {0} times. | |
TF53015 | A crash report has been prepared for Microsoft using the Watson Crash Reporting Mechanism. The prepared report has been queued and may be sent to Microsoft through administrator control. | |
TF53016 | Unable to contact the web service; examine the event log for other correlating entries. | |
TF53017 | Request processing is being shut down due to the exception shown below. | |
TF53018 | The application tier {0} is attempting to connect to a data tier with an incompatible version. | |
TF53019 | The data tier schema version for the {0} database cannot be found. | |
TF56044 | The identity you are attempting to edit is not an application group. | |
TF56044 | The identity you are attempting to edit is not an application group. | |
TF56045 | The group, {0}, resolved as a Windows identity. If an application group with the same name exists on the server, you must specify a 'domain' that is either '[{1}]', the project URI, or the project name. | |
TF60001 | Unable to connect to Microsoft SQL Server: {0}. Retrying... | |
TF60002 | Unable to connect to Microsoft SQL Server -- {0} | |
TF60003 | Microsoft SQL Server: {0} database is full. Try migrating smaller projects from the VSS database. | |
TF60004 | VSS Database Data folder:{0} not found. Check that the VSS database is not corrupt and functioning as expected. | |
TF60005 | Destroy is not implemented. | |
TF60006 | Duplicate mapping of VSS user {0} in user map file. | |
TF60007 | File checked out before migration. | |
TF60008 | The VSS database version is older than 6.0. The VSS converter only supports database versions 6.0 or above. Please upgrade the database version and try again. | |
TF60009 | File '{0}' could not be found. | |
TF60010 | Input file {0} does not exist. | |
TF60010 | Input file {0} does not exist. | |
TF60011 | The action {0} is not supported on Team Foundation. | |
TF60012 | The password is incorrect. | |
TF60013 | The {0} file is empty or has incorrect formatting. | |
TF60014 | The username {0} in the user map file {1} is invalid. | |
TF60015 | The user {0} does not exist in VSS database {1}. | |
TF60016 | The source folder {0} does not exist in the VSS database {1}. | |
TF60017 | The source folder {0} is a file and not a folder. Provide a folder in the settings file. | |
TF60022 | Unable to connect to Microsoft SQL Server. | |
TF60023 | Unable to clear the intermediate database {0} | |
TF60024 | Unable to create the database on Microsoft SQL Server due to the following error: {0} | |
TF60025 | Unable to open VSS database {0}. The connection failed due to the following error: {1} | |
TF60026 | Unrecognized input {0} for usermap. | |
TF60031 | Network error occurred while connecting to the VSS database. Retrying... | |
TF60032 | The VSS Converter requires Visual SourceSafe 2005 or later to run. Please install Visual SourceSafe 2005 or later and try again. | |
TF60035 | Unable to open file {0}. Error {1} | |
TF60035 | Unable to open file {0}. Error {1} | |
TF60036 | File {0} could not be found. | |
TF60036 | File {0} could not be found. | |
TF60037 | Unrecognized command: {0} | |
TF60037 | Unrecognized command: {0} | |
TF60040 | Unable to create error file {0}. - {1}. | |
TF60040 | Unable to create error file {0}. - {1}. | |
TF60043 | Team Foundation folder {0} already exists in deleted state. Provide a different Team Foundation folder. | |
TF60044 | Cannot migrate to $/. Create a team project before migration. | |
TF60045 | Output file {0} already exists. Delete or rename this file and try again. | |
TF60047 | Converter is retrying to migrate the action that was failed to migrate. This could be due a temporary problem with network or server. Incase this problem persist then please check your network connection or Team Foundation Server. | |
TF60048 | The settings file {0} is not in the recognized format. | |
TF60050 | Unable to open file {0}. | |
TF60050 | Unable to open file {0}. | |
TF60052 | {0} is a file and not a folder. Specify a Team Foundation folder in the settings file. | |
TF60053 | Duplicate destination folder {0} in the settings file. | |
TF60054 | Duplicate source folder {0} in the settings file. | |
TF60055 | The Team Foundation Folder {0} specified in the settings file contains unsupported characters. | |
TF60056 | Destination folder not provided for source {0} in the settings file. | |
TF60057 | Source folder not provided for destination {0} in the settings file. | |
TF60058 | The file {0} already exists. | |
TF60059 | The Team Foundation folder {0} is not empty. Specify an empty folder for migration. | |
TF60060 | No team project {0} found. Create a team project before migration. | |
TF60061 | Application stopped by user. | |
TF60062 | Output file {0} already exists. | |
TF60063 | Timeout occurred while connecting to Visual Studio Team Foundation source control. Retrying... | |
TF60064 | Unable to connect to Team Foundation Server {0}. | |
TF60067 | Unable to create workspace in Team Foundation {0}. | |
TF60070 | Unable to connect to this Team Foundation Server: <server>. Please ensure that the Team Foundation Server exist and try again. | |
TF60071 | Your user account does not have permission to connect to the Team Foundation Server <server>. Please contact your Team Foundation Server administrator and request that the appropriate permission be added to your account. | |
TF60071 | Your user account does not have permission to connect to the Team Foundation Server '{0}'. Please contact your Team Foundation Server administrator and request that the appropriate permission be added to your account. | |
TF60085 | No file or folder to migrate. | |
TF60087 | Failed to initialize user mapper | |
TF60088 | Merge failed for {0} from {1} at versions {2} to {3}, it is migrated as edit. | |
TF60089 | {0} is in improper xml format XMLError: | |
TF60090 | Unsupported protocol {0} | |
TF60091 | Start Reporting Failed | |
TF60092 | Too many arguments specified | |
TF60093 | Node {0} not found in file {1}. | |
TF60094 | Validation failed for file '{0}'. Error: {1} | |
TF60095 | Validation failed for file '{0}'. Line: {1}, Col: {2}, Error: {3} | |
TF60096 | Unable to migrate due to Team Foundation Error: {0} | |
TF60097 | Unable to migrate label due to Team Foundation Error: {0} | |
TF60098 | Error removing mappings from SQL Database: {0}. Please clear DB before running incremental migration for the same repository. | |
TF60099 | Given folder mappings do not match with last migrated mappings. Following was the original mapping please use this only for incremental migration.\ {0} | |
TF60700 | Please contact your administrator. There was an error contacting the server. Technical information (for administrator): {0} | |
TF60701 | Invalid input {0} for output report file. | |
TF60702 | Unable to start migration. Manually delete the following workspaces and try again. | |
TF60703 | Unable to migrate folder recursively due to IO Error: {0} | |
TF61000 | The converter could not convert work item {0}. The field '{1}' has an unsupported value '{2}', and the default value is also not supported. Check the value mappings and default values in the field map file '{3}'. | |
TF61001 | File {0} contains unsupported attribute value '{1}' for 'refer'. Only 'UserMap' value is supported for this attribute. Run the converter again after fixing the attribute value. | |
TF61002 | Field Map validation failed for file '{0}'. Field(s) '{1}' does not exist in work item type '{2}' in Team Foundation Server. Please create these fields in your work item type or remove the fields from the field map file. | |
TF61004 | The converter could not find the team project '{0}' on the Team Foundation Server. Please create the team project and try again. | |
TF61008 | The converter could not convert work item '{0}'. The field '{1}' has an unsupported value '{2}', and there is no default value specified in the field map file '{3}'. | |
TF61009 | The User Map file '{0}' contains unrecognized Team Foundation users. Check that the users specified in the User Map file are all existing Team Foundation users or remove them from the User Map file. Unrecognized users: {1} | |
TF61013 | The converter could not provision the work item type specified in the file {0} because of the following error: {1} | |
TF61014 | The converter could not provision the work item type specified in the file {0} because of the following error at Line: {1} Col: {2}: Error: {3} | |
TF61015 | Attachment '{0}' save failed for work item '{1}' with the following error: {2} | |
TF61016 | User '{0}' is not a member of 'Service Accounts' group. It is required for the user running converter to be part of 'Service Accounts' security group." | |
TF61018 | The name of the work item specified in definition file '{0}' does not match with the TargetWIT '{1}' in the schema map file '{2}'. Please update the WORKITEMTYPE node of the corresponding work item type definition file or the TargetWIT attribute in the schema map file so that both are the same and try running the converter again. | |
TF61019 | The Work Item Type Definition file '{0}' specified in schema map file '{1}' is invalid. It does not contain root element 'WITD'. | |
TF61020 | The Work Item Type Definition file '{0}' specified in schema map file '{1}' is invalid. It does not contain element 'WORKITEMTYPE' under 'WITD' node. | |
TF61021 | The Work Item Type Definition file '{0}' specified in schema map file '{1}' is invalid. | |
TF61022 | The Work Item Type Definition file '{0}' specified in schema map file '{1}' is not a valid xml file. Issue: {2} Line: {3} Column: {4} | |
TF61023 | Converter is unable to create the Area Path '{0}' as it contains some invalid characters. See Team Foundation work item help for a list of invalid characters. Please provide a value mapping for this field value to replace the invalid characters with some valid characters. | |
TF61024 | Converter is unable to create the Iteration Path '{0}' as it contains some invalid characters. See Team Foundation work item help for a list of invalid characters. Please provide a value mapping for this field value to replace the invalid characters with some valid characters. | |
TF61025 | Unable to serialize object due to unknown error: {0} | |
TF61036 | Unrecognized command {0} | |
TF61037 | Missing Argument /s:<schema map file>. The Schema Map xml file parameter is required with the Migrate command. | |
TF61038 | Unsupported Argument /s:{0}. The Schema Map xml file parameter is not used with the Analyze command. | |
TF61100 | Base Entity '{0}' has to be converted. Include the base entity in migration by adding the name in SourceEntity element in '{1}'. | |
TF61101 | Entity Type '{0}' does not exist in ClearQuest database. Please fix SourceEntity element in '{1}'. | |
TF61102 | Field Map validation failed for file '{0}'. Field(s) '{1}' does not exist in ClearQuest Entity '{2}'. | |
TF61103 | The converter could not find a supported version of the ClearQuest client. Please refer to CQConverter help for a list of supported versions. | |
TF61105 | The ClearQuest credentials you provided do not have admin rights on the ClearQuest database. Verify that the user specified in <UserID> element in the configuration file '{0}' has admin rights. | |
TF61106 | The query name '{0}' was not recognized. Correct the query name in the configuration file '{1}' and try again. | |
TF61110 | The converter could not create work item '{0}' because of the following error: {1}. | |
TF61111 | The converter could not convert work item '{0}' because of the following error: {1}. | |
TF61112 | The query is not based on the Submit type entity. CQConverter supports only submit type entities for conversion. Correct the query in the configuration file '{0}' and try again. | |
TF61114 | The converter could not find a work item type definition (WITD) file in the Schema Map file '{0}'. The WITD file is needed to create the work item type '{1}'. | |
TF61115 | Unable to find details for Connection <connection>, User Database <database>. Check these values in configuration file <filename>. | |
TF61116 | The converter could not create the output directory because of the following error: {0}. Correct the directory name in the configuration file '{1}' and try again. | |
TF61116 | The converter could not create the output directory because of the following error: {0}. Correct the directory name in the configuration file '{1}' and try again. | |
TF61117 | Query '{0}' specified in configuration file '{1}' does not contain 'dbid' field. Please edit the query to include 'dbid' field. | |
TF61118 | ClearQuest API call failed with the following error: {0} Refer ClearQuest documentation for more help. | |
TF61119 | Connection to ClearQuest failed with the following error: <error>: {0} - Check the ClearQuest information in the configuration file {1}. - Check to see if you can access ClearQuest from the ClearQuest client. | |
TF61120 | The converter could not migrate Clear Quest item with dbid='{0}' because of the following error: {1}. | |
TF611202 | The converter could not migrate the referenced record with value '{0}' associated with record '{1}' because of the following error: {2}. | |
TF61121 | The converter could not migrate parent record '{0}' of '{1}' because of the following error: {2}. | |
TF80005 | Could not publish work item changes. Cannot change the work item type for existing work items. | |
TF80006 | Team Foundation needs a work item type to publish work items. Select a work item type for the work items you have added and then try again. | |
TF80011 | The document cannot be opened because the application {0} is busy. Please close all {0} dialog boxes and try again. | |
TF80012 | The document cannot be opened because there is a problem with the installation of the Visual Studio 2005 Team Foundation Office integration components. Please see the Team Foundation Installation Guide for more information. | |
TF80013 | Cannot add the attachment because it was already added to the database version with different data. | |
TF80014 | Cannot add the link because it was already added to the database version with different data. | |
TF80015 | Cannot modify the attachment because the database version has changed since you last refreshed. | |
TF80016 | Cannot delete the attachment because the database version has changed since you last refreshed. | |
TF80017 | Cannot delete the link since the database version has changed since you last refreshed. | |
TF80020 | Cannot modify the link because the database version has changed since you last refreshed. | |
TF80022 | Could not connect to the team project for namespace: {0} | |
TF80025 | No service interfaces found. | |
TF80026 | No work item service interface found. | |
TF80027 | Could not find any work item types for the team project {0}. | |
TF80028 | Could not find the Team Foundation Core Services registry entries for service {0}. | |
TF80030 | Unsupported type of DocumentProperty while reading internal Team System data from DocumentProperties. | |
TF80031 | Unsupported format of compressed data. | |
TF80032 | Key refers to a type that is not a string or a primitive value. | |
TF80033 | Key refers to a value that does not exist. | |
TF80034 | Unsupported node in the XML code. | |
TF80035 | Unsupported value for the type attribute. | |
TF80038 | This work item contains unsupported field values. Edit the work item and choose a supported value. | |
TF80039 | The version information was not set for a work item. | |
TF80041 | This work item contains unsupported values. Edit the work item and choose a supported value. | |
TF80042 | The document cannot be opened because you do not have {0} 2003 or one of its components installed. Please see the Team Foundation Installation Guide for more information. | |
TF80043 | Could not contact the Team Foundation Server. Check that you have a network connection and that your Team Foundation Server is available. | |
TF80045 | Unknown or unsupported document type. | |
TF80046 | Microsoft Visual Studio Team Foundation requires {0} 2003, you have version {1} installed. Please see the Team Foundation Installation Guide for more information. | |
TF80047 | DomainPicker returned invalid data | |
TF80048 | Could not get Registration Proxy for namespace. | |
TF80049 | Missing DocumentProperty while reading internal Team System data from DocumentProperties. | |
TF80050 | Currently only string values are supported as indexes for CustomProperties. | |
TF80051 | IPropertySetStorage interface is not available for this document. | |
TF80052 | Property does not exist. | |
TF80053 | Unsupported type of property value. | |
TF80054 | StgOpenStorage() failed. | |
TF80055 | Error decompressing data. | |
TF80056 | Specified element is not a structured storage. | |
TF80057 | Specified storage name does not exist. | |
TF80058 | Key refers to a type that is not a string. | |
TF80059 | Value must be of a primitive type | |
TF80060 | Only string and integer types are supported as property values. | |
TF80061 | Error parsing value. | |
TF80062 | Data in the document properties is corrupt and cannot be decoded. | |
TF80063 | Unsupported operation type when applying change list | |
TF80064 | Could not authenticate with server {0} | |
TF80065 | Could not initialize Team Foundation Server {0} | |
TF80066 | You are not authorized to perform this operation. Please contact your Team Foundation administrator. | |
TF80067 | An error occurred on the Team Foundation server while attempting to perform this operation. Operation aborted. | |
TF80068 | Team Foundation encountered an error while communicating with the server. Please check your connection and try again. | |
TF80069 | Team Foundation encountered an error while updating data in the application. | |
TF80070 | Team Foundation encountered an error while performing the operation. It is recommended that you save your work and restart the application. | |
TF80071 | Team Foundation encountered an error while accessing the work item database. Please contact the Team Foundation Server administrator. | |
TF80072 | Team Foundation was unable to connect to the Team Foundation Server. The network connection might be lost or the server down. Please fix the problem and try again. | |
TF80074 | Team Foundation was unable to load the document because the document properties have been corrupted. The document will no longer be associated with a Team Foundation server. Please contact your Team Foundation administrator. | |
TF80075 | Work Item has already been modified in the Team Foundation Server. Please try saving again to publish this work item. | |
TF80076 | The data in the work item is not valid or you do not have permissions to modify the data. Please correct the problem and retry. | |
TF80077 | The Team Foundation server rejected the change to the work item. Please correct the problem and retry. | |
TF80078 | Unable to retrieve data from the work items database server. The network connection might be lost or the server down. Please fix the problem and try again. | |
TF80079 | This attachment has been deleted in the database version. | |
TF80080 | This link has been deleted in the database version. | |
TF82001 | Cannot connect to the Team Foundation server. Please contact your server administrator. | |
TF82002 | Could not start MSDN Help. Install MSDN Help or repair the installation and try again. | |
TF82004 | Could not create document. | |
TF82005 | Cannot open document. | |
TF82006 | There was a problem setting up the fields for the current field mapping. | |
TF82010 | This field is read only for the work item type "{0}." To restore the original value, close this message and then press the Escape key. | |
TF82014 | Could not find mapping document on the server. | |
TF82016 | Could not publish work item data. | |
TF82019 | The mapping file contains unrecognized XML. | |
TF82022 | The new field mapping is incomplete or contains unrecognized fields. The mapping document must include ID, Rev, and Work Item Type. | |
TF82023 | The following fields could not be mapped because the field type of the destination field is incompatible with the field type of the source field: | |
TF82024 | The following fields could not be mapped because the fields could not be found on the server: | |
TF82025 | The following field names in the new mapping are not supported and must be renamed: {0}. | |
TF82026 | The mapping file contains an unsupported project field name for {0} : {1}. | |
TF82026 | The mapping file contains an unsupported project field name for {0} : {1}. All project field names must begin with {2}. | |
TF82027 | Unsupported PublishOnly attribute for field {0}. Supported attributes are 'true' and 'false'. | |
TF82028 | The mapping file contains unsupported units for {0}. | |
TF82029 | The following field occurs more than once in the XML document: {0}. | |
TF82030 | Could not find the mapping document on the server. | |
TF82031 | An area or iteration path field is not mapped to a field that can contain a hierarchical tree view. The following field needs to be mapped to a task outlinecode field: {0} | |
TF82032 | You have entered data into the following fields, which are used by Team Foundation and will be overwritten: {0} Copy the content of these fields into another column. | |
TF82033 | Team Foundation could not initialize the project plan. This document will no longer be associated with a Team Foundation server. | |
TF82034 | There was a problem initializing the Microsoft Project Team Foundation AddIn. Re-installing the Team Foundation Client may be required. | |
TF82035 | There was a problem shutting down the Microsoft Project Team Foundation AddIn. Re-installing the Team Foundation Client may be required. | |
TF82036 | Problem accessing Native field of Project: {0}. Please contact your administrator to ensure that the field {0} is mapped to a valid MS Project field. | |
TF82037 | Must specify either the ProjectField or the ContextField attribute for this field: {0}. | |
TF82038 | Process Guidance cannot be launched. Please check if MSDN Help is installed properly and the portfolio project is created successfully on the Team Foundation Server. | |
TF82039 | Team Foundation was unable to modify the project plan. Please fix the problem and try again. | |
TF82041 | Team Foundation does not support editing tasks in a subproject from within the master project. Open the subproject to edit, publish, or refresh tasks. To restore the original value, close this message and then press the Escape key. | |
TF82042 | Could not connect to Team Foundation Server {0}. Check your network connection and try again. | |
TF82043 | "The new value is an Invalid work item type." Please close this message and then press the Escape key to select the work item type via the dropdown. | |
TF84000 | Could not open the document. | |
TF84005 | Could not insert a new column. There may be data to the right of this work item list that could not be moved automatically. | |
TF84006 | The work item list has been corrupted and Team Foundation could not correct the error. The work item list has been removed from the team project. | |
TF84009 | Could not run the query for this work item list. | |
TF84011 | Could not connect to team project {0}. | |
TF84012 | Document storage could not be found or is corrupted. This work item list will not be connected to a team project. | |
TF84013 | This value is assigned by the work item database and cannot be changed. | |
TF84014 | There are not enough entries in the list. The list must contain at least one entry. | |
TF84015 | There are too many entries in the list. This list cannot contain more than 65535 entries. | |
TF84018 | Unsupported property name: ""{0}"". | |
TF84019 | Unsupported work item type. | |
TF84021 | Team Foundation could not create the work item list. | |
TF84022 | Could not connect to Team Foundation Server {0}. Check your network connection and try again. | |
TF84023 | Failed to initialize the validation manager: could not create read-only validation range | |
TF84024 | No storage found for list object | |
TF84025 | Not an ELead hidden worksheet | |
TF84026 | No space to add new range | |
TF84027 | This field is not available for this type of work item and must be left blank. | |
TF84028 | Help topic cannot be displayed because the Visual Studio MSDN Help system is not installed. Please install the Help system and try again. | |
TF84029 | Cannot set SelectAQueryText to null or empty string. | |
TF84030 | Cannot set PublicQueriesText to null or empty string. | |
TF84031 | Cannot set PrivateQueriesText to null or empty string. | |
TF84032 | Team Foundation could not insert the work item list because there is data in the worksheet that cannot be moved. Select a location where there is enough space to insert the list. | |
TF84033 | Team Foundation was unable to modify the list. It is likely that this is caused by data in the worksheet that cannot be moved. Please fix the problem and try again. | |
TF84034 | Team Foundation was unable to initialize the workbook. This document will no longer be associated with a Team Foundation server. | |
TF84035 | Unable to initialize: List object was found without an ID column. | |
TF84036 | Process Guidance cannot be launched. Please check if MSDN Help is installed properly and the portfolio project is created successfully on the Team Foundation Server. | |
TF84037 | There was a problem initializing the Microsoft Excel Team Foundation AddIn. Re-installing the Team Foundation Client may be required. | |
TF84038 | There was a problem shutting down the Microsoft Excel Team Foundation AddIn. Re-installing the Team Foundation Client may be required. | |
TF84039 | There was a problem opening the specified document. | |
TF84040 | There was a problem creating the document. | |
TF84042 | The value you entered is not supported in this field. Select a supported value from the list. | |
TF84043 | Team Foundation could not find the query associated with this work item list. The query may have been deleted, or may be a private query created by another Team Foundation user. To publish or refresh changes to this work item list, you can change it to an input list, restore or recreate the deleted query, or contact the person who created the list to obtain a copy of the query. | |
TF84044 | One or more work items have fields that exceed the maximum cell length limit of 32,767 characters in Microsoft Excel. These work items will be displayed as blank rows to prevent data loss when publishing to the work item database. To display these work items, remove any columns that exceed the cell length limit from the list. | |
TF84045 | The column {0} could not be added to the list. One or more work items contain data in the column that exceed the 32,767 character size limit in Microsoft Excel. | |
TF86000 | Could not start MSDN Help. Install MSDN Help or repair the installation and try again. | |
TF86001 | Team Foundation was unable to load the Office AddIn. This may be caused by a Team Foundation Client installation problem or lack of .NET Programmability Support in the Office Application. Please see the Team Foundation Installation Guide for more information. | |
TF86002 | Team Foundation was unable to initialize the Office AddIn. This may be caused by a Team Foundation Client installation problem or lack of .NET Programmability Support in the Office Application. Please see the Team Foundation Installation Guide for more information. | |
TF87000 | TFSFieldMapping could not locate the directory because the file path was not found. | |
TF87001 | The file name is missing. Enter a file name and try again. | |
TF87002 | The file path is missing. Enter a file path and try again. | |
TF87003 | The project name is missing. Enter a project name and try again. | |
TF87004 | The URL for the server is missing. Enter a URL and try again. | |
TF87005 | File missing. Please enter another file path. | |
TF87006 | Unsupported arguments. | |
TF87007 | TFSFieldMapping could not locate the file because the file path was not found. | |
TF87008 | Your user account does not have sufficient permissions to access the file. Contact your Team Foundation Server administrator and request that permission be added to your account. | |
TF87009 | Team Foundation does not support long file paths. Enter a shorter file path and try again. | |
TF87010 | TFSFieldMapping requires a minimum of {0} arguments. Provide the additional arguments and try again. | |
TF87011 | TFSFieldMapping requires a maximum of {0} arguments. Remove the surplus arguments and try again. | |
... | ... | ... |
TF400813 | Resource not available for anonymous access. Client authentication required. | Ce message d'erreur permet d'indiquer que les ressources ne sont pas disponibles pour l'accès anonyme. Une authentification client est requise. |
TF402455 | Pushes to this branch are not permitted; you must use a pull request to update this branch. | Ce message d'erreur permet d'indiquer que les transmissions de type push vers cette branche ne sont pas autorisées. Vous devez utiliser une requête de tirage pour mettre à jour cette branche. |
Dernière mise à jour : Mardi, le 27 mars 2018