SQL Server 2008 R2

  1. The dimension, '%{IMBITableId/}', cannot be created in VertiPaq mode because the attribute, '%{IMBIColumnId/}', binds to ...
  2. The direct cell writeback operation cannot be committed, because the '%{measuregroup/}' measure group has no direct write-enabled ...
  3. The direction of the self-join from the column '{1}' to the column '{2}' in '{0}' is not consistent with the logical key ...
  4. The DISCOVER_ENUMERATORS schema rowset returns the supported enumerators for a provider, including data types and values. ...
  5. The DISCOVER_LITERALS schema rowset returns the information about supported literals for a provider, including data types ...
  6. The DISCOVER_PROPERTIES schema rowset returns information about the properties supported by an XML for Analysis provider. ...
  7. The DISCOVER_SCHEMA_ROWSETS schema rowset returns a list of all RequestTypes enumeration values that are supported by the ...
  8. The discretization method specified for the '%{property/}' attribute is not valid because this attribute is bound to a non-numeric ...
  9. The discretization parameters (DiscretizationMethod and DiscretizationBucketCount) of the '%{column/}' column of the '%{structure/}' ...
  10. The discretized attribute with ID of '%{propertyId/}', Name of '%{propertyName/}'in the '%{dimension/}' dimension has a name ...
  11. The disk resource '{0}' could not be found on the SQL Server failover cluster. Ensure that the name you provided is correct, ...
  12. The disk resource '{0}' has a dependency on resource '{1}'. To use a disk in a new SQL Server failover cluster instance, ...
  13. The disk resource '{0}' is already in use by resource '{1}'. To use a disk in a new SQL Server failover cluster instance, ...
  14. The DisplayName property indicates the display name of the service. This string has a maximum length of 256 characters. The ...
  15. The distance from the range to the scale in percentage of the size of the gauge (height for horizontal gauges, width for ...
  16. The distributed transaction associated with UOW %1!s! is in PREPARE state. Use KILL UOW WITH COMMIT/ABORT syntax to kill ...
  17. The distributed transaction associated with UOW %1!s! is not in PREPARED state. Use KILL UOW to kill the transaction instead. ...
  18. The distributed transaction with UOW %1!s! was forced to commit. MS DTC became temporarily unavailable and forced heuristic ...
  19. The Distribution Agent encountered an error and was unable to write a tracer token to the MStracer_history table in the distribution ...
  20. The Distribution Agent is using the OLEDB streaming optimization for replicating binary large objects greater than %1!d! ...
  21. The Distribution Agent reached the end of current command (transaction: 1 command %2!d!), but the number of bytes read (%3!d!) ...
  22. The Distribution Agent was unable to update the cached log sequence numbers (LSNs) for Originator %1!s!, OriginatorDB %2!s!, ...
  23. The distribution database '%1!s!' cannot be opened due to inaccessible files. The database will be dropped, but distribution ...
  24. The distribution database '%1!s!' has a compatibility level of %2!s!, which is different from that of the master database. ...
  25. The distribution database '{0}' cannot be deleted until all Publishers using this distribution database have been disabled. ...
  26. The distribution database for the contacted Oracle instance does not match the expected name of the distribution database. ...
  27. The distribution database stores changes to transactional publications until Subscribers can be updated. It also stores historical ...
  28. The distribution Publisher property, 'distributor_password', has no usage and is not supported for a Distributor running ...
  29. The distributor login of the logreader agent must be a member of the sysadmin role or db_owner role in distribution database. ...
  30. The DLLs that are listed in the report define extended stored procedures that have not been registered using the full path. ...
  31. The DMX statement, INSERT INTO .COLUMN_VALUES, is not supported since the '%{structure/}' mining structure has one or more ...
  32. The DNS search list on computer {0} does not match. To correct this, synchronize the Public, not Private/heartbeat, network's ...
  33. The document cannot be created because the '{0}' type does not have an appropriate constructor. Make sure that the product ...
  34. The document cannot be created because the '{0}' type is not inherited from DocumentObject. Make sure that the product is ...
  35. The document could not be opened for editing. A compatible application could not be found to edit the document. Please install ...
  36. The DOM parser failed to load and parse the stream. URL:'%{strURL/}' Reason: '%{strReason/}' Source:'%{strSource/}'. File ...
  37. The domain group '{0}' failed to convert to the security identifier (SID). A reason can be the domain group is not a valid ...
  38. The domain network is not the first bound network. This will cause domain operations to run slowly and can cause timeouts ...
  39. The DTS upgrade analyzer utility analyzes DTS packages and lists issues that are likely to prove problematic while migrating ...
  40. The dynamic filters property for publication '%1!s!' has been incorrectly set. Use sp_changemergepublication to reset the ...
  41. The e-mail address {0} is not valid. E-mail address must be a valid e-mail address format. For example, '[email protected]'. ...
  42. The edition for the SQL Server Analysis Services feature is not the same on all nodes. The edition on computer {0} is not ...
  43. The edition for the SQL Server Database Services feature is not the same on all nodes. The edition on computer {0} is not ...
  44. The edition of Reporting Services that you are using only supports SQL Server relational databases for report data sources. ...
  45. The edition of Reporting Services that you are using requires that you use local SQL Server relational databases for report ...
  46. The edition of the Analysis Services instance to which a project will be deployed. This provides the default for new projects. ...
  47. The edition of the currently installed instance is different from the specified edition. When you add features to an existing ...
  48. The edition of the currently installed remote node cannot be determined. All failover cluster nodes must be the same SQL ...
  49. The element "{0}" in the ElementPath contains a reference to its value and a subelement. References to both value and subelement ...
  50. The element cannot be found in a collection. This error happens when you try to retrieve an element from a collection on ...
  51. The element indicates whether the client application displays the role's target entity fields and field folders when the ...
  52. The element name "{0}" cannot be used as a DataTable TableName since it only differs from the TableName of another DataTable ...
  53. The element that indicates the attributes that the client application should use to identify an instance of the entity to ...
  54. The element was specified for the parent condition type '{0}'. This is not supported for Conditions as output properties ...
  55. The element {3} named '{2}' is not valid for {0} '{1}'. The Writable flag can only be specified for the {3} collection on ...
  56. The encoded address '{0}' contains too many sections '{1}'. Sections are semicolon-delimited (;), and an encoded address ...
  57. The encoded address '{0}' does not have enough sections '{1}'. IPv4 and IPv6 sections are semicolon-delimited (;), and an ...
  58. The encoded IPv4 address '{0}' does not have enough sections'{1}. IPv4 sections are type, address, network, and subnet mask, ...
  59. The end of the data file was reached while reading header rows. Make sure the header row delimiter and the number of header ...
  60. The endpoint "%1!s!" is a built-in endpoint and cannot be dropped. Use the protocol configuration utilities to ADD or DROP ...
  61. The endpoint '%1!s!' has been established in metadata, but HTTP listening has not been enabled because HTTP support did not ...
  62. The endpoint of the line {1}' is negative. The value for Left plus the value for Width of a line cannot result in a negative ...
  63. The endpoint of the line {1}' is negative. The value for Top plus the value for Height of a line cannot result in a negative ...
  64. The endpoints of the server instances you have specified have conflicting port numbers. Endpoints for instances on the same ...
  65. The Enroll Instance Wizard will guide you through the process of enrolling an instance of SQL Server with the currently connected ...
  66. The entered value is out of the allowed range for the "{0}" data type. The valid values are greater than or equal to {1} ...
  67. The entire result set must be returned before this row can be updated. This operation is in progress and might take a long ...
  68. The entry point class name "{1}" was found during the migration of "{0}". The class will be renamed to "{2}" in the migrated ...
  69. The enumerator that defines how the client application generates a context-sensitive name for the attribute when the entity ...
  70. The enumerator that indicates the attribute's data type. If an Expression data type is also present, the Expression and DataType ...
  71. The enumerator that indicates whether this attribute should be sorted Ascending or Descending when the main attribute is ...
  72. The enumerator that overrides the ContextualName setting for attributes in the role's target entity when the role is used ...
  73. The error described above occurred when trying to delete this data at this location, possibly because the deletion violated ...
  74. The error described above occurred when trying to delete this data at this location, possibly because the deletion violated ...
  75. The error described above occurred when trying to delete this row. If you ignore this conflict, you should resolve it through ...