Web.QHMIT.com

SQL Server System Errors: 18000 - 18999

List of error messages between 18000 and 18999 in SQL Server 2017.

These error messages are all available by querying the sys.messages catalog view on the master database.

message_id severity is_event_logged text
18002201Exception 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.
18052160Error: %d, Severity: %d, State: %d.
18053160Error: %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.
18054161Error %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.
18055201Exception %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.
18056201The 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.
18057201Error: Failed to set up execution context.
18058171Failed 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.
18059161The 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.
18060161Failed 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.
18061201The 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.
18100101Process ID %d was killed by hostname %.*ls, host process ID %d.
18113101SQL Server shutdown after verifying system indexes.
18124101The default collation was successfully changed.
18126101Engine failed to load configuration for error detection, default configuration was applied.
18127101Engine is marking DB %d [%.*ls] as SUSPECT in cloud DB mode due to error %d, severity %d, state %d.
18204161%s: Backup device '%s' failed to %s. Operating system error %s.
18210161%s: %s failure on backup device '%s'. Operating system error %s.
18225101Tape '%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
18226101Tape mount is being requested on drive '%s'. Expected volume has (Family ID %d, sequence %d).
18227101Unnamed 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.
18228101Tape mount request on drive '%s' is cancelled. This is an informational message only. No user action is required.
18257101%s: Device or media does not support %s. To access this feature, use a different device or media.
18264101Database 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.
18265101Log 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.
18266101Database 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.
18267101Database 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.
18268101Log 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.
18269101Database 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.
18270101Database 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.
18271101Database 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.
18272161During 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.
18273161Could 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.
18274101Tape '%s' was dismounted from drive '%s'. This is an informational message. No user action is required.
18275101Unnamed tape was dismounted from drive '%s'. This is an informational message. No user action is required.
18276101Database 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.
18277101Database 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.
18279161During 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.
18280161The 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.
18300100 Reason: Infrastructure error occurred. Check for previous errors.
18301100 Reason: Could not find a login matching the name provided.
18302100 Reason: Failed to unprotect memory containing sensitive information.
18303100 Reason: Failed to unprotect memory containing sensitive information.
18304100 Reason: Could not find a login matching the name provided.
18305100 Reason: Attempting to use an NT account name with SQL Server Authentication.
18306100 Reason: An error occurred while evaluating the password.
18307100 Reason: Password did not match that for the login provided.
18308100 Reason: Invalid password provided.
18309100 Reason: Password validation failed with an infrastructure error. Check for previous errors.
18310100 Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors.
18311100 Reason: Login-based server access validation failed with an infrastructure error. Check for previous errors.
18312100 Reason: SQL Server service is paused. No new connections can be accepted at this time.
18313100 Reason: Interface for login to SQL Server is not supported.
18314100 Reason: Failed to open the specified database.
18315100 Reason: Failed to open the database for this login.
18316100 Reason: Unable to determine the initial language and date format.
18317100 Reason: The user must change the password, but it cannot be changed with the current connection settings.
18318100 Reason: Failed to unprotect memory containing sensitive information.
18319100 Reason: Simulation of a failure while redoing login on the connection.
18320100 Reason: SQL Server service is paused. Login could not be revalidated at this time.
18321100 Reason: Reinitialization of security context failed while revalidating the login on the connection.
18322100 Reason: Access to server validation failed while revalidating the login on the connection.
18323100 Reason: Failed to open the specified database while revalidating the login on the connection.
18324100 Reason: Failed to create the user instance while revalidating the login on the connection.
18325100 Reason: Failed to attach the specified database while revalidating the login on the connection.
18326100 Reason: Failed to open the database for this login while revalidating the login on the connection.
18327100 Reason: Failed to determine the language and date format while revalidating the login on the connection.
18328100 Reason: An exception was raised while revalidating the login on the connection. Check for previous errors.
18329100 Reason: Simulation of a failure while reauthenticating login.
18330100 Reason: SQL Server service is paused. Login cannot be reauthenticated at this time.
18331100 Reason: Failed to reinitialize security context while reauthenticating login.
18332100 Reason: Failed to access server for validation while reauthenticating login.
18333100 Reason: Failed to open the specified database while reauthenticating login.
18334100 Reason: An error occurred while reauthenticating login. Check for previous errors.
18335100 Reason: Could not retrieve database name or map database to an item.
18336100 Reason: Cannot connect with a login that does not specify a share.
18337100 Reason: Failed to open the explicitly specified database '%.*ls'.
18338100 Reason: Unable to determine the database name from the specified file name.
18339100 Reason: Failed to open the database '%.*ls' specified in the login properties.
18340100 Reason: Failed to store database name and collation. Check for previous errors.
18341100. Reason: Current collation did not match the database's collation during connection reset.
18342100 Reason: Failed to send an environment change notification to a log shipping partner node.
18343100 Reason: Failed to retrieve database name or map database to an item while revalidating the login on the connection.
18344100 Reason: Connection with a login which does not specify a share is not allowed while revalidating the login on the connection.
18345100 Reason: Failed to open the database '%.*ls' configured in the login object while revalidating the login on the connection.
18346100 Reason: Failed to determine database name from a given file name while revalidating the login on the connection.
18347100 Reason: Failed to open the database '%.*ls' specified in the login properties while revalidating the login on the connection.
18348100 Reason: Failed to store database name and collation while revalidating the login on the connection. Check for previous errors.
18349100 Reason: Current collation did not match the database's collation during connection reset.
18350100 Reason: Failed to send an environment change notification to a log shipping partner node while revalidating the login.
18351100 Reason: Client impersonation failed.
18352100 Reason: Failed to revert impersonation to self.
18353100 Reason: Failed to get security token information.
18354100 Reason: Failed to duplicate of security token.
18355100 Reason: Failed attempted retry of a process token validation.
18356100 Reason: An error occurred while attempting to change password.
18357100 Reason: An attempt to login using SQL authentication failed. Server is configured for Integrated authentication only.
18358100 Reason: Could not find a user matching the name provided. [Database: '%.*ls']
18359100 Reason: Failed to unprotect memory containing sensitive information. [Database: '%.*ls']
18360100 Reason: Failed to unprotect memory containing sensitive information. [Database: '%.*ls']
18361100 Reason: Could not find a user matching the name provided. [Database: '%.*ls']
18362100 Reason: Attempting to use an invalid user type with SQL Server Authentication. [Database: '%.*ls']
18363100 Reason: An error occurred while evaluating the password. [Database: '%.*ls']
18364100 Reason: Password did not match that for the user provided. [Database: '%.*ls']
18365100 Reason: Invalid password provided. [Database: '%.*ls']
18366100 Reason: Password validation failed with an infrastructure error. Check for previous errors. [Database: '%.*ls']
18367100 Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [Database: '%.*ls']
18368100 Reason: Login-based server access validation failed with an infrastructure error. Check for previous errors. [Database: '%.*ls']
18369100attach
18370100restore
18371100Reason: The password hash is from an unsupported version of SQL Server. Reset the password or recreate the login.
18372100 Reason: An error occurred while obtaining a routing environment change notification.
18373100Reason: Database could not accept user connections at this time.
18374101 Reason: An error occurred while recovering the Identity_Insert session state requested by the recovery login.
18375101 Reason: Failed to open the database '%.*ls' configured in the session recovery object while recovering the connection.
18376101 Reason: Failed to open the database '%.*ls' configured in the session recovery object while revalidating the login on the recovered connection.
18377100 Reason: The current collation did not match the database's collation as indicated by session recovery object in login.
18378101 Reason: An error occurred while recovering the @@identity session state requested by the recovery login.
18379100Reason: The account is currently locked out. The system administrator can unlock it.
18380100Reason: The certificate is invalid or expired.
18381100Reason: The logical master database was not found.
18382100Reason: Unable to retrieve client IP Address.
18383100Reason: The client was blocked by the firewall.
18384100Reason: Unable to open the logical master database.
18385100Reason: Unable to connect to logical master database.
18386100Reason: Remote authentication failed.
18387100Reason: The DosGuard had an error while checking a connection.
18388100Reason: The DosGuard rejected the connection.
18389100Reason: Unable to retrieve server firewall rules.
18390100Reason: An unknown error occurred while attempting to authenticate the user.
18391100Reason: The login to SQL Azure DB failed due to empty username.
18392100Reason: The login to SQL Azure DB failed due to empty password.
18393100Reason: The login to SQL Azure DB failed due to empty password when using PreTDS7 client.
18394100Reason: Opening the database requested by the user failed unexpectedly.
18395100Reason: Authentication was successful, but database was not found on this logical server.
18396100Reason: Authentication was successful, but database could not be found on current instance.
18397100Reason: Unable to retrieve database firewall rules.
18398100Reason: Catch exception from FindLogin during contained database authentication.
18399100Reason: Unsecured connection to the database is disallowed. The secured connection string should be used instead. [Database: '%.*ls']
18400161The 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.
18401141Login failed for user '%.*ls'. Reason: Server is in script upgrade mode. Only administrator can connect at this time.%.*ls
18451141Login failed for user '%.*ls'. Only administrators may connect at this time.%.*ls
18452141Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication.%.*ls
18453101Login succeeded for user '%.*ls'. Connection made using Integrated authentication.%.*ls
18454101Login succeeded for user '%.*ls'. Connection made using SQL Server authentication.%.*ls
18455101Login succeeded for user '%.*ls'.%.*ls
18456141Login failed for user '%.*ls'.%.*ls%.*ls
18458141Login 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
18459141Login failed. The workstation licensing limit for SQL Server access has already been reached.%.*ls
18460141Login 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
18461141Login failed for user '%.*ls'. Reason: Server is in single user mode. Only one administrator can connect at this time.%.*ls
18462140The login failed for user "%.*ls". The password change failed. The password for the user is too recent to change. %.*ls
18463140The login failed for user "%.*ls". The password change failed. The password cannot be used at this time. %.*ls
18464140Login failed for user '%.*ls'. Reason: Password change failed. The password does not meet operating system policy requirements because it is too short.%.*ls
18465140Login failed for user '%.*ls'. Reason: Password change failed. The password does not meet operating system policy requirements because it is too long.%.*ls
18466140Login failed for user '%.*ls'. Reason: Password change failed. The password does not meet operating system policy requirements because it is not complex enough.%.*ls
18467140The login failed for user "%.*ls". The password change failed. The password does not meet the requirements of the password filter DLL. %.*ls
18468140The login failed for user "%.*ls". The password change failed. An unexpected error occurred during password validation. %.*ls
18469100 [CLIENT: %.*s%.*ls]
18470141Login failed for user '%.*ls'. Reason: The account is disabled.%.*ls
18471140The login failed for user "%.*ls". The password change failed. The user does not have permission to change the password. %.*ls
18482161Could not connect to server '%.*ls' because '%.*ls' is not defined as a remote server. Verify that you have specified the correct server name. %.*ls.
18483161Could 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.
18485161Could 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
18486141Login failed for user '%.*ls' because the account is currently locked out. The system administrator can unlock it. %.*ls
18487141Login failed for user '%.*ls'. Reason: The password of the account has expired.%.*ls
18488141Login failed for user '%.*ls'. Reason: The password of the account must be changed.%.*ls
18489100The dedicated administrator connection is in use by "%.*ls" on "%.*ls".%.*ls
18491161SQL Server could not start because of an invalid serial number. The serial number information retrieved at startup appears invalid. To proceed, reinstall SQL Server.
18492161SQL 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.
18493161The user instance login flag is not supported on this version of SQL Server. The connection will be closed.%.*ls
18494161The user instance login flag is not allowed when connecting to a user instance of SQL Server. The connection will be closed.%.*ls
18495161The user instance login flag cannot be used along with an attach database file name. The connection will be closed.%.*ls
18496101System Manufacturer: '%ls', System Model: '%ls'.
18497100 [SERVER: %.*s%.*ls]
18596160%.*ls cannot start because your system is low on memory.
18597160Your %.*ls installation is either corrupt or has been tampered with (%hs). Please uninstall then re-run setup to correct this problem
18598160%.*ls could not find the default instance (%.*ls) - error %d. Please specify the name of an existing instance on the invocation of sqlservr.exe.nnIf you believe that your installation is corrupt or has been tampered with, uninstall then re-run setup to correct this problem.
18599160%.*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.nnIf you believe that your installation is corrupt or has been tampered with, uninstall then re-run setup to correct this problem.
18750160%ls: The parameter '%ls' is not valid.
18751160%ls procedure was called with the wrong number of parameters.
18752160Only 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.
18755160Could not allocate memory for replication. Verify that SQL Server has sufficient memory for all operations.
18756160Could not retrieve replication information for table %d. Verify that the table has a primary key, and then rerun the Log Reader Agent.
18757160Unable to execute procedure. The database is not published. Execute the procedure in a database that is published for replication.
18760160Invalid %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.
18761160Commit record at {%08lx:%08lx:%04lx} has already been distributed.
18762160Invalid begin LSN {%08lx:%08lx:%04lx} for commit record {%08lx:%08lx:%04lx}. Check DBTABLE.
18763160Commit record {%08lx:%08lx:%04lx} reports oldest active LSN as (0:0:0).
18764160Execution of filter stored procedure %d failed. See the SQL Server errorlog for more information.
18765160The "%s" log sequence number (LSN) that was specified for the replication log scan is invalid.
18766160The replbeginlsn field in the DBTABLE is invalid.
18767160The specified begin LSN {%08lx:%08lx:%04lx} for replication log scan occurs before replbeginlsn {%08lx:%08lx:%04lx}.
18768160The specified LSN {%08lx:%08lx:%04lx} for repldone log scan occurs before the current start of replication in the log {%08lx:%08lx:%04lx}.
18769160The specified LSN {%08lx:%08lx:%04lx} for repldone log scan is not a replicated commit record.
18770160The specified LSN {%08lx:%08lx:%04lx} for repldone log scan is not present in the transaction log.
18771160Invalid storage type %d specified writing variant of type %d.
18772160Invalid server data type (%d) specified in repl type lookup.
18773160Could not locate text information records for the column "%.*ls", ID %d during command construction.
18774160The stored procedure %s must be executed within a transaction.
18775160The Log Reader Agent encountered an unexpected log record of type %u encountered while processing DML operation.
18776160An error occurred while waiting on the article cache access event.
18777160%s: Error initializing MSMQ components
18778160%s: Error opening Microsoft Message Queue %s
18780160You have specified a value for the @dts_package_password parameter. You must also specify a value for the @dts_package_name parameter.
18781160The value specified for the @backupdevicetype parameter is not valid. The value must be 'logical', 'disk', or 'tape'.
18782160Could 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.
18783160The 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.
18784160The 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.
18786160The 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'.
18787160Snapshot publications cannot use the option to initialize a subscription from a backup. This option is only supported for transactional publications.
18790160Cannot 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.
18795160The 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.
18796160The valid new types of a log based table article are 'logbased', 'logbased manualfilter', 'logbased manualview', and 'logbased manualboth' only.
18799160Only 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.
18801160Unable to allocate memory for replication schema version node.
18802160Cannot insert a new schema change into the systranschemas system table. HRESULT = '0x%x'. If the problem persists, contact Customer Support Services.
18803160The topic %.*ls is not a supported help topic. To see the list of supported topics, execute the stored procedure sp_replhelp N'helptopics'.
18804160Peer-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.
18805160The 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.
18806160Cannot initialize the replication resource. Ensure that SQL Server has sufficient memory. If the problem persists, restart SQL Server.
18807160Cannot 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.
18808160Article information is not valid. Stop the Log Reader Agent, execute the stored procedure sp_replflush, and then restart the Log Reader Agent.
18809160END_UPDATE log record {%08lx:%08lx:%04lx} encountered without matching BEGIN_UPDATE.
18810160Cannot restart the scan on table '%s'. HRESULT = '0x%x'. Stop and restart the Log Reader Agent. If the problem persists, contact Customer Support Services.
18811160Invalid %s log record.
18812160Can not lock the database object in article cache.
18815160Expecting %I64d bytes of data, but only %I64d were found in the transaction log. For more information, contact Customer Support Services.
18817160Text information block not valid. Contact Customer Support Services.
18818160Failed to scan to log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services.
18819160Failed to lock the current log record at log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services.
18821160The rowset does not contain any column with offset %d. Back up the publication database and contact Customer Support Services.
18823160Invalid value %d for %s.
18826160Failed 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.
18827160The 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.
18828160Invalid filter procedure definition.
18829160Failed to scan to the delete log record of an update base on log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services.
18830160A 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.
18832160The 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.
18834160An 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.
18835160Encountered 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.
18836160%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}.
18837160Cannot 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.
18838160The 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.
18840160Cannot 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.
18842160Failed 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.
18843160Failed to allocate or reallocate buffer for replication command, old size %d, new size %d.
18844160Invalid compensation range: begin {%08lx:%08lx:%04lx}, end {%08lx:%08lx:%04lx}. Reinitialize all subscriptions to the publication.
18845160Cannot retrieve the rowset ID from log records generated from a text pointer based operation. Reinitialize all subscriptions to the publication.
18846160Possible 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.
18847160Cannot retrieve the peer-to-peer database information. Contact Customer Support Services.
18849160Failed 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.
18850160Unexpected %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}}
18851160Failed 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.
18852160Failed to read the TXF_REPLICATION_RECORD_WRITE structure. Last error returned '%ld'. If the problem persists, contact Customer Support Services.
18853100Replication 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.
18854160One or more subscriptions have been marked inactive. Drop and re-create all subscriptions for this node that are failing with this error.
18855110Can not rename the database name because it is published or it is a distribution database used by replication.
18856160Agent '%s' is retrying after an error. %d retries attempted. See agent job history in the Jobs folder for more details.
18857160The subscription to this publication is not active yet. No user action is required.
18896160Failed to compare delete and insert log record for column ID %ld with table ID %ld
18897160Access Denied.