I have a file event trigger that has just stopped a few times since I set it up. It isn't deactivated, there are no errors in VC's log or in the system log. I was notified that there was a problem today and when I opened the task it started working again - I hadn't saved it or anything, I literally double clicked and saw it start running again. It monitors a shared folder on a Win2003 server using a UNC path. Any ideas or anywhere else I should be looking?

This can happen if the connection to the server is lost in some way (network disturbance or that server restarts).

What you can do is to increase the retry times on the File Trigger.

---