SQL Server 2012

  1. The log file '{0}' already exists. Would you like to overwrite this file or append conflict information to the end of it? ...
  2. The log file name "%1!s!" is invalid. Verify that the file exists and that the SQL Server service account has access to it. ...
  3. The log file path '%ws' to the ETW target is invalid. Verify that the path exists and that the process startup account has ...
  4. The log for database '%1!s!' is not available. Check the event log for related error messages. Resolve any errors and restart ...
  5. The log in this backup set begins at LSN %1!s!, which is too recent to apply to the database. An earlier log backup that ...
  6. The log in this backup set begins at LSN %1!s!, which is too recent to apply to the database. This restore sequence needs ...
  7. The log in this backup set contains bulk-logged changes. Point-in-time recovery was inhibited. The database has been rolled ...
  8. The log in this backup set terminates at LSN %1!s!, which is too early to apply to the database. A more recent log backup ...
  9. The log provider "%1!s!" cannot log messages on the installed %2!s! of SQL Server. The log provider requires %3!s! or higher. ...
  10. The log provider "%1!s!" cannot log messages on the installed edition of SQL Server. The log provider requires %2!s! or higher. ...
  11. The log provider for SQL Server Profiler was unable to load pfclnt.dll. Please check that SQL Server Profiler is installed. ...
  12. The log provider type "%1!s!" specified for log provider "%2!s!" is not recognized as a valid log provider type. This error ...
  13. The log provider type is not recognized as a valid log provider type. This error occurs when an attempt is made to create ...
  14. The Log Reader Agent encountered a NULL command that is not valid. Restart the agent if it has stopped. If the problem persists, ...
  15. The Log Reader Agent is scanning the transaction log for commands to be replicated. Approximately %1!d! log records have ...
  16. The Log Reader Agent scanned to the end of the log before processing all transactions in the hash table. %1!s! transactions ...
  17. The Log Reader Agent scanned to the end of the log while processing a bounded update. BEGIN_UPDATE LSN {%1!s!:%2!s!:%3!s!}, ...
  18. The Log Reader Agent was unable to connect to the Publisher using the specified login. Make sure that the login used by the ...
  19. The log reader encountered a 'CANNOT SERIALIZE TRANSACTION' error (ORA-08177) while creating an XactSet at the publisher. ...
  20. The log reader encountered a 'SNAPSHOT TOO OLD' error (ORA-01555) while creating an XactSet at the publisher. The creation ...
  21. The log reader encountered an 'OBJECT NOT FOUND' error (ORA-00942) while creating an XactSet at the publisher. The creation ...
  22. The log scan number %1!s! passed to log scan in database '%2!s!' is not valid. This error may indicate data corruption or ...
  23. The log shipping primary database %1!s!.%2!s! has backup threshold of %3!s! minutes and has not performed a backup log operation ...
  24. The log shipping secondary database %1!s!.%2!s! has restore threshold of %3!s! minutes and is out of sync. No restore was ...
  25. The log was not truncated because records at the beginning of the log are pending replication or Change Data Capture. Ensure ...
  26. The Log-Scan Process failed to construct a replicated command from log sequence number (LSN) {%1!s!:%2!s!:%3!s!}. Back up ...
  27. The logging level '%1!s!' is undefined. Provide one of the following logging levels: 0 (None), 1 (Basic), 2 (Performance), ...
  28. The logical file cannot be found inside the physical file. Physical file: %{PhysicalFile/}. Logical file: %{LogicalFile/}. ...
  29. The logical primary key of the selected dimension table contains column types not supported as key columns. Clear the check ...
  30. The logical record relationship between articles "%1!s!" and "%2!s!" cannot be added because at least one of the articles ...
  31. The login '%1!s!' does not have access permission on publication '%2!s!' because it is not in the publication access list. ...
  32. The login attempt failed for "%1!s!". This error occurs when the login credentials provided are incorrect. Verify the login ...
  33. The login failed for user "%1!s!". The password change failed. An unexpected error occurred during password validation. %2!s! ...
  34. The login failed for user "%1!s!". The password change failed. Password change during login is not supported in this version ...
  35. The login failed for user "%1!s!". The password change failed. The password does not meet the requirements of the password ...
  36. The login failed for user "%1!s!". The password change failed. The user does not have permission to change the password. ...
  37. The login has insufficient authority. Membership of the sysadmin role is required to use VIRTUAL_DEVICE with BACKUP or RESTORE. ...
  38. The login name of the user who originated the session. For example, if you connect to SQL Server using Login1 and execute ...
  39. The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the ...
  40. The login you entered does not have the necessary permissions to save the security configuration on server instance '{0}'. ...
  41. The login you specified when connecting to server instance '{0}' has limited permissions for monitoring database mirroring. ...
  42. The Lookup output that handles rows with no matching entries in the reference dataset. Use this output when the NoMatchBehavior ...
  43. The Lookup output that handles rows with no matching entries in the reference dataset. Use this output when the NoMatchBehavior ...
  44. The lookup transform must contain at least one input column joined to a reference column, and none were specified. You must ...
  45. The Lookup transformation failed to retrieve any rows. The transform fails when the FailOnLookupFailure is set to TRUE and ...
  46. The Lookup transformation reference metadata contains too few columns. Check the SQLCommand property. The SELECT statement ...
  47. The machine is clustered, but the cluster is not online or cannot be accessed from one of its nodes. To continue determine ...
  48. The magnitude of the result of a function call was too big to fit in the result type, and overflowed the type of the operand. ...
  49. The main assembly has the same public key as the components installed by SQL Server Setup, you cannot use it as the main ...
  50. The main assembly has the same public key as the components installed by SQL Server Setup. You cannot use it as the main ...
  51. The Management Data Warehouse version "%s" is not supported by the current data collector. Please upgrade the Management ...
  52. The Management Data Warehouse version is incompatible with the current reports. Please contact the administrator for the ...
  53. The Management Portal for SQL Azure cannot connect to server {0}'. To continue, use the Windows Azure Portal to update the ...
  54. The Many-to-many and Many-to-one conversion options are not valid because a single currency has been selected as the base ...
  55. The map, {0}, was detected in the report. SQL Server 2008 Reporting Services does not support map report items. Either reduce ...
  56. The mapping for column '%1' of article '%2', publication '%3' is not suitable for parameterized commands. Change the mapping ...
  57. The marked transaction "%1!s!" failed. A timeout occurred while attempting to place a mark in the log by committing the marked ...
  58. The master merge started at the end of the full crawl of table or indexed view '%1!s!' failed with HRESULT = ' 2!s!'. Database ...
  59. The master server operator will be created on the master server and each of the target servers. Multiserver jobs can only ...
  60. The matching configuration has been changed by another user, Your changes cannot be saved. The new settings are about to ...
  61. The matrix {1}' contains a different number of MatrixColumn elements than the number of StaticColumn elements. If the matrix ...
  62. The matrix {1}' contains a different number of MatrixRow elements than the number of StaticRow elements. If the matrix contains ...
  63. The matrix {1}' has a MatrixRow that contains a different number of MatrixCell elements than the number of StaticColumn elements ...
  64. The maximum allow integer identity value has been reached. Consider re-building the error tolerant index to use any gaps ...
  65. The maximum amount of time, in minutes, that Database Engine Tuning Advisor will spend tuning. In general, longer times produce ...
  66. The Maximum insert commit size property of the OLE DB destination "%1!s!" is set to 0. This property setting can cause the ...
  67. The Maximum insert commit size property of the OLE DB destination "{0}" is set to 0. This property setting can cause the ...
  68. The maximum number of days that a stored parameter can be stored. Valid values are 1 through 2,147,483,647. The default value ...
  69. The maximum number of snapshots that are stored for a report. Valid values are -1 and 1 through 2,147,483,647. If the value ...
  70. The maximum system-generated unique value for a duplicate group was exceeded for index with partition ID %1!s!. Dropping ...
  71. The maximum time, in seconds, that the principal server instance waits for a PING message from another instance in the mirroring ...
  72. The MAXIMUM_BUCKETS_FOR_CONTINUOUS_SPLIT parameter for the '%{modelname/}' model is not valid. MAXIMUM_BUCKETS_FOR_CONTINUOUS_SPLIT ...
  73. The MAXIMUM_CLUSTER_COUNT parameter is negative in the '%{modelname/}' Microsoft Sequence Clustering model. MAXIMUM_CLUSTER_COUNT ...
  74. The MAXIMUM_CONTINUOUS_INPUT_ATTRIBUTES parameter for the %{modelname/} model is not valid. MAXIMUM_CONTINUOUS_INPUT_ATTRIBUTES ...
  75. The MAXIMUM_INPUT_ATTRIBUTES parameter for the %{modelname/} model is not valid. MAXIMUM_INPUT_ATTRIBUTES must be at least ...