FIX: You Cannot Synchronize Between a Replication Publisher and a Replication Republisher

This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 356627 (SQL Server 8.0)
SYMPTOMS
If you have a republisher (also known as a publishing subscriber) that has the same name as the original publisher, and you make schema changes to an article on the original publisher, the subscriber may not synchronize with the republisher. You may receive an error message that is similar to one of the following in the agent history of the republisher:
  • The row was inserted at <central publisher> but could not be inserted at <republisher>. Procedure or function sp_ins_<guid> has too many arguments specified.
  • The row was updated at <subscriber> but could not be updated at <republisher>. Procedure or function sp_upd_<guid> has too many arguments specified.
Additionally, if you run a trace session by using SQL Profiler on the computer where the republisher is running, you may receive an error message that is similar to the following in the trace window:
Error: 8144, Severity: 16, State: 2 ( Procedure or function %.*ls has too many arguments specified.)
RESOLUTION

Service pack information

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 How to obtain the latest SQL Server 2000 service pack

Hotfix information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version            Size    File name   -------------------------------------------------------------------   31-May-2003  06:15  2000.80.818.0      78,400  Console.exe         24-Jun-2003  12:31  2000.80.818.0      33,340  Dbmslpcn.dll        24-Apr-2003  13:42                    786,432  Distmdl.ldf   24-Apr-2003  13:42                  2,359,296  Distmdl.mdf   29-Jan-2003  13:25                        180  Drop_repl_hotfix.sql   23-Jun-2003  10:10  2000.80.837.0   1,557,052  Dtsui.dll           23-Jun-2003  10:10  2000.80.837.0     639,552  Dtswiz.dll          23-Apr-2003  14:21                    747,927  Instdist.sql   02-May-2003  13:26                      1,581  Inst_repl_hotfix.sql   07-Feb-2003  18:10  2000.80.765.0      90,692  Msgprox.dll         31-Mar-2003  13:37                      1,873  Odsole.sql   04-Apr-2003  13:16  2000.80.800.0      62,024  Odsole70.dll        07-May-2003  08:11  2000.80.819.0      25,144  Opends60.dll        02-Apr-2003  09:18  2000.80.796.0      57,904  Osql.exe            02-Apr-2003  10:45  2000.80.797.0     279,104  Pfutil80.dll        22-May-2003  10:27                     19,195  Qfe469571.sql   11-Jul-2003  04:34                  1,084,147  Replmerg.sql   04-Apr-2003  09:23  2000.80.798.0     221,768  Replprov.dll        07-Feb-2003  18:10  2000.80.765.0     307,784  Replrec.dll         11-Jul-2003  04:26                  1,085,925  Replsys.sql   31-May-2003  12:31  2000.80.818.0     492,096  Semobj.dll          31-May-2003  05:57  2000.80.818.0     172,032  Semobj.rll   28-May-2003  11:59                    115,944  Sp3_serv_uni.sql   31-May-2003  12:31  2000.80.818.0   4,215,360  Sqldmo.dll          07-Apr-2003  05:14                     25,172  Sqldumper.exe       19-Mar-2003  05:50  2000.80.789.0      28,672  Sqlevn70.rll   01-Jul-2003  11:48  2000.80.834.0     180,736  Sqlmap70.dll        07-Feb-2003  18:10  2000.80.765.0      57,920  Sqlrepss.dll        10-Jul-2003  09:30  2000.80.840.0   7,553,105  Sqlservr.exe        07-Feb-2003  18:10  2000.80.765.0      45,644  Sqlvdi.dll          24-Jun-2003  12:31  2000.80.818.0      33,340  Ssmslpcn.dll        31-May-2003  12:31  2000.80.818.0      82,492  Ssnetlib.dll        31-May-2003  12:31  2000.80.818.0      25,148  Ssnmpn70.dll        31-May-2003  12:31  2000.80.818.0     158,240  Svrnetcn.dll        31-May-2003  06:29  2000.80.818.0      76,416  Svrnetcn.exe        30-Apr-2003  11:22  2000.80.816.0      45,132  Ums.dll             01-Jul-2003  11:49  2000.80.834.0      98,816  Xpweb70.dll         23-Jun-2003  10:10  2000.80.837.0   1,557,052  Dtsui.dll           23-Jun-2003  10:10  2000.80.837.0     639,552  Dtswiz.dll          02-Apr-2003  09:18  2000.80.796.0      57,904  Osql.exe            02-Apr-2003  10:45  2000.80.797.0     279,104  Pfutil80.dll        31-May-2003  12:31  2000.80.818.0     492,096  Semobj.dll          31-May-2003  05:57  2000.80.818.0     172,032  Semobj.rll   31-May-2003  12:31  2000.80.818.0   4,215,360  Sqldmo.dll          07-Apr-2003  05:14                     25,172  Sqldumper.exe       31-May-2003  12:31  2000.80.818.0     158,240  Svrnetcn.dll        31-May-2003  06:29  2000.80.818.0      76,416  Svrnetcn.exe 				
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
WORKAROUND
To work around this problem, use a different name for the republisher and the original publisher.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
MORE INFORMATION

Steps to Reproduce the Problem

To reproduce this problem, follow these steps.

Note To reproduce the problem, you must have a central publisher, a republisher, and a subscriber.
  1. Set up a publication named "A" to act as a central publisher.
  2. Set up a push subscription from the central publisher.
  3. On the subscriber that you set up in step 2, set up a publication that has the same name as the central publisher ("A") to act as a republisher.
  4. Set up a push subscription from the republisher to a subscriber.
  5. Make sure that the initial snapshots are applied on each subscriber.
  6. On the central publisher, add a column to the published table. For more information about how to add a column, visit the following Microsoft Web site:
  7. Insert a row in the published table on the central publisher.
  8. Run the Merge Agent on the central publisher to synchronize the data with the republisher.
  9. Click the publisher, and then view the conflicts.

    You may receive one of the error messages that are mentioned in the "Symptoms" section of this article.
Properties

Article ID: 825025 - Last Review: 02/27/2014 21:19:34 - Revision: 5.4

  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000, Workgroup Edition
  • Microsoft SQL Server 2000 Desktop Engine (Windows)
  • Microsoft SQL Server 2000 Enterprise Edition 64-bit
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbqfe kberrmsg kbreplication kbsqlserv2000presp4fix kbfix kbbug KB825025
Feedback