SQL Server 2008 R2

  1. The configuration type in one of the configuration entries was not valid. Valid types are listed in the DTSConfigurationType ...
  2. The configuration value for the registry configuration was not found in key "%1!s!". Add a value called Value to the registry ...
  3. The configurations settings could not be applied to the '{0}' data source because the data source does not exist in the database. ...
  4. The configurations settings could not be applied to the '{0}' dimension because the dimension is not present in the database. ...
  5. The configurations settings could not be applied to the '{0}' measure group in the '{1}' cube because the measure group is ...
  6. The configurations settings could not be applied to the '{0}' mining structure because the mining structure is not present ...
  7. The configured executable file '{0}' does not exist or External Activator service does not have the permission to access ...
  8. The configured value for Extended Protection is not valid. Check Network Configuration settings in SQL Server Configuration ...
  9. The configured value for the Accepted SPNs list is not valid. Check Network Configuration settings in SQL Server Configuration ...
  10. The configured working directory '{0}' does not exist or External Activator service does not have the permission to access ...
  11. The conflict resolver chose to delete this row at '%1' due to a conflict in the logical record between '%1' and '%2' in which ...
  12. The conflict resolver chose to update or insert this row at '%1' with the data from '%2' due to a conflict in the logical ...
  13. The connected user is not an Analysis Services server administrator. Only an administrator can make changes to server properties. ...
  14. The connection "%1!s!" is not found. This error is thrown by Connections collection when the specific connection element ...
  15. The connection "%1!s!" specifies a SQL Server instance with a version that is not supported for transfer. Only versions 7, ...
  16. The connection failed because this instance of SQL Server is not supported. The editor cannot connect to SQL Server 2000 ...
  17. The connection has been dropped because the principal that opened it subsequently assumed a new security context, and then ...
  18. The connection has been lost with Microsoft Distributed Transaction Coordinator (MS DTC). Recovery of any in-doubt distributed ...
  19. The connection is no longer usable because the server failed to respond to a command cancellation for a previously executed ...
  20. The connection is no longer usable because the server response for a previously executed statement was incorrectly formatted. ...
  21. The connection manager "%1!s!" has an unsupported type "%2!s!". Only "FILE" and "OLEDB" connection managers are supported. ...
  22. The connection manager "%1!s!" is an incorrect type. The type required is "%2!s!". The type available to the component is ...
  23. The connection manager "%1!s!" is not found. A component failed to find the connection manager in the Connections collection. ...
  24. The connection manager "%1!s!" will not acquire a connection because the package OfflineMode property is TRUE. When the OfflineMode ...
  25. The connection manager named "{0}" is not supported by this release. Only Ado.Net connections to Microsoft SQL Server 2000 ...
  26. The connection manager state information from the clipboard for the connection manager with moniker '{0}' could not be loaded. ...
  27. The connection string cannot be found. Open Microsoft SQL Server Management Studio and, in the Analysis Server Properties ...
  28. The connection string components cannot contain unquoted semicolons. If the value must contain a semicolon, enclose the entire ...
  29. The connection string format is not valid. It must consist of one or more components of the form X=Y, separated by semicolons. ...
  30. The connection string is not valid. Press OK to build a new connection string, or press Cancel to edit the existing connection ...
  31. The connection string to repository needs to be specified in the 9.0 server properties (see . section in msmdsrv.ini file ...
  32. The connection to the Analysis Services server database using connection manager '{0}' failed to connect. Verify that the ...
  33. The connection to the current workbook has been closed because a newer version of the workbook exists in SharePoint. To continue, ...
  34. The connection to the database could not be created. Only connections to local database files (Sql .MDF and Jet .MDB) are ...
  35. The connection to the server on which the agent runs must impersonate the process account. The process account must be a ...
  36. The connection to the server on which the agent runs must impersonate the process account. The process account must be a ...
  37. The connection type "%1!s!" specified for connection manager "%2!s!" is not recognized as a valid connection manager type. ...
  38. The connection type of the data source has changed. Connection managers that are based upon this data source are no longer ...
  39. The connection type specified for connection manager is not a valid connection manager type. This error occurs when an attempt ...
  40. The consistency check operation for blob store took more than three times the maximum allowed wait time of {2} seconds. Trying ...
  41. The constraint "%1!s!" was not created because one or more columns in the constraint is not published. Either include all ...
  42. The constraint is used by merge replication for identity management and cannot be dropped directly. Execute sp_changemergearticle ...
  43. The constraints of %1!s! name, "%2!s!", have been violated. The object does not support binding to actions or predicates. ...
  44. The container can not be dropped because changes exist that require a log backup. Take a log backup and then retry the ALTER ...
  45. The container cannot be set to the offline state because changes exist that require a log backup. Take a log backup and then ...
  46. The content model of type '%1!s!' contains two elements with the same name '%2!s!' and different types, nullability, or value ...
  47. The content type of the '%{column/}' column of the '%{structure/}' mining structure can only be used to classify other columns. ...
  48. The contents of the attribute with Id of '%{attributeId/}', Name of '%{attributeName/}' cannot be updated because the dimension ...
  49. The contents of the file "%1!s!" are not consistent with a transition into the restore sequence. A restore from a backup ...
  50. The Context object cannot be used since there is no available server context. This typically occurs because the AdomdServer ...
  51. The context of the output column could not be retrieved. To add an output column, select either an output or another output ...
  52. The context transaction which was active before entering user defined routine, trigger or aggregate "%1!s!" has been ended ...
  53. The continuous content type cannot be determined due to the following problem: {0} You may manually change each mining structure ...
  54. The continuous key column reference (KEY TIME, KEY SEQUENCE) is not supported in a SELECT DISTINCT statement at line %d{Line/}, ...
  55. The conversation endpoint with conversation handle '%1!s!' is in an inconsistent state. Check the SQL Server error logs and ...
  56. The conversation endpoint with ID '%1!s!' and is_initiator: %2!s! is referencing the invalid conversation group '%3!s!'. ...
  57. The conversation endpoint with ID '%1!s!' and is_initiator: %2!s! is referencing the invalid conversation handle '%3!s!'. ...
  58. The conversation endpoint with ID '%1!s!' and is_initiator: %2!s! is referencing the missing service contract with ID %3!s!. ...
  59. The conversation with ID '%1!s!' and initiator: %2!s! references a missing conversation group '%3!s!'. Run DBCC CHECKDB to ...
  60. The conversion of the result of the expression"%1!s!" from type "%2!s!" to a supported type failed with error code 3!8.8X!. ...
  61. The copy columns, "%1!s!" and "%2!s!", do not have equal data types or are not trivially convertible string types. This occurs ...
  62. The CPU architecture of installing feature(s) is different than the instance specified. To continue, add features to this ...
  63. The CPU architectures of feature(s) you selected to removed are different then Setup. To remove these features, Setup architecture ...
  64. The CPU architectures of upgrading feature(s) and this installation program are different. To upgrade these features, Setup ...
  65. The CPU platform for the {0} feature is inconsistent between the nodes of the cluster. To cluster an instance, the platform ...
  66. The CREATE %1!s! statement is missing the required parameter '%2!s!'. Validate the statement against the index-creation syntax. ...
  67. The Create command cannot be executed since it is attempting to create an object in a read only database with the name of ...
  68. The CREATE DATABASE statement failed. The primary file must be at least %1!s! MB to accommodate a copy of the model database. ...
  69. The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name '%1!s!' and the index ...
  70. The Create Utility Control Point Wizard will help you to create a UCP on an instance of SQL Server to manage your SQL Server ...
  71. The CreateFolderOnSQLServer method has encountered OLE DB error code 1!8.8X! (%2!s!) The SQL statement issued has failed. ...
  72. The creation of adapter factory of type '{0}' failed. Make sure the factory type is a non-abstract class with parameterless ...
  73. The credentials you provided for the Analysis Services service are invalid. To continue, provide a valid account and password ...
  74. The credentials you provided for the Full-text service are invalid. To continue, provide a valid account and password for ...
  75. The credentials you provided for the Integration Services service are invalid. To continue, provide a valid account and password ...