Stephanie,
I'd enable logging then restart the agent.
http://support.microsoft.com/?id=312292
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Hi all,
I found that the distribution agent was stopped unexpectedly for
transactional replication in MSSQL2005 and there is no error captured in the
job history, replication monitor or event log. I can only find out the
suspect entry in trace when the the time of agent stop.

dbcc incrementinstance ("SQL Replication Agents", "Running", "Distribution",
-1)

Is there any way to find out the reason? Thanks in advance

Up to this moment, can't find any idea from the log.
From the SQL agent history, the distribution agent delivered some commands
and stop 'successfully' with the summary as below.
But I found that the replication would stop in some tables with triggers.
will the distribution agent stop by trigger error handling,e.g. rollback,
raiserror ? Thanks in advance

===================================
Message
11-06-2006 15:40:57

Total Run Time (ms) : 157261656 Total Work Time : 329220
Total Num Trans : 178 Num Trans/Sec : 0.54
Total Num Cmds : 2 Num Cmds/Sec : 0.01
Total Idle Time : 156088606

Writer Thread Stats
Total Number of Retries : 13
Time Spent on Exec : 0
Time Spent on Commits (ms): 0 Commits/Sec : 85.72
Time to Apply Cmds (ms) : 0 Cmds/Sec : 0.00
Time Cmd Queue Empty (ms) : -156088606 Empty Q Waits > 10ms: 0
Total Time Request Blk(ms): 0
P2P Work Time (ms) : 0 P2P Cmds Skipped : 0

Reader Thread Stats
Calls to Retrieve Cmds : 31419
Time to Retrieve Cmds (ms): 329220 Cmds/Sec : 0.01
Time Cmd Queue Full (ms) : 0 Full Q Waits > 10ms : 0
*******************************************************************************

2006-11-06 07:40:57.760 A total of 178 transaction(s) with 2 command(s) were
delivered.

Executed as user: ccbhk.com\ccbadmin. The replication agent completed
successfully. See the previous job step history message or Replication
Monitor for more information. The step succeeded.






[quoted text, click to view]