I am having an issue when running WD as a service against a newtork directory.  Everything works fine for several days and then stops working.  I need to stop the WD service and restrart the WD service so that it will recogonize the any new files after the restart.

The service was created with the follwoing parameters:

Directory  to watch : \\ameri\d$\ftp\FTPSHE
Monitoring Method used : polling 60 seconds
FILENEW (only)
Hide watchDirectory
NT4 Compatibility fix
if connection lost... 10 times
verbose ouput
service friendly

it is watching a directory in the same workgroup and the watched directory is on a Windows 2000 SP4 machine.  watchDirectory is running on a Windows 200 SP4 machine.

Any help would be greatly appreciated.

Gert, i had the same problem as well. I got around it by restarting the service frequently. I am using Fire Daemon to run the service now. I was originally using the built in tool, but had the same results.

I am having the same problem with both local and network drives.
WD will  work fine for a while and then ignore files, i.e. there are files in the watched folders but they are not processed, in this case ftp'd.
I have found that restarting the service will not always send the files involved, even though I have it looking for new files on startup.
I have to remove the files from the watched folder and put them back.
It will then work again for a while.
I have tried Fast, Default and Polling, all do the same.

Gert,

I am still experiencing issues with WD.  I followed your directions above and tried attaching a backup to this message.  Becasue of the size of the zip file, it did not work.  Is there a direct email address I can send it to or an FTP site?

Basically every thing will run fine for several days, a few errors will be logged and then WD no longer processes files.  If I stop and restart, WD will find the new files.

Any help would be greatly appreciated.

Thanks,

Bill

I just uploaded the file. 

Thanks for your great support.

Bill Geoghan