Select the product you need help with

FIX: Replication Log Reader Agent fails with "18773" and "18805" error messages if you set the 'large value types out of row' table option to ON for the publication article table

Article ID: 2655789 - View products that this article applies to.

Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 (SP1) or Microsoft SQL Server 2012 fixes in one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 R2 Service Pack 1 (SP1) or Microsoft SQL Server 2012 update release.

Back to the top | Give Feedback

SYMPTOMS

Consider the following scenario:

You have a table that is used as a publication article in Microsoft SQL Server 2008 R2 or in Microsoft SQL Server 2012.
You set the 'large value types out of row' table option to ON for the table.
You run a BULK INSERT command to import a data file into the table.

In this scenario, when the Replication Log Reader Agent tries to transfer transactions from the publisher to distributors, the synchonization might fail, and you may receive the following error messages:

Status: 0, code: 18773, text: 'Could not locate text information records for column # during command construction.'.

Status: 0, code: 18805, text: 'The Log-Scan Process failed to construct a replicated command from log sequence number (LSN) {00000017:000001d3:0029}. Back up the publication database and contact Customer Support Services.'

Back to the top | Give Feedback

CAUSE

This issue occurs because the BULK INSERT command does not generate a certain transaction log record that is only for replication.

Back to the top | Give Feedback

RESOLUTION

Cumulative update information

SQL Server 2012

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2679368

(http://support.microsoft.com/kb/2679368/LN/ )

Cumulative update package 1 for SQL Server 2012

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2692828

(http://support.microsoft.com/kb/2692828/LN/ )

The SQL Server 2012 builds that were released after SQL Server 2012 was released

You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.

Cumulative update package 5 for SQL Server 2008 R2 SP1

The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

2659694

(http://support.microsoft.com/kb/2659694/ )

Cumulative update package 5 for SQL Server 2008 R2 SP1

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 SP1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2567616

(http://support.microsoft.com/kb/2567616/ )

The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 SP1 was released

Back to the top | Give Feedback