Post reply

Error 8144 - Too Many Arguments Specified - setting up merge replication

  • February 8, 2005 at 7:33 am

    #165899

    Hi, all.

    I'm trying to set up merge replication between our location (server1) and our co-located SQL Server machine at our ISP (server2).  I've created the publication and the subscription, but whenever I attempt to start the replication, I get the following error:

    "Procedure or function sp_MSaddinitialarticle has too many arguments specified.  (Source: SERVER2 (Data Source); Error number: 8144)

    -------------------------------------------------------------------

    The process could not deliver the snapshot to the Subscriber. (Source: Merge Replication Provider (Agent); Error number -2147201001)"

    Server1 is running MS SQL 2000 SP3a on Windows 2003 Server, and Server 2 is running MS SQL 2000 SP3a on Windows 2000 Server.  I had both machines on Windows 2000 server at one point, and had the same issue.

    So far I've reinstalled SQL Server on Server1 and re-created the table so that it had contiguous colid's.  I haven't been able to find much on this error, other than what it already states (too many arguments).

    Thanks in advance!

    -Chris

     

  • February 9, 2005 at 6:50 am

    #541345

    I had a very similiar problem with transactional replication but I can't remember the stored procedure name.  It wound up being a failed SP3 (or 3a) upgrade on the sunscriber.  I presume the failure could be on either server though and cause a similiar problem.  Both servers in my situation reported the same SP level, but upon investigation of the actual stored procedure one was not up to date - it had gotten missed in the upgrade.  A reapply of the service pack fixed it.  The servers in my situation were both also supposed to be running SP3 or 3A - I can't remember which at the time.

     

     

  • February 9, 2005 at 8:42 am

    #541369

    That did it.  Thanks!

    The other issue that I ran into was that the server's DNS name was different from the NetBIOS name (and hence the SQL Server name).  Figured that one out on my own, though. 

     

  • February 9, 2005 at 8:49 am

    #541371

    I'm just glad I could help.  Sometimes I think I'm the only one that strugles with obscure problems.  Just don't seem like they happen to other people...

  • February 10, 2005 at 11:00 am

    #541632

    >>Sometimes I think I'm the only one that strugles with obscure problems.  Just don't seem like they happen to other people... <<

    For what is worth: A LOT OF US THINK THE SAME AS YOU DO


    * Noel

  • March 8, 2007 at 10:30 am

    #693882

    Just wanted to add my thanks - we had two MSSQL 2000 servers, and on trying to set up a new replication, I got the same error message. Existing replications were fine. Running @@version on each server showed both were patched the same:

    8.00.2039

    I re-applied SP4 to one of the servers, rebooted and then a new replication worked without a hitch. Must have been something not quite right the first time SP4 was applied.

    Thanks for your help.

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply