SQL Server 2016

  1. The lineage identifier of an input column that contains a PivotedValue or the value -1. The value -1 indicates the column ...
  2. The linearRing input is not valid because there are not enough points in the input. A linearRing must have at least 4 points, ...
  3. The Linguistics property is specified for the {0}, but the Name property is omitted. Linguistics cannot be specified for ...
  4. The linked %{typename/} with the ID of '%{id/}', Name of '%{name/}' cannot be processed because it contains MG dimension ...
  5. The linked %{typename/} with the ID of '%{id/}', Name of '%{name/}' cannot be processed because its source object is not ...
  6. The list below shows which objects will be affected by the processing task. To process an object, select its check box. Selected ...
  7. The list of pages provided with the RESTORE PAGE statement is incorrectly formatted. Prior to the problem %1!s! pages were ...
  8. The listener for the WSFC resource '%1!s!' failed to start, and returned error code %2!s!, '%3!s!'. For more information ...
  9. The listener is not configured for the availability group. Either configure the listener now on the Specify Replicas page, ...
  10. The listener with DNS name '%1!s!' does not conform to SQL Server listener guidelines, and cannot be configured through SQL ...
  11. The listener with DNS name '%1!s!' for the availability group '%2!s!' is already listening on the TCP port %3!s!. Please ...
  12. The LoadFromSQLServer method has encountered OLE DB error code 1!8.8X! (%2!s!). The SQL statement that was issued has failed. ...
  13. The local availability replica of availability group '%1!s!' cannot accept signal '%2!s!' in its current replica role, '%3!s!', ...
  14. The local availability replica of availability group '%1!s!' cannot become the primary replica. The last-known primary availability ...
  15. The local availability replica of availability group '%1!s!' did not become primary. A concurrent operation may have changed ...
  16. The local availability replica of availability group '%1!s!' is in a failed state. The replica failed to read or update the ...
  17. The local computer is an owner of a cluster group that contains the SQL Server service, Analysis Services service or a generic ...
  18. The local computer is not an owner of an online cluster group for a failover cluster instance that contains the SQL Server ...
  19. The local computer is the only node left in the failover cluster that has not been upgraded, or it is a single-node failover ...
  20. The local connection is not available. This typically occurs because the AdomdServer object model is not being used within ...
  21. The local data source '{0}' contains a connection string that is an expression and cannot be converted to a shared data source. ...
  22. The local node is not part of quorum and is therefore unable to process this operation. This may be due to one of the following ...
  23. The local node is not part of quorum and is unable to initiate a failover. This could be caused by one of the following reasons: ...
  24. The local node is not part of quorum. This could be caused by one of the following reasons: The local node is not able to ...
  25. The local node of the failover cluster has already been upgraded, and no other nodes have been upgraded. It is not possible ...
  26. The local partition map for database %1!s! is starting up in reduced functionality mode because of log full. Pending partition ...
  27. The local service account is different from the active node. Use the SQL Configuration Manager to change the service account ...
  28. The localized description given in the {0} element which defined the {1} package could not be loaded, refer to the inner ...
  29. The location for temporary storage of buffer data. You can specify multiple directories by using semicolons to delimit the ...
  30. The location for temporary storage of columns that contain binary large object (BLOB) data. You can specify multiple directories ...
  31. The location of the gauge image inside the gauge container. The coordinates are measured as a percentage of the container's ...
  32. The location of the gauge inside the gauge container. The coordinates are measured as a percentage of the container's width ...
  33. The location of the gauge inside the gauge container. The coordinates are measured as a percentage of the container's width/height. ...
  34. The location of the gauge label inside the gauge container. The coordinates are measured as a percentage of the container's ...
  35. The location of the indicator inside the gauge container. The coordinates are measured as a percentage of the container's ...
  36. The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred ...
  37. The log configuration has been changed by another user, Your changes cannot be saved. The new settings are about to be loaded. ...
  38. The log file '{0}' already exists. Would you like to overwrite this file or append conflict information to the end of it? ...
  39. The log file name "%1!s!" is invalid. Verify that the file exists and that the SQL Server service account has access to it. ...
  40. The log file path '%ws' to the ETW target is invalid. Verify that the path exists and that the process startup account has ...
  41. The log for database '%1!s!' is not available. Check the event log for related error messages. Resolve any errors and restart ...
  42. 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 ...
  43. The log in this backup set begins at LSN %1!s!, which is too recent to apply to the database. This restore sequence needs ...
  44. The log in this backup set contains bulk-logged changes. Point-in-time recovery was inhibited. The database has been rolled ...
  45. 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 ...
  46. The log provider "%1!s!" cannot log messages on the installed edition of SQL Server. The log provider requires %2!s! or higher. ...
  47. The log provider for SQL Server Profiler was unable to load pfclnt.dll. Please check that SQL Server Profiler is installed. ...
  48. The log provider type "%1!s!" specified for log provider "%2!s!" is not recognized as a valid log provider type. This error ...
  49. The log provider type is not recognized as a valid log provider type. This error occurs when an attempt is made to create ...
  50. The Log Reader Agent encountered a NULL command that is not valid. Restart the agent if it has stopped. If the problem persists, ...
  51. The Log Reader Agent is scanning the transaction log for commands to be replicated. Approximately %1!d! log records have ...
  52. The Log Reader Agent scanned to the end of the log before processing all transactions in the hash table. %1!s! transactions ...
  53. 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!}, ...
  54. The Log Reader Agent was unable to connect to the Publisher using the specified login. Make sure that the login used by the ...
  55. The log reader encountered a 'CANNOT SERIALIZE TRANSACTION' error (ORA-08177) while creating an XactSet at the publisher. ...
  56. The log reader encountered a 'SNAPSHOT TOO OLD' error (ORA-01555) while creating an XactSet at the publisher. The creation ...
  57. The log reader encountered an 'OBJECT NOT FOUND' error (ORA-00942) while creating an XactSet at the publisher. The creation ...
  58. The log scan number %1!s! passed to log scan in database '%2!s!' is not valid. This error may indicate data corruption or ...
  59. The log shipping primary database %1!s!.%2!s! has backup threshold of %3!s! minutes and has not performed a backup log operation ...
  60. The log shipping secondary database %1!s!.%2!s! has restore threshold of %3!s! minutes and is out of sync. No restore was ...
  61. The log was not truncated because records at the beginning of the log are pending replication or Change Data Capture. Ensure ...
  62. The Log-Scan Process failed to construct a replicated command from log sequence number (LSN) {%1!s!:%2!s!:%3!s!}. Back up ...
  63. The logging level '%1!s!' is undefined. Provide one of the following logging levels: 0 (None), 1 (Basic), 2 (Performance), ...
  64. The logical file cannot be found inside the physical file. Physical file: %{PhysicalFile/}. Logical file: %{LogicalFile/}. ...
  65. The logical primary key of the selected dimension table contains column types not supported as key columns. Clear the check ...
  66. The logical record relationship between articles "%1!s!" and "%2!s!" cannot be added because at least one of the articles ...
  67. The login '%1!s!' does not have access permission on publication '%2!s!' because it is not in the publication access list. ...
  68. The login attempt failed for "%1!s!". This error occurs when the login credentials provided are incorrect. Verify the login ...
  69. The login failed for user "%1!s!". The password change failed. An unexpected error occurred during password validation. %2!s! ...
  70. The login failed for user "%1!s!". The password change failed. Password change during login is not supported in this version ...
  71. The login failed for user "%1!s!". The password change failed. The password does not meet the requirements of the password ...
  72. The login failed for user "%1!s!". The password change failed. The user does not have permission to change the password. ...
  73. The login has insufficient authority. Membership of the sysadmin role is required to use VIRTUAL_DEVICE with BACKUP or RESTORE. ...
  74. The login name of the user who originated the session. For example, if you connect to SQL Server using Login1 and execute ...
  75. The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the ...