BUG: Wrong Synchronization Status Displayed

 Last reviewed: May 5, 1997
Article ID: Q152545
The information in this article applies to:
  • Microsoft SQL Server, version 6.0

SYMPTOMS

The synchronization status of the subscriptions is incorrect when the choice of replication frequency is Scheduled Table Refresh. The status displayed is NOT SYNC'ED even if the sync and distribution tasks run successfully and the tables are replicated on the subscribers. The same erroneous status is displayed with both automatic and manual methods of synchronization. The Transaction Based replication does not exhibit this behavior. Only scheduled table refresh exhibits this behaviour.

WORKAROUND

The correct status can be viewed in the history of the sync task and the distribution task. If the tasks were successfully executed, check for the tables in the subscribing database. Alternately, you can check whether the last job ID in the MSlast_job_info table in the susbcribing database matches the most recent job ID in the MSsusbcriber_status table in the distribution database to see if synchronizaton took place. The commands relevant to the job ID can be obtained from the MSjob_commands table in the distribution database.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words:
Keywords : kbbug6.00
Version : 6.0
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: May 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.