When I run Toucan 3.1 on the command line verbose parameters such as "--job=" work OK, but I use Win Scheduler http://www.splinterware.com/products/wincron.htm to do my overnight jobs and for some reason Toucan will now only accept the terse forms such as "-j"
Toucan starts, throws up a message (but too fast to read it properly) and quits. Using the short forms seems to work.
I've converted my scheduled tasks so more irritating than anything else, but I als notice that if I try to run two Toucan jobs at the same time, the first to start works fine and the second pops up a dialog box with the message "caught unhandled unknown exception, terminating" and quits. I've also had one case when testing this that bothj obs freeze (I think Is tarted them almost simultaneously) This is more annoying as I now have to space out a few of my jobs a bit more.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
mentionned in the release announcement I am no longer working on developing Toucan. However thank you for the report, it is quite surprising that the long forms don't work.
I also thought I had fixed issue with running multiple copies at once, are you running the toucan.exe in the App folder?
I did spot the comment, I mentioned the short/long forms as I thought it might help other people. It is also some odd interaction, as if I run the command directly from a DOS window, long forms work, but if I use my scheduler they don't.
I'll check the folder it's running from: again because they are scheduled jobs I have to set a working directory for the job to start in & it is always possible I've forgotten to do so in a few places.