SQL Server Error Messages 18001 to 19000

In this post, we’ll list out the SQL Server Error Messages from the error codes 18001 to 19000 and references to the detailed post to know more about the errors and how to fix them when using SQL Server as database in your application.

SQL Server Error Messages 18001 to 19000

ErrorCodeSeverityErrorMessage
1800220Exception happened when running extended stored procedure ‘%.*ls’ in the library ‘%.*ls’. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx. To generate a minidump, create an xevent session using the dump routine event with the create dump action.
1805216Error: %d, Severity: %d, State: %d.
1805316Error: %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.
1805416Error %d, severity %d, state %d was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage.
1805520Exception %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.
1805620The client was unable to reuse a session with SPID %d, which had been reset for connection pooling. The failure ID is %d. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
1805720Error: Failed to set up execution context.
1805817Failed to load format string for error %d, language id %d. Operating system error: %s. Check that the resource file matches SQL Server executable, and resource file in localized directory matches the file under English directory. Also check memory usage.
1805916The 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.
1806016Failed to format string for error %d, language id %d.  This may be caused by low memory in server, or error happening while formatting the message.
1806120The 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.
1810010Process ID %d was killed by hostname %.*ls, host process ID %d.
1811310SQL Server shutdown after verifying system indexes.
1812410The default collation was successfully changed.
1812610Engine failed to load configuration for error detection, default configuration was applied.
1812710Engine is marking DB %d [%.*ls] as SUSPECT in cloud DB mode due to error %d, severity %d, state %d.
1820416%s: Backup device ‘%s’ failed to %s. Operating system error %s.
1821016%s: %s failure on backup device ‘%s’. Operating system error %s.
1822510Tape ‘%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
1822610Tape mount is being requested on drive ‘%s’. Expected volume has (Family ID %d, sequence %d).
1822710Unnamed 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.
1822810Tape mount request on drive ‘%s’ is cancelled. This is an informational message only. No user action is required.
1825710%s: Device or media does not support %s. To access this feature, use a different device or media.
1826410Database backed up. Database: %s, creation date(time): %s(%s), pages dumped: %I64d, 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.
1826510Log 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.
1826610Database file was backed up. Database: %s, creation date(time): %s(%s), file list: (%s), pages dumped: %I64d, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required.
1826710Database 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.
1826810Log was 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.
1826910Database 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.
1827010Database differential changes were backed up. Database: %s, creation date(time): %s(%s), pages dumped: %I64d, first LSN: %s, last LSN: %s, full backup LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message. No user action is required.
1827110Database 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.
1827216During restore restart, an I/O error occurred on checkpoint file ‘%s’ (operating system error %s). The statement is proceeding but cannot be restarted. Ensure that a valid storage location exists for the checkpoint file.
1827316Could 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.
1827410Tape ‘%s’ was dismounted from drive ‘%s’. This is an informational message. No user action is required.
1827510Unnamed tape was dismounted from drive ‘%s’. This is an informational message. No user action is required.
1827610Database file differential changes were backed up. Database: %s, creation date(time): %s(%s), file list: (%s), pages dumped: %I64d, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required.
1827710Database 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.
1827916During a RESTORE operation, an I/O error occurred on checkpoint file ‘%s’ (operating system error %s).  Ensure that a valid storage location exists for the checkpoint file and try the operation again.
1828016The file %s is being removed from the database, but is not being removed from the filesystem because file snapshots are still associated with the file.
1830010 Reason: Infrastructure error occurred. Check for previous errors.
1830110 Reason: Could not find a login matching the name provided.
1830210 Reason: Failed to unprotect memory containing sensitive information.
1830310 Reason: Failed to unprotect memory containing sensitive information.
1830410 Reason: Could not find a login matching the name provided.
1830510 Reason: Attempting to use an NT account name with SQL Server Authentication.
1830610 Reason: An error occurred while evaluating the password.
1830710 Reason: Password did not match that for the login provided.
1830810 Reason: Invalid password provided.
1830910 Reason: Password validation failed with an infrastructure error. Check for previous errors.
1831010 Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors.
1831110 Reason: Login-based server access validation failed with an infrastructure error. Check for previous errors.
1831210 Reason: SQL Server service is paused. No new connections can be accepted at this time.
1831310 Reason: Interface for login to SQL Server is not supported.
1831410 Reason: Failed to open the specified database.
1831510 Reason: Failed to open the database for this login.
1831610 Reason: Unable to determine the initial language and date format.
1831710 Reason: The user must change the password, but it cannot be changed with the current connection settings.
1831810 Reason: Failed to unprotect memory containing sensitive information.
1831910 Reason: Simulation of a failure while redoing login on the connection.
1832010 Reason: SQL Server service is paused. Login could not be revalidated at this time.
1832110 Reason: Reinitialization of security context failed while revalidating the login on the connection.
1832210 Reason: Access to server validation failed while revalidating the login on the connection.
1832310 Reason: Failed to open the specified database while revalidating the login on the connection.
1832410 Reason: Failed to create the user instance while revalidating the login on the connection.
1832510 Reason: Failed to attach the specified database while revalidating the login on the connection.
1832610 Reason: Failed to open the database for this login while revalidating the login on the connection.
1832710 Reason: Failed to determine the language and date format while revalidating the login on the connection.
1832810 Reason: An exception was raised while revalidating the login on the connection. Check for previous errors.
1832910 Reason: Simulation of a failure while reauthenticating login.
1833010 Reason: SQL Server service is paused. Login cannot be reauthenticated at this time.
1833110 Reason: Failed to reinitialize security context while reauthenticating login.
1833210 Reason: Failed to access server for validation while reauthenticating login.
1833310 Reason: Failed to open the specified database while reauthenticating login.
1833410 Reason: An error occurred while reauthenticating login. Check for previous errors.
1833510 Reason: Could not retrieve database name or map database to an item.
1833610 Reason: Cannot connect with a login that does not specify a share.
1833710 Reason: Failed to open the explicitly specified database ‘%.*ls’.
1833810 Reason: Unable to determine the database name from the specified file name.
1833910 Reason: Failed to open the database ‘%.*ls’ specified in the login properties.
1834010 Reason: Failed to store database name and collation. Check for previous errors.
1834110. Reason: Current collation did not match the database’s collation during connection reset.
1834210 Reason: Failed to send an environment change notification to a log shipping partner node.
1834310 Reason: Failed to retrieve database name or map database to an item while revalidating the login on the connection.
1834410 Reason: Connection with a login which does not specify a share is not allowed while revalidating the login on the connection.
1834510 Reason: Failed to open the database ‘%.*ls’ configured in the login object while revalidating the login on the connection.
1834610 Reason: Failed to determine database name from a given file name while revalidating the login on the connection.
1834710 Reason: Failed to open the database ‘%.*ls’ specified in the login properties while revalidating the login on the connection.
1834810 Reason: Failed to store database name and collation while revalidating the login on the connection. Check for previous errors.
1834910 Reason: Current collation did not match the database’s collation during connection reset.
1835010 Reason: Failed to send an environment change notification to a log shipping partner node while revalidating the login.
1835110 Reason: Client impersonation failed.
1835210 Reason: Failed to revert impersonation to self.
1835310 Reason: Failed to get security token information.
1835410 Reason: Failed to duplicate of security token.
1835510 Reason: Failed attempted retry of a process token validation.
1835610 Reason: An error occurred while attempting to change password.
1835710 Reason: An attempt to login using SQL authentication failed. Server is configured for Integrated authentication only.
1835810 Reason: Could not find a user matching the name provided. [Database: ‘%.*ls’]
1835910 Reason: Failed to unprotect memory containing sensitive information. [Database: ‘%.*ls’]
1836010 Reason: Failed to unprotect memory containing sensitive information. [Database: ‘%.*ls’]
1836110 Reason: Could not find a user matching the name provided. [Database: ‘%.*ls’]
1836210 Reason: Attempting to use an invalid user type with SQL Server Authentication. [Database: ‘%.*ls’]
1836310 Reason: An error occurred while evaluating the password. [Database: ‘%.*ls’]
1836410 Reason: Password did not match that for the user provided. [Database: ‘%.*ls’]
1836510 Reason: Invalid password provided. [Database: ‘%.*ls’]
1836610 Reason: Password validation failed with an infrastructure error. Check for previous errors. [Database: ‘%.*ls’]
1836710 Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [Database: ‘%.*ls’]
1836810 Reason: Login-based server access validation failed with an infrastructure error. Check for previous errors. [Database: ‘%.*ls’]
1836910attach
1837010restore
1837110Reason: The password hash is from an unsupported version of SQL Server. Reset the password or recreate the login.
1837210 Reason: An error occurred while obtaining a routing environment change notification.
1837310Reason: Database could not accept user connections at this time.
1837410 Reason: An error occurred while recovering the Identity_Insert session state requested by the recovery login.
1837510 Reason: Failed to open the database ‘%.*ls’ configured in the session recovery object while recovering the connection.
1837610 Reason: Failed to open the database ‘%.*ls’ configured in the session recovery object while revalidating the login on the recovered connection.
1837710 Reason: The current collation did not match the database’s collation as indicated by session recovery object in login.
1837810 Reason: An error occurred while recovering the @@identity session state requested by the recovery login.
1837910Reason: The account is currently locked out. The system administrator can unlock it.
1838010Reason: The certificate is invalid or expired.
1838110Reason: The logical master database was not found.
1838210Reason: Unable to retrieve client IP Address.
1838310Reason: The client was blocked by the firewall.
1838410Reason: Unable to open the logical master database.
1838510Reason: Unable to connect to logical master database.
1838610Reason: Remote authentication failed.
1838710Reason: The DosGuard had an error while checking a connection.
1838810Reason: The DosGuard rejected the connection.
1838910Reason: Unable to retrieve server firewall rules.
1839010Reason: An unknown error occurred while attempting to authenticate the user.
1839110Reason: The login to SQL Azure DB failed due to empty username.
1839210Reason: The login to SQL Azure DB failed due to empty password.
1839310Reason: The login to SQL Azure DB failed due to empty password when using PreTDS7 client.
1839410Reason: Opening the database requested by the user failed unexpectedly.
1839510Reason: Authentication was successful, but database was not found on this logical server.
1839610Reason: Authentication was successful, but database could not be found on current instance.
1839710Reason: Unable to retrieve database firewall rules.
1839810Reason: Catch exception from FindLogin during contained database authentication.
1839910Reason: Unsecured connection to the database is disallowed. The secured connection string should be used instead. [Database: ‘%.*ls’]
1840016The background checkpoint thread has encountered an unrecoverable error. The checkpoint process is terminating so that the thread can clean up its resources. This is an informational message only. No user action is required.
1840114Login failed for user ‘%.*ls’. Reason: Server is in script upgrade mode. Only administrator can connect at this time.%.*ls
1845114Login failed for user ‘%.*ls’. Only administrators may connect at this time.%.*ls
1845214Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication.%.*ls
1845310Login succeeded for user ‘%.*ls’. Connection made using Integrated authentication.%.*ls
1845410Login succeeded for user ‘%.*ls’. Connection made using SQL Server authentication.%.*ls
1845510Login succeeded for user ‘%.*ls’.%.*ls
1845614Login failed for user ‘%.*ls’.%.*ls%.*ls
1845814Login failed. The number of simultaneous users already equals the %d registered licenses for this server. To increase the maximum number of simultaneous users, obtain additional licenses and then register them through the Licensing item in Control Panel.%.*ls
1845914Login failed. The workstation licensing limit for SQL Server access has already been reached.%.*ls
1846014Login failed. The number of simultaneous users has already reached the limit of %d licenses for this ‘%ls’ server. Additional licenses should be obtained and installed or you should upgrade to a full version.%.*ls
1846114Login failed for user ‘%.*ls’. Reason: Server is in single user mode. Only one administrator can connect at this time.%.*ls
1846214The login failed for user “%.*ls”. The password change failed. The password for the user is too recent to change. %.*ls
1846314The login failed for user “%.*ls”. The password change failed. The password cannot be used at this time. %.*ls
1846414Login failed for user ‘%.*ls’. Reason: Password change failed. The password does not meet operating system policy requirements because it is too short.%.*ls
1846514Login failed for user ‘%.*ls’. Reason: Password change failed. The password does not meet operating system policy requirements because it is too long.%.*ls
1846614Login failed for user ‘%.*ls’. Reason: Password change failed. The password does not meet operating system policy requirements because it is not complex enough.%.*ls
1846714The login failed for user “%.*ls”. The password change failed. The password does not meet the requirements of the password filter DLL. %.*ls
1846814The login failed for user “%.*ls”. The password change failed. An unexpected error occurred during password validation. %.*ls
1846910 [CLIENT: %.*s%.*ls]
1847014Login failed for user ‘%.*ls’. Reason: The account is disabled.%.*ls
1847114The login failed for user “%.*ls”. The password change failed. The user does not have permission to change the password. %.*ls
1848216Could not connect to server ‘%.*ls’ because ‘%.*ls’ is not defined as a remote server. Verify that you have specified the correct server name. %.*ls.
1848316Could 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.
1848516Could not connect to server ‘%.*ls’ because it is not configured to accept remote logins. Use the remote access configuration option to allow remote logins.%.*ls
1848614Login failed for user ‘%.*ls’ because the account is currently locked out. The system administrator can unlock it. %.*ls
1848714Login failed for user ‘%.*ls’.  Reason: The password of the account has expired.%.*ls
1848814Login failed for user ‘%.*ls’.  Reason: The password of the account must be changed.%.*ls
1848910The dedicated administrator connection is in use by “%.*ls” on “%.*ls”.%.*ls
1849116SQL Server could not start because of an invalid serial number. The serial number information retrieved at startup appears invalid. To proceed, reinstall SQL Server.
1849216SQL Server cannot start because the license agreement for this ‘%ls’ version of SQL Server is invalid. The server is exiting. To proceed, reinstall SQL Server with a valid license.
1849316The user instance login flag is not supported on this version of SQL Server. The connection will be closed.%.*ls
1849416The user instance login flag is not allowed when connecting to a user instance of SQL Server. The connection will be closed.%.*ls
1849516The user instance login flag cannot be used along with an attach database file name. The connection will be closed.%.*ls
1849610System Manufacturer: ‘%ls’, System Model: ‘%ls’.
1849710 [SERVER: %.*s%.*ls]
1859616%.*ls cannot start because your system is low on memory.
1859716Your %.*ls installation is either corrupt or has been tampered with (%hs).  Please uninstall then re-run setup to correct this problem
1859816%.*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.
1859916%.*ls could not find the specified named 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.
1875016%ls: The parameter ‘%ls’ is not valid.
1875116%ls procedure was called with the wrong number of parameters.
1875216Only 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.
1875516Could not allocate memory for replication. Verify that SQL Server has sufficient memory for all operations.
1875616Could not retrieve replication information for table %d. Verify that the table has a primary key, and then rerun the Log Reader Agent.
1875716Unable to execute procedure. The database is not published. Execute the procedure in a database that is published for replication.
1876016Invalid %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.
1876116Commit record at {%08lx:%08lx:%04lx} has already been distributed.
1876216Invalid begin LSN {%08lx:%08lx:%04lx} for commit record {%08lx:%08lx:%04lx}. Check DBTABLE.
1876316Commit record {%08lx:%08lx:%04lx} reports oldest active LSN as (0:0:0).
1876416Execution of filter stored procedure %d failed. See the SQL Server errorlog for more information.
1876516The “%s” log sequence number (LSN) that was specified for the replication log scan is invalid.
1876616The replbeginlsn field in the DBTABLE is invalid.
1876716The specified begin LSN {%08lx:%08lx:%04lx} for replication log scan occurs before replbeginlsn {%08lx:%08lx:%04lx}.
1876816The specified LSN {%08lx:%08lx:%04lx} for repldone log scan occurs before the current start of replication in the log {%08lx:%08lx:%04lx}.
1876916The specified LSN {%08lx:%08lx:%04lx} for repldone log scan is not a replicated commit record.
1877016The specified LSN {%08lx:%08lx:%04lx} for repldone log scan is not present in the transaction log.
1877116Invalid storage type %d specified writing variant of type %d.
1877216Invalid server data type (%d) specified in repl type lookup.
1877316Could not locate text information records for the column “%.*ls”, ID %d during command construction.
1877416The stored procedure %s must be executed within a transaction.
1877516The Log Reader Agent encountered an unexpected log record of type %u encountered while processing DML operation.
1877616An error occurred while waiting on the article cache access event.
1877716%s: Error initializing MSMQ components
1877816%s: Error opening Microsoft Message Queue %s
1878016You have specified a value for the @dts_package_password parameter. You must also specify a value for the @dts_package_name parameter.
1878116The value specified for the @backupdevicetype parameter is not valid. The value must be ‘logical’, ‘disk’, or ‘tape’.
1878216Could not locate backup header information for database ‘%s’ in the specified backup device. Specify a backup device that contains a backup of the Publisher database.
1878316The 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.
1878416The alternate snapshot folder path generated by replication has been truncated. Reconfigure the publication to use a shorter alternate snapshot folder path, and then retry the operation.
1878616The 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’.
1878716Snapshot publications cannot use the option to initialize a subscription from a backup. This option is only supported for transactional publications.
1879016Cannot 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.
1879516The valid new types of a log based indexed view article are ‘indexed view logbased’, ‘indexed view logbased manualfilter’, ‘indexed view logbased manualview’,  and ‘indexed view logbased manualboth’ only.
1879616The valid new types of a log based table article are ‘logbased’, ‘logbased manualfilter’, ‘logbased manualview’,  and ‘logbased manualboth’ only.
1879916Only users who are members of the following roles can perform this operation: sysadmin fixed server role; dbowner or dbcreator fixed database role in the current database.
1880116Unable to allocate memory for replication schema version node.
1880216Cannot insert a new schema change into the systranschemas system table. HRESULT = ‘0x%x’. If the problem persists, contact Customer Support Services.
1880316The topic %.*ls is not a supported help topic. To see the list of supported topics, execute the stored procedure sp_replhelp N’helptopics’.
1880416Peer-to-peer replication has been enabled, and the Log Reader Agent was unable to find an Extended-Originator-Record (EOR) for a transaction that did not originate at this server. Contact Customer Support Services.
1880516The 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.
1880616Cannot initialize the replication resource. Ensure that SQL Server has sufficient memory. If the problem persists, restart SQL Server.
1880716Cannot 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.
1880816Article information is not valid. Stop the Log Reader Agent, execute the stored procedure sp_replflush, and then restart the Log Reader Agent.
1880916END_UPDATE log record {%08lx:%08lx:%04lx} encountered without matching BEGIN_UPDATE.
1881016Cannot restart the scan on table ‘%s’. HRESULT = ‘0x%x’. Stop and restart the Log Reader Agent. If the problem persists, contact Customer Support Services.
1881116Invalid %s log record.
1881216Can not lock the database object in article cache.
1881516Expecting %I64d bytes of data, but only %I64d were found in the transaction log. For more information, contact Customer Support Services.
1881716Text information block not valid. Contact Customer Support Services.
1881816Failed to scan to log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services.
1881916Failed to lock the current log record at log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services.
1882116The rowset does not contain any column with offset %d. Back up the publication database and contact Customer Support Services.
1882316Invalid value %d for %s.
1882616Failed 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.
1882716The Log Reader Agent scanned to the end of the log before processing all transactions in the hash table. %d transactions in the hash table, %d transactions processed, end of log LSN {%08lx:%08lx:%04lx}. Back up the publication database and contact Customer Support Services.
1882816Invalid filter procedure definition.
1882916Failed to scan to the delete log record of an update base on log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services.
1883016A 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.
1883216The Log Reader Agent scanned to the end of the log while processing a bounded update. BEGIN_UPDATE LSN {%08lx:%08lx:%04lx}, END_UPDATE LSN {%08lx:%08lx:%04lx}, current LSN {%08lx:%08lx:%04lx}. Back up the publication database and contact Customer Support Services.
1883416An 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.
1883516Encountered an unexpected Text Information End (TIE) log record. Last Text Information Begin (TIB) processed: (textInfoFlags 0x%x, coloffset %ld, newSize %I64d, oldSize %I64d),  text collection state %d. Contact product support.
1883616%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}.
1883716Cannot find rowset ID %I64d in the current schema. Stop and restart the Log Reader Agent. If the problem persists, reinitialize all subscriptions to the publication.
1883816The 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.
1884016Cannot locate database information in the article cache. Stop and restart SQL Server and the Log Reader Agent. If the problem persists, back up the publication database, and then contact Customer Support Services.
1884216Failed 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.
1884316Failed to allocate or reallocate buffer for replication command, old size %d, new size %d.
1884416Invalid compensation range: begin {%08lx:%08lx:%04lx}, end {%08lx:%08lx:%04lx}. Reinitialize all subscriptions to the publication.
1884516Cannot retrieve the rowset ID from log records generated from a text pointer based operation. Reinitialize all subscriptions to the publication.
1884616Possible 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.
1884716Cannot retrieve the peer-to-peer database information. Contact Customer Support Services.
1884916Failed 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.
1885016Unexpected %s log record encountered, last FILESTREAMInfo node processed : {%d, {{%I64d, %I64d}, %I64d, %I64d, %d, %d}, %d, %ld, %I64d, %I64d, %I64d, %I64d, {%08lx:%08lx:%04lx}, %d, {{%I64d, %I64d},  %I64d, %I64d, %d, %d}, {%08lx:%08lx:%04lx}}
1885116Failed 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.
1885216Failed to read the TXF_REPLICATION_RECORD_WRITE structure. Last error returned ‘%ld’. If the problem persists, contact Customer Support Services.
1885310Replication 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.
1885416One or more subscriptions have been marked inactive. Drop and re-create all subscriptions for this node that are failing with this error.
1885511Can not rename the database name because it is published or it is a distribution database used by replication.
1885616Agent ‘%s’ is retrying after an error. %d retries attempted. See agent job history in the Jobs folder for more details.
1885716The subscription to this publication is not active yet. No user action is required.
1889616Failed to compare delete and insert log record for column ID %ld with table ID %ld
1889716Access Denied.