Errors 1000 - 1999

1002

16

No

Line %d: Specified scale %d is invalid.

1004

16

No

Invalid column prefix '%.*ls': No table name specified

1006

15

No

CREATE TRIGGER contains no statements.

1008

15

No

The SELECT item identified by the ORDER BY number %d contains a variable as part of the expression identifying a column position. Variables are only allowed when ordering by an expression referencing a column name.

1010

15

No

Invalid escape character '%.*ls'.

1012

15

No

The correlation name '%.*ls' has the same exposed name as table '%.*ls'.

1014

15

No

TOP clause contains an invalid value.

1016

15

No

Outer join operators cannot be specified in a query containing joined tables.

1019

15

No

Invalid column list after object name in GRANT/REVOKE statement.

1021

10

No

FIPS Warning: Line %d has the non-ANSI statement '%ls'.

1023

15

No

Invalid parameter %d specified for %ls.

1025

10

No

FIPS Warning: The length of identifier '%.*ls' exceeds 18.

1028

15

No

The CUBE, ROLLUP, and GROUPING SETS constructs are not allowed in a GROUP BY ALL clause.

1030

16

No

Only constants are allowed here. Time literal is not permitted because it refers to the current date.

1032

16

No

Cannot use the column prefix '%.*ls'. This must match the object in the UPDATE clause '%.*ls'.

1034

15

No

Syntax error: Duplicate specification of the action "%.*s" in the trigger declaration.

1036

15

No

File option %hs is required in this CREATE/ALTER DATABASE statement.

1038

15

No

An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.

1041

15

No

Option %.*ls is not allowed for a LOG file.

1043

16

No

'%hs' is not yet implemented.

1045

15

No

Aggregates are not allowed in this context. Only scalar expressions are allowed.

1047

15

No

Conflicting locking hints specified.

1049

15

No

Mixing old and new syntax to specify cursor options is not allowed.

1051

15

No

Cursor parameters in a stored procedure must be declared with OUTPUT and VARYING options, and they must be specified in the order CURSOR VARYING OUTPUT.

1053

15

No

For DROP STATISTICS, you must provide both the object (table or view) name and the statistics name, in the form "objectname.statisticsname".

1055

15

No

'%.*ls' is an invalid name because it contains a NULL character or an invalid unicode character.

1057

15

No

The IDENTITY function cannot be used with a SELECT INTO statement containing a UNION, INTERSECT or EXCEPT operator.

1059

15

No

Cannot set or reset the 'parseonly' option within a procedure or function.

1061

16

No

The text/ntext/image constants are not yet implemented.

1063

16

No

A filegroup cannot be added using ALTER DATABASE ADD FILE. Use ALTER DATABASE ADD FILEGROUP.

1065

15

No

The NOLOCK and READUNCOMMITTED lock hints are not allowed for target tables of INSERT, UPDATE, DELETE or MERGE statements.

1067

15

No

The SET SHOWPLAN statements must be the only statements in the batch.

1069

16

No

Index hints are only allowed in a FROM or OPTION clause.

1071

16

No

Cannot specify a JOIN algorithm with a remote JOIN.

1073

15

No

'%.*ls' is not a recognized cursor option for cursor %.*ls.

1075

15

No

RETURN statements in scalar valued functions must include an argument.

1077

15

No

INSERT into an identity column not allowed on table variables.

1079

15

No

A variable cannot be used to specify a search condition in a fulltext predicate when accessed through a cursor.

1081

16

No

%s does not allow specifying the database name as a prefix to the assembly name.

1083

15

No

OWNER is not a valid option for EXECUTE AS in the context of server and database level triggers.

1085

15

No

'%.*ls' event type does not support event notifications.

1087

15

No

Must declare the table variable "%.*ls".

1089

15

No

The SET FMTONLY OFF statement must be the last statement in the batch.

1091

15

No

The option "%ls" is not valid for this function.

1093

16

No

%.*ls is not a valid broker name.

1095

15

No

%.*ls has already been specified as an event type.

1097

15

No

Cannot use If UPDATE within this CREATE TRIGGER statement.

1099

15

No

The ON clause is not valid for this statement.

1105

17

Yes

