sp_MSadd_logreader_history has too many arguments

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2005 Forums

Replication (2005)

sp_MSadd_logreader_history has too many arguments

Author

Topic

angief
Starting Member

2 Posts

Posted - 2010-12-08 : 18:32:53

I get the following error on my log reader once I setup subscriptions to my Publisher. My Publisher and Distributor are the same server.

'Procedure or function sp_MSadd_logreader_history has too many arguments specified.'.

After reading a few articles online I find that my stored procedure "sp_MSadd_logreader_history" in fact is missing one value when I compare it to my test server replication, which is running fine.

This is on my Production Server
CREATE PROCEDURE sys.sp_MSadd_logreader_history
(
@agent_id int,
@runstatus int,
@comments nvarchar(4000),
@xact_seqno varbinary(16) = NULL,
@delivery_time int = 0, -- Current delivery time (milliseconds)
@delivered_transactions int = 0, -- Running total of session
@delivered_commands int = 0, -- Running total of session
@delivery_latency int = 0, -- Current latency
@log_error bit = 0,
@perfmon_increment bit = 1,
@update_existing_row bit = 0,
@do_raiserror bit = 1
)
AS
BEGIN
This is on my Test Server
CREATE PROCEDURE sys.sp_MSadd_logreader_history
(
@agent_id int,
@runstatus int,
@comments nvarchar(4000),
@xact_seqno varbinary(16) = NULL,
@delivery_time int = 0, -- Current delivery time (milliseconds)
@delivered_transactions int = 0, -- Running total of session
@delivered_commands int = 0, -- Running total of session
@delivery_latency int = 0, -- Current latency
@log_error bit = 0,
@perfmon_increment bit = 1,
@update_existing_row bit = 0,
@do_raiserror bit = 1,
@updateable_row bit = 1 -- used to override history verbose level to decide
-- whether the row being added can be updated by another.
)
AS
BEGIN

A couple of questions.......
How can the stored procedures be different ?
If I script the one that is working on my test server and run an update on my live server will this bring my log reader back in line?

My servers are both SQL Server 2005 SP3
This was a new replication database created on the new production server. I really do not want to have to uninstall a production server and reinstall.

Appreciate any feedback
Cheers
Angie

russell
Pyro-ma-ni-yak

5072 Posts

Posted - 2010-12-08 : 19:22:13

did you see this?

angief
Starting Member

2 Posts

Posted - 2010-12-08 : 20:51:45

Yes, but there is no resolution really.
Cheers
Angie

Angie Field

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources