SQL Server 2016

  1. The backup of the file or filegroup "%1!s!" is not permitted because it is not online. Container state: "%2!s!" (%3!s!). ...
  2. The backup of the system database on the device %1!s! cannot be restored because it was created by a different version of ...
  3. The backup on the secondary database "%1!s!" was terminated, but a terminate backup message could not be sent to the primary ...
  4. The backup operation has detected an unexpected file in a FILESTREAM container. The backup operation will continue and include ...
  5. The backup operation on database '{0}' was skipped because it is part of an availability group and not its preferred backup ...
  6. The backup set cannot be restored because the database was damaged when the backup occurred. Salvage attempts may exploit ...
  7. The backup set on device '%1!s!' was terminated while it was being created and is incomplete. RESTORE sequence is terminated ...
  8. The backup store file '%{pathname/}'is empty or doesn't contain proper header; database can not be succesfully restored. ...
  9. The backup store stream is empty or doesn't contain proper header; database can not be succesfully restored. Operation cancelled. ...
  10. The backup type of all the archive segments is not the same. Copy the correct backup files to the backup location, and retry ...
  11. The Backup, Restore or Synchronize command cannot be executed within a user initiated transaction or in transactional batch. ...
  12. The BackupDirectory registry key is not configured correctly. This key should specify the root path where disk backup files ...
  13. The BaseEntity of the {0} is the {1}. Based on the SelectedPath, the specified DrillthroughContext can be used only if the ...
  14. The batch '{0}' cannot be found. This error occurs when the batch was not previously opened by the CreateBatch method. It ...
  15. The begin and end action at postition %I64u are not of the same type. Specify matching actions that are the same type and ...
  16. The begin and end columns at position %I64u are not of the same type. Specify matching columns that are the same type and ...
  17. The BI semantic model in the '%{database/}' database is inconsistent. A database must contain a cube when the database contains ...
  18. The binary code for the script is not found. Please open the script in the designer by clicking Edit Script button and make ...
  19. The binary field is too large. The adapter attempted to read a binary field that was %1!d! bytes long, but expected a field ...
  20. The binary operation "%1!s!" failed with error code 2!8.8X!. An internal error occurred, or an out-of-memory condition exists. ...
  21. The binary representaion of the data that was read from the file. This data is used for troubleshooting by Microsoft support. ...
  22. The binding is missing for the {0}. Role must have exactly one Relation binding, unless the containing Entity is bound to ...
  23. The binding of the measure group '%{measuregroupid/}' references a server measure group '%{remotemgid/}' that does not exist. ...
  24. The binding or the grouping for layer '{2}' in the {0} '{1}' is not valid. A spatial element cannot have more than one matching ...
  25. The bindings for this relationship are not valid. To correct this issue, you can either delete and re-create the relationship, ...
  26. The blob store returned a stream that corresponds to a new blob, which has its initial position set to a value other than ...
  27. The blob store returned a stream that corresponds to an existing blob, which has its its initial position set to a value ...
  28. The Boolean property value that specifies whether the linked server supports remote procedure calls (RPCs) with output parameters. ...
  29. The boolean that indicates whether the client application allows the user to group on this attribute. This value should be ...
  30. The boolean that indicates whether the client application should display the target entity as a look-up when the containing ...
  31. The boolean that indicates whether the client application should treat the entity as a lookup table or as a full-fledged ...
  32. The boolean that indicates whether the client application shows the role to the user and whether the fields of the related ...
  33. The BottomCount function returns the last n-item rows of the table expression, ordered in ascending order by the rank expression. ...
  34. The BottomPercent function returns the smallest number of rows in increasing order such that the sum of the rank expression ...
  35. The BottomSum function returns the smallest number of rows in increasing order such that the sum of the rank expression values ...
  36. The BottomSum function returns the smallest number of rows in increasing order such that the sum of the rank expression values ...
  37. The boundary value '{0}' was not recognized as a valid {1} value. Enter the value in a supported string literal datetime ...
  38. The Broker Configuration conversation on dialog handle '%1!s!' closed due to an error. To troubleshoot this problem, investigate ...
  39. The browser has encountered an error while querying the current hierarchy and has been disabled. Click Reconnect to reload ...
  40. The browser is disabled because custom MDX expressions defined in the Advanced tab were not validated due to the following ...
  41. The Bucket Count of a NONCLUSTERED HASH index is the number of buckets in the hash table. It is recommended to set the fill ...
  42. The bucket for event index {0} could not be located, which prevents a FeatureError from being returned for the {1} feature. ...
  43. The buffer manager attempted to push an error row to an output that was not registered as an error output. There was a call ...
  44. The buffer manager cannot create a file to spool a long object on the directories named in the BLOBTempStoragePath property. ...
  45. The buffer manager cannot create a temporary storage file on any path in the BufferTempStoragePath property. There is an ...
  46. The buffer manager could not create a temporary file on the path "%1!s!". The path will not be considered for temporary storage ...
  47. The buffer manager detected that the system was low on virtual memory, but was unable to swap out any buffers. %1!d! buffers ...
  48. The buffer manager failed a memory allocation call for %3!d! bytes, but was unable to swap out any buffers to relieve memory ...
  49. The buffer manager has allocated %1!d! bytes, even though the memory pressure has been detected and repeated attempts to ...
  50. The buffer manager ran out of memory while trying to extend the table of buffer types. This is caused by an out-of-memory ...
  51. The bulk copy (bcp) client has sent a row length of %1!s!. This is not a valid size. The maximum row size is %2!s!. Use a ...
  52. The bulk copy (bcp) client sent a row length of %1!s!. This size is not valid. The minimum row size is %2!s!. Use a supported ...
  53. The bulk data source provider string has a syntax error near character position %1!s!. Expected '%2!s!', but found '%3!s!'. ...
  54. The Bulk Insert operation of SQL Server Destination has timed out. Please consider increasing the value of Timeout property ...
  55. The bulk load failed. The column is too long in the data file for row %1!s!, column %2!s!. Verify that the field terminator ...
  56. The bulk load failed. Unexpected NULL value in data file row %1!s!, column %2!s!. The destination column (%3!s!) is defined ...
  57. The bulk-copying of data from '{0}' has been chosen as a deadlock victim, the operation will be retried in {1} milliseconds. ...
  58. The business rule cannot be saved. The entity is the target of a sync relationship, and a target entity cannot contain business ...
  59. The byte order mark (BOM) value for the file "%1!s!" is 2!4.4X!, but the expected value is 3!4.4X!. The ExpectBOM property ...
  60. The byte order mark (BOM) value for the file is not valid. The ExpectBOM property was set for this file, but the BOM value ...
  61. The cabinet file '[2]' required for this installation is corrupt and cannot be used. This could indicate a network error, ...
  62. The cache directory is not set, and the collector could not get an accessible temporary directory. Assign a cache directory ...
  63. The cache file is damaged, or the file was not created by using the Cache connection manager. Provide a valid cache file. ...
  64. The cache index position, %1!d!, is not valid. For non-index columns, the index position should be 0. For index columns, ...
  65. The cache refresh plan '{0}' cannot be found. The cache refresh plan identifier that is provided to an operation cannot be ...
  66. The cache refresh plan cannot be created or edited because caching is not enabled for the item '{0}'. Do you want to enable ...
  67. The cache window setting is invalid. Specify a positive integer to indicate the number of temporary collection files to keep. ...
  68. The cached MSI file '{0}' is missing. Its original file is '{1}' and it was installed for product '{2}' from '{3}', version ...
  69. The cached patch file "{0}" is missing. The original file for this cached file is "{1}", which can be installed from "{2}", ...
  70. The CALCULATE command controls the aggregation of leaf cells in the cube. If deleted or modified, the data within the cube ...
  71. The CALCULATE command controls the aggregation of leaf cells in the cube. If the CALCULATE command is deleted or modified, ...
  72. The calculated column '%{table/}'['%{column/}' cannot be defined as Binary because this data type is not supported for calculated ...
  73. The call format VCALL cannot be used for the specified article. VCALL format can be used only for articles in publications ...
  74. The call to sp_MScdc_capture_job by the Capture Job for database '%1!s!' failed. Look at previous errors for the cause of ...
  75. The cancel operation is in progress. It may take a few minutes for the controller and all clients to reach a ready state. ...