SQL Server 2012

  1. The project location is not trusted:{0}{0}{1}{0}{0}Running the application may result in security exceptions when it {0}attempts ...
  2. The project reference "{0}" was not added to the project during the migration of "{1}". The missing project reference may ...
  3. The PromoteLookup property of the {0} is true but the IsLookup property of the {1} is not true. Both the entity containing ...
  4. The properties 'PublisherRpcLogin' and 'PublisherRpcPassword' must be set when 'PublisherRpcSecurityMode' is Standard mode ...
  5. The properties on this dialog allow you to change the default behavior of different visualization types and default grouping ...
  6. The property "%1!s!" cannot be set on "%2!s!". The property being set is not supported on the specified object. Check the ...
  7. The property "%1!s!" is write-only. This error occurs when trying to retrieve the value of a property through a property ...
  8. The property "{0}" of connection manager "{1}" is configured to use an environment variable, but no environment has been ...
  9. The property "{0}" of connection manager "{1}" is configured to use an environment variable, but no environment has been ...
  10. The property "{0}" of connection manager "{1}" is configured to use an environment variable, but no environment has been ...
  11. The property %1!s! must either be empty, or a number between %2!u! and %3!u!. The Keys or CountDistinctKeys property has ...
  12. The property %{relatedpropertyname/}, which is related to key property %{property/}, can not have relationship type set to ...
  13. The property '{0}' cannot have multiple output locations associated with it. Specify only a single input setting or datastore ...
  14. The property '{0}' which is attributed to return the '{1}' sequence does not have a get method. Properties with the SequenceDefinitionAttribute ...
  15. The property '{0}' with type '{1}' cannot be created from the XML located in the '{2}' document of the datastore at the '{3}' ...
  16. The property '{0}.{1}' has type {3}, but declared as '{2}' in the mappings. The '{4}' extension doesn't provide a type converter ...
  17. The property '{0}.{1}' has type {3}, but declared as '{2}' in the mappings. The '{4}' extension is required to convert types. ...
  18. The property value containing the '{0}' character (at index {1} in the connection string) must be enclosed in quotation marks. ...
  19. The property will not have effect unless SmartLabels.Disabled is set to true. Do you want to set the SmartLabels.Disabled ...
  20. The property, '%1!s!', cannot be changed because the Integration Services database is not in single-user mode. In Management ...
  21. The protection level of the package does not apply to the cache file. If the cache file contains sensitive information, use ...
  22. The protection level, ServerStorage, cannot be used when saving to this destination. The system could not verify that the ...
  23. The protection level, ServerStorage, cannot be used when saving to this destination. The system could not verify that the ...
  24. The ProtectionLevel property of the project has changed. To build the project, the packages need to have the same protection ...
  25. The provided IFeatureResultStore instance of type {0} did not supply any outcomes, and so no product feature outcomes can ...
  26. The provider '{0}' has declared support for more than one version of domain '{1}'. The request cannot resolve to a single ...
  27. The provider instance of type '{0}' used with this method has not been created in the current runtime context and cannot ...
  28. The provider library does not contain a required feature for the database configuration. Upgrade the provider library or ...
  29. The provider used by the '%{datasource_name/}' data source referenced in the OPENQUERY clause cannot be used by this instance. ...
  30. The provider {0} is attached to a domain and cannot be deleted. Please detach the provider from all domains before deleting. ...
  31. The publication "%1!s!" cannot allow multiple subscriptions per partition if it contains articles using @partition_options ...
  32. The publication '%1!s!' could not be added because non-SQL Server Publishers only support the @sync_method parameter values ...
  33. The publication '%1' contains logical record relationships. Logical records are not supported when using Web synchronization ...
  34. The publication '{0}' contains filtered articles and can not be configured via the Peer-To-Peer Topology wizard. This type ...
  35. The publication cannot use precomputed partitions because there is at least one circular reference in the join filters specified ...
  36. The publication does not support stand-alone Distribution Agents and cannot accept subscriptions created using Active X controls. ...
  37. The publication does not support this type of subscribers. Only publications in character bcp mode support heterogeneous ...
  38. The publication must support Subscriber-requested partitioned snapshot generation because one or more articles use subscription-based ...
  39. The publication property '%1!s!' cannot be modified because the peer-to-peer publication '%2!s!' is not enabled for conflict ...
  40. The publication uses parameterized filtering which has been configured to have only one subscriber per partition. Another ...
  41. The published object {0} ({1}) is dependent on the unpublished object {2} ({3}), creation of the published object at the ...
  42. The published stream adapters are not available. This is an indication that the server metadata is corrupted. If the metadata ...
  43. The publisher '%1!s!' uses distribution database '%2!s!' and not '%3!s!' which is required in order to host the publishing ...
  44. The publisher '%1!s!' with distributor '%2!s!' is not known as a publisher at distributor '%3!s!'. Run sp_adddistpublisher ...
  45. The Publisher and Subscribers can update the published data independently after the Subscribers receive an initial snapshot ...
  46. The Publisher cannot be assigned a new range of identity values, because the values for the identity column's data type have ...
  47. The Publisher failed to allocate a new set of identity ranges for the subscription. This can occur when a Publisher or a ...
  48. The publisher login must be a member of the 'db_owner' role at the publisher database when generating a regular snapshot. ...
  49. The publisher login of the snapshot agent must be granted permission to create databases in order to generate a replication ...
  50. The Publisher must use this password when it automatically connects to the Distributor to perform replication administrative ...
  51. The publisher name of the contacted Oracle instance does not match the configured name for the publisher at this distributor. ...
  52. The Publisher or Distributor is not configured properly for replication, or you do not have permission to retrieve information ...
  53. The Publisher to which you connected, '{0}', is a database mirroring partner of the original Publisher, '{1}'. The subscription ...
  54. The Publisher was dropped at the Distributor, but information on the Publisher '%1!s!' was not dropped. Connect to the Oracle ...
  55. The pull subscription to publication '%1' has not been configured correctly. Create an entry for this subscription at the ...
  56. The qualifier cannot be an empty string. If line break suppression is required, the qualifier cannot contain the newline ...
  57. The qualifier has not been set on this instance of the connection manager. Setting the qualifier is required to complete ...
  58. The query '{0}' (query template '{1}') is not started and the diagnostic settings of its operators and streams cannot be ...
  59. The query '{0}' (query template '{1}') is not started and the diagnostic settings of its operators and streams cannot be ...
  60. The query '{0}' (query template '{1}') is not started and the diagnostic settings of its operators and streams cannot be ...
  61. The query '{0}' (query template '{1}') is not started and the diagnostic views of its operators and streams cannot be retrieved. ...
  62. The query against the '%{Name/}' model cannot be performed because this edition of Analysis Services does not support predictions ...
  63. The query application must be specified explicitly because none of query inputs are bound to queries. Use an overload that ...
  64. The query application must be specified explicitly because the query inputs are bound to published streams in different applications. ...
  65. The query at the redirected publisher '%1!s!' to determine the health of the availability group associated with publisher ...
  66. The query at the redirected publisher '%1!s!' to determine whether the publisher database '%2!s!' belonged to an availability ...
  67. The query at the redirected publisher '%1!s!' to determine whether the SQL Server instance is a replication publisher failed ...
  68. The query at the redirected publisher '%1!s!' to determine whether there were sysserver entries for the subscribers of the ...
  69. The query cannot be executed because some files are either missing or not registered. Run setup again to make sure the required ...
  70. The query contains a grouping based on the expression "{0}" which returns a large value type. Expressions which return large ...
  71. The query contains secure information '{0}' or '{1}'. It may create security threat to the product. Do you want to continue? ...
  72. The query could not be generated because the same column (TableId='%{table/}', ColumnId='%{column/}') is being ordered more ...
  73. The query definition projects one or more expressions with duplicate aliases. Ensure that all projected expressions specify ...
  74. The query designer could not be loaded. Verify your connection string and query string or enter a valid query to continue. ...
  75. The query for this visualization failed due to an error. Click the Refresh button in the ribbon to retry the query or Undo ...