SQL Server 2008

  1. A corrupted message has been received. The MIC size is %1!s!, however it must be no greater than %2!s! bytes in length. This ...
  2. A corrupted message has been received. The salt size is %1!s!, however it must be %2!s! bytes. This occurred in the message ...
  3. A corrupted message has been received. The security certificate key fields must both be present or both be absent. This occurred ...
  4. A corrupted message has been received. The security dialog message header is invalid. This occurred in the message with Conversation ...
  5. A corrupted message has been received. The service pair security header destination certificate, the key exchange key, the ...
  6. A corrupted message has been received. The service pair security header size is %1!s!, however it must be between %2!s! and ...
  7. A corrupted message has been received. The service pair security header source certificate and the signature must both be ...
  8. A corrupted message has been received. The session key ID is missing. This occurred in the message with Conversation ID '%1!s!', ...
  9. A corrupted message has been received. The session key ID size is %1!s!, however it must be %2!s! bytes. This occurred in ...
  10. A corrupted message has been received. The unsigned dialog message header is invalid. This occurred in the message with Conversation ...
  11. A cryptographic operation failed. This error indicates a serious problem with SQL Server. Check the SQL Server error log ...
  12. A cursor plan could not be generated for the given statement because the textptr() function was used on a LOB column from ...
  13. A custom data source is defined specifically for this data-driven subscription and cannot be used by other data-driven subscriptions. ...
  14. A custom property in the {0} {1}' has the name "{2}". Custom property names cannot be null and must be unique within the ...
  15. A custom property named "%1!s!" is invalid because there is a stock property with that name. A custom property cannot have ...
  16. A custom role cannot contain both system-level and non-system-level tasks in the same role definition. You must specify different ...
  17. A data source does not provide features such as caching metadata, adding relationships, adding calculations, and adding annotations. ...
  18. A data source view must be created before performing this action. This can be accomplished with the Schema Generation Wizard. ...
  19. A data type that stores values of various SQL Server-supported data types, except text, ntext, timestamp, and sql_variant. ...
  20. A database must have primary FILESTREAM log filegroup and log file in order for it to contain other FILESTREAM filegroups. ...
  21. A database or filegroup cannot be set to read-only mode when any files are subject to a RESTORE PAGE operation. Complete ...
  22. A database should have no more than {0} parent-child dimensions that have the UnaryOperatorColumns, CustomRollupColumns, ...
  23. A database user associated with the secure conversation was dropped before credentials had been exchanged with the far endpoint. ...
  24. A database with ID '{0}' already exists on the '{1}' server. If you proceed with deployment, the database will be overwritten. ...
  25. A database with ID '{0}' on '{1}' has changed since the last time the project was deployed. If you proceed with deployment, ...
  26. A DDL change was made on one or more articles in the publication after the last regular snapshot was run. You need to rerun ...
  27. A deadlock encountered when reading the publication meta data has prevented the Log Reader from loading its cache. The maximum ...
  28. A deadlock was detected while trying to lock variable "%1!s!" for read access. A lock could not be acquired after 16 attempts ...
  29. A deadlock was detected while trying to lock variables "%1!s!" for read access and variables "%2!s!" for read/write access. ...
  30. A deadlock was detected while trying to lock variables "%1!s!" for read/write access. A lock cannot be acquired after 16 ...
  31. A dedicated administrator connection (DAC) allows an administrator to connect to a server when the Database Engine will not ...
  32. A DEFAULT constraint cannot be created on the column '%1!s!' in the table '%2!s!' because the column is a sparse column or ...
  33. A default instance of SQL Server 2000 (64-bit) Analysis Services was detected. To continue, install a named instance of SQL ...
  34. A definition for the '%{strAttrID/}' attribute is missing, although the attribute is specified as a new related attribute ...
  35. A delete-delete conflict was detected and resolved. The row could not be deleted from the peer since the row does not exist. ...
  36. A delete-update conflict between peer %1!s! (incoming) and peer %2!s! (on disk) was detected and could not be resolved automatically. ...
  37. A delete-update conflict between peer %1!s! (incoming) and peer %2!s! (on disk) was detected and resolved. The incoming delete ...
  38. A destination property was specified on a property mapping that is invalid. This occurs when a property is specified on a ...
  39. A dimension exists that does not have exactly one attribute for original ID, effective start date, effective end date, and ...
  40. A distributor failed to give a buffer to thread "%1!s!" because of error 2!8.8X!. The target thread is probably shutting ...
  41. A duplicate attribute key has been found when processing: %1[Table: '%{Table/}', Column: '%{Column/}', Value: '%{Value/}'%]%[; ...
  42. A dynamic snapshot is required because the publication '%1' contains both dynamic filters and logical record relationships. ...
  43. A fact dimension has been defined in a way that the user interface does not support, but the server might. If you are unsure ...
  44. A fact relationship cannot be defined. The dimension and measure group must be based on the same table in the same data source ...
  45. A failure occurred on task "%1!s!": 2!8.8X! while retrieving dependencies. The runtime was retrieving dependencies from the ...
  46. A failure occurred validating columns in the custom DataSet object supplied by the business logic handler. Verify that the ...
  47. A failure occurred validating the row in the custom DataSet object supplied by the business logic handler. Verify that the ...
  48. A failure occurred validating the table defined by the custom DataSet object supplied by the business logic handler. Verify ...
  49. A failure occurred when accessing '%1' due to an operating system error %2!d!='%3' during Web synchronization. Ensure that ...
  50. A failure occurred when the Merge Agent attempted to validate the partitioning function used to generate the partitioned ...
  51. A failure occurred while FILESTREAM configuration was being changed or applied. For more information, see the SQL Server ...
  52. A failure occurred while reading Metadata information from a Table-Valued Parameter Rowset. Either PRECISION or SCALE data ...
  53. A failure occurred while reading Metadata information from a Table-Valued Parameter Rowset. Failure occurred in IRowset::GetNextRows ...
  54. A failure occurred while reading Metadata information from a Table-Valued Parameter Rowset. Failure occurred in the method ...
  55. A failure occurred while reading Metadata information from a Table-Valued Parameter Rowset. One of NUMBER, TYPE, FLAGS or ...
  56. A failure occurred while reading Metadata information from a Table-Valued Parameter Rowset. One of user-defined type catalog/schema/typename ...
  57. A failure occurred while reading Metadata information from a Table-Valued Parameter Rowset. One of xml type catalog/schema/"schema ...
  58. A failure occurred while reading Metadata information from a Table-Valued Parameter Rowset. The number of columns in the ...
  59. A failure occurred while reading Metadata information from a Table-Valued Parameter Rowset. The OLE DB type (%1!u!) for Column ...
  60. A failure occurred while sending row data for a Table-Valued Parameter Rowset. Error occurred in method IRowset::GetData ...
  61. A failure occurred while sending row data for a Table-Valued Parameter Rowset. Error occurred in method IRowset::GetNextRows ...
  62. A failure occurred while sending row data for a Table-Valued Parameter Rowset. Error occurred in method IRowset::ReleaseRows ...
  63. A failure occurred while sending row data for a Table-Valued Parameter Rowset. Error occurred in method IRowset::RestartPosition ...
  64. A failure occurred while sending row data for a Table-Valued Parameter Rowset. No data was provided for Row %1!Iu!, Column ...
  65. A failure occurred while sending row data for a Table-Valued Parameter Rowset. Null value was provided for Row %1!Iu!, Column ...
  66. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The data provided for Row %1!Iu!, Column %2!Iu! ...
  67. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The data provided for Row %1!Iu!, Column %2!Iu! ...
  68. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The failure occurred at Row %1!Iu!, Column ...
  69. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The length (%1!Iu!) for Row %2!Iu!, Column ...
  70. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The length (%1!Iu!) for Row %2!Iu!, Column ...
  71. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The length was not provided by the consumer ...
  72. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The provider failed to convert data for Row ...
  73. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The status (%1!u!) provided for Row %2!Iu!, ...
  74. A failure occurred while the file store was being cleared. Physical file: %{PhysicalFile/}. Logical file: %{LogicalFile/}. ...
  75. A fatal error occurred during a full-text population and caused the population to be cancelled. Population type is: %1!s!; ...