SQL Server 2008

  1. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'ProbabilityVariance'. ...
  2. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'Stddev'. Column=%{ColumnName/}]. ...
  3. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'Support'. Column=%{ColumnName/}]. ...
  4. The specified algorithm cannot handle columns of the mining model, %{modelname/}, with content of type 'Variance'. Column=%{ColumnName/}]. ...
  5. The specified batch separator contains invalid characters. Check the batch separator and then try again. Spaces are not allowed ...
  6. The specified breakpoint ID already exists. This error occurs when a task calls CreateBreakpoint with the same ID multiple ...
  7. The specified clustered upgrade is not currently supported. This cluster upgrade will be supported by the final release of ...
  8. The specified column set value causes the estimated row size to be at least %1!s! bytes. This exceeds the maximum allowed ...
  9. The specified connection "%1!s!" is either not valid, or points to an invalid object. To continue, specify a valid connection. ...
  10. The specified connection string is not valid. Do you want to reset the connection string? If you click OK, the existing connection ...
  11. The specified credentials for the SQL Server service are not valid. To continue, provide a valid account and password for ...
  12. The specified credentials that were provided for the SQL Server service are not valid. To continue, provide a valid account ...
  13. The specified data source folder is not valid. Specify a value for the TargetDataSourceFolder property in the deployment ...
  14. The specified database does not exist. You must choose an initialization option that creates the database when restoring ...
  15. The specified database folder '%{filename/}' is not valid. It does not match the Analysis Services naming convention of 'ID.version.db'. ...
  16. The specified delimiters do not match the delimiters used to build the pre-existing match index "%1!s!". This error occurs ...
  17. The specified disk resource '{0}' is not a valid cluster physical disk resource name. To continue, specify a valid disk resource ...
  18. The specified drive is FAT32 file system. It is recommended that you install SQL Server on a NTFS file system as it is more ...
  19. The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2008 version ...
  20. The specified filegroup '%1!s!' is not a valid filegroup for database '%2!s!'. Specify a valid existing filegroup or create ...
  21. The specified FILESTREAM share name already exists. You should delete the share if it exists or specify a different share ...
  22. The specified FILESTREAM share name does not match the file share resource of the current failover cluster. Change the FILESTREAM ...
  23. The specified FILESTREAM share name is not a valid Windows share name. Verify that the share name is a valid Windows share ...
  24. The specified filter returns more members than can be displayed. Only the first {0} members are displayed. Consider specifying ...
  25. The specified folder uses a special share name that can usually be accessed only by a login with administrative privileges ...
  26. The specified header or data row delimiter "{1}" is not found after scanning {2} bytes of the file "{0}". Do you want to ...
  27. The specified header or data row delimiter "{1}" is not found after scanning {2} bytes of the file "{0}". The preview cannot ...
  28. The specified holdout parameters, HoldoutMaxPercent=%{holdoutmaxpercent\}, HoldoutMaxCases=%{holdoutmaxcases\}, will cause ...
  29. The specified holdout parameters, HoldoutMaxPercent=%{holdoutmaxpercent\}, HoldoutMaxCases=%{holdoutmaxcases\}, will cause ...
  30. The specified ID is in the empty (or SMDL) namespace but it is not a GUID. IDs in the empty (or SMDL) namespace must match ...
  31. The specified input does not represent a valid geography instance because it exceeds a single hemisphere. Each geography ...
  32. The specified instance name is already used by an existing SQL Server instance. To continue, specify a unique instance name ...
  33. The specified item is not a report definition (.rdl). Specify a report by opening the tool pane and specifying the path and ...
  34. The specified job '%1!s!' is not created for maintenance plans. Verify that the job has at least one step calling xp_sqlmaint. ...
  35. The specified login is not a member of the db_owner fixed database role for the publication database and is not a member ...
  36. 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!}. ...
  37. The specified maximum size limit for the audit log file is less than the minimum value allowed. The maximum size limit must ...
  38. The specified maximum size limit is greater than the maximum value allowed. The maximum size limit must be less than 16777215 ...
  39. 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 ...
  40. The specified name prefix will generate partition names that already exist. Do you want to overwrite these partitions: {0}? ...
  41. The specified network name for this SQL Server failover cluster instance is too long. Network names are limited to {0} characters. ...
  42. The specified number of maximum parallel tasks is not valid. The value of the parameter must be an integer that is greater ...
  43. The specified package path does not contain a package name. This occurs when the path does not contain at least one backslash ...
  44. The specified pattern did not return any files or does not represent a valid file share. Verify the pattern parameter and ...
  45. The specified pre-existing match index "%1!s!" was not originally built with fuzzy match information for column "%2!s!". ...
  46. The specified publication does not allow subscriptions to be initialized from a backup. To allow initialization from a backup, ...
  47. The specified Publisher is not enabled as a remote Publisher at this Distributor. Ensure the value specified for the parameter ...
  48. The specified remote server name may not be the network name of the remote server or the remote server is unreachable due ...
  49. The specified remote server name might not correspond to the network name of the remote server or the remote server was unreachable ...
  50. The specified report folder is not valid. Specify a value for the TargetReportFolder property in the deployment settings. ...
  51. The specified sa password does not meet strong password requirements. For more information about strong password requirements, ...
  52. The specified schema name '%1!s!' for classifier user-defined function either does not exist, or the user does not have permission ...
  53. The specified sets in the '%{func/} function have incompatible hierarchies at position %{iHier/}. The sets are incompatible. ...
  54. The specified source object must be a user-defined aggregate object if it is published as an 'aggregate schema only' type ...
  55. The specified source object must be a user-defined function object if it is going to be published as a 'func schema only' ...
  56. The specified statistic does not exist in the current data source or did not apply to the specified table or it does not ...
  57. The specified Subscriber cannot use transformable subscriptions using Data Transformation Services. Only SQL Server 2000, ...
  58. The specified subscription type is invalid. Verify that the -SubscriptionType parameter for the Merge Agent has been correctly ...
  59. The specified upgrade path for this SQL Server edition is supported, but the edition you want to upgrade to has more limited ...
  60. The specified value for the enable_level parameter of the sp_filestream_configure stored procedure is not valid. The value ...
  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 workload (file or table) has no tunable events. Events must be one of the following types - SQL:BatchStarting, ...
  64. The specified workload (file or table) has no tunable events. Events must be one of the following types - SQL:BatchStarting, ...
  65. The SQL Agent service domain group could not be recovered. To complete repair, SQL Agent Service domain group must be provided. ...
  66. The SQL Distribution ActiveX control should not be initialized (using the Initialize method) before calling this method. ...
  67. The SQL Distribution control could not write to the registry. Ensure that the user has sufficient permissions to access the ...
  68. The SQL Merge ActiveX Control does not support pull or anonymous subscriptions to the specified subscriber datasource type ...
  69. The SQL object name '%1!s!' specified for property '%2!s!' contains more than the maximum number of prefixes. The maximum ...
  70. The SQL Server '%1!s!' could not obtain Windows group membership information for login '%2!s!'. Verify that the Windows account ...
  71. The SQL Server 2000 Client Tools feature does not meet upgrade requirements. To continue, install Microsoft SQL Server 2000 ...
  72. The SQL Server 2005 Client Tools feature does not meet upgrade requirements. To continue, install Microsoft SQL Server 2005 ...
  73. The SQL Server 2005 Integration Services (SSIS) Package Migration Wizard does not migrate ActiveX Script code that accesses ...
  74. The SQL Server 2005 Integration Services (SSIS) Package Migration Wizard does not migrate ActiveX scripts associated with ...
  75. The SQL Server 2005 Integration Services (SSIS) Package Migration Wizard does not migrate complex Data Transformation tasks ...