Could not allocate space for object '%.*ls'%.*ls in database '%.*ls' because the '%.*ls' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

1121

17

No

Space allocator cannot allocate page in database %d.

1123

14

No

Table error: Page %S_PGID. Unexpected page type %d.

1125

14

No

Table error: Page %S_PGID. Test (%hs) failed. Slot %d, row extends into free space at 0x%x.

1127

14

No

Table error: Page %S_PGID. Test (%hs) failed. Values are %ld and %ld.

1129

16

No

Could not cleanup deferred deallocations from filegroup '%.*ls'.

1131

10

Yes

Failed to truncate AppendOnlyStorageUnit 0x%p. Will retry next time. This is an informational message only. No user action is required.

1203

20

Yes

Process ID %d attempted to unlock a resource it does not own: %.*ls. Retry the transaction, because this error may be caused by a timing condition. If the problem persists, contact the database administrator.

1205

13

No

Transaction (Process ID %d) was deadlocked on %.*ls resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

1207

10

Yes

Can't allocate %u locks on startup, reverting to %u and turning on dynamic lock allocation. Maximum allowed memory usage at startup is %I64u KB.

1209

21

Yes

Could not allocate initial %u lock owner blocks during startup. Can not start the server.

1212

10

Yes

Lock not logged: %-30ls Mode: %s

1214

17

Yes

Internal Error. There are too many parallel transactions.

1221

20

Yes

The Database Engine is attempting to release a group of locks that are not currently held by the transaction. Retry the transaction. If the problem persists, contact your support provider.

1223

16

No

Cannot release the application lock (Database Principal: '%.*ls', Resource: '%.*ls') because it is not currently held.

1225

16

No

An invalid application lock mode was passed to %ls.

1227

16

No

An invalid application lock time-out was passed to %ls.

1230

16

No

An invalid database principal was passed to %ls.

1402

20

Yes

