Visual Studio 2010
- TF246019: The Team Foundation Server trial period has expired, or the license is not valid. You must update your license ...
- TF246020: Microsoft SQL Server encountered an error while processing the results from one of the Team Foundation Server databases. ...
- TF246021: An error occurred while processing your request. Technical information (for administrator): SQL Server Error: {0} ...
- TF246022: Another synchronization task is already in progress. The additional background synchronization of identities will ...
- TF246023: The value must be unique for the following property: {0}. The following resource already has this value: {1}. You ...
- TF246024: An error occurred while attempting to build catalog nodes. A catalog node is missing the following path to its ...
- TF246025: The argument you specified is not valid. You cannot pass a value for Catalog Node to the Web service without also ...
- TF246026: The required node named '{0}' is missing from the catalog service. The most likely cause of this error is that ...
- TF246027: A catalog node cannot be created. No dependent node exists with the following association key: {0}. You must create ...
- TF246028: You cannot save the node. When saving a node with dependencies on the Web service you must specify the nodes upon ...
- TF246030: One or more changes that you specified are not valid. Two or more nodes at the same level point to the same catalog ...
- TF246032: You cannot non-recursively delete a catalog node of the following type: {0}. You must recursively delete this node ...
- TF246033: You cannot recursively delete a catalog node of the following type: {0}. You must non-recursively delete this node ...
- TF246034: One or more catalog nodes has a dependency upon itself. Catalog nodes cannot contain dependencies on themselves. ...
- TF246036: The following catalog resource type is not valid: {0}. The node must have a dependency with the following name: ...
- TF246037: No parent can be found for the following catalog node: {0}. Either the parent node does not exist, or it has not ...
- TF246039: The catalog service received an unexpected request from the following service host: {1}. The catalog service expected ...
- TF246040: The following catalog resource cannot be created: {0}. At least one node must reference the catalog resource in ...
- TF246042: The catalog node cannot be created with the following resource type: {0}. The catalog node cannot contain a resource ...
- TF246043: The catalog node cannot be created with the following resource type: {0}. The catalog node cannot contain a resource ...
- TF246044: A catalog node dependency is not valid, but has been loaded. The following catalog node path does not exist: {0}. ...
- TF246047: The following catalog resource type is not valid: {0}. A resource of this type must contain a property with the ...
- TF246048: The following catalog resource type is not valid: {0}. The type must contain a service reference with the following ...
- TF246049: You cannot move the node in the catalog web service unless you specify both the node being moved and the new parent ...
- TF246053: The location service received an unexpected request from the following service host: {1}. The location service ...
- TF246054: A service definition has already been registered with the specified service type and identifier. Service type: ...
- TF246055: The service definition cannot be updated. No service definition exists with the specified service type and identifier. ...
- TF246056: The following security token is not valid: {0}. This security namespace has a hierarchical structure with the following ...
- TF246057: The following security namespace is not valid: {0}. The ID of the namespace is: {1}. The namespace contains the ...
- TF246059: An error occurred in the following security namespace: {0}. The security namespace received an unexpected request ...
- TF246059: The security service received an unexpected request from the following service host: {1}. The security service ...
- TF246061: An unexpected ID was received from the database in the following location: {0}. The database is stamped with the ...
- TF246062: Two or more databases are in conflict because they are each designated as the owners of the following schema: {0}. ...
- TF246063: No database could be found as the designated owner of the following schema: {0}. The schema is for the host with ...
- 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 for the following database: {0}. Either restore the database, ...
- 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 was created using a beta release of Team Foundation ...
- 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 following database connection string: {0}. Connection strings ...
- TF247004: The root path of the branch is not accessible: {0}. Verify that the path is a branch or obtain required permissions ...
- TF247005: At least one changeset cannot be tracked because an item is not contained in a branch. You need to identify a container ...
- TF247006: There are {0} items to track. When tracking more than {1} items you should select a path filter to avoid performance ...
- 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 ...