SQL Server 2016

  1. The package was digitally signed, but the signature is not valid. The contents of the package could have been modified by ...
  2. The package will still be able to load normally but the previous layout information will be lost and the designer will automatically ...
  3. The packages shown below contain Execute Package tasks. It's recommended that you let the wizard change each of these Execute ...
  4. The page %1!s!, object ID %2!s!, index ID %3!s!, partition ID %4!s!, allocation unit ID %5!s! (type %6!s!) has been modified, ...
  5. The PageName property specified on the data region, rectangle, or group {0}' was removed from the report. SQL Server 2008 ...
  6. The PageName property was detected in the data region, rectangle, or group {0}' SQL Server 2008 Reporting Services does not ...
  7. The parameter "%1!s!" cannot be found. This error occurs when an attempt to retrieve a parameter from a parameters collection ...
  8. The parameter "%1!s!" does not have the same encryption information as the one it was created with. Use sp_refresh_parameter_encryption ...
  9. The parameter "%1!s!" is not the same type as the type it was created with. Drop and recreate the module using a two-part ...
  10. The parameter "{0}" is configured to use an environment variable, but no environment has been selected. Check the "Environment" ...
  11. The parameter "{0}" is configured to use an environment variable, but no environment has been selected. Check the "Environment" ...
  12. The parameter "{0}" is configured to use an environment variable, but no environment has been selected. Select the "Environment" ...
  13. The parameter "{0}" references variable "{2}", which is not provided by project defaults. Choose a running environment that ...
  14. The parameter %1!s! cannot be provided for users that cannot authenticate in a database. Remove the WITHOUT LOGIN or PASSWORD ...
  15. The parameter %1!s! is not supported for non-SQL Server publications. The value specified for this parameter must be %2!s!. ...
  16. The parameter '%1!s!' has been declared as NOT NULL. NOT NULL parameters are only supported with natively compiled modules, ...
  17. The parameter '%1!s!' was deduced to be a table-valued parameter, which cannot be sent by client driver versions earlier ...
  18. The parameter '%1' cannot be specified because at least one publication already exists in this publication database that ...
  19. The parameter '{0}' does not allow multiple values. Change the parameter settings to allow multiple values or enclose the ...
  20. The parameter '{0}' is not an input-only parameter. The EntityClient provider only allows input-only parameters when the ...
  21. The parameter @state cannot be NULL, and should be 1 or 0. Specify 1 to start SQL Server Managed Backup to Windows Azure, ...
  22. The parameter @supports_net_changes is set to 1, but the source table does not have a primary key defined and no alternate ...
  23. The parameter must be 'description', 'taskid', 'sync_method', 'status', 'repl_freq', 'restricted', 'retention', 'immediate_sync', ...
  24. The parameter name 'r_rowsPerRead' is specified multiple times in 'sp_execute_external_script' call. The name 'r_rowsPerRead' ...
  25. The parameter name '{0}' is not valid. A valid parameter name must begin with a letter and contain only letters, numbers, ...
  26. The parameter SITE can not be prefixed by a scheme such as 'http://'. Valid values for SITE include {'*' | '+' | 'site_name'}. ...
  27. The parameter value could not be assigned because the data types did not match. The provided value was of type "%1!s!", the ...
  28. The parameter value could not be assigned because the data types did not match. The provided value was of type '{0}'. The ...
  29. The parameter value for notification email is not specified or is NULL. Please specify a valid email to enable notifications ...
  30. The parameter {1}' has no default. A default is required for all non-nullable parameters without a prompt or the valid values ...
  31. The parameter, '{0}', is not valid because it is not unique in the command. Combine parameters with the same name into one ...
  32. The parameterized FORCESEEK hint cannot be simultaneously used with INDEX hints or a non-parameterized FORCESEEK hint on ...
  33. The parameters @article and @join_articlename cannot have the same value. Specify different articles for the two parameters; ...
  34. The parameters for security, batch size, and scheduling have been deprecated and should no longer be used. For more information, ...
  35. The parameters given on the command line are not valid. The required command line parameters are: -PS -PD -PN -PT - publication ...
  36. The parameters given on the command line are not valid. The required command line parameters are: -S -E - if present, use ...
  37. The parameters given on the command line are not valid. The required command line parameters are: -S -E - if present, use ...
  38. The parameters given on the command line are not valid. Valid command line parameters are: -S - server on which to run the ...
  39. The parameters given on the command line are not valid. Valid command line parameters are: -S - server on which to run the ...
  40. The parameters given on the command line are not valid. Valid command line parameters are: -S - server on which to run the ...
  41. The parameters given on the command line are not valid. Valid command line parameters are: -S - server on which to run the ...
  42. The parameters given on the command line are not valid. Valid command line parameters are: -S - server on which to run the ...
  43. The parameters of Function '{0}' are converted to conceptual side type '{1}', and the function with the same conceptual side ...
  44. The Parameters property of the IDbCommand interface does not support the IList interface. External error: %1[%{exception/}%]%[;%{exceptioninner/}%]. ...
  45. The ParamValue cannot be inserted at this position. The index specified might be lesser than zero or greater than the length. ...
  46. The parent Action element for the DatastoreProperties element must provide a valid action. The parent action does not have ...
  47. The parent Action element for the {0} element must provide a valid action. The parent action does not have an Action instance, ...
  48. The parent MsiPackage element for the {0} element did not return any packages. Valid package data must be available to create ...
  49. The parent Rule element for the {0} element must provide a valid facet. The parent rule does not have a facet instance, which ...
  50. The parent type '{0}' for the DatastoreDocumentCondition element is invalid. The only valid parent is a Condition element. ...
  51. The parent type '{0}' for the DatastoreIntegration instance is not correct. The only supported types are SequenceTypeAction ...
  52. The parent type '{0}' for the FeatureUpgradeIncompleteCondition element is invalid. The only valid parent is a Condition ...
  53. The parent type '{0}' for the ProductFeatureScenarioCondition element is invalid. The only valid parent is a Condition element. ...
  54. The parent type '{0}' for the SequenceTypeActionDatastorePropertyRestrictions instance is missing a valid ActionDatastoreIntegration ...
  55. The parent type '{0}' for the SequenceTypeActionDatastorePropertyRestrictions instance is missing the name of the property ...
  56. The parent type '{0}' for the SequenceTypeActionDatastorePropertyRestrictions instance is not correct. It must extend from ...
  57. The parent type '{0}' for the StringInputSettingExistsCondition element is invalid. The only valid parent is a Condition ...
  58. The partition database was not found during pending schema scope cleanup, deleting partition metadata only (%1!s!, %2!s!). ...
  59. The partition key column '%1!s!' of table '%2!s!.%3!s!' is nullable or does not match the partition key type defined in the ...
  60. The partition merge operation cannot be executed since it is attempting to modify the contents of the read only database ...
  61. The partition scheme of table '%1!s!' cannot be changed because there exists one or more incremental statistics on the table. ...
  62. The partition with ID '%{partitionID/}' and name '%{partitionName/}' is a regular partition and cannot be altered to be a ...
  63. The partitioned snapshot available for this Subscriber is outdated. To initialize this Subscriber, you must generate a new ...
  64. The partitioned snapshot could not be generated because the agent failed to obtain a required application lock. If the snapshot ...
  65. The partitioned snapshot process cannot complete. Cannot retrieve the maximum timestamp information from the MSsnapshot_history ...
  66. The partitioned snapshot token for this subscription is invalid and validation of the partitioned snapshot will be skipped. ...
  67. The partitioned view "%1!s!" is not updatable because one or more of the non-partitioning columns of its member tables have ...
  68. The partitions for '{0}' are not included in the project. To include the partitions, exclude the cube item from the project, ...
  69. The partitions for the cube "{0}" are not included in the project. To correct the problem, exclude the cube from the project. ...
  70. The partner server instance name must be distinct from the server instance that manages the database. The ALTER DATABASE ...
  71. The pass phrase supplied does not meet the minimum complexity requirements. Please select another pass phrase that meets ...
  72. The passthrough columns, "%1!s!" and "%2!s!", do not have equal data types. Only columns with equal data types are supported ...
  73. The password entered on the Administrative Password Page is invalid. Contact the Distributor administrator or try again with ...
  74. The password for SA account could not be force regenerated and/or SA account cannot be disabled as requested by the -K startup ...
  75. The password of login '%1!s!' is invalid. A new password should be set for this login without specifying the old password. ...