SQL Server 2008 R2

  1. The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last ...
  2. The rule '{0}' has no ExpressionXml defined, and the ExpressionGeneratorType is not defined. The ExpressionGeneratorType ...
  3. The rule '{0}' has no ExpressionXml defined, but the element is optional only for Comparison type rules. For all other rules ...
  4. The rule '{0}' is defined as a cluster comparison, but the ExpressionXml element was specified. This element is not allowed ...
  5. The rule cannot determine whether Windows Firewall is enabled. Any access from a remote computer will be blocked if a firewall ...
  6. The rule cannot verify Internet access on this version of Windows. There might be delays in starting a .NET application like ...
  7. The runtime connection manager with the ID "%1!s!" cannot be found. Verify that the connection manager collection has a connection ...
  8. The runtime object cannot be loaded from the specified XML node. This happens when trying to load a package or other object ...
  9. The same column(s) of the same row was updated at both '%1' and '%2'. The resolver chose the update from '%3' as the winner. ...
  10. The SaveToSQLServer method has encountered OLE DB error code 1!8.8X! (%2!s!). The SQL statement that was issued has failed. ...
  11. The scalar values property for the {2} of the {0} {1}' is set to true. Scalar cannot be true if the axis has more than one ...
  12. The scalar values property for the {2} of the {0} {1}' is set to true. Scalar cannot be true if the dynamic grouping has ...
  13. The scalar values property for the {2} of the {0} {1}' is set to true. Therefore the specified label expression will be ignored. ...
  14. The scale %1!u! exceeded the maximum limit of 7 for time/datetime2/datetimeoffset column %2!Iu!. InMemory Rowset creation ...
  15. The schedule '{0}' already exists and cannot be created or renamed. This error occurs when the schedule name is not unique. ...
  16. The schedule '{0}' at the Share Point site '{1}' already exists and cannot be created or renamed. This error occurs when ...
  17. The schedule '{0}' cannot be found. The schedule identifier that is provided to an operation cannot be located in the report ...
  18. The schedule was not attached to the specified job. The schedule owner and the job owner must be the same or the operation ...
  19. The schema at the Publisher (version: %2!d! and guid: '%1') does not match the schema at the Subscriber (version: %4!d! and ...
  20. The schema change failed during execution of an internal replication procedure. For corrective action, see the other error ...
  21. The schema definition of the destination table '%1'.'%2' in the subscription database does not match the schema definition ...
  22. The schema for the article %1!s! was either not generated properly or was not applied properly during initial synchronization. ...
  23. The schema of the custom DataSet object implemented in the business logic handler does not match the schema of the source ...
  24. The schema option to script out the FILESTREAM attribute on varbinary(max) columns has been enabled for article '%1!s!'. ...
  25. The schema options available for a procedure, function, synonym, or aggregate schema article are: 0x00000001, 0x00000020, ...
  26. The schema options available for a view schema article are: 0x00000001, 0x00000010, 0x00000020, 0x00000040, 0x00000100, 0x00001000, ...
  27. The schema script '%1' could not be propagated to the subscriber due to an error in creating index. A possible cause of this ...
  28. The schema {0} does not have any corresponding user or role. Schema objects are not supported in the target database version, ...
  29. The score override argument, if present in one of the subqueries, must be present in all subqueries and must be the same ...
  30. The script component is configured to pre-compile the script, but binary code is not found. Please visit the IDE in Script ...
  31. The script exceeds the Transact-SQL IntelliSense maximum script size setting. You can change the setting on the Text Editor/Transact-SQL/IntelliSense ...
  32. The script level for '%1!s!' in database '%2!s!' cannot be downgraded from %3!s! to %4!s!, which is supported by this server. ...
  33. The Script Task "{0}" uses a version of Visual Studio Tools for Application (VSTA) that is not supported in this release ...
  34. The second argument in a Top or Bottom function must be a column. The error occurred at line %d{Line/}, column %d{Column/}. ...
  35. The security certificate bound to database principal (Id: %1!s!) has been disabled for use with BEGIN DIALOG. See the Books ...
  36. The security certificate bound to database principal (Id: %1!s!) has expired. Create or install a new certificate for the ...
  37. The security certificate bound to database principal (Id: %1!s!) is not yet valid. Either wait for the certificate to become ...
  38. The security identifier (SID) retrieved from registry value '{1}' in registry key 'HKEY_LOCAL_MACHINE\{0}' failed to convert ...
  39. The security identifier (SID) retrieved from registry value '{2}' in registry key 'HKEY_LOCAL_MACHINE\{1}' on the cluster ...
  40. The security identifier (SID) {0} failed to convert to a qualified account name. A reason can be the account for this SID ...
  41. The security mode specified requires the server '%1!s!' to be registered as a linked server. Use sp_addlinkedserver to add ...
  42. The security settings that are defined for this item will be replaced by the security settings of its parent {0}. Do you ...
  43. The Select expression for grouping stream is not referencing any non-grouping key, which is not supported. The following ...
  44. The Select followed by OrderBy oeperator needs to be a simple select on the element of event. The following expression is ...
  45. The SELECT item identified by the ORDER BY number %1!s! contains a variable as part of the expression identifying a column ...
  46. The SELECT item identified by the ORDER BY number {0} contains a variable as part of the expression identifying a column ...
  47. The select list for the INSERT statement contains fewer items than the insert list. The number of SELECT values must match ...
  48. The select list for the INSERT statement contains fewer items than the insert list. The number of SELECT values must match ...
  49. The select list for the INSERT statement contains more items than the insert list. The number of SELECT values must match ...
  50. The select list for the INSERT statement contains more items than the insert list. The number of SELECT values must match ...
  51. The selected action cannot be completed because of the following error. {0} This error may have occurred because the definition ...
  52. The selected configuration could not be moved after the next configuration. Verify that a configuration is selected and there ...
  53. The selected configuration could not be moved before the previous configuration. Verify that a configuration is selected ...
  54. The selected connection manager does not use a SQL Server provider. Bulk insert operations require a connection that uses ...
  55. The selected connection manager uses an earlier version of a SQL Server provider. Bulk insert operations require a connection ...
  56. The selected data extension {0} is not installed or cannot be loaded. Verify that the selected data extension is installed ...
  57. The selected database contains foreign keys that create a cycle. Publishing data only is not supported for databases with ...
  58. The selected database does not have the Recovery Model property set to full. This is required in order to back up the transaction ...
  59. The selected database is not a Master Data Services database. Select a SQL Server database that contains Master Data Services ...
  60. The selected image is not located on a report server. Specify an image from the same report server or SharePoint site as ...
  61. The selected instance for installation is already installed and clustered on computer {0}. To continue, select a different ...
  62. The selected instance is already installed and clustered on this or other cluster nodes. To continue, use AddNode to add ...
  63. The selected instance is clustered and cannot be removed as specified. To remove the selected instance, select "Remove Node" ...
  64. The selected instance is SQL Server 2000 at Service Pack 4 (SP4) and meets the requirements or is not a SQL Server 2000 instance. ...
  65. The selected map contains no layer with embedded spatial data. Choose a map with a layer that has embedded polygons, lines, ...
  66. The selected Master Data Services instances will be removed from the scale-out deployment. To add a Master Data Services ...
  67. The selected members cannot be moved together because they are not from the same level in the hierarchy. Only members that ...
  68. The selected Reporting Services instances will be removed from the scale out deployment. To add a Reporting Services instance ...
  69. The selected shapefile is not located on a report server. Specify a shapefile from the same report server or SharePoint site ...
  70. The selected SQL Server 2000 instance does not meet the requirements for upgrade. To continue install Microsoft SQL Server ...
  71. The selected SQL Server 2008 instance does not meet the requirements for build-to-build upgrade. To continue, you must remove ...
  72. The selected SQL Server 2008 instance does not meet the requirements for slipstream build-to-build upgrade. The mimimum requirement ...
  73. The selected SQL Server 2008 instance meets the requirements for build-to-build slipstream upgrade or the selected instance ...
  74. The selected SQL Server 2008 instance meets the requirements for build-to-build upgrade or the selected instance is not SQL ...
  75. The SelectedDates collection can be changed only in a multiple selection mode. Use the SelectedDate in a single selection ...