Microsoft KB Archive/300269

= FIX: Replication Conflict Viewer Reports That Merge Published Database Is Not Published =

Article ID: 300269

Article Last Modified on 11/16/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q300269



BUG #: 354199 (SHILOH_BUGS)



SYMPTOMS
The Replication Conflict Viewer that is released with SQL Server 2000 (Wzcnflct.exe) may incorrectly report that a published merge replication database is not published with the following error message:

The database you have chosen to connect to is not a Publisher or Subscriber.

This problem can occur if the following conditions are true:
 * The Publisher is a SQL Server 7.0 server.
 * Both a merge publication and a transactional publication are configured for this published database.



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack



WORKAROUND
Use the SQL Server 7.0 Replication Conflict Viewer to view SQL Server 7.0 merge publication conflicts when a transactional publication is configured for the same database.

To use the SQL Server 7.0 Replication Conflict Viewer, follow these steps:  Download the latest SQL Server 7.0 Service Pack from the following Web site:

http://technet.microsoft.com/en-us/sqlserver/bb331754.aspx

 Expand the Service Pack and look for the Wzcnflct.exe file in the \X86\BINN folder. Copy the Wzcnflct.exe file to a folder on the system where the Conflict Viewer will be used. Create a shortcut on the desktop.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 2000. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.

Keywords: kbbug kbfix KB300269

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.