I've set up transactional replication with queued updating. If I stop the queue reader agent through EM, I can't start it again. Agent's history says "Queue Reader aborting. The step failed."
All servers are SQL Server 2000 SP3.
Help is greatly appreciated!OK, I found what my problem was (actually not really mine - it's all EM's fault). When you stop the Queue Reader agent through EM, in reality that process is not stoped, but continues to run on the machine. However, the EM doesn't see it and when you try to start it again, of course , it doesn't want to start another instance of Queue Reader agent.
Basically, I had to go and manually stop the process, and only then start it again through EM.
Bad, bad Enterprise Manager!
Saturday, February 25, 2012
Queue Reader agent fails to start when stopped through Enterprise Menager
Labels:
agent,
database,
enterprise,
fails,
menager,
microsoft,
mysql,
oracle,
queue,
queued,
replication,
server,
sql,
transactional,
updating
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment