Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Replication Issue on SQL 2005 sp3 64bit win2k r2 sp2

57 views
Skip to first unread message

RG

unread,
Aug 12, 2010, 4:18:03 PM8/12/10
to
Looking at the log below, why would I get this error? I found that bunch of
stored procedures were invalidated at around the same time. Could this have
something to do with it?

Thanks in advance

2010-08-12 00:00:35.78 spid17s This instance of SQL Server has been
using a process ID of 1592 since 8/11/2010 8:08:22 AM (local) 8/11/2010
12:08:22 PM (UTC). This is an informational message only; no user action is
required.
2010-08-12 09:27:17.60 spid64 Error: 14151, Severity: 18, State: 1.
2010-08-12 09:27:17.60 spid64 Replication-Replication Transaction-Log
Reader Subsystem: agent MYSERVER-apdb-6 failed. The process could not execute
'sp_replcmds' on 'MYSERVER'.
2010-08-12 09:28:18.47 spid206 Error: 14151, Severity: 18, State: 1.
2010-08-12 09:28:18.47 spid206 Replication-Replication Transaction-Log
Reader Subsystem: agent MYSERVER-apdb-6 failed. The process could not execute
'sp_repldone/sp_replcounters' on 'MYSERVER'.
2010-08-12 09:29:19.20 spid156 Error: 14151, Severity: 18, State: 1.
2010-08-12 09:29:19.20 spid156 Replication-Replication Transaction-Log
Reader Subsystem: agent MYSERVER-apdb-6 failed. The process could not execute
'sp_repldone/sp_replcounters' on 'MYSERVER'.
2010-08-12 09:30:19.92 spid174 Error: 14151, Severity: 18, State: 1.
2010-08-12 09:30:19.92 spid174 Replication-Replication Transaction-Log
Reader Subsystem: agent MYSERVER-apdb-6 failed. The process could not execute
'sp_repldone/sp_replcounters' on 'MYSERVER'.
2010-08-12 09:31:20.65 spid218 Error: 14151, Severity: 18, State: 1.
2010-08-12 09:31:20.65 spid218 Replication-Replication Transaction-Log
Reader Subsystem: agent MYSERVER-apdb-6 failed. The process could not execute
'sp_repldone/sp_replcounters' on 'MYSERVER'.
2010-08-12 09:32:21.36 spid198 Error: 14151, Severity: 18, State: 1.
2010-08-12 09:32:21.36 spid198 Replication-Replication Transaction-Log
Reader Subsystem: agent MYSERVER-apdb-6 failed. The process could not execute
'sp_repldone/sp_replcounters' on 'MYSERVER'.
2010-08-12 09:33:22.10 spid89 Error: 14151, Severity: 18, State: 1.
2010-08-12 09:33:22.10 spid89 Replication-Replication Transaction-Log
Reader Subsystem: agent MYSERVER-apdb-6 failed. The process could not execute
'sp_repldone/sp_replcounters' on 'MYSERVER'.
2010-08-12 09:34:22.80 spid119 Error: 14151, Severity: 18, State: 1.
2010-08-12 09:34:22.80 spid119 Replication-Replication Transaction-Log
Reader Subsystem: agent MYSERVER-apdb-6 failed. The process could not execute
'sp_repldone/sp_replcounters' on 'MYSERVER'.
2010-08-12 09:35:23.52 spid95 Error: 14151, Severity: 18, State: 1.
2010-08-12 09:35:23.52 spid95 Replication-Replication Transaction-Log
Reader Subsystem: agent MYSERVER-apdb-6 failed. The process could not execute
'sp_repldone/sp_replcounters' on 'MYSERVER'.
2010-08-12 09:36:24.24 spid153 Error: 14151, Severity: 18, State: 1.
2010-08-12 09:36:24.24 spid153 Replication-Replication Transaction-Log
Reader Subsystem: agent MYSERVER-apdb-6 failed. The process could not execute
'sp_repldone/sp_replcounters' on 'MYSERVER'.

Ben Thul

unread,
Aug 13, 2010, 10:00:38 AM8/13/10
to
I'd check a couple of things:

1) Does the stored procedure exist at the publisher? If not,
something turned replication off in that database.
2) Does whatever account you're using for the logreader to connect to
the publisher have db_owner at the publisher database? According to
BOL, that's what it needs (sad, but true).

If neither of those point you in the right direction, I'd set up a
trace for sp_replcmds at the publisher and see what error it's
getting.

HTH,
Ben

RG

unread,
Aug 13, 2010, 2:42:06 PM8/13/10
to
> 2) Does whatever account you're using for the logreader to connect to
> the publisher have db_owner at the publisher database? According to
> BOL, that's what it needs (sad, but true).

I am assuming it is whatever user running sqlagent. This is interesting,
because that user doesn't have dbo privileges to the publisher db. Now, the
user that sqlagent runs under is local administrator. Shouldn't have all the
privileges under the sun? If, in fact, this is the cause, what kind issues
does this create?

Thanks again

"Ben Thul" wrote:

> .
>

Ben Thul

unread,
Aug 13, 2010, 4:59:44 PM8/13/10
to
It depends; if you left BUILTIN\Administrators in the sysadmin group,
then yes, it should be able to do anything on the box. What did the
sql trace turn up? Without knowing what error is being thrown, it's
difficult to prescribe a solution.
--
Ben
0 new messages