Visual Studio 2012
- TF401054: The requested service level property {0} did not match the expected value. The job agent requires the {1} service ...
- TF401057: There are no upgradeable configuration databases on this SQL Server instance; however, there are one or more databases ...
- TF401058: A connection cannot be made to the following SQL Server Instance after {1} tries: '{0}'. Verify that you have entered ...
- TF401059: Skipping team '{0}' due to invalid process configuration settings. The team cannot use the Agile planning features ...
- TF401060: We were unable to provision the settings for the kanban board / CFD chart for team '{0}' (Team ID: {1}). Visit ...
- TF401061: The server URL for this instance of Team Foundation Server is {0} and might need to be updated. You can modify ...
- TF401062: The notification URL for this instance of Team Foundation Server could not be retrieved and might need to be updated. ...
- TF401066: You are about to upgrade TFS on a machine that contains an underscore in its name. Running TFS on a machine with ...
- TF401067: Installing TFS on a machine that contains an underscore is strongly discouraged. Doing so will block certain administrative ...
- TF401069: An exception occurred during upgrade that may prevent new or changed user identities to be recognized by the work ...
- TF401074 : TFS does not currently support the "/layout" switch. To proceed, please download the ISO images or use the web ...
- TF401090 : The build service was originally configured for HTTPS, but the certificate was not found in the certificate store. ...
- TF401091 : The build service was previously configured to run interactively. However, '{0}' was specified as the service ...
- TF401131: The Team Foundation Server web application was previously configured with one or more bindings that are not currently ...
- TF401145: The Team Foundation Server web application was previously configured with one or more bindings that have ports ...
- TF401148: None of the previously configured ports (including the TFS default 8080 port) are availble. See the log for additional ...
- TF401149: None of the previously configured ports were available. Using the default TFS port (8080). See the log for additional ...
- TF401150 - None of the previously configured ports are available on the server. If you continue, TFS will be configured using ...
- TF401151 - Port {0} is currently unavailable. If you continue, TFS will be configured using the default 8080 port. Afterwards, ...
- TF401163: The identity with type '{0}' and identifier '{1}' could not be found. Continuing to process remaining identities. ...
- TF401218: The project collection '{0}' cannot be detached. The host is in the process of being serviced. The servicing may ...
- TF401219: The team project collection '{0}' cannot be detached because its version ID is different than the ID for the configuration ...
- TF42006: The build service could not get the project file for build definition {0}. Ensure the project file exists and the ...
- TF42008: The test case management package could not be loaded. Verify that Visual Studio Test Tools is installed and try ...
- TF42015: The build definition file TfsBuild.proj for build definition {0} could not be read. The format of the file is invalid, ...
- TF42017: Unable to create the build definition specified because the connection to the server timed out. Wait for few minutes ...
- TF42018: The DoNotDownloadBuildType flag in configuration file of TFSBuildService.exe is set to true but {0} does not exist. ...
- TF42018: The DoNotDownloadBuildType property is set to true but {0} does not exist. Set the DoNotDownloadBuildType property ...
- TF42022: The workspace {0} does not have any working folder mappings. Verify the working folder mappings of selected workspace ...
- TF42023: Failed to get test metadata (.vsmdi) file for the selected workspace {0}. Verify that the workspace contains one ...
- TF42024: Failed to start the wizard. The workspace {0} is preventing the wizard from creating temporary workspace required ...
- TF42025: The wizard could not check the build definition files into source control. Verify the network connection and try ...
- TF42026: Failed to start the wizard. The temporary workspace {0} needed for this operation already exists. Delete this workspace ...
- TF42027: Team Build could not get the solution files for the team project. Verify that the {0} workspace mapping is correct ...
- TF42036: There is no build definition available to build the team project {0}. Create a new build definition and try again. ...
- TF42043: Team Foundation Build could not load the correct editor. Verify that the Team Foundation Client is installed and ...
- TF42050: Invalid build directory: {0}. The build directory cannot be a UNC path, relative path or drive name. Specify the ...
- TF42052: The file system on the build machine does not support access control lists. Specify build directory on a file system ...
- TF42053: The build machine is not configured to build for server {0}. The build machine is configured for one Team Foundation ...
- TF42054: Invalid drop location: {0}. The drop location must be a UNC path or a valid TFS server path under a team project. ...
- TF42058: The build process was not able to set access control on {0}. Grant the user account running the build process full ...
- TF42067: The configuration '{0}' contains characters which are not allowed. Characters which are not allowed include ' ', ...
- TF42092: A work item could not be created for a failure in build '{0}'. Verify that the work item type '{1}' is supported ...
- TF42092: A work item could not be created for a failure in build '{0}'. Verify that the work item type '{1}' is supported ...
- TF42093: The work item {0} could not be updated with build information. The field {1} is not available on this work item. ...
- TF42094: A work item could not be created for build failure. Verify valid properties are specified as name=value pairs separated ...
- TF42098: A work item could not be created for build failure. The build service account does not have the permissions to save ...
- TF500223: The Compare Labels command cannot be used with this version of the database. Please compare labels with another ...
- TF500224: The maximum allowed server path length has been decreased on the server which is not supported. Please contact ...
- TF50233: A cyclic group containment error occurred when adding a group member. The group {1} already has the group {0} as ...
- TF50241: The following Team Foundation group name is not valid: '{0}'. For more information about valid naming conventions ...
- TF50251: Background synchronization of identities was aborted. Synchronization will restart when the Team Foundation Server ...
- TF50279: The Team Foundation Server Group Security subsystem has returned an error. See the Team Foundation Server event ...
- TF50309: The following account does not have sufficient permissions to complete the operation: {0}. One of the following ...
- TF50309: The following account does not have sufficient permissions to complete the operation: {0}. The following permissions ...
- TF50313: The reclassification node and the deleted node must be in the same hierarchy. Deleted node: {0}. Reclassification ...
- TF50316: The following name is not valid: {0}. Verify that the name does not exceed the maximum character limit, only contains ...
- TF50329: The root structure names are not unique. Each root structure must have a unique name. For more information about ...
- TF50364: The following distinguished name (DN) is not formatted correctly or contains an empty string: '{0}'. Make sure that ...
- TF50610: Unable to delete access control entry for object {0}, permission {1}, user {2}, and deny {3} since it does not exist. ...
- TF50615: GSS: There was a failure reading group membership from Active Directory. No action is required, and another method ...
- TF50621: The Team Foundation group that you wish to manage is not owned by service host {0}, it is owned by {1}. Please target ...
- TF50633: This group cannot be removed. Team Foundation requires the existence of this Administrators group for its operation. ...
- TF50634: This group cannot be removed. Team Foundation requires the existence of this Valid Users group for its operation. ...
- TF50635: This group cannot be removed. Team Foundation requires the existence of this Service Accounts group for its operation. ...
- TF50643: Team Foundation Server was unable to retrieve identity information from Active Directory for {0}\{1} because the ...
- TF51215: Reporting for Team Foundation Server contains metadata which is not valid. Dimension {0} does not exist. Use Team ...
- TF51218: Reporting for Team Foundation Server contains metadata which is not valid. Fact {1} does not contain field {0}. ...
- TF51229: The measure {1} cannot be added to measure group {2} because measure type {0} is not supported by the Analysis Services ...
- TF51230: The measure {2} cannot be added to measure group {3} because measure type {0} cannot be converted to {1}. Use Team ...
- TF51309: Cannot upload the file because the value for Area Node URI is missing. Check and make sure the work item version ...
- TF51316: The maximum attachment size exceeds the allowable maximum of {0} bytes. Upload a smaller file, or change the maximum ...
- TF51516: The field name contains characters that are not supported. Field names can contain alphanumeric characters, underscores, ...
- TF51548: There are no metadata row versions provided, or the versions do not match the number of metadata tables requested. ...
- TF51582: The column name you entered contains unsupported characters. Enter a column name using only alphanumeric characters. ...