SQL Server 2016

  1. A corrupted message has been received. The destination certificate issuer name size is %1!s!, however it must be no greater ...
  2. A corrupted message has been received. The destination certificate serial number is missing. This occurred in the message ...
  3. A corrupted message has been received. The destination certificate serial number size is %1!s!, however it must be no greater ...
  4. A corrupted message has been received. The encrypted offset of the envelope does not match the payload encrypted offset. ...
  5. A corrupted message has been received. The encrypted session key size is %1!s!, however it must be %2!s! bytes. This occurred ...
  6. A corrupted message has been received. The encryption flag is set, however the message body, MIC or salt is missing. This ...
  7. A corrupted message has been received. The End of Conversation and Error flags are both set. This occurred in the message ...
  8. A corrupted message has been received. The End of Conversation and Error flags may not be set in the first sequenced message. ...
  9. A corrupted message has been received. The End of Conversation flag has been set on an unsequenced message. This occurred ...
  10. A corrupted message has been received. The envelope payload is bigger than the message. This occurred in the message with ...
  11. A corrupted message has been received. The highest seen message number must be greater than the acknowledged message number. ...
  12. A corrupted message has been received. The key exchange key ID is invalid. This occurred in the message with Conversation ...
  13. A corrupted message has been received. The key exchange key size is %1!s!, however it must be between %2!s! and %3!s! bytes. ...
  14. A corrupted message has been received. The maximum number of private variable data elements (%1!s!) has been exceeded. Private ...
  15. A corrupted message has been received. The maximum number of public variable data elements (%1!s!) has been exceeded. Public ...
  16. A corrupted message has been received. The message body is not properly padded for encryption. This occurred in the message ...
  17. A corrupted message has been received. The message type is missing for this message. This occurred in the message with Conversation ...
  18. A corrupted message has been received. The message type must not be set in this message. This occurred in the message with ...
  19. A corrupted message has been received. The MIC and session key ID are in an invalid state. This occurred in the message with ...
  20. A corrupted message has been received. The MIC is present, however the message body or encryption flag is missing. This occurred ...
  21. 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 ...
  22. A corrupted message has been received. The salt size is %1!s!, however it must be %2!s! bytes. This occurred in the message ...
  23. A corrupted message has been received. The security certificate key fields must both be present or both be absent. This occurred ...
  24. A corrupted message has been received. The security dialog message header is invalid. This occurred in the message with Conversation ...
  25. A corrupted message has been received. The service pair security header destination certificate, the key exchange key, the ...
  26. A corrupted message has been received. The service pair security header size is %1!s!, however it must be between %2!s! and ...
  27. A corrupted message has been received. The service pair security header source certificate and the signature must both be ...
  28. A corrupted message has been received. The session key ID is missing. This occurred in the message with Conversation ID '%1!s!', ...
  29. A corrupted message has been received. The session key ID size is %1!s!, however it must be %2!s! bytes. This occurred in ...
  30. A corrupted message has been received. The unsigned dialog message header is invalid. This occurred in the message with Conversation ...
  31. A CPU with the id of {0} does not exist on this system. Use sys.dm_os_schedulers to locate valid CPUs for this system or ...
  32. A credential conflicting with '%1!s!' already exists in credential cache in memory. Use alter step to change the secret. ...
  33. A cryptographic operation failed. This error indicates a serious problem with SQL Server. Check the SQL Server error log ...
  34. A cursor plan could not be generated for the given statement because the textptr() function was used on a LOB column from ...
  35. A custom data source is defined specifically for this data-driven subscription and cannot be used by other data-driven subscriptions. ...
  36. A custom element was found that has no registered XML parser, which means the XML is invalid. The element namespace is {0} ...
  37. A custom property in the {0} {1}' has the name "{2}". Custom property names cannot be null and must be unique within the ...
  38. A custom property named "%1!s!" is invalid because there is a stock property with that name. A custom property cannot have ...
  39. A custom role cannot contain both system-level and non-system-level tasks in the same role definition. You must specify different ...
  40. A data source does not provide features such as caching metadata, adding relationships, adding calculations, and adding annotations. ...
  41. A data source view must be created before performing this action. This can be accomplished with the Schema Generation Wizard. ...
  42. A data type that stores values of various SQL Server-supported data types, except text, ntext, timestamp, and sql_variant. ...
  43. A data type was found in an event source that is not readable by this verion of the QueryableXEventData provider. This exception ...
  44. A database cannot be enabled for both Database Mirroring and FILESTREAM or for both Database Mirroring and MEMORY_OPTIMIZED_DATA ...
  45. A database credential with the name '%1!s!' was not found. A database credential must be created before stretching a database ...
  46. A database must have primary FILESTREAM log filegroup and log file in order for it to contain other FILESTREAM filegroups. ...
  47. A database named '{0}' was found on the specified instance of SQL Server. To continue, delete or rename this database before ...
  48. A database or filegroup cannot be set to read-only mode when any files are subject to a RESTORE PAGE operation. Complete ...
  49. A database should have no more than {0} parent-child dimensions that have the UnaryOperatorColumns, CustomRollupColumns, ...
  50. A database user associated with the secure conversation was dropped before credentials had been exchanged with the far endpoint. ...
  51. A database with ID '{0}' already exists on the '{1}' server. If you proceed with deployment, the database will be overwritten. ...
  52. A database with ID '{0}' on '{1}' has changed since the last time the project was deployed. If you proceed with deployment, ...
  53. A DDL change was made on one or more articles in the publication after the last regular snapshot was run. You need to rerun ...
  54. A deadlock encountered when reading the publication meta data has prevented the Log Reader from loading its cache. The maximum ...
  55. A deadlock was detected while trying to lock variable "%1!s!" for read access. A lock could not be acquired after 16 attempts ...
  56. A deadlock was detected while trying to lock variables "%1!s!" for read access and variables "%2!s!" for read/write access. ...
  57. A deadlock was detected while trying to lock variables "%1!s!" for read/write access. A lock cannot be acquired after 16 ...
  58. A dedicated administrator connection (DAC) allows an administrator to connect to a server when the Database Engine will not ...
  59. A DEFAULT constraint cannot be created on the column '%1!s!' in the table '%2!s!' because the column is a sparse column or ...
  60. A DEFAULT constraint cannot be created on the column '{0}' in the table '{1}' because the column is a sparse column or sparse ...
  61. A definition for the '%{strAttrID/}' attribute is missing, although the attribute is specified as a new related attribute ...
  62. A delete-delete conflict was detected and resolved. The row could not be deleted from the peer since the row does not exist. ...
  63. A delete-update conflict between peer %1!s! (incoming) and peer %2!s! (on disk) was detected and could not be resolved automatically. ...
  64. A delete-update conflict between peer %1!s! (incoming) and peer %2!s! (on disk) was detected and resolved. The incoming delete ...
  65. A description of the lock resource. The description of the lock resource depends on the type of lock. This is the same value ...
  66. A destination property was specified on a property mapping that is invalid. This occurs when a property is specified on a ...
  67. A dimension exists that does not have exactly one attribute for original ID, effective start date, effective end date, and ...
  68. A disconnect event was raised when server is waiting for Federated Authentication token. This could be due to client close ...
  69. A DISCOVER operation is only supported for a tabular model database for which you have administrative permissions. Either ...
  70. A distributor failed to give a buffer to thread "%1!s!" because of error 2!8.8X!. The target thread is probably shutting ...
  71. A duplicate attribute key has been found when processing: %1[Table: '%{Table/}', Column: '%{Column/}', Value: '%{Value/}'%]%[; ...
  72. A duplicate availability replica '%1!s!' was specified in the READ_ONLY_ROUTING_LIST for availability replica '%2!s!'. Inspect ...
  73. A durable memory-optimized table requires a primary key. Choose the columns you wish to include in the primary key of the ...
  74. A durable memory-optimized table requires at least one primary key. Choose the columns you wish to include in the primary ...
  75. A dynamic snapshot is required because the publication '%1' contains both dynamic filters and logical record relationships. ...