Visual Studio 2013
- TF401101: This command is not supported on Team Foundation Server 2012 or older. Use agileprocessconfig or commonprocessconfig ...
- TF401102: To update the project configuration in this version of Team Foundation Server, you need to use the new project ...
- TF401103: The following plural name contains invalid characters: {0}. The following characters are not valid: @ ~ ; ' + = ...
- TF401131: The Team Foundation Server web application was previously configured with one or more bindings that are not currently ...
- TF401133: Your account doesn't have permissions to enter this Team Room. To get the permissions have an administrator grant ...
- TF401145: The selected database {0} is a TFS 2008 database. These databases cannot be upgraded to TFS 2013 directly. You ...
- 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 {0} port) are availble. See the log for additional ...
- TF401149: None of the previously configured ports were available. Using the default TFS port ({0}). 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 {1} port. Afterwards, ...
- TF401155: The selected database is only compatible with a newer major version of Team Foundation Server. You need to cancel ...
- TF401158: Team Foundation Server requires SQL Server 2012 SP1 (11.00.3000) or greater. The SQL Server instance {0} you supplied ...
- TF401158: The SQL Server instance you specified ({0}) is version {1}, which cannot be used in place or upgraded. Either uninstall ...
- TF401159: Team Foundation Server requires SQL Server 2012 SP1 (11.00.3000) or greater. The SQL Server instance {0} you supplied ...
- TF401159: The SQL Server instance you specified ({0}) is version {1}, which cannot be used in place or upgraded. For more ...
- TF401160: The following SQL instance is not supported by the local SharePoint Foundation 2013 installation: {0}. SharePoint ...
- TF401172: The team you have selected in the mapping panel has been deleted. To update the list of available teams refresh ...
- TF401173: The team you have selected in the mapping panel has invalid configuration settings. Before you can use this team, ...
- TF401174: The item '{0}' could not be found in the repository '{1}' at the version specified by '{2}' (resolved to commit ...
- TF401178: You lack the permission(s) required for the operation you are attempting. You need to have '{0}'. Please contact ...
- TF401190: The local workspace {0} has {1} items in it, which exceeds the recommended limit of {2} items. To improve performance, ...
- TF401191: A version control folder for the team project '{0}' could not be created because another source control system ...
- TF401196: The upgrade will create {0} new system fields, but there is only space for {1} of them in Team Project Collection: ...
- TF401196: The upgrade will create {0} new system fields, but there is only space for {1} of them in the Team Project Collection. ...
- TF401200 : Team Foundation Server SharePoint Extensions has detected that this version of Windows is a client operating system. ...
- TF401201 : Team Foundation Server SharePoint Extensions has detected that this version of Windows is a Domain Controller. ...
- TF401202 : Team Foundation Server SharePoint Extensions has detected that this is not a supported version of Windows Server. ...
- TF401203: You cannot use a custom template stored in a Git repository for {0}. To use a custom template stored in a Git repository, ...
- TF401210: TFS cannot configure a stand-alone installation of SharePoint. Re-install SharePoint in farm or web front end mode. ...
- TF401213: You are trying to view a chart that contains links or a tree of work items. Charts can only be rendered for queries ...
- TF401222: TFS has detected that you have SQL Server installed on this machine. SharePoint Foundation 2013 includes a new ...
- TF401223: An error occurred while installing the prerequisites for SharePoint Foundation 2013. For more information, review ...
- TF401226: Cannot save service definition with type {0} identifier {1} because parent definition with type {2} identifier ...
- TF401252 : You cannot reuse your previous installation path when performing a major upgrade of Team Foundation Server. To ...
- TF401255: This element defines the fields that appear on the add panel for your product backlog. Fields must be one of the ...
- TF401270: Validation of the newly installed version of SQL Express failed. See the configuration logs for additional details. ...
- TF401293: The specified SQL Server instance '{0}' is invalid. A port number and a named instance cannot be specified simultaneously. ...
- TF401300: The specified SQL Server instance '{0}' is invalid. The specified port number does not fall within the valid range ...
- TF401312: The Work Item Chart Transform uses an AssignedToMe query, but the chart owner identification does not match the ...
- TF401313: The Work Item Chart Transform uses an AssignedToMe query, but information to identify the owner could not be found ...
- TF401317: An error occurred while recording the collation of the following database: {0}. The server hosting the database ...
- 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 ...
- TF50364: The following distinguished name (DN) is not formatted correctly or contains an empty string: '{0}'. Make sure that ...
- 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. ...