WatchDirectory home page
WatchDirectory Startseite (Deutsche Version)
Site WatchDirectory (Français)
  Welcome, Guest. Please Login or Register
YaBB - Yet another Bulletin Board
Page Index Toggle Pages: 1
WatchDirectory tasks are not executing (Read 2589 times)
YaBB Newbies

Posts: 1
WatchDirectory tasks are not executing
Jul 20th, 2011 at 10:14pm
We are using WatchDirectory version watchDirectory Professional 4.6.5. We have multiple task configured in the WatchDirectory. These tasks use 'Fast' method to detect file events. The files are on a Network Drive. Sometimes these services stop working (running but not responding to file events). We don't know if this is because of connection lost from Network drive or some other factor is contributing to this. Few questions:

1. Is there a way to find out what would be causing the tasks to not trigger even after the generation of event? logs/dumps anything?
2. Is there a log where we can see watch directory lost connection so that we can write a script to restart watch directory and associated services?
3. What would be the best method to monitor the file events that are occuring over network drives?
4. If there is a an issue with network drive and not closing the handle for task, has this been fixed in any subsequent relese?

Back to top
IP Logged
YaBB Administrator

Posts: 669
South Germany
Re: WatchDirectory tasks are not executing
Reply #1 - Jul 21st, 2011 at 8:33am
How many task have you running under the same user account as windows services? How many services at all are running under that user account on your server?
Back to top

Viele Grüße / Best regards
Dirk - GdP Software

dirk [at] gdpsoftware [dot] com
IP Logged
YaBB Administrator

Posts: 2260
The Netherlands
Re: WatchDirectory tasks are not executing
Reply #2 - Jul 21st, 2011 at 8:36am

WD's FAST and DEFAULT monitoring methods rely on the operating system to detect and deliver events to WD. When you are monitoring network drives, you have the network and the remote computer thrown into the mix.
We have been looking at issues where at the remote side, the "handle" to the monitored directory is closed without notifying the "local" computer (so WD could detect it). Solving this little puzzle is hard.

Your best option is to switch the monitoring method to "Polling" or "File Age" for network drives.

About your other question (the log), see this blogpost:
Back to top

Gert Rijs - gert (at) gdpsoftware (dot) com
End Alzheimer's:
WWW WWW GdPSoftware  
IP Logged
Page Index Toggle Pages: 1