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