Visual Studio 2012
- TF246064: No database could be found for the following host: {0}. The host has the following ID: {1}. To fix this problem, ...
- TF246065: No framework connection string could be found for the following host: {0}. The host has the following ID: {1}. ...
- TF246069: The following database could not have its lease renewed because it cannot be reached: {0}. The database is hosted ...
- TF246070: An exception error occurred while logging user requests for the following host: {0}. No further exceptions for ...
- TF246077: No identity provider could be found for the following identity type: {0}. Either the provider does not exist, or ...
- TF246078: The instance stamp is either corrupt or does not exist. Either restore the database, or contact customer support ...
- TF246079: A team project collection already exists with the following ID: {0}. Collections must be unique within a deployment ...
- TF246081: An error occurred while attempting to attach the team project collection. The collection was not detached properly. ...
- TF246082: The call to EnterMethod was not valid because the following method is currently executing: {0}. The following process ...
- TF246083: The configuration of Team Foundation Server is not valid. You must remap the databases in order to fix the configuration. ...
- TF246084: There is an error with the configuration of Team Foundation Server. No default access mapping could be found for ...
- TF246086: The following access point is not valid: {0}. It conflicts with the following access point: {1}. That access point ...
- TF246087: The path to the registry contains one or more characters that are not allowed. Characters which are not allowed ...
- TF246088: The team project collection cannot be attached. The collection needs to be upgraded, and the following issue prevents ...
- TF246089: The value for the dataDirectory configuration is not valid and will be ignored. The value must be an absolute path, ...
- TF246090: An error occurred while parsing the following dataDirectory configuration value: {0}:{1}. The value will be ignored. ...
- TF246091: The team project collection cannot be attached because its version ID is higher than the ID for the configuration ...
- TF246092: An error occurred while attempting to change the state of the following team project collection: {0}. The collection ...
- TF246093: An error occurred while attempting to change the state of the configuration database for Team Foundation Server. ...
- TF246094: The following catalog change type is not valid when saving a catalog node: {0}. Change the type or remove the entry, ...
- TF246095: The following catalog change type is not valid when saving a catalog resource: {0}. Change the type or remove the ...
- TF246097: Authentication using Team Foundation identities is not supported for Team Foundation Server. You must use Windows ...
- TF246098: A team project collection already exists with the following name: {0}. Collection names must be unique within a ...
- TF246099: The following team project collection name is not valid: {0}. Collection names cannot contain duplicate periods. ...
- TF246102: The following virtual path is not valid: {0}. The path conflicts with a reserved path or with a virtual path that ...
- TF246103: The following team project collection name is not valid: {0}. The collection name is reserved for use by Team Foundation ...
- TF246104: There is a problem with the following database: {0}. The database might be corrupt, or it might not be compatible ...
- TF246106: A team project collection already exists with the proposed database connection string. Connection strings must ...
- TF247004: The root path of the branch is not accessible: {0}. Verify that the path is a branch or obtain required permissions ...
- TF247006: You are attempting to track one or more changesets that contain a total of {0} items, but the maximum number items ...
- TF247009: You cannot track any of the specified changesets from the starting branch you specified ({0}) because it is not ...
- TF248001: You have specified a project-scoped group, '{0}', which is not allowed for a global list or a global workflow that ...
- TF248003: You cannot create categories of work item types. Either this feature is not enabled on this server, or it is running ...
- TF248004: You cannot create custom types of links between work items. Either this feature is not enabled on this server, ...
- TF248005: You cannot create a field of the GUID. Either this feature is not enabled on this server, or it is running a version ...
- TF248006: You cannot create a field of the Boolean type. Either this feature is not enabled on this server, or it is running ...
- TF248007: You cannot use the 'in group' operator to run a query. Either this feature is not enabled on this server, or it ...
- TF248008: You cannot run a query for revisions. Either this feature is not enabled on this server, or it is running a version ...
- TF248009: You cannot run a query that compares fields. Either this feature is not enabled on this server, or it is running ...
- TF248010: You cannot lock a link between work items. Either this feature is not enabled on this server, or it is running ...
- TF248011: You cannot save work items to more than one project in a single operation. Either this feature is not enabled on ...
- TF248013: The {0} and {1} links control elements are not compatible. Either do not set the {2} attribute of the {1} element ...
- TF248015: Your work item query could not be completed due to an unexpected error returned by the Microsoft SQL Server Full-text ...
- TF248016: You cannot use the In Group operator with the field '{0}'. You can use the In Group operator only with the Work ...
- TF248017: You cannot specify the "renamesafe" attribute for field '{0}'. You can only specify the "{2}" attribute for a field ...
- TF248018: You cannot change the "{1}" attribute of field '{0}' in a work item type definition. You can only change the value ...
- TF248020: You cannot specify the 'Reportable' attribute for field '{0}'. You can only define the reportable attribute for ...
- TF248021: You have specified a query string that is not valid when you use the query method for a flat list of work items. ...
- TF248022: You have specified a query string that is not valid when you use the query method for linked work items. You cannot ...
- TF248023: Your work item has not been saved. Review the history which contains conflicting changes made recently by another ...
- TF248024: Your changes were not saved because the work item was updated recently by another user and the resulting merged ...
- TF249001: You have specified the URL for a project collection, but the application instance that contains the project collection ...
- TF249002: Your user account does not have permission to connect to the Team Foundation Server at {0}. Ask your server administrator ...
- TF249004: The reference to reports and dashboards for this site could not be changed. An error occurred while attempting ...
- TF249011: The specified site is not valid. You must specify a SharePoint site on a server that is running a version of SharePoint ...
- TF249016: Reports could not be configured for the server. The Visual Studio Team System cube does not point to the data warehouse ...
- TF249020: A SharePoint site could not be created at the following location: {0}. The user account does not have the required ...
- TF249021: The following relative path is not valid: {0}. The relative path must be a single subdirectory beneath the root ...
- TF249029: A list of reports could not be retrieved from the server. Either no reports are stored on the server, or the server ...
- TF249029: A list of reports could not be retrieved from the server. Either no reports are stored on the server, or the server ...
- TF249030: A folder with the following name already exists on the server: {0}. You must specify a different name for the folder. ...
- TF249031: A folder with the following name could not be created: {0}. The user account does not have permissions to create ...
- TF249032: A folder with the following name could not be accessed: {0}. Either that folder does not exist, or the user account ...
- TF249033: The site template is not available for the locale identifier (LCID). The site template name is: {0}. The LCID is: ...
- TF249034: A folder could not be created. The account might not have the required permissions to create a folder in this location. ...
- TF249035: The following file could not be uploaded: {0}. The file name contains one or more characters that are not allowed. ...
- TF249038: The following Web service is not available: {0}. This Web service is used for the Team Foundation Server Extensions ...
- TF249040: The catalog does not contain a team project with the following URL: {0}. Verify that the specified URL is correct. ...
- TF249044: A report can only be uploaded once to any location. The process template uploads the following report more than ...
- TF249046: The URL could not be resolved for the following service: {0}. Service zone and location information might not be ...
- TF249049: Team Foundation Server could not open the dialog because the threading model must be single-threaded apartment. ...
- TF249051: No URL can be found that corresponds to the following server name: {0}. Verify that the server name is correct. ...
- TF249053: Team Explorer cannot write to the project list configuration file. Free up space on the local hard disk. If the ...
- TF249053: The timeout limit for servicing the collection has been exceeded. The servicing job will continue to run, but no ...
- TF249058: The path that you specified for the report item, '{0}', is not valid. The path must not be empty, must begin with ...