SQL Server 2016

  1. The value specified for the @login parameter is not valid. User '%1!s!' is not a user in database '%2!s!'. Add the user account ...
  2. The value specified for the @pubid parameter of procedure '%1!s!' is not valid or is NULL. Verify that the Merge Agent is ...
  3. The value specified for the @type parameter of sp_addsubscriber or the @subscriber_type parameter of sp_addsubscription is ...
  4. The value specified for the code page parameter of the cast to data type DT_STR or DT_TEXT is not valid. The specified code ...
  5. The value specified for the code page parameter of the NULL function with data type DT_STR or DT_TEXT is not valid. The code ...
  6. The value specified for the length parameter of a cast operation is not valid. The length must be positive. The length specified ...
  7. The value specified for the length parameter of a NULL function is not valid. The length must be positive. The length specified ...
  8. The value specified for the MINIMUM_DEPENDENCY_PROBABILITY parameter of the '%{modelname/}' mining model is not valid. The ...
  9. The value specified for the Mode property "{0}" is not valid. Use the adapter editor to set the Mode property to a valid ...
  10. The value specified for the parameter @pollinginterval cannot exceed 24 hours or be less than 0. Specify a polling interval ...
  11. The value specified for the parameter @pollinginterval must be null or 0 when the stored procedure 'sys.sp_cdc_scan' is not ...
  12. The value specified for the precision parameter of a NULL function is not valid. The precision that was specified is out ...
  13. The value specified for the property filter_type is not valid. Valid values are 1 (join filter only), 2 (logical record relation ...
  14. The value specified for the scale parameter of a cast operation is out of range for the type cast. Scale must not exceed ...
  15. The value specified for the scale parameter of a NULL function is not valid. The scale that was specified is out of range ...
  16. The value specified for the variable "%1!s!" in the OPTIMIZE FOR clause could not be implicitly converted to that variable's ...
  17. The value specified for TYPE option is not supported in this version of SQL Server. Allowed values are E (EXTERNAL_USER) ...
  18. The value supplied for the change_columns argument of CHANGE_TRACKING_IS_COLUMN_IN_MASK function is not valid. The value ...
  19. The value was not set for key '%1!s!' because the total size of keys and values in the session context would exceed the 1 ...
  20. The value {0} for the number of TempDB files exceeds the allowed limit. Setup allows the value up to {1} or the number of ...
  21. The value {0} for the TempDB file growth increment exceeds the allowed limit. Setup allows the value up to {1} MB. You can ...
  22. The value {0} for the TempDB file size exceeds the allowed limit. Setup allows the value up to {1} MB because of the impact ...
  23. The value {0} for the TempDB log file growth increment exceeds the allowed limit. Setup allows the value up to {1} MB. You ...
  24. The value {0} for the TempDB log file size exceeds the allowed limit. Setup allows the value up to {1} MB because of the ...
  25. The value {0} is not valid for ParameterTypeSemantics attribute. Valid values are 'ExactMatchOnly', 'AllowImplicitPromotion' ...
  26. The value {3}' of the {2} property of the {0} {1}' has an invalid schema. URLs in reports may only use http://, https://, ...
  27. The value {3}' of the {2} property of the {0} {1}' is invalid. This value is the name of a group or dataset over which to ...
  28. The value, %1!d!, specified for the code page parameter of the cast to data type "%2!s!", is not valid. The code page is ...
  29. The values for {0} and {1} are not properly defined. {0} must be less or equal to {1}, or {0} must be less or equal to 1. ...
  30. The values in the time series on the x axis do not increase at regular intervals. We have filled in %{insertedDataRatio/} ...
  31. The values of a continuous key column (that is, a column whose content type is set to 'KEY TIME' or 'KEY SEQUENCE') cannot ...
  32. The values shown in CPU Time, Memory Usage, # Reads and # Writes columns are cumulative values of all the active sessions ...
  33. The variable "%1!s!" cannot be found. This error occurs when an attempt to retrieve a variable from a variables collection ...
  34. The variable "%1!s!" cannot be used as an "out" parameter or return value in a parameter binding because it is read-only. ...
  35. The variable "%1!s!" is a 64-bit integer variable, which is not supported on this operating system. The variable has been ...
  36. The variable "%1!s!" is already on the read list. A variable may only be added once to either the read lock list or the write ...
  37. The variable "%1!s!" is already on the write list. A variable may only be added once to either the read lock list or the ...
  38. The variable "%1!s!" specified by VariableName property is not a valid variable. Need a valid variable name to write to. ...
  39. The variable "%1!s!" specified by VariableName property is not an integer. Change the variable to be of type VT_I4, VT_UI4, ...
  40. The variable '%1!s!' cannot be used as a parameter because a CURSOR OUTPUT parameter must not have a cursor allocated to ...
  41. The variable cannot be found. This occurs when an attempt is made to retrieve a variable from the Variables collection on ...
  42. The variable name '%1!s!' has already been declared. Variable names must be unique within a query batch or stored procedure. ...
  43. The variable name '{0}' has already been declared. Variable names must be unique within a query batch or stored procedure. ...
  44. The variable name '{0}' has already been declared.Variable names must be unique within a query batch or stored procedure. ...
  45. The variable name '{0}' has already been declared.Variable names must be unique within a query batch or stored procedure. ...
  46. The variable name is ambiguous because multiple variables with this name exist in different namespaces. Specify namespace-qualified ...
  47. The variable value assignment is not valid. This error happens when the client or a task assigns a runtime object to a variable ...
  48. The Variables collection has not been returned from the VariableDispenser. An operation was attempted that is only allowed ...
  49. The Variables collection was returned the from VariableDispenser and cannot be modified. Items cannot be added to or removed ...
  50. The variation '%{variation/}' for column '%{column/}' specified in the '%{func/}' function was not found in the input table. ...
  51. The version (%1!s!) of the pre-existing match index "%2!s!" is not supported. The version expected is "%3!s!". This error ...
  52. The version number cannot be negative. This error occurs when the VersionMajor, VersionMinor, or VersionBuild property of ...
  53. The version number of the local SQL Server Analysis Services (PowerPivot) instance does not match the version associated ...
  54. The version of MSXMLSQL.DLL that was found is older than the minimum required version. Found version "%1!s!.%2!s!.%3!s!". ...
  55. The version of provider name in configuration is older than the current version. The value in configuration will be used, ...
  56. The version of SQL Server instance {2} does not match the version expected by the SQL Server update. The installed SQL Server ...
  57. The version of SQL Server running at the Subscriber is incompatible with the publication. Either upgrade the Subscriber to ...
  58. The version of SQL Server running on the Subscriber does not support synchronizing with a peer-to-peer publication. All participants ...
  59. The version of SQL Server that was used to develop the project. The versions may include SQL Server 2005 Beta (1), SQL Server ...
  60. The version of SQL Server used to download the Oracle package code does not match the version of SQL Server running at the ...
  61. The version of SQL*PLUS that is accessible through the system Path variable is not current enough to support Oracle publishing. ...
  62. The version of the Analysis Services instance to which a project will be deployed. This provides the default for new projects. ...
  63. The version of the language components used by full-text catalog '%1!s!' in database '%2!s!' is different from the version ...
  64. The version of the linked %{typename/} with the ID of '%{id/}' ID, Name of '%{name/}' on the remote instance has changed. ...
  65. The version of the linked %{typename/}, with the ID of '%{id/}', Name of '%{name/}' on the remote server has changed. Repeat ...
  66. The version of the linked %{typename/}, with the name of '%{name/}', on the remote instance has changed. Repeat the operation ...
  67. The version of the loaded mapping files must be the same as the version of loaded EdmItemCollection and StoreItemCollection. ...
  68. The version of the project has changed since the instance of the execution has been created. Create a new execution instance ...
  69. The version of the report server database is either in a format that is not valid, or it cannot be read. The found version ...
  70. The version of the report server web service definition (WSDL) is either not valid or unrecognized. The server is not a compatible ...
  71. The version of the specified SQL Server instance does not support the selected operation. Specify a different SQL Server ...
  72. The version of the SQL Server in the image you have selected could not be verified. We recommend selecting an image with ...
  73. The version of the SQL Server in the image you have selected is lower than the version of the source SQL Server you have ...
  74. The version of the SSISDB catalog schema ({0}) is higher than the server schema version expected by the SSIS runtime ({1}). ...
  75. The version of the SSISDB catalog schema ({0}) is lower than the server schema version expected by the SSIS runtime ({1}). ...