Is this a network drive? If you are running this task as a service you need to set a userid/password for the service, see http://blog-en.gdpsoftware.com/2010/04/watchdirectory-tasks-as-windows-service.h...

The Task will retry when you configure it to do so.

So you only have  to wait 1000 seconds between each attemp to reconnect. 1000 seconds are ~ 16 minutes.

Maybe you want to lower that....

If your network drive get lost because of a network error, the task stays green and try to reach the network again after the time period you have configured.

In your case:

Quote:


at 13:05:54 the problem occured,
and at 13.22.34 - this is exactly 16,5minutes = 1000 seconds later -  the next try found the Network resource reachable again and was able to watch the directory again:

Quote:


Everthing looks good as you have configured it this was.


Now you need to know that if you use the Fast Monitoring Method Windows at the watched computer informs WatchDirectory about the detected changes. When the network connection is dropped, this notification can get lost, so WatchDirectory never knows about the Change - and does not process anything.

I recommend to change the monitor method into "polling" with an reasonable intervall. With this setting WatchDirectory itself will scan the target and found the changes happened during the network connection was interupted.

The task does reconnect to the network drive, the log you send confirms this:

Quote:


Please try the polling method to see if it solves the problem.

Thanks for the explanation I will change it to polling.

Best regards,

Ruud