Witness did not find an entry for database mirroring GUID {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. A configuration mismatch exists. Retry the command, or reset the witness from one of the database mirroring partners.

1404

16

No

The command failed because the database mirror is busy. Reissue the command later.

1406

16

No

Unable to force service safely. Remove database mirroring and recover database "%.*ls" to gain access.

1408

16

No

The remote copy of database "%.*ls" is not recovered far enough to enable database mirroring.

1410

16

No

The remote copy of database "%.*ls" is already enabled for database mirroring.

1412

16

No

The remote copy of database "%.*ls" has not been rolled forward to a point in time that is encompassed in the local copy of the database log.

1414

16

No

The database is being closed before database mirroring is fully initialized. The ALTER DATABASE command failed.

1416

16

No

Database "%.*ls" is not configured for database mirroring.

1418

16

No

The server network address "%.*ls" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.

1420

16

No

Database mirroring was unable to obtain the network hostname. Operating system error %ls encountered. Verify the network configuration.

1422

16

No

The mirror server instance is not caught up to the recent changes to database "%.*ls". Unable to fail over.

1424

16

No

The remote server instance has a more recent value for the property '%.*ls'. Property value not changed.

1426

16

No

To issue ALTER DATABASE SET WITNESS, all three server instances must be interconnected, and the mirror database must be caught up. When these conditions are met, reissue the command.

1428

16

No

The request is refused because the responding server instance is not in a state to service the request.

1430

16

No

Database '%.*ls' is in an unstable state for removing database mirroring, so recovery may fail. Verify the data after recovery.

1432

10

No

Database mirroring is attempting to repair physical page %S_PGID in database "%.*ls" by requesting a copy from the partner.

1434

16

Yes

Invalid or unexpected database mirroring %ls message of type %d was received from server %ls, database %.*ls.

1436

16

No

The Service Broker ID for the remote copy of database "%.*ls" does not match the ID on the principal server.

1438

16

Yes

The server instance %ls rejected configure request; read its error log file for more information. The reason %u, and state %u, can be of use for diagnostics by Microsoft. This is a transient error hence retrying the request is likely to succeed. Correct the cause if any and retry.

1440

10

Yes

Database mirroring is active with database '%.*ls' as the principal copy. This is an informational message only. No user action is required.

1442

10

Yes

Database mirroring is inactive for database '%.*ls'. This is an informational message only. No user action is required.

1444

10

Yes

Bypassing recovery for database '%ls' because it is marked as a mirror database, which cannot be recovered. This is an informational message only. No user action is required.

1446

10

No

The "%.*ls" server instance is already acting as the witness.

1448

16

No

The remote copy of database "%.*ls" does not exist. Check the database name and reissue the command.

1450

16

No

The ALTER DATABASE command failed because the worker thread cannot be created.

1452

16

No

The partner server instance name must be distinct from the server instance that manages the database. The ALTER DATABASE SET PARTNER command failed.

1454

17

Yes

Database mirroring will be suspended. Server instance '%.*ls' encountered error %d, state %d, severity %d when it was acting as a mirroring partner for database '%.*ls'. The database mirroring partners might try to recover automatically from the error and resume the mirroring session. For more information, view the error log for additional error messages.

1456

16

Yes

The ALTER DATABASE command could not be sent to the remote server instance '%.*ls'. The database mirroring configuration was not changed. Verify that the server is connected, and try again.

1458

17

Yes

The principal copy of the '%.*ls' database encountered error %d, status %d, severity %d while sending page %S_PGID to the mirror. Database mirroring has been suspended. Try to resolve the error condition, and resume mirroring.

1460

16

No

The database "%.*ls" is already configured for database mirroring on the remote server. Drop database mirroring on the remote server to establish a new partner.

1462

16

No

Database mirroring is disabled due to a failed redo operation. Unable to resume.

1464

16

No

Database mirroring cannot be enabled for the remote copy of database "%.*ls" because the database is not in a recovering state. The remote database must be restored using WITH NORECOVERY.

1466

16

No

Database mirroring cannot be enabled because the "%.*ls" database is read-only on one of the partners.

1468

16

No

The operation cannot be performed on database "%.*ls" because it is involved in a database mirroring session.

1470

16

No

The alter database for this partner config values may only be initiated on the current principal server for database "%.*ls".

1472

16

No

The database mirroring connection terminated. Communications error sending message for database "%.*ls".

1474

16

No

Database mirroring connection error %d '%.*ls' for '%.*ls'.

1476

16

No

Database mirroring timeout value %d exceeds the maximum value 32767.

1478

16

No

The mirror database, "%.*ls", has insufficient transaction log data to preserve the log backup chain of the principal database. This may happen if a log backup from the principal database has not been taken or has not been restored on the mirror database.

1480

10

No

The mirrored database "%.*ls" is changing roles from "%ls" to "%ls" due to %S_MSG.

1485

10

No

Database mirroring has been enabled on this instance of SQL Server.

1487

10

No

Database mirroring is starting %d parallel redo thread(s) with database '%.*ls' as the mirror copy. This is an informational message only. No user action is required.

1489

10

No

Database Mirroring is disabled on this server due to error %d. Check the errorlog and configuration for more information.

1501

20

Yes

Sort failure. Contact Technical Support.

1509

20

Yes

Row comparison failed during sort because of an unknown data type on a key column. Metadata might be corrupt. Contact Technical Support.

1511

20

Yes

Sort cannot be reconciled with transaction log.

1523

20

Yes

Sort failure. The incorrect extent could not be deallocated. Contact Technical Support.

1533

20

Yes

Cannot share extent %S_PGID. The correct extents could not be identified. Retry the transaction.

1535

20

Yes

Cannot share extent %S_PGID. Shared extent directory is full. Retry the transaction. If the problem persists, contact Technical Support.

1538

20

Yes

Cannot insert a row into a sort when the sort is not in row input phase.

1541

16

No

Sort failure. A defective CLR type comparison function is suspected.

1543

10

Yes

Operating system error '%ls' resulted from attempt to read the following: sort run page %S_PGID, in file '%ls', in database with ID %d. Sort is retrying the read.

1702

16

No

CREATE TABLE failed because column '%.*ls' in table '%.*ls' exceeds the maximum of %d columns.

1707

16

No

Cannot specify TEXTIMAGE_ON filegroup for a partitioned table.

1709

16

No

Cannot use TEXTIMAGE_ON when a table has no text, ntext, image, varchar(max), nvarchar(max), varbinary(max), xml or large CLR type columns.

1711

16

No

Cannot define PRIMARY KEY constraint on column '%.*ls' in table '%.*ls'. The computed column has to be persisted and not nullable.

1713

16

No

Cannot execute %ls on/using table '%.*ls' since the table is the target table or part of cascading actions of a currently executing trigger.

1715

16

No

Foreign key '%.*ls' creation failed. Only NO ACTION referential update action is allowed for referencing computed column '%.*ls'.

1717

16

No

FILESTREAM_ON cannot be specified together with a partition scheme in the ON clause.

1719

16

No

FILESTREAM data cannot be placed on an empty filegroup.

1721

16

No

Altering table '%.*ls' failed because the row size using vardecimal storage format exceeds the maximum allowed table row size of %d bytes.

1723

16

No

Cannot %S_MSG %S_MSG '%.*ls' since a partition scheme was specified for FILESTREAM data but not for the table.

1725

16

No

Cannot add FILESTREAM column to %S_MSG '%.*ls' because an INSTEAD OF trigger exists on the %S_MSG.

1727

16

No

Cannot create non-clustered index '%.*ls' on table '%.*ls' with the FILESTREAM_ON clause.

1729

16

No

Cannot create table '%.*ls' because the partitioning column '%.*ls' uses a FILESTREAM column.

1731

16

No

Cannot create the sparse column '%.*ls' in the table '%.*ls' because an option or data type specified is not valid. A sparse column must be nullable and cannot have the ROWGUIDCOL, IDENTITY, or FILESTREAM properties. A sparse column cannot be of the following data types: text, ntext, image, geometry, geography, or user-defined type.

1733

16

No

Cannot create the sparse column set '%.*ls' in the table '%.*ls' because a sparse column set must be a nullable xml column. Modify the column definition to allow null values.

1736

16

No

The column '%.*ls' in the table '%.*ls' cannot be referenced in a CHECK constraint or computed column definition because the column is a sparse column set. A sparse column set cannot be referenced in a a CHECK constraint or computed column definition.

1750

10

No

Could not create constraint. See previous errors.

1753

16

No

Column '%.*ls.%.*ls' is not the same length or scale as referencing column '%.*ls.%.*ls' in foreign key '%.*ls'. Columns participating in a foreign key relationship must be defined with the same length and scale.

1755

16

No

Defaults cannot be created on columns of data type timestamp. Table '%.*ls', column '%.*ls'.

1757

16

No

Column '%.*ls.%.*ls' is not of same collation as referencing column '%.*ls.%.*ls' in foreign key '%.*ls'.

1759

16

No

Computed column '%.*ls' in table '%.*ls' is not allowed to be used in another computed-column definition.

1761

16

No

Cannot create the foreign key "%.*ls" with the SET NULL referential action, because one or more referencing columns are not nullable.

1763

16

No

Cross-database foreign key references are not supported. Foreign key '%.*ls'.

1765

16

No

Foreign key '%.*ls' creation failed. Only NO ACTION and CASCADE referential delete actions are allowed for referencing computed column '%.*ls'.

1767

16

No

Foreign key '%.*ls' references invalid table '%.*ls'.

1769

16

No

Foreign key '%.*ls' references invalid column '%.*ls' in referencing table '%.*ls'.

1771

16

No

Cannot create foreign key '%.*ls' because it references object '%.*ls' whose clustered index '%.*ls' is disabled.

1773

16

No

Foreign key '%.*ls' has implicit reference to object '%.*ls' which does not have a primary key defined on it.

1775

16

No

Cannot create foreign key '%.*ls' because it references object '%.*ls' whose PRIMARY KEY index '%.*ls' is disabled.

1778

16

No

Column '%.*ls.%.*ls' is not the same data type as referencing column '%.*ls.%.*ls' in foreign key '%.*ls'.

1781

16

No

Column already has a DEFAULT bound to it.

1785

16

No

Introducing FOREIGN KEY constraint '%.*ls' on table '%.*ls' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.

1787

16

No

Cannot define foreign key constraint '%.*ls' with cascaded DELETE or UPDATE on table '%.*ls' because the table has an INSTEAD OF DELETE or UPDATE TRIGGER defined on it.

1789

16

No

Cannot use CHECKSUM(*) in a computed column definition.

1791

16

No

A DEFAULT constraint cannot be created on the column '%.*ls' in the table '%.*ls' because the column is a sparse column or sparse column set. Sparse columns or sparse column sets cannot have a DEFAULT constraint.

1802

16

No

CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

1806

16

No

CREATE DATABASE failed. The default collation of database '%.*ls' cannot be set to '%.*ls'.

1810

16

No

The model database must be updatable before a new database can be created.

1813

16

No

Could not open new database '%.*ls'. CREATE DATABASE is aborted.

1815

16

No

The %ls property cannot be used with database snapshot files.

1817

16

No

Only the owner of database "%.*s" or the system administrator can create a database snapshot on it.

1819

10

No

Could not create default log file because the name was too long.

1822

16

No

The database must be online to have a database snapshot.

1824

16

No

Cannot attach a database that was being restored.

1826

16

No

User-defined filegroups are not allowed on "%ls".

1828

16

No

The logical file name "%.*ls" is already in use. Choose a different name.

1830

16

No

The files '%.*ls' and '%.*ls' are both primary files. A database can only have one primary file.

1832

20

No

Cannot attach the file '%.*ls' as database '%.*ls'.%.*ls

1834

16

No

The file '%ls' cannot be overwritten. It is being used by database '%.*ls'.

1836

10

No

Cannot create the default data files because the name that was supplied is too long.

1838

10

No

Offline database file(s) have been overwritten while being reverted to online state from a database snapshot. The reverted file might contain invalid pages. Please run database consistency checks to assess the data integrity.

1842

16

No

The file size, max size cannot be greater than 2147483647 in units of a page size. The file growth cannot be greater than 2147483647 in units of both page size and percentage.

1844

16

No

%ls is not supported on %ls.

1846

16

No

Cannot find SQL Volume Shadow Copy (VSS) Writer component for database '%ls' while creating auto-recovered VSS snapshot for online DBCC check.

1848

16

No

Volume Shadow Copy Service (VSS) failed to create an auto-recovered snapshot of database '%ls' for online DBCC check.

1901

16

No

Cannot create index or statistics '%.*ls' on view '%.*ls' because key column '%.*ls' is imprecise, computed and not persisted. Consider removing reference to column in view index or statistics key or changing column to be precise. If column is computed in base table consider marking it PERSISTED there.

1904

16

No

The %S_MSG '%.*ls' on table '%.*ls' has %d column names in %S_MSG key list. The maximum limit for index or statistics key column list is %d.

1908

16

No

Column '%.*ls' is partitioning column of the index '%.*ls'. Partition columns for a unique index must be a subset of the index key.

1910

16

No

Could not create %S_MSG '%.*ls' because it exceeds the maximum of %d allowed per table or view.

1912

16

No

Could not proceed with index DDL operation on %S_MSG '%.*ls' because it conflicts with another concurrent operation that is already in progress on the object. The concurrent operation could be an online index operation on the same object or another concurrent operation that moves index pages like DBCC SHRINKFILE.

1914

16

No

Index cannot be created on object '%.*ls' because the object is not a user table or view.

1916

16

No

CREATE INDEX options %ls and %ls are mutually exclusive.

1919

16

No

Column '%.*ls' in table '%.*ls' is of a type that is invalid for use as a key column in an index.

1922

16

No

Filegroup '%.*ls' has no files assigned to it. Tables, indexes, and large object columns cannot be created on this filegroup. Use ALTER DATABASE to add one or more files to the filegroup.

1925

16

No

Cannot convert a clustered index to a nonclustered index by using the DROP_EXISTING option. To change the index type from clustered to nonclustered, delete the clustered index, and then create a nonclustered index by using two separate statements.

1929

16

No

Statistics cannot be created on object '%.*ls' because the object is not a user table or view.

1931

16

No

The SQL statement cannot be executed because filegroup '%.*ls' is offline. Use the sys.database_files or sys.master_files catalog view to determine the state of the files in this filegroup and then restore the offline file(s) from backup.

1935

16

No

Cannot create index. Object '%.*ls' was created with the following SET options off: '%.*ls'.

1938

16

No

Index cannot be created on view '%.*ls' because the underlying object '%.*ls' has a different owner.

1940

16

No

Cannot create %S_MSG on view '%.*ls'. It does not have a unique clustered index.

1942

16

No

Cannot create %S_MSG on view '%.*ls'. It contains text, ntext, image, FILESTREAM or xml columns.

1945

10

No

Warning! The maximum key length is %d bytes. The index '%.*ls' has maximum length of %d bytes. For some combination of large values, the insert/update operation will fail.

1947

16

No

Cannot create %S_MSG on view "%.*ls". The view contains a self join on "%.*ls".

1956

16

No

Cannot create %S_MSG on the '%.*ls' view because it uses the nondeterministic user-defined function '%.*ls'. Remove the reference to the function, or make it deterministic.

1959

16

No

Cannot create an index on a view or computed column because the compatibility level of this database is less than 80. Use sp_dbcmptlevel to raise the compatibility level of the database.

1962

16

No

Cannot create %S_MSG on view '%.*ls' because column '%.*ls' that is referenced by the view in the WHERE or GROUP BY clause is imprecise. Consider eliminating the column from the view, or altering the column to be precise.

1964

16

No

Cannot create %S_MSG on view "%.*ls". The view contains an imprecise constant.

1966

16

No

Cannot create %S_MSG on view '%.*ls'. The view contains an imprecise aggregate operator.

1968

16

No

Cannot convert a nonclustered index to a clustered index online using DROP_EXISTING option.

1970

10

No

Warning: Online index operation on table '%.*ls' will proceed but concurrent access to the table may be limited due to residual lock on the table from a previous operation in the same transaction.

1972

16

No

Cannot disable clustered index '%.*ls' on table '%.*ls'. Permission denied to alter the referencing view '%.*ls' while disabling its clustered index.

1974

16

No

Cannot perform the specified operation on %S_MSG '%.*ls' because its clustered index '%.*ls' is disabled.

1976

16

No

Cannot create index or statistics '%.*ls' on view '%.*ls' because cannot verify key column '%.*ls' is precise and deterministic. Consider removing column from index or statistics key, marking column persisted in base table if it is computed, or using non-CLR-derived column in key.

1978

16

No

Column '%.*ls' in table '%.*ls' is of a type that is invalid for use as a key column in an index or statistics.

1980

16

No

Index cannot be created on computed column '%.*ls' of table '%.*ls' because the underlying object '%.*ls' has a different owner.

1982

16

No

Cannot create %S_MSG on view '%.*ls' because the view references non-deterministic or imprecise member function '%.*ls' on CLR type '%.*ls'. Consider removing reference to the function or altering the function to behave in a deterministic way. Do not declare a CLR function that behaves non-deterministically to have IsDeterministic=true, because that can lead to index corruption. See Books Online for details.

1984

16

No

Index '%.*ls' cannot be created or rebuilt. The specified row length for this index using the vardecimal storage format exceeds the maximum allowed length of '%d' bytes.

1986

10

No

Cannot replace non-hypothetical index '%.*ls' with a hypothetical index using the DROP_EXISTING option.

1988

16

No

Cannot rebuild clustered index '%.*ls' online because it is disabled.

1990

16

No

Cannot define an index on a view with ignore_dup_key index option. Remove ignore_dup_key option and verify that view definition does not allow duplicates, or do not index view.

1992

10

No

Warning: Foreign key '%.*ls' on table '%.*ls' referencing table '%.*ls' was disabled as a result of disabling the index '%.*ls'.

1994

16

No

Cannot create or update statistics on view "%.*ls" because both FULLSCAN and NORECOMPUTE options are required.

1996

16

No

Could not create index enforcing primary key constraint '%.*ls' using DROP_EXISTING option because table has an XML or spatial index. Drop the XML or spatial index, create the primary key contstraint, and recreate the XML or spatial index.

1998

10

No

Warning: Clustered index '%.*ls' on view '%.*ls' referencing table '%.*ls' was disabled as a result of disabling the index '%.*ls'.