SQL Server 2016

  1. Invalid data encountered. A required relationship is missing. Examine StateEntries to determine the source of the constraint ...
  2. Invalid data type for column "%1!s!". The data type cannot be text, ntext, image, binary, varchar(max), nvarchar(max), varbinary(max), ...
  3. Invalid definition for element '%1!s!'. SQL Server does not currently permit additions to existing substitution groups via ...
  4. Invalid definition for element or attribute '%1!s!'. Value constraints on components of type QName are not supported in this ...
  5. Invalid definition for type '%1!s!'. An 'all' group may not appear as the child or parent of any other model group, it must ...
  6. Invalid definition for type '%1!s!'. Cannot specify use="prohibited" for attribute '%2!s!' because there is no corresponding ...
  7. Invalid definition for type '%1!s!'. SQL Server does not permit the built-in XML Schema types 'ID' and 'IDREF' or types derived ...
  8. Invalid device name. The length of the device name provided exceeds supported limit (maximum length is:%1!s!). Reissue the ...
  9. Invalid distribution command, state %1!d!: transaction 2 command %3!d!{offset : %4!d! token offset: %5!d! state: %6!d!) }. ...
  10. Invalid IDTSComponentMetaData90 or property name provided when requesting persistence of component's design time property. ...
  11. Invalid image URL format. #SEQ formatter must be followed by (300,3), where 300 is a max sequence number and 3 is an image ...
  12. Invalid item type for list type '%1!s!'. The item type of a list may not itself be a list, and types derived from ID may ...
  13. Invalid locale ID was specified. Please verify that the locale ID is correct and corresponding language resource has been ...
  14. Invalid log on credentials specified for data source connection '{0}'. Windows authentication mode is not a valid for the ...
  15. Invalid message received on the ExternalMailQueue. conversation_handle: %1!s!. message_type_name: %2!s!. message body: %3!s!. ...
  16. Invalid number of coordinates for the circle map area shape. Three coordinates must be provided: the center of the circle ...
  17. Invalid number of coordinates for the polygon map area shape. "x1,y1,x2,y2.xn,yn" Each x,y pair contains the coordinates ...
  18. Invalid number of coordinates for the polygon map area shape. "x1,y1,x2,y2.xn,yn" Each x,y pair contains the coordinates ...
  19. Invalid number of coordinates for the rectangle map area shape. Four coordinates must be provided: x,y coordinates of the ...
  20. Invalid number of coordinates specified for the circle map area shape. Three coordinates must be provided: center of the ...
  21. Invalid number of coordinates specified for the polygon map area shape. 'x1,y1,x2,y2.xn,yn' Each x,y pair should contain ...
  22. Invalid number of coordinates specified for the rectangle map area shape. Four coordinates must be provided: x,y coordinates ...
  23. Invalid number of database copies: '%1!s!'. Only one database copy is currently allowed to be created along with the database ...
  24. Invalid object id %1!s! provided as input for procedure '%2!s!'. The object id must refer to a memory-optimized table with ...
  25. Invalid ObjectExpansion '%{objectExpansion/}' specified for DISCOVER_XML_METADATA. Allowed values are: ExpandFull, ExpandObject, ...
  26. Invalid option "%1" for SqlLocalDB operation "%2". Use the "-?" command-line option to see the available operations and options. ...
  27. Invalid OrderByAttributeID '%{orderby/}' set in dimension '%{IMBITableId/}' attribute '%{IMBIColumnId/}' pointing to a Row ...
  28. Invalid OrderByAttributeID '%{orderby/}' set in table '%{IWTableName/}' attribute '%{IWColumnName/}' pointing to a Row Number ...
  29. Invalid parameter %1!s! ('%2!s!'): Data type 3!s! is a deprecated large object, or LOB, but is marked as output parameter. ...
  30. Invalid parameter detected while initializing TCP listening port. Error: %1!s!, state: %2!s!. Contact Technical Support. ...
  31. Invalid parameter specified. XML Schema Collections can only be created from a string literal, or from a variable typed as ...
  32. Invalid pipeline request statement. A pipeline processing request can only appear directly under an Execute/Command statement. ...
  33. Invalid range boundary value '{0}'. All range boundary values must be hexadecimal literals (prefixed with '0x'), if the partition ...
  34. Invalid redefinition of attribute '%1!s!' in type '%2!s!'. Must be of a type which is a valid restriction of the corresponding ...
  35. Invalid redefinition of attribute '%1!s!' in type '%2!s!'. Must be prohibited in the derived type if it is prohibited in ...
  36. Invalid redefinition of attribute '%1!s!' in type '%2!s!'. Must be required in the derived type if it is required in the ...
  37. Invalid restriction for type '%1!s!'. If the base type has empty content, then the derived type must as well, and if the ...
  38. Invalid restriction for type '%1!s!'. The attribute wildcard in the restricted type must be a valid subset of the corresponding ...
  39. Invalid restriction for type '%1!s!'. The effective total range of the model group in the restricted type must be a valid ...
  40. Invalid restriction for type '%1!s!'. The element in the restricted type may not be nillable if the corresponding element ...
  41. Invalid restriction for type '%1!s!'. The element in the restricted type may not have a 'block' value more permissive than ...
  42. Invalid restriction for type '%1!s!'. The element in the restricted type must be fixed to the same value as the corresponding ...
  43. Invalid restriction for type '%1!s!'. The element in the restricted type must be in one of the namespaces allowed by the ...
  44. Invalid restriction for type '%1!s!'. The element in the restricted type must have the same name as and a more restrictive ...
  45. Invalid restriction for type '%1!s!'. The particle in the restricted type may not have an occurrence range more permissive ...
  46. Invalid restriction for type '%1!s!'. The Wildcard in the restricted type must be a valid subset of the corresponding wildcard ...
  47. Invalid root element found in the mapping file. Make sure that the root element's local name is 'Mapping' and the namespaceURI ...
  48. Invalid ROWS value or REPEATABLE seed "%1!s!" in the TABLESAMPLE clause for table "%2!s!". The value or seed must be greater ...
  49. Invalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table "%1!s!". The value or seed must be an integer. ...
  50. Invalid schema option specified for publication that allows updating subscribers. Need to set the schema option to include ...
  51. Invalid server name "%1!s!". SSIS service does not support multi-instance, use just server name instead of "server name\instance". ...
  52. Invalid SQLUserInstance.dll found at the location specified in the registry. Verify that the Local DB feature of SQL Server ...
  53. Invalid string or buffer length. The length in bytes for SQL_WCHAR, SQL_WVARCHAR or SQL_WLONGVARCHAR data type should be ...
  54. Invalid subscription type is specified. A subscription to publication '%1!s!' already exists in the database with a different ...
  55. Invalid Time Series node unique ID encountered in the mining model, '%{modelname/}'. Make sure node unique IDs are consistent ...
  56. Invalid transactional state while saving embedded PowerPivot data for dimension '%{dimname/}'. Server State='%{serversta ...
  57. Invalid type '%1!s!' for WAITFOR. Supported data types are CHAR/VARCHAR, NCHAR/NVARCHAR, and DATETIME. WAITFOR DELAY supports ...
  58. Invalid type definition for type '%1!s!', 'minExclusive' must be less than or equal to 'maxExclusive' and less than 'maxInclusive' ...
  59. Invalid type definition for type '%1!s!', 'minInclusive' must be less than or equal to 'maxInclusive' and less than 'maxExclusive' ...
  60. Invalid type definition for type '%1!s!', the derivation was illegal because 'final' attribute was specified on the base ...
  61. Invalid type definition for type '%1!s!', types with complex content can only be derived from base types which have complex ...
  62. Invalid type definition for type '%1!s!', types with simple content can only be derived from base types which have simple ...
  63. Invalid type definition for type '%1!s!'. A type may not have both 'minInclusive' and 'minExclusive' or 'maxInclusive' and ...
  64. Invalid type definition for type '%1!s!'. The base and derived types must have the same value for 'mixed' unless deriving ...
  65. Invalid type definition: Type or content model '%1!s!' is too complicated. It may be necessary to reduce the number of enumerations ...
  66. Invalid type for element '%1!s!'. SQL Server does not permit the built-in XML Schema types 'ID' and 'IDREF' or types derived ...
  67. Invalid use of query hints. Using same query hint more than once is not allowed. Remove duplicate query hints and rerun the ...
  68. Invalid use of schema or catalog for OLE DB provider "%1!s!" for linked server "%2!s!". A four-part name was supplied, but ...
  69. Invalid use of the "$(TARGETPROCESS)" instance name. This instance may only be used with counters from the Process object. ...
  70. Invalid value "%1!s!" specified for the parameter @identityrangemangementoption. Valid values are "auto", "manual", or "none". ...
  71. Invalid value '%1!s!' specified while executing sp_changemergearticle on article '%2!s!' for the 'identityrangemanagementoption' ...
  72. Invalid value (%1!s!) of the @cache_window parameter. Allowable values are: -1 (cache all upload data from previous upload ...
  73. Invalid value for property @subscriber_upload_options. Valid values are 0 (allow uploads), 1 (disable uploads), 2 (disable ...
  74. Invalid value specified for %1!s!. Valid values are 'day', 'days', 'dd', 'year', 'years', 'yy', 'yyyy', 'month', 'months', ...
  75. Invalid value. The minimum score for auto correction must be equal or greater than the minimum score for auto suggestion. ...