Dear Experts

No matter what I do, my replication does not work, and there is no information applicable on the MS support site. This is the error that I get. I am trying to replicate a single table from one server to another, transactional replication. My table is 'hclientcalls'

Connecting to Subscriber 'EMERGSERVER' Connecting to Distributor 'EMERG' Initializing

37000 Could not find stored procedure 'sp_MSupd_hclientcalls'. 2812 Error executing a batch of commands. Retrying individual commands. Agent message code 20046. Could not find stored procedure 'sp_MSupd_hclientcalls '. Category:COMMAND Source: Failed Command Number: Message: {CALL sp_MSupd_hclientcalls (NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NU LL,NULL,NULL,NULL,NULL,30,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL ,NULL,NULL,NULL,NULL,0,0,NULL,NULL,NULL,NULL,NULL,0,NULL,NULL,1,1,0x0020000000)}

Category:SQLSERVER Source: EMERGSERVER Number: 2812 Message: Could not find stored procedure 'sp_MSupd_hclientcalls'.

-- Anonymous, May 07, 2002

Answers

Frederico,

This probably happens because you decided not to synchronize the articles (meaning drop & create).

One solution is to, when defining the articles to publish, use regular replication. When you use the wizard to define the articles (tables) you want to publish, you will see a little button on the right of the table name. Press it and choose not to use stored procedures.

Another solution is to create the replication SP's manually. You should run scripting SP's for each article in sysarticles to get the script for these SP's and run them on the subscriber.

The scripting SP's are sp_scriptdelproc, sp_scriptinsproc, and sp_mappedupdproc.

Hope this helps,

Eric

-- Anonymous, May 08, 2002