Microsoft KB Archive/317350

= BUG: Conflict Tables Not Created When Publisher Is In a Workgroup =

Article ID: 317350

Article Last Modified on 6/27/2002

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q317350



BUG #: 200002 (SQLBUG_70)

BUG #: 200003 (SQLBUG_70)



SYMPTOMS
If a SQL Server 7.0 merge replication publisher is not a member of a domain (a Workgroup member only), and the associated distributor and subscribers are members of a domain, the SQL Server Snapshot Agent fails to create conflict scripts for the merge publication. The Snapshot Agent does not register a failure and seemingly completes successfully.

When the Merge Agent detects a conflicting change, an error message similar to the following occurs:

PUBLISHER.PublishedDB: {call sp_MSgetconflictinsertproc (?,?) }

Percent Complete: 0

The process could not log conflict information.

Category:COMMAND

Source: Failed Command

Number:

Message: {call sp_MSgetconflictinsertproc (?,?) }

Category:SQLSERVER

Source: PUBLISHER

Number: 206

Message: Operand type clash: uniqueidentifier is incompatible with int



CAUSE
The Snapshot Agent uses the sp_MSsetconflictscript system stored procedure to create conflict tables at the publisher. The sp_MSsetconflictscript stored procedure makes a call to the xp_cmdshell extended stored procedure to execute the DDL operations required to actually create the conflict tables. The DDL is contained in the CFT script that is stored in the distributor's snapshot folder for the publication. The publisher cannot access the share, because it is a part of a workgroup, so the xp_cmdshell call fails.



WORKAROUND
To work around this problem, connect to the publishing server from the distributor by using Query Analyzer, or a similar query tool, and manually run the CFT Transact-SQL scripts stored in the distributor's snapshot directory for each article in the publication. The path to the article's conflict script is stored in the conflict_script column of the sysmergearticles system table.



STATUS
Microsoft has confirmed that this is a problem in SQL Server 7.0.

Additional query words: repl

Keywords: kbbug kbpending KB317350

-

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

© Microsoft Corporation. All rights reserved.