Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
kwilliams
194 Posts |
 Posted - 2003-05-28 : 17:49:40
|
| First, the quick facts:I have replication set up in the following way using SQL Server 7:1) There are 2 servers: an internal server for testing and maintenance of 2 websites (internet & intranet site) and an external server that displays replicated data for the internet site. The internal server is both the Distributor & Publisher.2) There are 4 DB tables in one DB: 3 use Transactional Replication with Push Subscriptions, and the 4th uses Merge Replication with a Pull Subscription.And now the problem:My problem is that this system works pretty well, but every few months the Distributor seems to shut down. The strange thing is that the Replication moniter will show that the replication was successful, even though the data on the external server's DB table didn't get updated. The only way for me to solve this is to completely delete all replication, including the distributor, and then redo it all....this is of course a big waste of time, and I don't know what's going on. Any help from some SQL experts would be helpful. Thanks in advance.P.S. I've looked at the actual job in the Enterprise Mgr's Management folder, and I noticed that the Distribution job keeps executing with this message: "Executing Job Step 2 '(Run agent)'", even after the job has been successful.It's eventually failed or cancelled by the NA.KWilliams |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-05-28 : 18:47:13
|
| Check your SQL Server error log to determine what the error is. There should be an error that corresponds to when the job failed.Tara |
 |
|
|
kwilliams
194 Posts |
Posted - 2003-05-29 : 12:08:47
|
| Hello Tara,I checked the error logs for all of the subscriptions, but they all showed the jobs as being successful. The details section said that there was nothing to update, since nothing had changed (even though it had changed).Concerning the Distributor, it's still running the same job I started yesterday afternoon. It get's stuck on the 2nd step-Run Agent. The only way to stop the job is to manually cancel it. Do you know what may be going on? I know that a lot of these problems only started after I added the merge replicated table to the other for transactional replicated tables. Thanks for any help Tara, or anyone else.KWilliams |
|
|
|
Shastryv
Posting Yak Master
145 Posts |
|
|
VyasKN
SQL Server MVP & SQLTeam MVY
313 Posts |
Posted - 2003-05-29 : 13:08:10
|
| Are you talking about the merge agent that is hanging? If so, next time when it happens, stop the agent. Go to the server directly (distributor in case of push subscription, subscriber in case of pull), open command prompt and run replmerg.exe by passing the required parameters. These parameters can be obtained from the 'Run Agent' job step. See if you get any detailed error messages.Also, try changing the agent schedule from running continuously, to running say, every 5 minutes and see if that makes a difference.--HTH,Vyashttp://vyaskn.tripod.com |
|
|
|
kwilliams
194 Posts |
Posted - 2003-05-29 : 17:03:25
|
| Wow, thanks for all of the great responses. I will go do some debugging, and I'll let you know of the outcome...hopefully a good one. Thanks again.KWilliams |
|
|
|
|
|
|
|
|
Replication/Distribution errors...Pls Help!!!