Friday, February 24, 2012

Agent is suspect

I'm getting this error on the distribution agent. Am I correct when I say
this would be expected in a testing environment where transactions are not
being processed by the database regularly? I have now up'd the inactivity
threshold to like 720 :-)
Also, what’s the best way to recover and/or bypass the error?
Thanks,
Mark
You are not correct that you will get this error when there are no
transactions to be applied - you get this message when the agent is busy. I
would investigate what the agent is hanging on using profiler on the
subscriber or by doing logging.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"mrprice" <mrprice@.discussions.microsoft.com> wrote in message
news:F4B92F11-ECEC-41BF-8B6C-5F0DA2F179D8@.microsoft.com...
> I'm getting this error on the distribution agent. Am I correct when I say
> this would be expected in a testing environment where transactions are not
> being processed by the database regularly? I have now up'd the inactivity
> threshold to like 720 :-)
> Also, what's the best way to recover and/or bypass the error?
> Thanks,
> Mark

No comments:

Post a Comment