SQL Server 2012

  1. The value specified for the scale parameter of a NULL function is not valid. The scale that was specified is out of range ...
  2. The value specified for the variable "%1!s!" in the OPTIMIZE FOR clause could not be implicitly converted to that variable's ...
  3. The value supplied for the change_columns argument of CHANGE_TRACKING_IS_COLUMN_IN_MASK function is not valid. The value ...
  4. The value {3}' of the {2} property of the {0} {1}' has an invalid schema. URLs in reports may only use http://, https://, ...
  5. 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 ...
  6. 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 ...
  7. 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. ...
  8. The values of a continuous key column (that is, a column whose content type is set to 'KEY TIME' or 'KEY SEQUENCE') cannot ...
  9. The values shown in CPU Time, Memory Usage, # Reads and # Writes columns are cumulative values of all the active sessions ...
  10. The variable "%1!s!" cannot be found. This error occurs when an attempt to retrieve a variable from a variables collection ...
  11. The variable "%1!s!" cannot be used as an "out" parameter or return value in a parameter binding because it is read-only. ...
  12. The variable "%1!s!" is a 64-bit integer variable, which is not supported on this operating system. The variable has been ...
  13. 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 ...
  14. 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 ...
  15. The variable "%1!s!" specified by VariableName property is not a valid variable. Need a valid variable name to write to. ...
  16. The variable "%1!s!" specified by VariableName property is not an integer. Change the variable to be of type VT_I4, VT_UI4, ...
  17. The variable '%1!s!' cannot be used as a parameter because a CURSOR OUTPUT parameter must not have a cursor allocated to ...
  18. The variable cannot be found. This occurs when an attempt is made to retrieve a variable from the Variables collection on ...
  19. The variable name '%1!s!' has already been declared. Variable names must be unique within a query batch or stored procedure. ...
  20. The variable name '{0}' has already been declared.Variable names must be unique within a query batch or stored procedure. ...
  21. The variable name is ambiguous because multiple variables with this name exist in different namespaces. Specify namespace-qualified ...
  22. The variable value assignment is not valid. This error happens when the client or a task assigns a runtime object to a variable ...
  23. The Variables collection has not been returned from the VariableDispenser. An operation was attempted that is only allowed ...
  24. The Variables collection was returned the from VariableDispenser and cannot be modified. Items cannot be added to or removed ...
  25. The version (%1!s!) of the pre-existing match index "%2!s!" is not supported. The version expected is "%3!s!". This error ...
  26. The version number cannot be negative. This error occurs when the VersionMajor, VersionMinor, or VersionBuild property of ...
  27. The version number of the local SQL Server Analysis Services (PowerPivot) instance does not match the version associated ...
  28. The version of MSXMLSQL.DLL that was found is older than the minimum required version. Found version "%1!s!.%2!s!.%3!s!". ...
  29. The version of provider name in configuration is older than the current version. The value in configuration will be used, ...
  30. The version of SQL Server instance {2} does not match the version expected by the SQL Server update. The installed SQL Server ...
  31. The version of SQL Server running at the Subscriber is incompatible with the publication. Either upgrade the Subscriber to ...
  32. The version of SQL Server running on the Subscriber does not support synchronizing with a peer-to-peer publication. All participants ...
  33. The version of SQL Server that was used to develop the project. The versions may include SQL Server 2005 Beta (1), SQL Server ...
  34. The version of SQL Server used to download the Oracle package code does not match the version of SQL Server running at the ...
  35. The version of SQL*PLUS that is accessible through the system Path variable is not current enough to support Oracle publishing. ...
  36. The version of the Analysis Services instance to which a project will be deployed. This provides the default for new projects. ...
  37. The version of the language components used by full-text catalog '%1!s!' in database '%2!s!' is different from the version ...
  38. The version of the linked %{typename/} with the ID of '%{id/}' ID, Name of '%{name/}' on the remote instance has changed. ...
  39. The version of the linked %{typename/}, with the ID of '%{id/}', Name of '%{name/}' on the remote server has changed. Repeat ...
  40. The version of the linked %{typename/}, with the name of '%{name/}', on the remote instance has changed. Repeat the operation ...
  41. The version of the project has changed since the instance of the execution has been created. Create a new execution instance ...
  42. The version of the report server database is either in a format that is not valid, or it cannot be read. The found version ...
  43. The version of the report server web service definition (WSDL) is either not valid or unrecognized. The server is not a compatible ...
  44. The version of the specified SQL Server instance does not support the selected operation. Specify a different SQL Server ...
  45. The version of the SSISDB catalog schema ({0}) is higher than the server schema version expected by the SSIS runtime ({1}). ...
  46. The version of the SSISDB catalog schema ({0}) is lower than the server schema version expected by the SSIS runtime ({1}). ...
  47. The version of the XML index that you are trying to use is not supported anymore. Please drop and recreate the XML index. ...
  48. The version of {0} is not compatible with this version of the DataFlow. The version or pipeline version or both for the specified ...
  49. The version or edition of SharePoint on this computer does not meet the software requirements of PowerPivot for SharePoint. ...
  50. The version or patch level for the SQL Server Analysis Services feature is not the same on all nodes. The version or patch ...
  51. The version or patch level for the SQL Server Database Services feature is not the same on all nodes. The version or patch ...
  52. The version range has a minimum version from product '{0}' and a maximum version from product '{1}'. Both versions must belong ...
  53. The versioned extension '{0}' cannot be placed on metadata element '{1}' which does not support versioning, or does support ...
  54. The versioned trait '{0}' cannot be placed on metadata element '{1}' which does not support versioning, or it does support ...
  55. The view that the report viewer control '{0}' requested could not be found. Check that the DataMember property on the report ...
  56. The virtual directory specified is not valid. Make sure the specified name is not too long and doesn't contain illegal characters. ...
  57. The virtual directory specified is not valid. Make sure the specified name is not too long and doesn't contain illegal characters. ...
  58. The virtual log file sequence 1!s! at offset 2!s! bytes in file '%3!s!' is active and cannot be overwritten with sequence ...
  59. The virtual network name '%1!s!' has been used to identify the redirected publisher for original publisher '%2!s!' and database ...
  60. The visual designer supports auto-generated queries only. Switching to the visual designer will discard the query. Do you ...
  61. The volume mounted on "%1!s!" does not have the expected backup set identity. The volume may be obsolete due to a more recent ...
  62. The volume on device "%1!s!" is sequence number %2!s! of media family %3!s!, but sequence number %4!s! of media family %5!s! ...
  63. The volume on device '%1!s!' is a continuation volume for the backup set. Remove it and insert the volume holding the start ...
  64. The volume on the device "%1!s!" is not part of the media set that is currently being processed. Ensure that the backup devices ...
  65. The VSTA debugger is already in use. Cannot start another instance of the debugger. Remove any breakpoint(s) that are no ...
  66. The web application cannot be configured because the selected site does not have a binding of HTTP or HTTPS. Use Internet ...
  67. The Web server is using an insecure transport method (HTTP). The XML for Analysis provider is configured to require a secure ...
  68. The WebMethodInfo specified is not correct. The ParamValue supplied does not match the ParamType. The DTSParamValue found ...
  69. The WebMethodInfo specified is not correct. The ParamValue supplied does not match the ParamType. The DTSParamValue found ...
  70. The WebMethodInfo specified is not correct. The ParamValue supplied does not match the ParamType. The DTSParamValue found ...
  71. The WebMethodInfo you have specified is incorrect. The ParamValue supplied does not match the ParamType. DTSParamValue found ...
  72. The WebMethodInfo you have specified is incorrect. The ParamValue supplied does not match the ParamType. DTSParamValue found ...
  73. The WebMethodInfo you have specified is incorrect. The ParamValue supplied does not match the ParamType. DTSParamValue found ...
  74. The WebMethodInfo you have specified is incorrect. The ParamValue supplied does not match the ParamType. DTSParamValue found ...
  75. The WebMethodInfo you have specified is incorrect. The ParamValue supplied does not match the ParamType. DTSParamValue is ...