Select the product you need help with
FIX: You Cannot Synchronize Between a Replication Publisher and a Replication RepublisherArticle ID: 825025 - View products that this article applies to. BUG #: 356627 (SQL Server 8.0) On This PageSYMPTOMSIf 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:
Error: 8144, Severity: 16, State: 2 ( Procedure or function %.*ls
has too many arguments specified.) RESOLUTIONService pack informationTo 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
(http://support.microsoft.com/kb/290211/
)
How to obtain the latest SQL Server 2000 service packHotfix informationThe 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 WORKAROUNDTo work around this problem, use a different name for the
republisher and the original publisher. STATUSMicrosoft
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 INFORMATIONSteps to Reproduce the ProblemTo reproduce this problem, follow these steps.Note To reproduce the problem, you must have a central publisher, a republisher, and a subscriber.
PropertiesArticle ID: 825025 - Last Review: November 2, 2007 - Revision: 5.4 APPLIES TO
|


Back to the top








