SQL Server 2016

  1. An invalid value was specified for parameter @subscription_type. Valid values are 'push', 'pull', 'both', 'anonymous' or ...
  2. An item already exists in "{0}" and it is not a mobile report. Pick another location to save the report, rename the report, ...
  3. An item referring to the file '{1}' was found in the project file '{0}'. Since this file is located within a system directory, ...
  4. An item requires at least one role assignment. This error occurs when an attempt is made to delete all security for the current ...
  5. An MDX expression identifying a member in the dimension. This is used as an optimization, and indicates that when slicing ...
  6. An MDX statement was expected. An MDX expression or a (possibly empty) collection of custom rollup properties was specified ...
  7. An object identifier is required for model permission operations. The Identifier must have an existing GUID for create, update ...
  8. An object named "{0}" cannot be found. Check the selected object types for accuracy and ensure that you typed the object ...
  9. An object of type '{0}' cannot be added, attached, or removed from an EntityCollection that contains objects of type '{1}'. ...
  10. An object of type '{1}' was assigned to variable '{0}'. Only objects of type ForEachEnumerator can be assigned to variables. ...
  11. An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, ...
  12. An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, ...
  13. An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, ...
  14. An object that has a key that matches the key of the supplied object could not be found in the ObjectStateManager. Verify ...
  15. An object was created but the attempt to add it to a collection failed. This can occur due to an out-of-memory condition. ...
  16. An object with a key that matches the key of the supplied object could not be found in the ObjectStateManager. Verify that ...
  17. An object with the '%{objectname/}' name already exists on the instance. (The AllowOverwrite flag only applies to the '%{objectid/}' ...
  18. An object with the name {0} in extension with Id {1} could not be created as the extension has not been registered with the ...
  19. An object with the name {0} of type {1} in extension with Id {2} could not be created as the type does not have a public ...
  20. An object with the name {0} of type {1} in extension with Id {2} could not be created as the type is abstract and cannot ...
  21. An object with the name {0} of type {1} in extension with Id {2} could not be created due to an exception raised during instantiation. ...
  22. An object with the same '%{objectId/}' ID but different '%{objectname/}' Name already exists on the instance. (The AllowOverwrite ...
  23. An object with the same key already exists in the ObjectStateManager. The existing object is in the {0} state. An object ...
  24. An object with the same key already exists in the ObjectStateManager. The ObjectStateManager cannot track multiple objects ...
  25. An online operation cannot be performed for %1!s! '%2!s!' because the index contains column '%3!s!' of data type text, ntext, ...
  26. An online operation cannot be performed for '%1!s!' because the index contains column of large object type, and in the same ...
  27. An online operation cannot be performed for index '{0}' because the index contains columns of data type text, ntext, image, ...
  28. An operation to read/write to the Query Store failed. Check the error logs to correct the source of the read/write failure ...
  29. An operation to read/write to the Query Store failed. Partition or delete data, drop indexes, or consult the documentation ...
  30. An out of memory condition has occurred in the Service Broker message transmitter (operation %1!s!). Message transmission ...
  31. An out of memory condition has occurred in the Service Broker transport layer. A service broker connection is closed due ...
  32. An out-of-line binding was specified in the request, but its target is not a valid object. The specified ID must be a valid ...
  33. An output column must have exactly one CopyColumn or PassThruColumn property specified. This error occurs when neither the ...
  34. An overflow occurred while converting from data type "%1!s!" to data type "%2!s!". The source type is too large for the destination ...
  35. An overflow was encountered while converting a predicted value to the '%{ColumnName/}' column, at line %d{Line/}, column ...
  36. An SSL binding already exists for the specified IP address and port combination. The existing binding uses a different certificate ...
  37. An uncommittable transaction was detected at the beginning of the batch. The transaction was rolled back. This was caused ...
  38. An unexpected error occurred while checking the sector size for file '%1!s!'. Move the file to a local NTFS volume, where ...
  39. An unexpected error occurred while connecting to the report server. Verify that the Reporting Services Service Application ...
  40. An unexpected error occurred while executing a Backup/Restore command. Refer to the SQL Server error log for information ...
  41. An unexpected error occurred. Click Continue to ignore this error and attempt to continue. Click Quit to shut down the application ...
  42. An unexpected error was detected. The schema of the store declared that a column can never contain null values, but a null ...
  43. An unexpected error with HRESULT 1!s! occurred while processing backup files. Refer to the SQL Server error log for information ...
  44. An unexpected file id was encountered. File id %1!s! was expected but %2!s! was read from "%3!s!". Verify that files are ...
  45. An unexpected inconsistency was detected while loading the data model. The column '%{colname/}' in table '%{table/}' could ...
  46. An unexpected locking issue was detected. The database '%{strObjectName/}' was not properly locked in Write mode during the ...
  47. An unexpected null value was encountered for the following measure during processing: '%{Measure/}' of Measure Group: '%{Detail/}' ...
  48. An unexpected NULL value was returned for column "%1!s!.%2!s!" from OLE DB provider "%3!s!" for linked server "%4!s!". This ...
  49. An unexpected Text Information Begin (TIB) log record was encountered while processing the TIB for offset %1!s!. Last TIB ...
  50. An unexpected XML construct was found in the character data of the "%1!s!" element (in the "%2!s!" namespace) of the SOAP ...
  51. An unexpected XML node "%1!s!" (in the namespace "%2!s!") was found in the "%3!s!" element (in the "%4!s!" namespace) of ...
  52. An unhandled exception occured; we intercepted it, but have to terminate the process according to config setting Log\Exception\ExceptionHandlingMode ...
  53. An unknown error occurred while creating an encrypted connection or retrieving the credentials. Verify that the certificate ...
  54. An unknown error occurred with the Reporting Services endpoint on this SharePoint site. Contact the SharePoint site administrator ...
  55. An unknown internal error (%1!s!) occurred while looking up the public key certificate associated with this SQL Server instance. ...
  56. An unsupported data type is used with a unary operator. The operand type is not supported for the operation. To perform this ...
  57. An unsupported data type was used with a binary operator. The type of one, or both, of the operands is not supported for ...
  58. An unsupported schema option combination was specified. Non-SQL Server publications only support the following schema options: ...
  59. An update-delete conflict was detected and unresolved. The row could not be updated since the row does not exist. The incoming ...
  60. An update-update conflict between peer %1!s! (incoming) and peer %2!s! (on disk) was detected and resolved. The incoming ...
  61. An update-update conflict between peer %1!s! (incoming) and peer %2!s! (on disk) was detected and resolved. The incoming ...
  62. An upgrade operation failed for database '%1!s!' attempting to upgrade the XTP component from version %2!s!.%3!s! to version ...
  63. An upgrade script batch failed to execute for database '%1!s!' due to compilation error. Check the previous error message ...
  64. An upper limit (in milliseconds) that sets the threshold for completing a long running request. Relatively few requests should ...
  65. An upper limit (in milliseconds) that sets the threshold for completing a query in an expected amount of time. For reporting ...
  66. An upper limit (in milliseconds) that sets the threshold for completing a trivial request, such as server-to-server communications ...
  67. An upper limit (in milliseconds) that sets the threshold for completing requests quickly. For reporting purposes, a quick ...
  68. An XML document that provides information about the specific activity being performed on the notification subscription. The ...
  69. An XML document that provides information about the specific background activity for query notifications. The document conforms ...
  70. An XML document that provides information about the specific operation being performed on the parameter table. The document ...
  71. An XPress9 Header was detected on Data Stream, and this scenario is not supported. XPress9 compressed files are only written/read ...
  72. An XTP checkpoint operation encountered an error ('%1!s!') while processing log record ID %2!s! for database '%3!s!'. Checkpoint ...
  73. An {0} element can only be declared for a FunctionImport declaring an EntitySet. FunctionImport '{1}' does not declare an ...
  74. Analysis Services can load assemblies that contain user-defined functions. These functions can be based on the common language ...
  75. Analysis Services cluster repair could not be completed. Please run the CompleteFailoverInstance action, then run cluster ...