SQL Server 2012

  1. The reference to column "%1!s!" is not allowed in an argument to the NTILE function. Only references to columns at an outer ...
  2. The reference to the variable, parameter or goto label '%1!s!' resolves differently in the target metadata collation '%2!s!' ...
  3. The referenced report model file has an embedded DataSourceView, but {0} already exists. Are you sure you want to overwrite ...
  4. The referenced table does not exist or has not been created by SQL Server Profiler. Only tables created by SQL Profiler can ...
  5. The refresh of Oracle publisher '%1!s!' by sp_refresh_heterogeneous_publisher was not successful. The Oracle publisher meta ...
  6. The refresh operation failed because the source data base or the table does not exist, or because you do not have access ...
  7. The refresh operation failed because the source does not contain the column that was requested. You can fix this problem ...
  8. The registry key 'HKEY_LOCAL_MACHINE\{1}' does not exist on machine '{0}'. SQL Server Setup expects a valid security identifier ...
  9. The registry key '{0}' cannot be opened. The specified registry key is required to find sqlboot.dll and retrieve edition ...
  10. The registry key '{0}' is missing so the SQL Support files cannot run properly. To resolve this problem reinstall SQL Support. ...
  11. The registry settings for SNI protocol configuration are incorrect. The server cannot accept connection requests. Error: ...
  12. The registry value '{0}' is missing so the SQL Support files cannot run properly. To resolve this problem reinstall SQL Support. ...
  13. The registry value '{2}' in registry key 'HKEY_LOCAL_MACHINE\{1}' on machine '{0}' does not exist. SQL Server Setup expects ...
  14. The registry value '{2}' in registry key 'HKEY_LOCAL_MACHINE\{1}' on machine '{0}' does not exist. SQL Server Setup expects ...
  15. The registry value '{2}' in registry key 'HKEY_LOCAL_MACHINE\{1}' on machine '{0}' is unexpected registry type. SQL Server ...
  16. The regular snapshot for this publication has become obsolete or expired. The regular snapshot needs to be regenerated before ...
  17. The related table, {0}, was not included in the new dimension as a lookup table because it contains either a self-join or ...
  18. The RelatedRoleID property for the {0} is a self-reference. The RelatedRoleID property of a Role must refer to a Role other ...
  19. The RelatedRoleID property for the {0} refers to the {2}, but the RelatedRoleID for "{3}" does not refer to "{1}". The RelatedRoleID ...
  20. The relation '{0}' cannot be traversed from an instance of type '{1}' because that type is not a source type of the relation. ...
  21. The Relation property of the {0} references the {1} end of the {2}. This property must reference a Relation end that refers ...
  22. The Relation property of the {0} references the {2} end of the {3}, but the Relation property of the RelatedRole "{1}" also ...
  23. The Relation property of the {0} references the {2}, but the Relation property of the RelatedRole "{1}" references the {3}. ...
  24. 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 ...
  25. The relationship '%{strNewRelationship/}' cannot be created since relationship '%{strExistingRelationship/}' already exists ...
  26. The relationship '%{strNewRelationship/}' cannot be created since relationship '%{strExistingRelationship/}' already exists ...
  27. The relationship between the table in Excel and the table in the PowerPivot window was lost. It might have been lost either ...
  28. The relationship cannot be created because each column contains duplicate values. Select at least one column that contains ...
  29. The relationship cannot be created in the requested direction. When you click create, the direction of the relationship will ...
  30. The relationship for {0} '{1}' specifies NaturalJoin but the containing grouping '{3}' does not specify NaturalGroup. NaturalJoin ...
  31. The relationship has been identified as damaged. You can try to edit it, but editing might fail. The safest way to fix the ...
  32. The relationship is currently between a primary key column and a non-primary key column. If this is incorrect, click Reverse. ...
  33. The Remote Blob Storage server-side data cannot be removed because existing blobs are registered. This data can only be removed ...
  34. The remote copy of database "%1!s!" cannot be opened. Check the database name and ensure that it is in the restoring state, ...
  35. The remote copy of database "%1!s!" has not been rolled forward to a point in time that is encompassed in the local copy ...
  36. 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 ...
  37. The remote copy of database "%1!s!" is not recovered far enough to enable database mirroring or to join it to the availability ...
  38. The remote server "%1!s!" does not exist, or has not been designated as a valid Publisher, or you may not have permission ...
  39. The remote server '%1!s!' is not defined as a subscription server. Ensure you specify the server name rather than a network ...
  40. The remote server cannot be accessed. Either the server is not running, you do not have sufficient permissions to access ...
  41. The remote server cannot be accessed. Either the server is not running, you do not have sufficient permissions to access ...
  42. The remote server cannot be accessed. This may be because the server is not running, you do not have sufficient permissions ...
  43. The remote service has sent a message body of type '%1!s!' that does not match the message body encoding format. This occurred ...
  44. The RemoveFromSQLServer method encountered OLE DB error code 1!8.8X! (%2!s!) The SQL statement that was issued has failed. ...
  45. The Reorganize Index task defragments and compacts clustered and non-clustered indexes on tables and views. This will improve ...
  46. The Reorganize Index task defragments and compacts clustered and nonclustered indexes on tables and views. This will improve ...
  47. The repeat count %1!d! is negative and is not valid for function "%2!s!". The repeat count parameter cannot be negative. ...
  48. The Replay operation failed because the number of selected clients is larger than the number of SPIDs (StressScaleGranularity ...
  49. The replication administrative user for Oracle Publisher "%1!s!" has insufficient permissions. Refer to the script /MSSQL/Install/oracleadmin.sql ...
  50. The replication agent completed successfully. See the previous job step history message or Replication Monitor for more information. ...
  51. The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information. ...
  52. The replication agent encountered an error and is set to restart within the job step retry interval. See the previous job ...
  53. The Replication agent had detected inconsistent data in replication system table. It is possible that an article was added ...
  54. The replication agent had encounter an unexpected null '{0}' value from the database back end. Contact Technical Support. ...
  55. The replication agent had encountered an exception. Source: {0} Exception Type: {1} Exception Message: {2} Message Code: ...
  56. The replication agent had encountered an unexpected exception, a memory dump containing information about the exception has ...
  57. The replication agent had encountered at least one unhandled exception during execution. Extended error information can be ...
  58. The replication agent has not logged a progress message in %1!s! minutes. This might indicate an unresponsive agent or high ...
  59. The replication agent is being shut down because execution time for status callback handlers has exceeded the system limit ...
  60. The replication agent job '%1!s!' was not removed because it has a non-standard name; manually remove the job when it is ...
  61. The replication agent responded to a shutdown/cancel request and has been stopped. See the previous job step history message ...
  62. The Replication Conflict Viewer is not registered on '%1', or %9 could not retrieve information about the Viewer from the ...
  63. The replication Merge Agent failed to change metadata on one or more database objects at the Subscriber when applying the ...
  64. The replication Merge Agent failed to propagate a Publisher schema change to the Subscriber. When troubleshooting, restart ...
  65. The replication Merge Agent failed to retrieve subscription partitioning information from the Publisher. When troubleshooting, ...
  66. The replication settings on SQL Server version 6.0 cannot be upgraded directly to SQL Server 2000. You must first upgrade ...
  67. The replication upgrade task was not able to completely transfer your existing replication configuration settings to SQL ...
  68. The report '{0}' cannot be opened because no data source is associated with it. Associate a model data source with this report ...
  69. The report '{0}' cannot be opened because the data source '{1}' associated with it is not a report model. This report was ...
  70. The report '{0}' cannot be opened because you do not have permission to access the data source: '{0}'. Contact your administrator. ...
  71. The report '{0}' contains a reference to a data source that is not valid. Verify that the shared data sources and models ...
  72. The report '{0}' contains a reference to a dataset that is not valid. Verify that the shared datasets that are required for ...
  73. The report '{0}' is in an earlier report format and must be automatically upgraded before opening it in Report Builder 3.0. ...
  74. The Report Builder launch URL is not valid. It can be an absolute or relative URL and must include the .application file ...
  75. The report cannot be rendered. A filter is required to prevent too much data from being returned. Add a filter to your report. ...