Post reply

Snapshot Replication error

  • May 13, 2004 at 12:54 am

    #82673

    This is a rare one for me! I have been configuring SQL Server Replication for 4.5 years now and must say I'm very fluent with it however, I have never seen this error before!

    "sp_MSset_subscription_properties has too many arguments"

    I'm basically just trying to perform a Snapshot of a Database from 1 SQL Server to another.

    Both SQL Servers are running SQL 2000 with SP3a.

    Hopefully someone can assist me!

    Kindest Regards,

  • May 13, 2004 at 6:24 am

    #506281

    That sp is executed when you add the subscription.

    Are you using EM or sp_addsubscription? If using sp, then check the parameters that you are using because it seems that a parameter may be wrong.

  • May 13, 2004 at 5:10 pm

    #506392

    racosta,

    I configured and setup the Subscription via EM. This is a bit of a worry when EM has done this! Not sure what to do from here!

    Kindest Regards,

  • May 13, 2004 at 5:22 pm

    #506394

    1 more thing!

    This error occurs when SQL Server attempts to perfrom the snapshot.In other words the schema & data files getcreated successfully but fails whit that error when the snapshot starts.

    Kindest Regards,

  • May 13, 2004 at 9:18 pm

    #506403

    I havediscovered the problem. It is to do with 2 different service packs on the 2 SQL Servers.

    Kindest Regards,

  • January 26, 2005 at 9:56 am

    #539179

    I'm relatively new at setting up Replications in a real world enviroment and I've been experiencing the same problem above.  I checked both servers and they are both SQL 2000 SP3.  Is there any patches or other fixes out there?

    Thanks

    Debbie

  • April 19, 2005 at 11:58 pm

    #553646

    I had a similar error stating "sp_MSset_subscription_properties has too many arguments" while setting up transactional rep. from a server on 2003 (SQL standard) to and XP desktop (personal SQL). I tracked the sp down in the master database on the server and compared it to the version on the desktop's master db. They were different with differning numbers of arguments (thus the error) even though both have the same service packs (sp_server_info and select @@version show this). Many other sp's have different dates so I'm not sure if the service pack ran properly as I didn't set it up.

    I copied the server version of sp_MSset_subscription_properties accross to the desktop and got the next error stating it couldn't find the table MSsubscription_agents (which I could see in the subscription dbase). All the sp seems to do is update some of the values in MSsubscription_agents, so I did this manually and temporarily edited the sp so it would do nothing (thus succeding) and then reset it back to it's original form after replication started. We have a fair few replications going so I could compare the MSsubscription_agents tables.

    Now I don't know why the SQL's were different but it works now so I'm happy, but I am expecting it to fall down around my ears so I'm watching it carefully.

  • April 20, 2005 at 10:33 am

    #553840

    For some reason (it has happened to me ) reapplying sp3 seems to "cure" these kind of problems sometimes

     


    * Noel

  • April 25, 2005 at 6:06 pm

    #554732

    That's good to know it's not just my computers.

    Cheers

    Fred

Viewing 9 posts - 1 through 8 (of 8 total)

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