Errors 18000 - 18999

18002

20

Yes

Exception happened when running extended stored procedure '%.*ls' in the library '%.*ls'. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx.

18053

16

No

Error: %d, Severity: %d, State: %d. (Params:%ls). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.

18055

20

Yes

Exception %d, %d occurred when the server tried to reset connection %d. Because the server cannot recover from the failure to reset the connection, the connection has been dropped. Please contact Microsoft technical support.

18057

20

Yes

Error: Failed to set up execution context.

18059

16

Yes

The connection has been dropped because the principal that opened it subsequently assumed a new security context, and then tried to reset the connection under its impersonated security context. This scenario is not supported. See "Impersonation Overview" in Books Online.

18061

20

Yes

The client was unable to join a session with SPID %d. This error may have been caused by an earlier operation failing or a change in permissions since the session was established. Check the error logs for failed operations immediately before this error message.

18113

10

Yes

SQL Server shutdown after verifying system indexes.

18204

16

Yes

%s: Backup device '%s' failed to %s. Operating system error %s.

18225

10

Yes

Tape '%s' (family ID %d, sequence %d, media_set_guid %s) is mounted on tape drive '%s'. This is an informational message only. No user action required

18227

10

Yes

Unnamed tape (family ID %d, sequence %d, media_set_guid %s) is mounted on tape drive '%s'. This is an informational message only. No user action required.

18257

10

Yes

%s: Device or media does not support %s. To access this feature, use a different device or media.

18265

10

Yes

Log was backed up. Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required.

18267

10

Yes

Database was restored: Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). Informational message. No user action required.

18269

10

Yes

Database file was restored. Database: %s, creation date(time): %s(%s), file list: (%s), number of dump devices: %d, device information: (%s). This is an informational message. No user action is required.

18271

10

Yes

Database changes were restored. Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message. No user action is required.

18273

16

Yes

Could not clear '%s' bitmap in database '%s' because of error %d. As a result, the differential or bulk-logged bitmap overstates the amount of change that will occur with the next differential or log backup. This discrepancy might slow down later differential or log backup operations and cause the backup sets to be larger than necessary. Typically, the cause of this error is insufficient resources. Investigate the failure and resolve the cause. If the error occurred on a data backup, consider taking a data backup to create a new base for future differential backups.

18275

10

Yes

Unnamed tape was dismounted from drive '%s'. This is an informational message. No user action is required.

18277

10

Yes

Database file changes were restored. Database: %s, creation date(time): %s(%s), file list: (%s), number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required.

18301

10

No

Reason: Could not find a login matching the name provided.

18303

10

No

Reason: Failed to unprotect memory containing sensitive information.

18305

10

No

Reason: Attempting to use an NT account name with SQL Server Authentication.

18307

10

No

Reason: Password did not match that for the login provided.

18309

10

No

Reason: Password validation failed with an infrastructure error. Check for previous errors.

18311

10

No

Reason: Login-based server access validation failed with an infrastructure error. Check for previous errors.

18313

10

No

Reason: Interface for login to SQL Server is not supported.

18315

10

No

Reason: Failed to open the database for this login.

18317

10

No

Reason: The user must change the password, but it cannot be changed with the current connection settings.

18319

10

No

Reason: Simulation of a failure while redoing login on the connection.

18321

10

No

Reason: Reinitialization of security context failed while revalidating the login on the connection.

18323

10

No

Reason: Failed to open the specified database while revalidating the login on the connection.

18325

10

No

Reason: Failed to attach the specified database while revalidating the login on the connection.

18327

10

No

Reason: Failed to determine the language and date format while revalidating the login on the connection.

18329

10

No

Reason: Simulation of a failure while reauthenticating login.

18331

10

No

Reason: Failed to reinitialize security context while reauthenticating login.

18333

10

No

Reason: Failed to open the specified database while reauthenticating login.

18335

10

No

Reason: Could not retrieve database name or map database to an item.

18337

10

No

Reason: Failed to open the explicitly specified database.

18339

10

No

Reason: Failed to open the database specified in the login properties.

18341

10

No

. Reason: Current collation did not match the database's collation during connection reset.

18343

10

No

Reason: Failed to retrieve database name or map database to an item while revalidating the login on the connection.

18345

10

No

Reason: Failed to open the database configured in the login object while revalidating the login on the connection.

18347

10

No

Reason: Failed to open the database specified in the login properties while revalidating the login on the connection.

18349

10

No

Reason: Current collation did not match the database's collation during connection reset.

18351

10

No

Reason: Client impersonation failed.

18353

10

No

Reason: Failed to get security token information.

18355

10

No

Reason: Failed attempted retry of a process token validation.

18357

10

No

Reason: An attempt to login using SQL Server Authentication failed. Server is configured for Windows Authentication only.

18401

14

Yes

Login failed for user '%.*ls'. Reason: Server is in script upgrade mode. Only administrator can connect at this time.%.*ls

18452

14

Yes

Login failed. The login is from an untrusted domain and cannot be used with Windows Authentication.%.*ls

18454

10

Yes

Login succeeded for user '%.*ls'. Connection made using SQL Server Authentication.%.*ls

18456

14

Yes

Login failed for user '%.*ls'.%.*ls%.*ls

18459

14

Yes

Login failed. The workstation licensing limit for SQL Server access has already been reached.%.*ls

18461

14

Yes

Login failed for user '%.*ls'. Reason: Server is in single user mode. Only one administrator can connect at this time.%.*ls

18463

14

No

The login failed for user "%.*ls". The password change failed. The password cannot be used at this time. %.*ls

18465

14

No

Login failed for user '%.*ls'. Reason: Password change failed. The password does not meet Windows policy requirements because it is too long.%.*ls

18467

14

No

The login failed for user "%.*ls". The password change failed. The password does not meet the requirements of the password filter DLL. %.*ls

18469

10

No

[CLIENT: %.*hs]

18471

14

No

The login failed for user "%.*ls". The password change failed. The user does not have permission to change the password. %.*ls

18483

16

Yes

Could not connect to server '%.*ls' because '%.*ls' is not defined as a remote login at the server. Verify that you have specified the correct login name. %.*ls.

18486

14

Yes

Login failed for user '%.*ls' because the account is currently locked out. The system administrator can unlock it. %.*ls

18488

14

Yes

Login failed for user '%.*ls'. Reason: The password of the account must be changed.%.*ls

18491

16

Yes

SQL Server could not start because of an invalid serial number. The serial number information retrieved at startup appears invalid. To proceed, reinstall SQL Server.

18493

16

Yes

The user instance login flag is not supported on this version of SQL Server. The connection will be closed.%.*ls

18495

16

Yes

The user instance login flag cannot be used along with an attach database file name. The connection will be closed.%.*ls

18596

16

No

%.*ls cannot start because your system is low on memory.

18598

16

No

%.*ls could not find the default instance (%.*ls) - error %d. Please specify the name of an existing instance on the invocation of sqlservr.exe.\n\nIf you believe that your installation is corrupt or has been tampered with, uninstall then re-run setup to correct this problem.

18750

16

No

%ls: The parameter '%ls' is not valid.

18752

16

No

Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time. If you executed a log-related procedure, drop the connection over which the procedure was executed or execute sp_replflush over that connection before starting the Log Reader Agent or executing another log-related procedure.

18756

16

No

Could not retrieve replication information for table %d. Verify that the table has a primary key, and then rerun the Log Reader Agent.

18760

16

No

Invalid %ls statement for article %d. Verify that the stored procedures that propagate changes to Subscribers use the appropriate call syntax, and then rerun the Log Reader Agent. Use sp_helparticle and sp_changearticle to view and change the call syntax.

18762

16

No

Invalid begin LSN {%08lx:%08lx:%04lx} for commit record {%08lx:%08lx:%04lx}. Check DBTABLE.

18764

16

No

Execution of filter stored procedure %d failed. See the SQL Server errorlog for more information.

18766

16

No

The replbeginlsn field in the DBTABLE is invalid.

18768

16

No

The specified LSN {%08lx:%08lx:%04lx} for repldone log scan occurs before the current start of replication in the log {%08lx:%08lx:%04lx}.

18770

16

No

The specified LSN {%08lx:%08lx:%04lx} for repldone log scan is not present in the transaction log.

18772

16

No

Invalid server data type (%d) specified in repl type lookup.

18774

16

No

The stored procedure %s must be executed within a transaction.

18776

16

No

An error occurred while waiting on the article cache access event.

18778

16

No

%s: Error opening Microsoft Message Queue %s

18781

16

No

The value specified for the @backupdevicetype parameter is not valid. The value must be 'logical', 'disk', or 'tape'.

18783

16

No

