Gert,

We have been unable to keep WD running today, all of the Plugins have crashed at some stage.
Some will run for a while but then crash as soon as they have processed a file.
They include zip and unzip, ftp, move.

We moved all of the processes onto a different pc and had the same issues.

I have attached a zip file of the history db's for all processes.

I have included all history db's I could not remember which ones gave the most problems.

I hope you can shed a bit of light on this.

Cheers

Jim

Hello Jim,

I can not see any real error in the history databases.

Did you install the ftp plugin from the beta forum? In that case you may want to go back to the original.
Otherwise:
Can you enable "write debug info" for one task, and start it again, I am interested in that history.db, please email it to me.

Gert

Jim,

The db shows that the plugin is called for a DELETED file. As this plugiun doesn't support the FILEDEL event, it crashes. I wonder what your settings on the events page ( http://www.watchdirectory.net/wdhelp/help/wdnewconfigpage4.html ) are.
Gert

Gert,

The problem may be with some files created by Macintosh OSX.

It creates a *.DS_Store file in the directories monitired by WD and it seems that WD will not delete it.

I have added an exception to the configs so that it ignores these files.

I notice that you have a global ignore directories setting, could one for global file ignore be added?

So that files of this type are not processed by all configs.

What does WD do with read only files? Could this cause the same issue?

Cheers

Jim

Gert,

Still getting plugin crashes.

This is the email message I get from wd

Plugin returned errorcode -1. Error message=No further info. watchDirectory will abort
Date/Time: 18/04/2006 3:50:21 PM
Computer: ~

Attached is a zip of the history file for this particular config.

It appears to crash after each file it ftp's.

This was a new config.  I trashed all of the others.

Cheers

Jim

Edited by Gert: removed attachment

Hello Jim,

When I look at the history database, I see an event for a "deleted file" (the one just uploaded, I assume you have "delete file after upload" checked).
As the FTP plugin does not support FILEDEL events, it returns -1. Can you send me the config file for this task (change your FTP password first if you like):

<task directory>\<yourtaskname>.config
<task directory>: press CTRL+9 inside the watchDirectory Control Center to explore this directory
<yourtaskname>: the name of your task

It looks like the FILEDEL event is enabled (it should not be). If you open the <task>.config with notepad, and search for "evtFileDel" it should be:

evtFileDel=-1

Gert

Jim,

Quote:

the evtXXX settings can have 3 values:
-1: this event is not supported (grayed out)
0: this event is supported, but not selected by you
1: this event is supported and selected by you

However, the gui also checks the wdopAutoFtp.dll to see if it supports filedel. The actual "runtime" (wdRun.exe) does not do these checks, it just does what is configured. I will change the next release so wdRun will also ignore events not supported by the plugin (instead of aborting).

I am very curious how your config got the "1" value for filedel if you didn't edit it manually. Can you do a disk-check (chkdsk) of the drive with the config files?

Quote:

You mean there is no [watchDirectoryEvents] heading anywhere in the config? weird indeed!

To fix the issue, you can manually edit the configs for those FTP tasks.

Gert

mmm,


can you send me one of those config files?

do you happen to know/remember something about those tasks, for example: are they all created by copying another task?

Anyway, just edit them with notepad and add
[watchDirectoryEvents]
evtFileNew=1
evtFileDel=-1
evtFileRen=-1
evtFileChng=0
evtFileChngBasedOnSize=0
evtDirNew=-1
evtDirDel=-1
evtDirRen=-1
evtQuiet=-1
evtQuietSecondsInterval=60

making sure no other [watchDirectoryEvents] section exists.

Gert

The Control Center only uses "normal" Windows functions to write your settings to the config files. If these functions misbehave on that computer, I would think that a lot of other programs would have trouble as well.
I am glad it is working ok again, but I would love to know the cause of the problems. Maybe a weird interaction with a virus-scanner?

Gert