SQL Server 2008 R2

  1. The raw certificate data cannot be obtained from the supplied certificate object (error: %1!s!). This occurs when CPackage::put_CertificateObject ...
  2. The raw source adapter opened a file, but the file contains no columns. The adapter will not produce data. This could indicate ...
  3. The RBS FILESTREAM Provider server-side data cannot be removed because there are existing blobs in the provider. This data ...
  4. The read operation for the notification polling process against the '%{datasource/}' data source failed, because the result ...
  5. The READPAST lock hint is only allowed on target tables of UPDATE and DELETE and on tables specified in an explicit FROM ...
  6. The Rebuild Index task reorganizes data on the data and index pages by rebuilding indexes. This improves performance of index ...
  7. The Rebuild task reorganizes data on the data and index pages by rebuilding indexes. This improves performance of index scans ...
  8. The reconciler process was stopped because the Subscriber that initiated the synchronization is no longer connected. If this ...
  9. The record was skipped because a null attribute key was encountered. Attribute: %{Property/} of Dimension: %{Dimension/} ...
  10. The record was skipped because the attribute key is a duplicate. Attribute: %{Property/} of Dimension: %{Dimension/} from ...
  11. The record was skipped because the attribute key was not found. Attribute: %{Property/} of Dimension: %{Dimension/} from ...
  12. The recovery model cannot be changed to SIMPLE when any files are subject to a RESTORE PAGE operation. Complete the restore ...
  13. The Rectangle '{0}' is too complex to export to Word. Please group the ReportItems together into rectangles to simplify. ...
  14. The reference column "%1!s!" may be a SQL timestamp column. When the fuzzy match index is built, and a copy of the reference ...
  15. The reference parameter given to XMLDT method '%1!s!' was generated from a different XML instance than the one it is being ...
  16. The reference table '%1!s!' contains a non-integer type identity column which is not supported. Use a view of the table without ...
  17. The reference table '%1!s!' does not have a clustered index on an integer identity column, which is required if the property ...
  18. The reference table name "%1!s!" is not a valid SQL identifier. This error occurs if the table name cannot be parsed from ...
  19. The reference table specified has too many rows. Fuzzy Lookup only works with reference tables having less than 1 billion ...
  20. The reference to column "%1!s!" is not allowed in the argument of the TOP clause. Only references to columns at an outer ...
  21. The referenced report model file has an embedded DataSourceView, but {0} already exists. Are you sure you want to overwrite ...
  22. The referenced table does not exist or has not been created by SQL Server Profiler. Only tables created by SQL Profiler can ...
  23. The refresh of Oracle publisher '%1!s!' by sp_refresh_heterogeneous_publisher was not successful. The Oracle publisher meta ...
  24. The refresh operation failed because the source data base or the table does not exist, or because you do not have access ...
  25. The refresh operation failed because the source does not contain the column that was requested. You can fix this problem ...
  26. The registry key 'HKEY_LOCAL_MACHINE\{0}' does not exist. SQL Server Setup expects a valid security identifier (SID) stored ...
  27. The registry key 'HKEY_LOCAL_MACHINE\{1}' does not exist on the cluster node '{0}'. SQL Server Setup expects a valid security ...
  28. The registry key '{0}' cannot be opened. The specified registry key is required to find sqlboot.dll and retrieve edition ...
  29. The registry key '{0}' is missing so the SQL Support files cannot run properly. To resolve this problem reinstall SQL Support. ...
  30. The registry settings for SNI protocol configuration are incorrect. The server cannot accept connection requests. Error: ...
  31. The registry value '{0}' is missing so the SQL Support files cannot run properly. To resolve this problem reinstall SQL Support. ...
  32. The registry value '{1}' in registry key 'HKEY_LOCAL_MACHINE\{0}' does not exist. SQL Server Setup expects a valid security ...
  33. The registry value '{1}' in registry key 'HKEY_LOCAL_MACHINE\{0}' is unexpected registry type. SQL Server Setup expects a ...
  34. The registry value '{2}' in registry key 'HKEY_LOCAL_MACHINE\{1}' on the cluster node '{0}' does not exist. SQL Server Setup ...
  35. The registry value '{2}' in registry key 'HKEY_LOCAL_MACHINE\{1}' on the cluster node '{0}' is unexpected registry type. ...
  36. The regular snapshot for this publication has become obsolete or expired. The regular snapshot needs to be regenerated before ...
  37. The related table, {0}, was not included in the new dimension as a lookup table because it contains either a self-join or ...
  38. The RelatedRoleID property for the {0} is a self-reference. The RelatedRoleID property of a Role must refer to a Role other ...
  39. The RelatedRoleID property for the {0} refers to the {2}, but the RelatedRoleID for "{3}" does not refer to "{1}". The RelatedRoleID ...
  40. The Relation property of the {0} references the {1} end of the {2}. This property must reference a Relation end that refers ...
  41. The Relation property of the {0} references the {2} end of the {3}, but the Relation property of the RelatedRole "{1}" also ...
  42. The Relation property of the {0} references the {2}, but the Relation property of the RelatedRole "{1}" references the {3}. ...
  43. The Relation property of the {0} refers to the {1} end of the {2}, which is not bound to a set of uniquely constrained columns ...
  44. The relationship '%{strNewRelationship/}' cannot be created since relationship '%{strExistingRelationship/}' already exists ...
  45. The relationship '%{strNewRelationship/}' cannot be created since relationship '%{strExistingRelationship/}' already exists ...
  46. The relationship between the table in Excel and the table in the PowerPivot window was lost. It might have been lost either ...
  47. The relationship cannot be created because each column contains duplicate values. Select at least one column that contains ...
  48. The relationship cannot be created in the requested direction. When you click create, the direction of the relationship will ...
  49. The relationship has been identified as damaged. You can try to edit it, but editing might fail. The safest way to fix the ...
  50. The relationship is currently between a primary key column and a non-primary key column. If this is incorrect, click Reverse. ...
  51. The Remote Blob Storage server-side data cannot be removed because existing blobs are registered. This data can only be removed ...
  52. The remote copy of database "%1!s!" cannot be opened. Check the database name and ensure that it is in the restoring state, ...
  53. The remote copy of database "%1!s!" has not been rolled forward to a point in time that is encompassed in the local copy ...
  54. The remote copy of database "%1!s!" has not had enough log backups applied to roll forward all of its files to a common point ...
  55. The remote server "%1!s!" does not exist, or has not been designated as a valid Publisher, or you may not have permission ...
  56. The remote server '%1!s!' is not defined as a subscription server. Ensure you specify the server name rather than a network ...
  57. The remote server cannot be accessed. Either the server is not running, you do not have sufficient permissions to access ...
  58. The remote server cannot be accessed. Either the server is not running, you do not have sufficient permissions to access ...
  59. The remote server cannot be accessed. This may be because the server is not running, you do not have sufficient permissions ...
  60. The remote service has sent a message body of type '%1!s!' that does not match the message body encoding format. This occurred ...
  61. The RemoveFromSQLServer method encountered OLE DB error code 1!8.8X! (%2!s!) The SQL statement that was issued has failed. ...
  62. The Reorganize Index task defragments and compacts clustered and non-clustered indexes on tables and views. This will improve ...
  63. The Reorganize Index task defragments and compacts clustered and nonclustered indexes on tables and views. This will improve ...
  64. The repeat count %1!d! is negative and is not valid for function "%2!s!". The repeat count parameter cannot be negative. ...
  65. The replication administrative user for Oracle Publisher "%1!s!" has insufficient permissions. Refer to the script /MSSQL/Install/oracleadmin.sql ...
  66. The replication agent completed successfully. See the previous job step history message or Replication Monitor for more information. ...
  67. The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information. ...
  68. The replication agent encountered an error and is set to restart within the job step retry interval. See the previous job ...
  69. The Replication agent had detected inconsistent data in replication system table. It is possible that an article was added ...
  70. The replication agent had encounter an unexpected null '{0}' value from the database back end. Contact Technical Support. ...
  71. The replication agent had encountered an exception. Source: {0} Exception Type: {1} Exception Message: {2} Message Code: ...
  72. The replication agent had encountered an unexpected exception, a memory dump containing information about the exception has ...
  73. The replication agent had encountered at least one unhandled exception during execution. Extended error information can be ...
  74. The replication agent has not logged a progress message in %1!s! minutes. This might indicate an unresponsive agent or high ...
  75. The replication agent is being shut down because execution time for status callback handlers has exceeded the system limit ...