Visual Studio 2010
- TF255477: You cannot configure the server because you are missing the following server scope permission: {0}. Consider adding ...
- TF255478: You cannot configure the server because you are missing the following permission: {0}. The database is: {1}. The ...
- TF255479: You attempted to attach a collection database that is already registered in Team Foundation Server. You cannot ...
- TF25547: One or more software updates could not be applied to the configuration database. The following error occurred: {0}. ...
- TF255480: The built-in security group IIS_IUSRS cannot be resolved. For more information about how to troubleshoot this issue, ...
- TF255481: You cannot configure Team Foundation Server because the built-in security group IIS_IUSRS has been renamed to: ...
- TF255482: Team Foundation Server could not start collecting Software Quality Metrics for Lab Management. Wait several minutes, ...
- TF255483: Team Foundation Server could not stop collecting Software Quality Metrics for Lab Management. Wait several minutes, ...
- TF255484: A Web site is configured to use the same port as the Web site for SharePoint Central Administration. You must manually ...
- TF255484: You have chosen to configure '{0}' as your Team Foundation Server and System Center Virtual Machine Manager Server. ...
- TF255485: Team Foundation Server failed to start. The following error occurred: {0}. For possible diagnosis of the problem, ...
- TF255486: Team Foundation Server failed to stop. The following error occurred: {0}. For possible diagnosis of the problem, ...
- TF255488: One or more software updates could not be applied to the following collection database: {0}. The following error ...
- TF255491: The following database is not at the same service level at the application tier: {0}. The database can be updated ...
- TF255492: The following database has a pre-release software update installed that is not installed on the application tier: ...
- TF255493: The following database has an unknown SERVICE_LEVEL_TO stamp and cannot be updated to the same level as the application ...
- TF255494: The following database has a more recent service level than this application tier: {0}. The following software ...
- TF255496: An uninstall operation for one or more software updates did not complete successfully on the following database: ...
- TF255501: The configuration database could not be updated to the level of the application tier. For more information, run ...
- TF255503: The following team project collection could not be updated to the level of the application tier: {0}. For more ...
- TF255504: The job to update the collection could not be queued for the following collection database: {0}. The following ...
- TF255506: The following database is a pre-release Team Foundation Server database: {0}. The database cannot be used with ...
- TF255507: The security identifier (SID) for the following SQL Server login conflicts with a specified domain or workgroup ...
- TF255508: The verification of XML serialization failed due to an exception. This error has a number of possible causes, including ...
- TF255509: A canonically ordered access control list (ACL) could not be found. The following path could not be checked: {0}. ...
- TF255510: The following path contains an access control list (ACL) that is not canonically ordered: {0}. This indicates that ...
- TF255511: A problem has been detected that will prevent the creation of the data sources for SQL Server Reporting Services. ...
- TF255512: You do not have a sufficient amount of RAM available on this computer to configure both the application tier and ...
- TF255513: The name of the server is not set. The @SERVERNAME variable returns NULL. The server that hosts the databases for ...
- TF255513: Verify that TFS Service account is a member of Administrator role in SCVMM. To ensure this, go to Lab Management, ...
- TF255514: An error occurred while attempting to verify that the @SERVERNAME variable is not NULL. The server that hosts the ...
- TF255514: Verify that the TFS Service account is a member of Administrator group on each host. To ensure this, for each project ...
- TF255515: The following database is mirrored: {0}. You must stop mirroring the database before you can service the database. ...
- TF255516: An error occurred while attempting to verify that the following database is not mirrored: {0}. The server that ...
- TF256002: Team Explorer cannot write to the project list configuration file. Free up space on the local hard disk. If the ...
- TF257000: The value for Action Pane Suppression could not be created in the registry. For more information, see the configuration ...
- TF257001: The information about the service account could not be changed. For more information about this error, review the ...
- TF257002: The information about the password for the service account could not be changed. For more information about this ...
- TF257003: Team Foundation Server could not update the Lab Management settings and returned the following message: {0}. For ...
- TF257007: An error occurred while the following management extension for Team Foundation was being loaded: {0}. For more ...
- TF257010: An error occurred while the snap-in for the Team Foundation Administration Console was being initialized in the ...
- TF257012: An unhandled exception occurred and the administration console will close. For more information, review the configuration ...
- TF257012: The snap-in for the Team Foundation Administration Console will be unloaded because of an unhandled exception error. ...
- TF257013: The Team Foundation Administration Console is open. You cannot use the TFSConfig RegisterDB command-line utility ...
- TF257014: The authentication mode is currently set to NTLM. You cannot change the authentication mode to Negotiate (Kerberos). ...
- TF258000: The following log file could not be created: {0}. Your account might not have the permissions required to write ...
- TF259001: Team Foundation Server could not find the network adapter with physical address {0} on virtual machine {1}. Retry ...
- TF259002: Team Foundation Server could not add virtual machine to environment {0} (ID:{1}, URI {2}). Additional Information: ...
- TF259003: The library shares in the following environment are not on deployed on same host for network isolation: {0} (ID: ...
- TF259004: Team Foundation Server could not import virtual machine: {0}. The virtual machine was disabled by the system administrator. ...
- TF259005: Team Foundation Server could not import the following virtual machine because it was deleted from VMM: {0}. Use ...
- TF259006: Team Foundation Server cannot cancel the operation: {0}. This operation is not cancellable. Wait for the operation ...
- TF259007: Team Foundation Server cannot find the snapshot with ID {0}. The snapshot might have been deleted. Select a different ...
- TF259009: The network agent could not configure the automatic DNS registration settings of the network adapter because of ...
- TF259010: The network agent could not configure NetBIOS on the network adapter because of platform error: {0}. Pause and ...
- TF259011: The virtual machine could not acquire an external IP address from DHCP because it might not be connected to an ...
- TF259012: Team Foundation Server could not retry the last unsuccessful operation: {1}. This operation cannot be retried when ...
- TF259013: The network agent could not assign DNS servers for the network adapter because of platform error: {0}. Pause and ...
- TF259014: Team Foundation Server could not configure network isolation capability for lab since an invalid DNS suffix was ...
- TF259015: Team Foundation Server could not validate given DNS suffix. DNS server reported the failure for this suffix: DNS ...
- TF259016: Team Foundation Server could not configure network isolation capability for lab since an invalid DNS suffix was ...
- TF259017: Team Foundation Server could not configure network isolation capability for lab. A non-empty DNS suffix is required ...
- TF259018: Team Foundation Server could not configure network isolation capability for lab since an invalid DNS suffix was ...
- TF259019: There are more than one network adapter with physical address {0} on virtual machine {1}. Contact your system administrator ...
- TF259020: Team Foundation Server could not pass KVP DataExchange items to LS {0} (VM {1}) in environment {2} on Hyper-V host ...
- TF259021: Team Foundation Server could not configure network isolation because either the virtual network components of this ...
- TF259022: The network agent could not locate the external network adapter on the virtual machine because of platform error: ...
- TF259023: The network agent encountered an error while starting because of platform error: {0}. Shutdown and start the environment ...
- TF259024: The use of the Team Foundation Server API is incorrect because the NoExternalNetworkConnection must always be set ...
- TF259025: The MAC address range in VMM is set to the default value. Assign unique values to the MAC address range, or make ...
- TF259026: Team Foundation Server found the virtual machine in a failed state: {0}. VMM returned the following information: ...
- TF259027: Team Foundation Server found the virtual machine in a failed state: {0}. Contact your system administrator and ...
- TF259028: Team Foundation Server is unable to find details of the virtual machine because the virtual machine host is not ...
- TF259029: Team Foundation Server could not import the following virtual machine because the virtual machine is not a golden ...
- TF259030: Team Foundation Server could not update the environment. Tags for virtual machines cannot be updated for a deployed ...