SQL Server 2016

  1. The specified name prefix will generate partition names that already exist. Do you want to overwrite these partitions: {0}? ...
  2. The specified named connection is either not found in the configuration, not intended to be used with the EntityClient provider, ...
  3. The specified network name for this SQL Server failover cluster instance is too long. Network names are limited to {0} characters. ...
  4. The specified number of maximum parallel tasks is not valid. The value of the parameter must be an integer that is greater ...
  5. The specified operation cannot be performed because the metadata element '{0}' is a leaf but must be a metadata element ref. ...
  6. The specified operation cannot be performed because the metadata element '{0}' is a ref but must be a leaf metadata element. ...
  7. The specified operation cannot be performed because the metadata element '{0}' is frozen and cannot have any further definition ...
  8. The specified operation cannot be performed because the metadata element '{0}' is not frozen and cannot be involved in this ...
  9. The specified operation cannot run under the current compatibility level. A common reason for this issue is that object contains ...
  10. The specified package path does not contain a package name. This occurs when the path does not contain at least one backslash ...
  11. The specified parameter '{0}' of type '{1}' is not valid. Only scalar parameters (such as Int32, Decimal, and Guid) are supported. ...
  12. The specified parameter name '{0}' is not valid. Parameter names must begin with a letter and can only contain letters, numbers, ...
  13. The specified parameter type '{0}' is not valid. Only scalar parameters (such as Int32, Decimal, and Guid) are supported. ...
  14. The specified parameter type '{0}' is not valid. Only scalar types, such as System.Int32, System.Decimal, System.DateTime, ...
  15. The specified patch could not be applied because a cumulative update at patch level {0} is already installed. To continue ...
  16. The specified patch could not be applied because general distribution release (GDR) {0} with KB {1} is already installed. ...
  17. The specified pattern did not return any files or does not represent a valid file share. Verify the pattern parameter and ...
  18. The specified port range {0} has only {1} available ports. To continue, provide a range with at least {2} available ports. ...
  19. The specified port range {0} is not valid. To continue, provide valid port numbers and at least {1} ports, for example {2}. ...
  20. The specified pre-existing match index "%1!s!" was not originally built with fuzzy match information for column "%2!s!". ...
  21. The specified precision value {0} for datetime/datetime2/smalldatetime parameter is not one of the permissible values (16, ...
  22. The specified publication does not allow subscriptions to be initialized from a backup. To allow initialization from a backup, ...
  23. The specified Publisher is not enabled as a remote Publisher at this Distributor. Ensure the value specified for the parameter ...
  24. The specified query name '{0}' is not valid. Query names must begin with a letter and can only contain letters, numbers, ...
  25. The specified range for NumaNode is not valid. The value for startIndex {0} must be less than the value for endIndex {1}. ...
  26. The specified range of Schedulers is not valid. The value for startIndex {0} must be less than the value for endIndex {1}. ...
  27. The specified related entity is not compatible with this new instance constructor. The constructed instance is not an instance ...
  28. The specified remote server name may not be the network name of the remote server or the remote server is unreachable due ...
  29. The specified remote server name might not correspond to the network name of the remote server or the remote server was unreachable ...
  30. The specified replica has one or more databases that are not synchronized. Failing over to this replica may result in the ...
  31. The specified report folder is not valid. Specify a value for the TargetReportFolder property in the deployment settings. ...
  32. The specified sa password does not meet strong password requirements. For more information about strong password requirements, ...
  33. The specified scale value {0} corresponding to specified precision value {1} is incorrect. The correct value corresponding ...
  34. The specified scaleout setting for Polybase is not the same as that specified for the active node in this SQL Server Failover ...
  35. The specified schema name '%1!s!' for classifier user-defined function either does not exist, or the user does not have permission ...
  36. The specified secondary replica is not currently synchronized, therefore performing failover of this availability group might ...
  37. The specified server '{0}' already exists but does not use the OLE DB Provider for SQL Server Integration Services as the ...
  38. The specified service account is not supported. Depending on the operating systems Virtual Accounts and Managed Service Accounts ...
  39. The specified service account {0} for {1} contains an invalid character ('). To continue, please specify an alternate service ...
  40. The specified sets in the %{func/} function have incompatible hierarchies at position %{iHier/}. The sets are incompatible. ...
  41. The specified source object must be a user-defined aggregate object if it is published as an 'aggregate schema only' type ...
  42. The specified source object must be a user-defined function object if it is going to be published as a 'func schema only' ...
  43. The specified statistic does not exist in the current data source or did not apply to the specified table or it does not ...
  44. The specified Subscriber cannot use transformable subscriptions using Data Transformation Services. Only SQL Server 2000, ...
  45. The specified subscription type is invalid. Verify that the -SubscriptionType parameter for the Merge Agent has been correctly ...
  46. The specified target entity reference expression is not valid because it does not produce a reference to an entity of the ...
  47. The specified target relationship End is not declared by the same relationship type as the specified source relationship ...
  48. The specified type member '{0}' is not supported in LINQ to Entities. Only initializers, entity members, and entity navigation ...
  49. The specified update was successfully applied, but Setup detected that some features in instance {1} are not at the Service ...
  50. The specified upgrade path for this SQL Server edition is supported, but the edition you want to upgrade to has more limited ...
  51. The specified URL points to a Block Blob. Backup and Restore operations on Block Blobs are not supported when WITH CREDENTIAL ...
  52. The specified use of parameter '{0}' to produce a value of type '{1}' is not supported by LINQ to Entities in a compiled ...
  53. The specified user account '{0}' for SQL Server Agent is a managed service account that is not supported for a SQL Server ...
  54. The specified user account '{0}' for SQL Server Agent is a virtual account that is not supported on this computer. To continue, ...
  55. The specified value '{0}' is invalid. To run in unattended mode, you must specify a valid ACTION. The valid values for ACTION ...
  56. The Specified value EnableUIOnServerCore for setting 'UIMODE' is invalid. The expected values are: Normal and AutoAdvance. ...
  57. The specified value for setting '{0}' is invalid. The count of provided items {1} doesn't match the count of items {2} of ...
  58. The specified value for the enable_level parameter of the sp_filestream_configure stored procedure is not valid. The value ...
  59. The specified value of '{0}' for UpdateSource is invalid. The valid values are 'MU', a valid folder path, a relative path ...
  60. The specified value {0} for ACTION is invalid. To run in unattended mode, you must specify a valid ACTION. The valid values ...
  61. The specified values for initial_file_name and audit_record_offset do not represent a valid location within the audit file ...
  62. The specified WebMethodInfo is not correct. The ParamValue supplied does not match the ParamType. The DTSParamValue is not ...
  63. The specified Windows Server Failover Clustering (WSFC) cluster, '%1!s!', is not ready to become the cluster context of Always ...
  64. The specified workload (file or table) has no tunable events. Events must be one of the following types - SQL:BatchStarting, ...
  65. The specified workload (file or table) has no tunable events. Events must be one of the following types - SQL:BatchStarting, ...
  66. The sp_configure value 'contained database authentication' must be set to 1 in order to %1!s! a contained database. You may ...
  67. The SQL Agent service domain group could not be recovered. To complete repair, SQL Agent Service domain group must be provided. ...
  68. The SQL Distribution ActiveX control should not be initialized (using the Initialize method) before calling this method. ...
  69. The SQL Distribution control could not write to the registry. Ensure that the user has sufficient permissions to access the ...
  70. The SQL Merge ActiveX Control does not support pull or anonymous subscriptions to the specified subscriber datasource type ...
  71. The SQL object name '%1!s!' specified for property '%2!s!' contains more than the maximum number of prefixes. The maximum ...
  72. The SQL Server '%1!s!' could not obtain Windows group membership information for login '%2!s!'. Verify that the Windows account ...
  73. The SQL Server 2008 features that have been selected to be upgraded to SQL Server 2016 are not at the required service pack. ...
  74. The SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2016 are not at the required service ...
  75. The SQL Server 2012 Data Mining Add-ins for Office cannot connect to an instance of SQL Server Analysis Services version ...