April 22, 2003 at 7:47 am
I am having trouble starting the distribution agent. The error message states that it 'Cannot drop the procedure 'sp_MSins_fund_recent_assets', because it does not exist in the system catalog.'
Any help explaining what this means would be extremely helpful!
Thanks,
Sandy
April 22, 2003 at 9:27 am
It seems that you are replicating stored procedures and you deleted one in the publisher, but sql coudn't deleted in the subscriber because it didn't exists.
You can create the stored procedure in the subscribers that is showing the error and re run the distribution agent, Or you can also ignore the error in the distribution agent profile.
To do this with EM, click over the replication monitor, then click over the publication, right click over the dist. agent and select Agent Profile.
You can create a new profile to specify the error number in skip errors,
or you can use the builtin profile "Continue on data consistency errors. "
to let SQL to skip it for you
April 22, 2003 at 9:35 am
Thanks for responding racosta!
I believe that the stored procedure sp_MSins_fund_recent_assets is the procedure created during replication used to insert records into my fund_recent_assets table. I have removed and added the subscription a couple of times now hoping to reinitialize, but it still is not creating the sp_MSins procedure for me.
The subscriber recently changed the username/password we use for replicating to them (used to be the sa user). Could this have anything to do with the problem?
Thanks,
Sandy
April 22, 2003 at 9:58 am
Yes you are right, that sp is used by sql toreplicate the updates. You should create the stored procedure again. You can use
the stored procedure:
EXEC sp_scriptdynamicupdproc @ArtID
to let SQL to create the stored procedure for you. You can find the Article ID of the table fund_recent_assets in distribution.dbo.MSArticles or also use sp_helpArticle.
Or you can also use scriptpublicationcustomprocs @Publication
to let SQL to create all the inserts, updates and deletes stored procedures
of the entire publication.
With the question about the password, I don 't think so, because the error is different. To see the user that the distribution agent is using you should check with EM the job of the distribution agent, the second step executes the distrib.exe command to start the distribution. One of the parameters is -SubscriberLogin and -SubscriberPassword, you should change it
or added it if you change the password.
To avoid problems when changing the sa password, I change my replication to use windows authentication,
by changing the -DistributorSecurityMode option to 1
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply