May 11, 2005 at 1:01 pm
My replication is transactional and I have two servers it replicate to one server continuously and another every 15 minutes. It was working until the upgrade of backupExec was done.
I did restart the server and SQLAgent, removed my subscriber and publication and recreated it even then I could not make it work.
Now I have asked my IT person to uninstall BackupExec and SQLServer instance and it was done fine. I just now created a Transactional agent and try to run it and it still gives me "The agent is suspect. No response within last 10 minutes". I also created an snapshot agent it also gave me the same error.
I looked in to the distribution database for records all my publication, subscriber and other information is registered.
Could any one help me find out the mystery.
Thanks in advance.
--Senthil.
May 13, 2005 at 5:07 am
This indicate that replication agent is too busy to respond while EM polls it.There can be many reason it will become busy.you have to change the refresh rate setting value to high under replication monitor.Also the agent suspect is an informational message and the following link may useful to u to find reason behind that
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q285106
May 18, 2005 at 3:21 am
I am not too clear from your post exactly which agent gives this message - it seems it is both agents. If it is the distribution agent, use the current activity window to find the relevant SPID and then double click to see what it is doing. This message is not necessarily an error message - I get it when the indexes are being created on the subscriber after a huge snapshot. If the message appears when creating the snapshot, configure the Veritas software to avoid the snapshot folders and see if this helps.
HTH,
Paul Ibison, SQL MVP
Paul Ibison
Paul.Ibison@replicationanswers.com
January 25, 2007 at 1:01 pm
Just a quick addition to the thread.
We encountered the same error message when adding replication back to the master server after making some schema changes and adding new publications. The sp_addpublication_snapshot line for the new publications had been copy-pasted from an existing one and modified. On one of the new sp_addpublication_snapshot lines we neglected to modify the name of the snapshot agent job, which resulted in an invalid setting in the MSsnapshot_agents table in the Replication_DB.
The fix was to correct the oversight in the script, delete the publication (we just used EM for the delete) and then rerun the scripts for that one publication.
January 29, 2007 at 2:21 am
Hi I got the same message.
It was fixed by increasing the query timeout
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply