SQL Server 2012

  1. The specified job '%1!s!' is not created for maintenance plans. Verify that the job has at least one step calling xp_sqlmaint. ...
  2. The specified listener with DNS name, '%1!s!', does not exist for the Availability Group '%2!s!'. Use an existing listener, ...
  3. The specified locale ID is not valid. Verify that the locale ID is correct and that a corresponding language resource has ...
  4. The specified login is not a member of the db_owner fixed database role for the publication database and is not a member ...
  5. The specified LSN {%1!s!:%2!s!:%3!s!} for repldone log scan occurs before the current start of replication in the log {%4!s!:%5!s!:%6!s!}. ...
  6. The specified Master Data Services database will be upgraded with the following upgrades. Verify that this information is ...
  7. The specified maximum size limit for the audit log file is less than the minimum value allowed. The maximum size limit must ...
  8. The specified maximum size limit is greater than the maximum value allowed. The maximum size limit must be less than 16777215 ...
  9. The specified maximum size limit is greater than the maximum value allowed. The maximum size limit must be less than 16777215 ...
  10. The specified MSX does not exist, or is a 6.5 (or earlier) version of SQLServer, or is version 7.0 but it's SQLServerAgent ...
  11. The specified name prefix will generate partition names that already exist. Do you want to overwrite these partitions: {0}? ...
  12. The specified network name for this SQL Server failover cluster instance is too long. Network names are limited to {0} characters. ...
  13. The specified number of maximum parallel tasks is not valid. The value of the parameter must be an integer that is greater ...
  14. The specified operation cannot be performed because the metadata element '{0}' is a leaf but must be a metadata element ref. ...
  15. The specified operation cannot be performed because the metadata element '{0}' is a ref but must be a leaf metadata element. ...
  16. The specified operation cannot be performed because the metadata element '{0}' is frozen and cannot have any further definition ...
  17. The specified operation cannot be performed because the metadata element '{0}' is not frozen and cannot be involved in this ...
  18. The specified operation cannot run under the current compatibility level. A common reason for this issue is that object contains ...
  19. The specified package path does not contain a package name. This occurs when the path does not contain at least one backslash ...
  20. The specified patch could not be applied because a cumulative update at patch level {0} is already installed. To continue ...
  21. The specified patch could not be applied because general distribution release (GDR) {0} with KB {1} is already installed. ...
  22. The specified pattern did not return any files or does not represent a valid file share. Verify the pattern parameter and ...
  23. The specified pre-existing match index "%1!s!" was not originally built with fuzzy match information for column "%2!s!". ...
  24. The specified publication does not allow subscriptions to be initialized from a backup. To allow initialization from a backup, ...
  25. The specified Publisher is not enabled as a remote Publisher at this Distributor. Ensure the value specified for the parameter ...
  26. The specified range for NumaNode is not valid. The value for startIndex {0} must be less than the value for endIndex {1}. ...
  27. The specified remote server name may not be the network name of the remote server or the remote server is unreachable due ...
  28. The specified remote server name might not correspond to the network name of the remote server or the remote server was unreachable ...
  29. The specified replica has one or more databases that are not synchronized. Failing over to this replica may result in the ...
  30. The specified report folder is not valid. Specify a value for the TargetReportFolder property in the deployment settings. ...
  31. The specified sa password does not meet strong password requirements. For more information about strong password requirements, ...
  32. The specified schema name '%1!s!' for classifier user-defined function either does not exist, or the user does not have permission ...
  33. The specified secondary replica is not currently synchronized, therefore performing failover of this availability group might ...
  34. The specified service account is not supported. Depending on the operating systems Virtual Accounts and Managed Service Accounts ...
  35. The specified sets in the %{func/} function have incompatible hierarchies at position %{iHier/}. The sets are incompatible. ...
  36. The specified source object must be a user-defined aggregate object if it is published as an 'aggregate schema only' type ...
  37. The specified source object must be a user-defined function object if it is going to be published as a 'func schema only' ...
  38. The specified statistic does not exist in the current data source or did not apply to the specified table or it does not ...
  39. The specified Subscriber cannot use transformable subscriptions using Data Transformation Services. Only SQL Server 2000, ...
  40. The specified subscription type is invalid. Verify that the -SubscriptionType parameter for the Merge Agent has been correctly ...
  41. The specified update was successfully applied, but Setup detected that some features in instance {1} are not at the Service ...
  42. The specified upgrade path for this SQL Server edition is supported, but the edition you want to upgrade to has more limited ...
  43. The specified user account '{0}' for SQL Server Agent is a managed service account that is not supported for a SQL Server ...
  44. The specified user account '{0}' for SQL Server Agent is a virtual account that is not supported on this computer. To continue, ...
  45. The specified value '{0}' is invalid. To run in unattended mode, you must specify a valid ACTION. The valid values for ACTION ...
  46. The Specified value EnableUIOnServerCore for setting 'UIMODE' is invalid. The expected values are: Normal and AutoAdvance. ...
  47. The specified value for the enable_level parameter of the sp_filestream_configure stored procedure is not valid. The value ...
  48. The specified value of '{0}' for UpdateSource is invalid. The valid values are 'MU', a valid folder path, a relative path ...
  49. The specified value {0} for ACTION is invalid. To run in unattended mode, you must specify a valid ACTION. The valid values ...
  50. The specified values for initial_file_name and audit_record_offset do not represent a valid location within the audit file ...
  51. The specified WebMethodInfo is not correct. The ParamValue supplied does not match the ParamType. The DTSParamValue is not ...
  52. The specified workload (file or table) has no tunable events. Events must be one of the following types - SQL:BatchStarting, ...
  53. The specified workload (file or table) has no tunable events. Events must be one of the following types - SQL:BatchStarting, ...
  54. The sp_configure value 'contained database authentication' must be set to 1 in order to %1!s! a contained database. You may ...
  55. The SQL Agent service domain group could not be recovered. To complete repair, SQL Agent Service domain group must be provided. ...
  56. The SQL Distribution ActiveX control should not be initialized (using the Initialize method) before calling this method. ...
  57. The SQL Distribution control could not write to the registry. Ensure that the user has sufficient permissions to access the ...
  58. The SQL Merge ActiveX Control does not support pull or anonymous subscriptions to the specified subscriber datasource type ...
  59. The SQL object name '%1!s!' specified for property '%2!s!' contains more than the maximum number of prefixes. The maximum ...
  60. The SQL Server '%1!s!' could not obtain Windows group membership information for login '%2!s!'. Verify that the Windows account ...
  61. The SQL Server 2000 Client Tools feature does not meet upgrade requirements. To continue, install Microsoft SQL Server 2000 ...
  62. The SQL Server 2005 Client Tools feature does not meet upgrade requirements. To continue, install Microsoft SQL Server 2005 ...
  63. The SQL Server 2005 features that have been selected to be upgraded to SQL Server 2012 are not at the required service pack. ...
  64. The SQL Server 2008 features that have been selected to be upgraded to SQL Server 2012 are not at the required service pack. ...
  65. The SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2012 are not at the required service ...
  66. The SQL Server 2012 Data Mining Add-ins for Office cannot connect to an instance of SQL Server Analysis Services version ...
  67. The SQL Server 2012 Data Mining Add-ins for Office help you uncover hidden patterns and relationships in your data and then ...
  68. The SQL Server 2012 Setup wizard has encountered an internal error as it was not able to find a way to determine what changes ...
  69. The SQL Server Agent Service '{0}' could not be started, please check the System Event log and the Agent Log files to find ...
  70. The SQL Server Agent service (SQLServerAgent) is missing and must be re-created as part of the repair operation. Since the ...
  71. The SQL Server Agent service (SQLServerAgent) is missing and must be re-created as part of the repair operation. To continue, ...
  72. The SQL Server Agent service account '{0}' cannot be used along with a proxy. Please change the SQL Server Agent service ...
  73. The SQL Server Agent Service account '{0}' cannot be used to run the Managed Instance job because it is a built-in account. ...
  74. The SQL Server Agent service must be started. If the specified instance of SQL Server is a SQL Server failover cluster instance, ...
  75. The SQL Server Agent service on the UCP must be started. If the specified instance of SQL Server is a SQL Server failover ...