I have created the new replication. Now what is issue I am facing:
When I go to start the 'View Agent Snapshot Status'
Its just start working and First line shows "Starting Agent" and just keep working, working and continuously working.
..
After sometime it show the following message: "The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active."
I try the following solution that I found, I have increased the value of @HeartBeat_interval property of distributor from 10 to 30 but no success.
I have Sql Server 2008 R2.
any help will be appreciated really.
Find errors with the Distribution Agent. The Distribution Agent finds data in the distribution database and then applies it to the subscriber. Connect to the publisher in SQL Server Management Studio. Expand the server node, right-click the Replication folder, and then select Launch Replication Monitor.
Replication uses a number of standalone programs, called agents, to carry out the tasks associated with tracking changes and distributing data. By default, replication agents run as jobs scheduled under SQL Server Agent, and SQL Server Agent must be running for the jobs to run.
If the SQL Server Agent Service is not running, this means that all the jobs created under that instance are not working, including the replication agent jobs. As a result, the overall replication site is not working.
Connect to the Subscriber in Management Studio, and then expand the server node. Expand the Replication folder, and then expand the Local Subscriptions folder. Right-click the subscription you want to monitor, and then click View Synchronization Status.
May be this will help to someone else:
I did the following changes and my replication is working perfect.
1 - Job username and Job password must have full access and permission of windows.
2 - You must be logged In to user that you will use in the replication script to create replication.
That's all.
Thanks!!
I had the same behavior. some of my articals are huge. while the replica's synch was over, the agent hanged up with the same message as yours. after ~20 minutes it began running as expected. I thought it is not not normal behavior, but after creating my second subscription, the error appeared again. it was gone approximately after 20 minutes.
I believe it is encounters high load of data (in case it is) and hangs up for while. hope it helps
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With