Replications..
The Process Could Not Execute sp_replcmds
Any ideas?
There are several causes for this error.
Please enable logging as per the below kb article and post the results back here.
http://support.microsoft.com/default...b;EN-US;312292
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"niv" wrote:
> I receive this error for one of my Transactional
> Replications..
> The Process Could Not Execute sp_replcmds
> Any ideas?
>
|||Niv, to run sp_replcmds you have to turn off the logreader, as the
connection you are using needs to effectively become the logreader itself.
Alternatively try sp_repltrans.
HTH,
Paul Ibison
|||I received this:
The step did not produce any output. The step failed.
>--Original Message--
>There are several causes for this error.
>Please enable logging as per the below kb article and
post the results back here.
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;312292
>--
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>
>"niv" wrote:
>.
>
|||Is the log reader stuck on initializing? If so you have to try the following
1) stop SQL Server agent, and restart it to see if this clears the error
2) stop SQL Server, and restart it to see if this clears the error
3) reboot, and see if this clears the error
IF you don't even get the initialization error, please post the command string for your log reader agent here.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Paul Ibison" wrote:
> Niv, to run sp_replcmds you have to turn off the logreader, as the
> connection you are using needs to effectively become the logreader itself.
> Alternatively try sp_repltrans.
> HTH,
> Paul Ibison
>
>
|||Hillary,
I have given up on trying to resolve this issue.
My solution was to delete the transactional replication
that I set up and create a merge replication instead.
Thanks for your help. I appreciate your quick replies and
your expert advice.
niv
BTW: I am sure that I will have a lot more questions for
you in the near future.. so rest up.
>--Original Message--
>Is the log reader stuck on initializing? If so you have
to try the following
>1) stop SQL Server agent, and restart it to see if this
clears the error
>2) stop SQL Server, and restart it to see if this clears
the error
>3) reboot, and see if this clears the error
>IF you don't even get the initialization error, please
post the command string for your log reader agent here.[vbcol=seagreen]
>
>--
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>
>"Paul Ibison" wrote:
logreader, as the[vbcol=seagreen]
the logreader itself.
>.
>
No comments:
Post a Comment