FIX: Logreader Fails to Replicate When Updating Non-NULL Text Fields with Empty Space

This article was previously published under Q215457
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 53984 (SQLBUG_70)
SYMPTOMS
Logreader stops delivering replication transactions to the distribution database. It reports the following message even if there are transactions in the log pending replication:
No replicated transactions are available.
CAUSE
The sp_replcmds stored procedure fails to recognize UPDATE transactions when they include an empty space change ('') to a non-NULL text field. The Logreader process uses sp_replcmds to locate the commands marked for replication. After this error is encountered, no further transactions are replicated by the Logreader. The publication must be unsubscribed and resubscribed before replication will continue.
WORKAROUND
To work around this problem, use white space (' ') to update non-NULL text fields.

If you cannot use this workaround but you use custom stored procedures (default) at the subscriber, you can use the following workaround instead:
  1. Unsubscribe your publications.
  2. Change each article. Locate the Articles Properties, Command tab. Click to clear the Send Stored Procedure Parameters In Binary Format option .
  3. Resubscribe the publications.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
232570INF: How to Obtain Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
repl log reader nonnull nonull
Properties

Article ID: 215457 - Last Review: 10/14/2013 15:36:38 - Revision: 2.1

  • Microsoft SQL Server 7.0 Standard Edition
  • kbnosurvey kbarchive kbbug kbfix kbqfe KB215457
Feedback