The subscription setup script path has been truncated, because the snapshot folder directory path is too long. Reconfigure the Distributor to use a shorter path for this Publisher, and then retry the operation.

18786

16

No

The specified publication does not allow subscriptions to be initialized from a backup. To allow initialization from a backup, use sp_changepublication: set 'allow_initialize_from_backup' to 'true'.

18790

16

No

Cannot enable the option to initialize a subscription from a backup. This is not supported for non-SQL Server Publishers; it is only supported for transactional publications from SQL Server Publishers.

18796

16

No

The valid new types of a log based table article are 'logbased', 'logbased manualfilter', 'logbased manualview', and 'logbased manualboth' only.

18801

16

No

Unable to allocate memory for replication schema version node.

18803

16

No

The topic %.*ls is not a supported help topic. To see the list of supported topics, execute the stored procedure sp_replhelp N'helptopics'.

18805

16

No

The Log-Scan Process failed to construct a replicated command from log sequence number (LSN) {%08lx:%08lx:%04lx}. Back up the publication database and contact Customer Support Services.

18807

16

No

Cannot find an object ID for the replication system table '%s'. Verify that the system table exists and is accessible by querying it directly. If it does exist, stop and restart the Log Reader Agent; if it does not exist, drop and reconfigure replication.

18809

16

No

END_UPDATE log record {%08lx:%08lx:%04lx} encountered without matching BEGIN_UPDATE.

18811

16

No

Invalid %s log record.

18815

16

No

Expecting %I64d bytes of data, but only %I64d were found in the transaction log. For more information, contact Customer Support Services.

18818

16

No

Failed to scan to log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services.

18821

16

No

The rowset does not contain any column with offset %d. Back up the publication database and contact Customer Support Services.

18826

16

No

Failed to delete rows from the systranschemas table. HRESULT = '0x%x'. The rows will be deleted the next time replication executes the stored procedure sp_replcmds.

18828

16

No

Invalid filter procedure definition.

18830

16

No

A bounded update was logged within the range of another bounded update within the same transaction. First BEGIN_UPDATE {%08lx:%08lx:%04lx}, current BEGIN_UPDATE {%08lx:%08lx:%04lx}. Contact Customer Support Services.

18834

16

No

An unexpected Text Information Begin (TIB) log record was encountered while processing the TIB for offset %ld. Last TIB processed: (textInfoFlags 0x%x, coloffset %ld, newSize %I64d, oldSize %I64d). Contact Customer Support Services.

18836

16

No

%s, ti: {RowsetId %I64d, {TextTimeStamp %I64d, {RowId {PageId %ld, FileId %u}, SlotId %d}}, coloffset %ld, textInfoFlags 0x%x, textSize %I64d, offset %I64d, oldSize %I64d, newSize %I64d}.

18838

16

No

The Log Reader Agent encountered a NULL command that is not valid. Restart the agent if it has stopped. If the problem persists, reinitialize all subscriptions to the publication.

18842

16

No

Failed to retrieve the oldest active log sequence number (LSN) from a commit record. Stop and restart SQL Server and the Log Reader Agent. If the problem persists, reinitialize all subscriptions to the publication.

18844

16

No

Invalid compensation range: begin {%08lx:%08lx:%04lx}, end {%08lx:%08lx:%04lx}. Reinitialize all subscriptions to the publication.

18846

16

No

Possible inconsistent state in the distribution database: dist_backup_lsn {%08lx:%08lx:%04lx}, dist_last_lsn {%08lx:%08lx:%04lx}. Execute "sp_repldone NULL, NULL, 0, 0, 1", and then execute sp_replflush. Reinitialize all subscriptions to the publication.

18849

16

No

Failed to evaluate the filter procedure or computed column. Cannot find the column offset information for column ID %d, rowsetId %I64d. Stop and restart the Log Reader Agent. If the problem persists, back up the publication database and then contact Customer Support Services.

18851

16

No

Failed to %s the replication context for TxF: {%I64d, %.*ls, %ld, %ld, %I64d, %I64d, %I64d, %I64d, {%08lx:%08lx:%04lx}, %I64d, %.*ls, {%08lx:%08lx:%04lx}}. If the problem persists, contact product support.

18853

10

No

Replication is skipping schema version logging because the systranschemas table is not present in database '%d'. This is an informational message only. No user action is required.

18855

11

No

Can not rename the database name because it is published or it is a distribution database used by replication.

18857

16

No

The subscription to this publication is not active yet. No user action is required.