FIX: Error when you use the replication feature in SQL Server 2014 or SQL Server 2012

Applies to: SQL Server 2014 DeveloperSQL Server 2014 DeveloperSQL Server 2014 Enterprise

Symptoms


When you use the Replication feature in Microsoft SQL Server 2012 or SQL Server 2014, the Log Reader Agent may fail intermittently. Additionally, you receive one of the following error messages in the SQL Server error log:

Error 1

<Date> <Time> <SPID> ***Stack Dump being sent to <DiskLocation>
<Date> <Time> <SPID> * *******************************************************************************
<Date> <Time> <SPID> *
<Date> <Time> <SPID> * BEGIN STACK DUMP:
<Date> <Time> <SPID> * <Date> <Time> <SPID>
<Date> <Time> <SPID> *
<Date> <Time> <SPID> * Location: replicat.cpp:2746
<Date> <Time> <SPID> * Expression: pRowset
<Date> <Time> <SPID> * SPID: <SPID>
<Date> <Time> <SPID> * Process ID: <ProcessID>
<Date> <Time> <SPID> *
<Date> <Time> <SPID> * Input Buffer 109 bytes -
<Date> <Time> <SPID> * 16 00 00 00 12 00 00 00 02 00 00 00 00 00 00 00 00 00
<Date> <Time> <SPID> * s p _ r e p 01 00 00 00 0b 00 73 00 70 00 5f 00 72 00 65 00 70 00
<Date> <Time> <SPID> * l c m d s & ô 6c 00 63 00 6d 00 64 00 73 00 00 00 00 00 26 04 04 f4
<Date> <Time> <SPID> * & & ÿ 01 00 00 00 00 26 04 04 00 00 00 00 00 00 26 04 04 ff
<Date> <Time> <SPID> * ÿÿÿ ¥ & ff ff ff 00 00 a5 0a 00 00 00 00 00 26 04 04 00 00 00
<Date> <Time> <SPID> * & & ¡ 00 00 00 26 04 04 00 00 00 00 00 00 26 04 04 20 a1 07
<Date> <Time> <SPID> * 00

Error 2

<Date> <Time> <SPID> Error: 5243, Severity: 22, State: 7.
<Date> <Time> <SPID> An inconsistency was detected during an internal operation. Please contact technical support.
<Date> <Time> <SPID> ex_raise2: Exception raised, major=52, minor=43, state=7, severity=22, attempting to create symptom dump
<Date> <Time> <SPID> **Dump thread - spid = 0, EC = 0x000000297EC97DE0
<Date> <Time> <SPID> ***Stack Dump being sent to <DiskLocation>
<Date> <Time> <SPID> * *******************************************************************************
<Date> <Time> <SPID> *
<Date> <Time> <SPID> * BEGIN STACK DUMP:
<Date> <Time> <SPID> * <Date> <Time> <SPID>
<Date> <Time> <SPID> *
<Date> <Time> <SPID> * ex_raise2: Exception raised, major=52, minor=43, state=7, severity=22
<Date> <Time> <SPID> *
<Date> <Time> <SPID> * Input Buffer 109 bytes -
<Date> <Time> <SPID> * 16 00 00 00 12 00 00 00 02 00 00 00 00 00 00 00 00 00
<Date> <Time> <SPID> * s p _ r e p 01 00 00 00 0b 00 73 00 70 00 5f 00 72 00 65 00 70 00
<Date> <Time> <SPID> * l c m d s & ô 6c 00 63 00 6d 00 64 00 73 00 00 00 00 00 26 04 04 f4
<Date> <Time> <SPID> * & & ÿ 01 00 00 00 00 26 04 04 00 00 00 00 00 00 26 04 04 ff
<Date> <Time> <SPID> * ÿÿÿ ¥ & ff ff ff 00 00 a5 0a 00 00 00 00 00 26 04 04 00 00 00
<Date> <Time> <SPID> * & & ¡ 00 00 00 26 04 04 00 00 00 00 00 00 26 04 04 20 a1 07
<Date> <Time> <SPID> * 00

Cause


This issue occurs when the same article is published in more than one transactional publication, or same article is part of CDC and transactional publication.

Resolution


Cumulative update information

The issue was first fixed in the following cumulative update of SQL Server:
 

 

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.