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