FIX: sp_MsHelpmergeconflictcounts Returns No Row Against the Chinese Name Table on English Windows 2000

This article was previously published under Q298923
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 235027 (SHILOH_BUGS)
After changing the locale on your server from English to Chinese (PRC) and setting up merge replication, if the publishing table name has Chinese characters, running the sp_MsHelpmergeconflictcounts stored procedure against the publication will have nothing returned. You can expect conflict counts instead.
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.

Steps to Reproduce Behavior

  1. On an English Windows 2000 server, set the locale to Chinese (PRC).
  2. From SQL Server Query Analyzer, execute the following code:
    -- create a table with Chinese name table on pubs database , where ?? is 2 Chinese Charactersuse pubsgoCREATE TABLE [dbo].[??] (	[c1] [int] NULL ) ON [PRIMARY]insert into  [??] values(1)					
  3. From SQL Enterprise Manager, choose the Replication wizard, choose the Configure Publishing and Distribution wizard, and then create a merge publication on the table.
  4. Create a push subscription to the Northwind database at the local server.
  5. Run the merge agent. Both tables shohld have one row with the value 1 on column c1.
  6. Change the value 1 on table [??] in the Pubs database to 2, and change it to 3 in the Northwind database at about the same time.
  7. Run the merge agent again, and the last action on the merge agent will show "merged one data changes ( ....1 resolved conflicts)".
  8. From Query Analyzer, execute the following:
    -- expect one row to indicate the conflict counts but no row returneduse pubsgosp_MsHelpmergeconflictcountsgo					

Article ID: 298923 - Last Review: 01/16/2015 22:36:57 - Revision: 3.3

Microsoft SQL Server 2000 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix kbsqlserv2000sp1fix KB298923