This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 356627 (SQL Server 8.0)
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.)
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
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.
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
To work around this problem, use a different name for the republisher and the original publisher.
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.
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.
Set up a publication named "A" to act as a central publisher.
Set up a push subscription from the central publisher.
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.
Set up a push subscription from the republisher to a subscriber.
Make sure that the initial snapshots are applied on each subscriber.
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:
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