FIX: Replicated UPDATE to Char Column May Cause Error 803

Last reviewed: April 9, 1997
Article ID: Q160180
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 15829 (Windows NT: 6.5)

SYMPTOMS

LogReader fails with error 803. The errorlog and the task history shows the following message:

   Error : 803, Severity: 20, State: 1
   Unable to place buffer %*.d holding logical page %*.d in sdes for object
   'syslogs' - either there is no room in sdes or buffer already in
   requested slot.

CAUSE

The server may encounter this error when all of the following are true:

  • You attempt to perform a replicated UPDATE on a character column.
  • The character column is a part of an index in a table.
  • The index is published, using partitioning, at least seven times in the same publication or multiple publications.

This problem only occurs with transaction-based publications.

WORKAROUND

To work around this problem, drop the index on the character column that is being updated. If this is not possible, use Scheduled Table Refresh for tables that are required to be published using partitioning at least seven times.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.


Additional query words: SEM hung unresponsive
Keywords : kbbug6.50 kbfix6.50.sp2 kbusage SSrvErr_Log SSrvRep
Version : 6.5
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.