SQL Server 2012

  1. Invalid parameter detected while initializing TCP listening port. Error: %1!s!, state: %2!s!. Contact Technical Support. ...
  2. Invalid parameter specified. XML Schema Collections can only be created from a string literal, or from a variable typed as ...
  3. Invalid pipeline request statement. A pipeline processing request can only appear directly under an Execute/Command statement. ...
  4. Invalid redefinition of attribute '%1!s!' in type '%2!s!'. Must be of a type which is a valid restriction of the corresponding ...
  5. Invalid redefinition of attribute '%1!s!' in type '%2!s!'. Must be prohibited in the derived type if it is prohibited in ...
  6. Invalid redefinition of attribute '%1!s!' in type '%2!s!'. Must be required in the derived type if it is required in the ...
  7. Invalid restriction for type '%1!s!'. If the base type has empty content, then the derived type must as well, and if the ...
  8. Invalid restriction for type '%1!s!'. The attribute wildcard in the restricted type must be a valid subset of the corresponding ...
  9. Invalid restriction for type '%1!s!'. The effective total range of the model group in the restricted type must be a valid ...
  10. Invalid restriction for type '%1!s!'. The element in the restricted type may not be nillable if the corresponding element ...
  11. Invalid restriction for type '%1!s!'. The element in the restricted type may not have a 'block' value more permissive than ...
  12. Invalid restriction for type '%1!s!'. The element in the restricted type must be fixed to the same value as the corresponding ...
  13. Invalid restriction for type '%1!s!'. The element in the restricted type must be in one of the namespaces allowed by the ...
  14. Invalid restriction for type '%1!s!'. The element in the restricted type must have the same name as and a more restrictive ...
  15. Invalid restriction for type '%1!s!'. The particle in the restricted type may not have an occurrence range more permissive ...
  16. Invalid restriction for type '%1!s!'. The Wildcard in the restricted type must be a valid subset of the corresponding wildcard ...
  17. Invalid ROWS value or REPEATABLE seed "%1!s!" in the TABLESAMPLE clause for table "%2!s!". The value or seed must be greater ...
  18. Invalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table "%1!s!". The value or seed must be an integer. ...
  19. Invalid schema option specified for publication that allows updating subscribers. Need to set the schema option to include ...
  20. Invalid server name "%1!s!". SSIS service does not support multi-instance, use just server name instead of "server name\instance". ...
  21. Invalid SQLUserInstance.dll found at the location specified in the registry. Verify that the Local DB feature of SQL Server ...
  22. Invalid StartTime EndTime combination for Insert on Enqueue. The event's StartTime of '{0:o}' should be less than the event's ...
  23. Invalid StartTime NewEndTime combination for Retraction on Enqueue. The event's StartTime of '{0:o}' should be less than ...
  24. Invalid string or buffer length. The length in bytes for SQL_WCHAR, SQL_WVARCHAR or SQL_WLONGVARCHAR data type should be ...
  25. Invalid subscription type is specified. A subscription to publication '%1!s!' already exists in the database with a different ...
  26. Invalid Time Series node unique ID encountered in the mining model, %{modelname/}. Make sure node unique IDs are consistent ...
  27. Invalid transactional state while saving embedded PowerPivot data for dimension '%{dimname/}'. Server State='%{serversta ...
  28. Invalid type '%1!s!' for WAITFOR. Supported data types are CHAR/VARCHAR, NCHAR/NVARCHAR, and DATETIME. WAITFOR DELAY supports ...
  29. Invalid type definition for type '%1!s!', 'minExclusive' must be less than or equal to 'maxExclusive' and less than 'maxInclusive' ...
  30. Invalid type definition for type '%1!s!', 'minInclusive' must be less than or equal to 'maxInclusive' and less than 'maxExclusive' ...
  31. Invalid type definition for type '%1!s!', the derivation was illegal because 'final' attribute was specified on the base ...
  32. Invalid type definition for type '%1!s!', types with complex content can only be derived from base types which have complex ...
  33. Invalid type definition for type '%1!s!', types with simple content can only be derived from base types which have simple ...
  34. Invalid type definition for type '%1!s!'. A type may not have both 'minInclusive' and 'minExclusive' or 'maxInclusive' and ...
  35. Invalid type definition for type '%1!s!'. The base and derived types must have the same value for 'mixed' unless deriving ...
  36. Invalid type definition: Type or content model '%1!s!' is too complicated. It may be necessary to reduce the number of enumerations ...
  37. Invalid type for element '%1!s!'. SQL Server does not permit the built-in XML Schema types 'ID' and 'IDREF' or types derived ...
  38. Invalid use of schema or catalog for OLE DB provider "%1!s!" for linked server "%2!s!". A four-part name was supplied, but ...
  39. Invalid use of the "$(TARGETPROCESS)" instance name. This instance may only be used with counters from the Process object. ...
  40. Invalid value "%1!s!" specified for the parameter @identityrangemangementoption. Valid values are "auto", "manual", or "none". ...
  41. Invalid value '%1!s!' specified while executing sp_changemergearticle on article '%2!s!' for the 'identityrangemanagementoption' ...
  42. Invalid value (%1!s!) of the @cache_window parameter. Allowable values are: -1 (cache all upload data from previous upload ...
  43. Invalid value for property @subscriber_upload_options. Valid values are 0 (allow uploads), 1 (disable uploads), 2 (disable ...
  44. Invalid value specified for %1!s!. Valid values are 'day', 'days', 'dd', 'year', 'years', 'yy', 'yyyy', 'month', 'months', ...
  45. Invalid value. The minimum score for auto correction must be equal or greater than the minimum score for auto suggestion. ...
  46. Invalid values for properties Instance.{0} and Instance.{1}. If you set Instance.{0} then you must provide a valid Instance.{1}. ...
  47. Invalid XML message format received on the ExternalMailQueue. conversation_handle: %1!s!. message_type_name: %2!s!. message ...
  48. IO Completion Listener ( 1!s!) Worker 2!s! appears to be non-yielding on Node %3!s!. Approx CPU Used: kernel %4!s! ms, user ...
  49. Is an aggregate function that causes an additional column to be output with a value of 1 when the row is added by either ...
  50. is an invalid WMI namespace. Namespaces in WMI cannot start with an underscore (_) nor can they contain hash (#) nor dollar ...
  51. is encrypted with a password and the password is unknown. Try to decrypt the package by opening the package in the designer ...
  52. is not a network path. This path will be accessed by copy jobs running on the secondary server instances. It must be a network ...
  53. is not a recognized table hints option. If it is intended as a parameter to a table-valued function, ensure that your database ...
  54. is not a valid container name. Container names must start with a letter or number, and can contain only lower case letters, ...
  55. is not a valid explicit published stream name. An example of a valid name is 'cep:/Server/Application/app1/PublishedStream/ps1'. ...
  56. is not a valid monitor server instance because it is not the correct version. Monitor server instances must be servers running ...
  57. is not a valid published stream name. Published stream names must be either a query name or an explicitly published stream ...
  58. is not a valid secondary server instance because it is not the correct version. Secondary server instances must be servers ...
  59. is not a valid witness server instance, which must be the Enterprise, Developer, Standard, Workgroup, or Express edition ...
  60. is not enabled as a Publisher at the Distributor, '{0}'. Contact the administrator of the Distributor to enable this server ...
  61. is not valid for one of the following reasons: - The format of the path is not supported. - The path refers to a file instead ...
  62. is using project connection managers. To make it compatible with the package deployment model, remove the project connection ...
  63. ISANCESTOR=1= Member1 , Member2 =Returns TRUE if a specified member is an ancestor of another specified member, FALSE otherwise. ...
  64. ISGENERATION=1= Member , Numeric Expression =Returns TRUE if a specified member is in a specified generation, FALSE otherwise. ...
  65. IsNull(ExecuteWql('Numeric', 'root\CIMV2', 'select category from Win32_NTLogEvent where EventCode=6008 and Logfile="System"'), ...
  66. ISSIBLING=1= Member1 , Member2 =Returns TRUE if a specified member is a sibling of another specified member, FALSE otherwise. ...
  67. IS[Server package path Optional. Ignored when running dtexec from the command line. Use this option when scheduling a job ...
  68. It is invalid to remove the default Publisher '%1!s!', publication database '%2!s!', and publication '%3!s!' from the list ...
  69. It is not possible to drop column '%1!s!' to article '%2!s!' because the snapshot for publication '%3!s!' has already been ...
  70. It is only possible to connect to SQL Server Desktop Engine databases and Microsoft Access databases with this version of ...
  71. It is strongly recommended that all replicated IDENTITY columns use the NOT FOR REPLICATION option. When automatic identity ...
  72. It looks like you don't have any items selected for cutting. Please check the checkbox next to an item on the tree to select ...
  73. Item security is inherited from a parent item. Do you want to apply security settings for this item that are different from ...
  74. Items refresh of the DataGrid failed. One of the probable causes is that the SortDescriptions added are not valid, in which ...
  75. Iterating through substitution properties for adding access control entries in order to configure the SQL Server Browser ...